Strategy Session / Session / Paid roadmap
Get the roadmap before you commit to the build.
Sixty minutes on your actual problem, then a written plan of attack you can hand to whoever does the work, including me.
// the problem
Most operators book a build first and find out halfway through what it should have been. The expensive mistakes happen before any code gets written: wrong scope, wrong order, a stack choice someone will be paying off for a year. An hour of working the problem out loud with someone who has shipped this stuff settles most of it. You leave with a plan you can run with your own team, hand to an agency, or bring back to me.
// the promise
One hour in, you know what to build, in what order, and what it should cost. In writing.
// this is for you if
- You are pricing a build and want a second opinion before you sign anything
- Someone handed you a stack and you need to know what to fix first
- There is a diagnostic on your desk and you want the execution plan to go with it
- An hour of straight answers from the person who would do the work sounds like a bargain
// what’s inside
01 / Before the call
When you book, you send a short brief: the problem, the stack, and what a win looks like. I read everything before we talk, so the hour starts at the real question.
- $A short intake at booking, ten minutes tops
- $I review your stack, site, and numbers ahead of time
- $The whole hour goes to the problem itself
02 / The hour
Sixty minutes working the problem live: scope, sequencing, stack choices, cost. Ask anything. Bring whoever you want on the call.
- $Screen share encouraged, we look at the real thing
- $Scope and sequencing worked out loud
- $Straight numbers on what each path should cost
03 / The written plan
Within 2 business days you get the plan of attack in writing: what I would do, in what order, with rough effort attached.
- $Ranked steps with rough effort per step
- $What to tackle first and what can wait
- $The traps I would avoid, named
04 / The credit
Book a project within 30 days and the $350 comes off the price. The session pays for itself the moment you move.
- $Full $350 credited toward any project we scope together
- $30-day window from your session date
- $The written plan usually names the project, so the decision is easy
// outcomes (from real implementations)
60
Minutes, live on your problem
2
Business days to the written plan
$350
Credited toward a project within 30 days
1
Recording, yours to keep
// common questions
Is this a sales call?
You are paying for it, so the hour goes to your problem. If a project makes sense afterward, the plan gives you the scope and the $350 comes off the price. Prefer to run it with your own team or an agency instead? The plan and the recording travel with you.
What happens right after I pay?
You land on a booking page and pick your slot on my calendar. Your confirmation email carries the same link, so you can book later if you get pulled away. The intake is a few short questions when you book.
How does the credit work?
Book any project with me within 30 days of your session and the full $350 comes off the first invoice. The plan of attack usually names the project, so most people know within a week whether they want to move.
What kinds of problems fit?
Tracking and attribution stacks, Shopify builds, marketing automation, AI tooling, and the sequencing questions around all of it: what to fix first, what to build versus buy, what a fair price looks like. If you are unsure whether your problem fits, email michael@michaeldishmon.com and ask. I will tell you straight.
Who should be on the call?
Whoever owns the decision, plus anyone who will touch the work. The recording covers everyone else.
Do you offer refunds?
Yes. If the hour does not leave you with a clearer plan than you walked in with, email michael@michaeldishmon.com within 14 days and I will refund you.
// proof: this is what it looks like in production
Not sure where to start? The free scan answers that in about a minute.