Process case study · The Wealth Experiment
When we made our Two Mondays workshop free, the next step needed to change with it. Here is how we clarified the offer and the handoff.
Implemented · outcomes still to be measured01 / Choose one journey
The owner chose to make the November 2 and 9 founding cohort free. The existing $99 checkout described a different offer. The new journey needed to explain both what someone was requesting and who would confirm their place.
A paid registration path could not represent a free, manually confirmed cohort. Pricing, the form, and the confirmation message needed to agree.
This is a product decision and a clarity finding. We have not established that the old price caused people to drop out.
After submitting a free request, does a person understand whether they have a seat and what happens next?
The hypothesis: clearer expectations may reduce confusion and help qualified requests reach confirmation. That remains a hypothesis until measured.
02 / Make the handoff explicit
Previous offer · summary
The workshop used a paid registration and checkout path. Registration was associated with payment.
That path belonged to the previous offer. It was not a free-place request.
Current offer · summary
Both Mondays are free. No card is required. A saved request does not reserve a seat.
Ashley reviews availability and confirms each place separately by email. Joining instructions follow through that manual process.
The specific Growth Fix-sized example is the request-to-confirmation handoff: define the status, write the next-step copy, name the owner, and check that the customer sees the right message.
Creating a new registration backend, changing payment handling, coordinating multiple websites, and producing a workshop are broader launch work. They are not all included in a single Growth Fix.
03 / The client experience
After payment, send one goal, the journey URL, available evidence, an approval owner, and suitable session times. You receive an intake checklist and a confirmed session date once scope and access are ready.
In this demonstration: workshop page → free request → manual confirmation.You receive the priority issue, the observations behind it, and the assumptions that still need testing.
Here: the free offer needs a request status that does not imply a reserved seat.Before implementation, we agree one feasible change, the required access, the approval owner, and the written-handoff date.
A suitable bounded brief: clarify one existing form’s success message and the manual next step. New backend development requires a separate scope.During a 60–90 minute working session, we make the agreed change using existing tools and check the actual customer path with you.
Acceptance criteria here: no payment required; request versus reservation is explicit; Ashley owns confirmation; the next step is visible.You receive editable copy or implementation links, the change record, checks performed, maintenance notes, one primary metric, and a 30-day measurement plan.
Unknown baselines stay marked unknown. A working form is evidence of function, not proof of demand.You receive prioritized follow-on work and 7 days for clarification questions after handoff. The 30-day plan is yours to use. Ongoing monitoring, another review session, or further implementation is separate.
You can use the next steps yourself, give them to your team, or request a separate proposal.04 / Separate delivery from results
| Item | Current evidence | What it does not establish |
|---|---|---|
| Workshop offer | The central workshop page describes both Mondays as free, with a request form and manual seat confirmation. | Demand, attendance, or a conversion improvement. |
| Request handling | The released flow saves free requests and describes the distinction between a saved request and a reserved place. Automated checks passed for the release. | That a human requester has received confirmation or joining details. |
| Payments | The old workshop payment link was deactivated as part of the free-cohort launch. | That wider payment work fits the scope of a single Growth Fix. |
| Distribution | Supporting promotion pages require a final consistency check before wider distribution. | That every portfolio banner has already been updated. |
| Business results | No verified before/after conversion result is presented here. | More leads, more revenue, or a causal lift from this change. |
Inspect the current workshop journey →
Primary measure: unique, eligible requests submitted before registration closes that receive a seat confirmation before the first session, divided by all unique, eligible requests in that cohort.
Guardrails: response time, requests still awaiting review, capacity-related declines or waitlisting, duplicate requests, and attendance among confirmed attendees. Count all confirmed seats against the 20-place limit.
Separate acquisition measure: valid requests divided by measured workshop landing sessions. Report the tracking coverage and definition; do not mix raw analytics traffic with an unfiltered request count.
Review: reconcile requests and confirmations before November 2, attendance after each Monday, and a written review around November 20. Report counts and denominators. Keep agency inquiries and paid Growth Fix orders separate from free workshop participation.
The price and journey changed together. A simple before/after comparison cannot isolate the effect of the handoff copy. Low volume, traffic mix, and the 20-seat capacity also limit conclusions.
05 / Apply the process to your business
The $997 Growth Fix includes preparation, a diagnosis, a 60–90 minute working session, one agreed improvement, a written handoff, a measurement plan, and 7 days of clarification support.
See the Growth Fix scope →Want to work through your own first pass? Use the free Growth Leak Audit.
You can also inspect the illustrative handoff template. It shows the document format with fictional sample details.