Build starting points (opening anchors)
Floor โ never build below$3,000
Core Workflow System โ site + 1โ3 workflowsfrom $6,000
Operational Engine โ 3โ8 workflows + integrationsfrom $15,000
Business OS โ 8โ15+ workflows, deep customfrom $30,000
Monthly retainers
Floor โ never run a system below$750/mo
Standard โ active optimization$1,500/mo
Managed โ revenue-critical system$4,000+/mo
Quote it live โ the sequence
1Open from the lead card โ you already know their industry, goal, pain & budget.
2Set the frontend โ a defined piece. The price lives in what it DOES.
3Scope the system tier โ Core / Operational Engine / Business OS = your anchor.
4Walk the multipliers out loud โ build the number transparently.
5Weigh operational dependency โ how much runs through it? Raise accordingly.
6Quote the pair โ build fee + monthly retainer. Always both.
7Justify with their math โ revenue earned or hours saved, their numbers.
Complexity multipliers (what raises the price)
Workflow count โ more workflows compound, not add. Each one is logic to build, test, maintain.
Integrations โ CRM, calendar, Stripe, Twilio, AI APIs, databases. Every one adds testing & edge cases.
Automation depth โ conditional routing, AI logic, memory, multi-step. Depth costs more than features.
White-label โ SaaS territory: multi-client, permissions, scaling. Price it way up.
Reliability โ payments/bookings must not fail. Redundancy & testing cost money.
The biggest lever โ operational dependency
Convenience (runs fine without it) โ base pricing.
Operational (daily ops run through it) โ raise materially.
Revenue-critical (money flows through it) โ premium; reliability priced in.
"The more your business runs THROUGH this system, the more engineering and support it needs. The question isn't what it costs โ it's what it costs you if it fails."
Pitching the retainer
"Your system isn't set-and-forget โ models change, integrations shift, your process evolves. The retainer keeps the engine running and improving. The more you depend on it, the more essential this is."
Objections
"That's more than I expected."
Reframe to value: "This isn't a website cost โ it's the system your business runs on. What's it worth to you to [their stated goal]?" Then walk the math.
"Can you do it cheaper?"
Hold the floor. Reduce scope, not price โ drop a workflow or integration. "We can start with the core system and add the rest later" โ never discount the build.
"Why the monthly fee?"
"It's a living system, not a file I hand over. The retainer is what keeps it reliable and improving. Skipping it means it slowly breaks."
"Let me think about it."
"Totally โ what specifically do you want to weigh? Let's make sure you have everything you need to decide." Then book the next step before the call ends.