I map the funnel. Then I build it.

I map where a funnel loses people, then build the fix myself. That covers the strategy, the pages, the automations and the code, so nothing is lost between the plan and the thing that ships.

Both, and that is the whole point. Most strategists hand over a document and leave. Most developers build exactly what they are given, including the parts that are wrong. Doing both halves removes the translation step where projects usually fail.

Yes, and it is usually faster than starting again. I audit what exists, find where it leaks, and rebuild only the parts that are costing you money.

That is where most of the work has been, because challenges and webinars live or die on the funnel. The problem itself is not specific to them. If someone has to click four times before they can pay you, there is something here worth looking at.

Some, yes. A funnel does not create demand, it stops you losing the demand you already have. If almost nobody is landing on your pages yet, your money is better spent getting the first few hundred visitors than optimising for them. I will say so on the call rather than take the work.

GoHighLevel, ClickFunnels and Kartra for funnels. HubSpot, Keap, Salesforce, Pipedrive, Zoho, ActiveCampaign, Klaviyo and Mailchimp for CRM and email. Stripe, PayPal, Paystack, Flutterwave, Klarna and Square for checkout. Zapier, n8n and Twilio for automation. Custom builds in Next.js and Supabase when a template will not do.

It depends on what the funnel needs, so I quote after the call rather than before it. Rebuilding one checkout page and building a full challenge funnel with the automations behind it are not the same job, and quoting them as if they were gets somebody the wrong thing. You get a scope and a number in writing before any work starts.

The build is rarely what holds a project up. Waiting on copy, logins and a decision about the offer is. Once those are in hand things move quickly. I give you a timeline on the call, once I know the scope, and I tell you which parts depend on you.

Less than most people expect, and nearly all of it at the start. Access to your platform, whatever copy and brand assets already exist, and a straight answer on what you are selling and who it is for. After that I would rather send you something to react to than ask you to write a brief.

I stay on it long enough to watch real traffic move through and fix what the first visitors expose, because that is when the honest problems show up. Nothing is locked to me. The logins, the pages and the automations are yours, and you can run the whole thing without me.

Yes. Often the useful thing is for me to write the plan and build the parts your team has not done before, then hand the rest over. If you already have people, using them is cheaper than using me.

You bring the funnel you are stuck on and I tell you where I believe it is losing people. There is no pitch. If the diagnosis is all you take from it, the fifteen minutes still paid for itself.

Yes. Same map, but you hold the pen. It suits people running their first webinar or challenge who want the structure without handing the whole build over.