Build Blueprint — Sample
Cascade Ridge Builders LLC — Job Scheduling + Lead Follow-Up System
SAMPLE — FICTIONAL CLIENT. Cascade Ridge Builders does not exist. Every name, number, and quote in this document is invented so prospects can see exactly what a paid Build Blueprint contains before buying one. A real Blueprint is built from the client's own intake answers, a workflow interview, and their actual tool/data access — the structure, depth, and fixed-price format below are the real thing.
| Prepared for | "Cascade Ridge Builders LLC" — residential remodeling contractor, 11 field staff + 2 office, ~$1.9M/yr revenue (fictional) |
| Prepared by | AI Build Concierge |
| Blueprint price | $995 flat — credited in full toward the Managed Build below if the client proceeds within 60 days |
| Delivery | 7 calendar days from paid intake |
| Verdict | BUILD — but build simpler than asked. The scheduling half is a configuration job on tools the client already pays for. The follow-up half is the real build. Details §2–§4. |
1. Problem map
The client came in asking for "a custom app that runs our whole business." The interview found four actual problems, in cost order:
| # | Problem | What it costs them (client's own estimates, fictional) |
|---|---|---|
| P1 | Leads go cold. New inquiries land in a shared inbox and the owner's phone. Nobody owns follow-up; the owner estimates 3–5 jobs a year are lost to slow/no response. At a ~$28k average remodel, that's $84k–$140k/yr of revenue walking away. | Highest cost, cheapest fix |
| P2 | Scheduling lives in three places. A whiteboard in the office, the owner's calendar, and a group text. Double-bookings and crew-shows-up-with-no-materials days happen ~twice a month. | Real, but a process problem first |
| P3 | Change orders are verbal. Scope changes agreed on-site never reach the invoice. Client estimates ~2% of revenue leaks here (~$38k/yr). | Fixed by one form, not an app |
| P4 | No view of the pipeline. The owner cannot answer "what's booked in the next 6 weeks and what's it worth" without an hour of digging. | Solved as a by-product of P1+P2 |
What we are NOT solving in v1: payroll, estimating/bid generation, accounting (QuickBooks already works), a customer-facing portal, and the "custom app" itself. Each is named in §5 as explicitly out of scope — that list is part of what the Blueprint fee buys.
2. Workflow audit — before / after
| Workflow step | Before (today) | After (with v1) |
|---|---|---|
| Lead arrives (web form, referral, phone) | Shared inbox + owner's personal phone; first response in 4–48 hrs, if at all | Every lead auto-enters the CRM pipeline within 1 minute; owner/office gets an instant alert; first-response target < 15 min in work hours |
| Lead follow-up | Memory. No cadence, no record. Leads silently die after 1–2 touches | Automated follow-up sequence (day 0 / 2 / 5 / 10) by email+SMS, written in the owner's voice, stops the moment a human replies; every touch logged on the lead |
| Estimate booked | Phone tag; appointment in owner's calendar only | Booking link sends confirmation + reminder to both sides; job record created automatically |
| Job scheduling | Whiteboard + group text; office re-types everything twice | One shared crew calendar (the tool they already pay for, properly structured §4); a change in one place is the only change |
| Change order on site | Verbal agreement, handshake | 60-second mobile form: description, photos, price delta, client taps approve → signed PDF + line item queued for the invoice |
| Invoicing | Office reconstructs the job from texts and memory | Invoice draft assembles from the job record (contract + approved change orders); human reviews and sends |
| Pipeline view | An hour of digging | One dashboard: next 6 weeks booked, value by stage, stale leads flagged |
3. Context-engineering assets included
This is the part a generic builder skips, and the reason AI output sounds like this business instead of a template. The Managed Build includes building and handing over:
- Business context file — services offered/not offered, service area, pricing posture, crew structure, seasonal patterns, the words the owner actually uses with customers.
- Voice pack — 12 real (redacted) past emails/texts from the owner, distilled into a follow-up voice guide, so automated messages read as the owner on a good day, not as a chatbot.
- Follow-up sequence library — the day 0/2/5/10 messages, each with an owner-approved variant for remodel vs. repair inquiries.
- Objection + FAQ sheet — the 15 questions this business actually gets ("do you do roofs?" → no, and here's the referral), so automated replies answer or route correctly instead of hallucinating.
- Escalation rules — what the system must never handle alone: pricing disputes, anything over a $500 change, an unhappy customer, any legal/permit question → straight to the owner's phone with full context.
All context assets are the client's property, delivered as plain documents they can hand to any future builder.
4. Build spec (v1 — pinned)
In scope:
- CRM pipeline (leads → contacted → estimate booked → quoted → won/lost) with the automated follow-up sequences of §2, on the client's existing accounts.
- Crew scheduling board: one calendar structure, color by crew, materials-needed field per job day, daily 6 AM text to each crew lead with their day.
- Change-order mobile form with client e-approval and PDF record, feeding the invoice draft.
- Invoice draft assembly from the job record (human sends; no auto-send).
- Owner dashboard: 6-week booked value, pipeline by stage, stale-lead list.
- Training: two recorded walkthroughs (owner, office) + a one-page runbook.
Out of scope (explicit): custom mobile app, customer portal, estimating engine, payroll, accounting migration, website rebuild, marketing/ads. Quoting any of these later is a separate Blueprint or a change order — never a mid-build addition.
Acceptance test: v1 is accepted when (a) a test lead travels inbox → follow-up sequence → booked estimate with no human touching it until the reply, (b) a test change order is approved on a phone and appears on the invoice draft, (c) the dashboard's booked value matches a hand count for the same week. The QA bot runs this checklist against this spec before handoff; it fails loudly, it does not pass silently.
5. Recommended stack
| Layer | Choice | Why |
|---|---|---|
| CRM + pipeline | HubSpot Free → Starter when volume forces it | Client's office manager already knows it; free tier covers v1 lead volume; no migration |
| Scheduling | Google Workspace calendars, restructured + a shared crew view | Already paid for. The problem was structure, not software — buying a scheduling platform here would be waste |
| Automation | Make (n8n if the client later wants self-hosting) | Connects form → CRM → SMS/email → calendar without custom code to maintain |
| Messaging | Twilio (SMS) + existing Gmail | Pay-per-use, ~$15–30/mo at this volume |
| Change orders | Mobile web form (Tally/Typeform-class) → PDF → job record | No app store, works on any crew phone today |
| Dashboard | The CRM's native reporting + one automation-fed summary sheet | No BI tool to learn |
Custom code in v1: none. That is a deliberate verdict, not a limitation — everything above is configuration + automation + the context assets of §3. If the business doubles, the Blueprint's §8 names the trigger points where custom code starts paying for itself.
6. Timeline
| Phase | Duration | Owner |
|---|---|---|
| Blueprint (this document) | 7 days from paid intake | AI Build Concierge |
| Client decision window | Up to 60 days — the $995 credit holds | Client |
| Managed Build: setup + automation wiring | Weeks 1–2 | Concierge + builder bench |
| Voice pack + sequences, owner approval round | Week 2 | Client (one ~45-min review) |
| Change-order form + dashboard + acceptance test | Week 3 | Concierge QA |
| Training + handover | Week 4 | Both |
| Total, decision → live | ~4 weeks |
7. Fixed price
| Item | Price | Terms |
|---|---|---|
| Build Blueprint (this document) | $995 | Paid at intake. Credited in full toward the Managed Build |
| Managed Build v1 (spec §4, complete) | $8,900 fixed | 50% ($4,450) to start, 50% on acceptance test passed. 2 revision rounds included. Kill fee: if the client stops the build mid-flight, work-to-date is invoiced at the milestone reached and everything built is handed over — no hostage code |
| Care Retainer (optional, from go-live) | $750/mo | Automation monitoring, sequence tuning, small changes (≤2 hrs/mo), monthly pipeline report. Tool costs (Make, Twilio, CRM tiers) pass through at cost — estimated $40–80/mo at this volume |
| Client's real first-year picture | $8,900 + ~$9,000 retainer + ~$700 tools ≈ $18,600 | Against one recovered remodel job (~$28k revenue) the system has paid for itself; P1's estimate was 3–5 jobs/yr |
All prices inside the Concierge's published pricing (Blueprint $995 flat · Managed Build $3,500–$15,000 · Retainer $500–$1,500/mo). Fixed means fixed: if the build takes longer than §6, that is our cost, not the client's — scope changes go through a written change order priced before work starts.
8. Risks — stated, not buried
| Risk | Honest read | Mitigation in this plan |
|---|---|---|
| The follow-up sequences sound robotic and hurt the brand | The #1 real risk. Bad automation is worse than slow humans | Voice pack from the owner's real messages (§3); owner approves every sequence before it sends; any reply stops automation instantly |
| Office manager resists a new pipeline | Adoption kills more small-business systems than technology does | v1 keeps her tools (HubSpot, Google) and removes her worst task (re-typing); she is trained first, owner second |
| Lead volume is lower than estimated, so P1's payoff shrinks | Possible — the $84k+ figure is the owner's estimate, not measured data | The Retainer's monthly report measures actual recovered leads; if the number is ~zero after 90 days, the honest recommendation is to cut the retainer, and this Blueprint says so in advance |
| Platform dependency (Make/HubSpot pricing changes) | Real but slow-moving | All data lives in the client's own accounts; context assets are portable documents; exit cost is days, not months |
| Scope creep toward "run our whole business" | The original ask, and the classic margin/reputation killer | §4's out-of-scope list is contractual; new ideas get their own Blueprint |
9. Next-step offer
- Proceed to Managed Build at the fixed $8,900 — the $995 Blueprint fee is credited, so starting costs $3,455 net new money (first milestone $4,450 − $995 credit). Signature on the MSA + SOW starts the clock.
- Or take this Blueprint anywhere. It is the client's property — spec, stack, and context assets are complete enough for any competent builder to execute. We'd rather earn the build than trap it.
- Or don't build. If the interview numbers were optimistic, the correct move may be a $0 version: the follow-up cadence of §2 run manually from a spreadsheet for 60 days to measure P1 before spending anything. This Blueprint's audit tables are structured so the client can do exactly that.
Contracts (mutual NDA, MSA, SOW with IP assignment to the client) are provided before any payment beyond the Blueprint. The client owns the code, the data, and every context asset from day one.