Competitive research

1. 1.Brad writes one page in a plain document: five sections in ladder order — Free AI Readiness Summary, $497 90-Minute Walkthrough, $1,500 Implement-Together, $2,500 Done-For-You, ~$500/mo Maintenance.
2. 2.For each rung write four lines only: what you get, what it costs, how long it takes, what you'll be able to do yourself afterward. Add a 'what this is not' line to each so nobody feels tricked.
3. 3.Add a short closing line: no obligation at any rung, you can stop after the free summary and take it elsewhere.
4. 4.Publish it on the ClearPath Labs site at /pricing (or /what-it-costs) and link it from the top navigation of every page.
5. 5.Make the free intake form the only button on the page, repeated after each rung.

Owner: Brad

Done when: A stranger can land on clearpathlabs.com, reach the pricing page in one click, and see all five dollar figures without filling in anything or talking to a person.

1. 1.Brad takes the summary already written for the active client, strips every identifying detail (business name, city, dollar amounts, people), and keeps the structure.
2. 2.Fix the structure at four parts: the three chores worth automating, rough hours per week each one eats, which ladder rung fits each, and what to do first.
3. 3.Cap it at 2-3 pages, export to PDF, name the file ClearPath-AI-Readiness-Summary-Sample.pdf.
4. 4.Build a page at /readiness-summary: what it is, what you get, that it's free, that it arrives within five business days, the embedded sample PDF, and the intake form underneath.
5. 5.Add one line to the intake form's confirmation email: 'Your summary arrives within five business days. Here's a sample of what it looks like: [link].'

Owner: Brad

Done when: The sample PDF is downloadable from the site without giving an email, and every new intake gets a summary in the same format within five business days.

1. 1.Brad writes a page at /proof headed 'We shipped the thing we sell.'
2. 2.Describe EDSI VMS plainly: what it does, that it is multi-tenant, that it has paying subscribers, when it went live. Include the public URL or a screenshot of the live login screen — no invented numbers.
3. 3.Underneath, add the single anonymized case study: the situation, what we built, what changed. Only facts we can defend; no client name unless written consent exists on file.
4. 4.Add the honest line about who is behind it: 71, ex-paramedic, no CS degree, shipped it anyway — stated flat, never as 'amazing for his age.'
5. 5.Link /proof from the site navigation and from the bottom of the pricing page.

Owner: Brad

Done when: A doubtful owner can click one link from the homepage and see a running product with paying customers before spending a dollar.

1. 1.Brad picks the three chores we can genuinely build in a session: quote-to-invoice, new-client onboarding, weekly numbers email.
2. 2.For each, write a card: the chore in the owner's own words, exactly what gets built, what tools it uses, the price ($1,500 implement-together), the timeline, and 'you keep the keys and we teach you to change it.'
3. 3.Add a short 'what we build with' block naming the actual tools — Make, Zapier, n8n, Airtable, whichever we really use — so a prospect can search them before calling.
4. 4.Publish the three cards side by side at /first-automation and link each one from the pricing page's $1,500 rung.
5. 5.After each of the next three engagements, Brad updates the matching card with what actually happened — real hours saved, real time to build — replacing estimates with facts.

Owner: Brad

Done when: Three named-chore cards are live with the $1,500 price, the tool names, and a timeline, and at least one card carries a real outcome from a delivered engagement.

1. 1.Brad rewrites the intake form to ask the questions that actually drive the summary: what the business does, how many people, the three tasks that eat the most time, what software they already pay for.
2. 2.Build the automation on the same stack we sell (Make or n8n plus an LLM API on our own key): on submit, generate a one-page preliminary snapshot — the 3-5 AI moves for that business — and email it back inside a minute.
3. 3.Every snapshot ends with the same two lines: the full written Readiness Summary from a human arrives within five business days, and here is the link to book the $497 walkthrough.
4. 4.Brad reviews the first twenty auto-generated snapshots by hand before they send, tightening the prompt until he'd sign his name to each one; only then let it send unattended.
5. 5.Add a booking link and a pay-now button for the $497 walkthrough on the snapshot email and on the pricing page.
6. 6.Log every submission in one spreadsheet or Airtable base so whoever runs ClearPath next can see the funnel: submitted, snapshot sent, summary sent, walkthrough booked, paid.

Owner: Brad

Done when: A form submitted at 2am on a Sunday produces a specific, accurate one-page snapshot in the inbox within a minute, with a bookable and payable $497 slot attached — and the funnel spreadsheet shows the counts.

1. 1.Brad drafts a one-page template with four fixed sections: what ran this month and how many times, what broke and how we fixed it, what it cost you in model and platform spend, what we suggest next.
2. 2.Turn the template into a document that gets filled in for every maintenance client on the first business day of the month.
3. 3.Add the run report to the maintenance description on the pricing page — 'you get a one-page report every month, in plain English, so you always know what you're paying for.'
4. 4.Send the first report to the active client and ask one question: is there anything here you don't understand? Rewrite anything they stumble on.
5. 5.Once two clients are on maintenance, automate the counts (runs, errors, spend) into the template with the same Make or n8n stack we sell, so the report takes Brad fifteen minutes not two hours.

Owner: Brad

Done when: Every maintenance client has received a one-page run report on the first business day of the month for two months running, and the promise is printed on the pricing page.