Pricing
What does it cost? Here’s the honest answer.
The right price starts with understanding what you need.
What it costs depends on the constraint you’re fixing and the systems it has to connect to. We scope it before we quote it: the build, software, ongoing support, and what counts as a change, in writing, before any work starts.
Start with a 30-minute conversation. If there’s a fit, we’ll define the scope before quoting the work.
Start with a conversation
Thirty minutes to talk it through.
Tell us what’s getting in the way, ask your questions, and get a clear view of whether we can help. If there’s a fit, we’ll define the scope before quoting the work.
Here’s what we can cover:
Tell us what's getting in the way.
Bring the problem, the tools you're using, and what you'd like to work better. You don't need a technical brief.
Ask your questions.
Talk through your priorities, constraints, and what working together could involve.
Decide on a useful next step.
We'll discuss whether we can help and what we'd need to understand before putting a scope and quote together. No obligation.
How we scope the work.
Start with the problem, agree on the work, then keep the system useful after it goes live. Each stage depends on what your business needs.
Step 1
Diagnose — Start with a conversation
Tell us what’s slowing your business down. We’ll ask about your goals, current tools, and constraints, then discuss whether we can help and what needs a closer look before we quote.
Step 2
Build — The work itself
Build the system your business needs — whether that means your pipeline, back office, or getting found. We agree on the scope, price, and responsibilities before work starts. The quote reflects the work required and the systems you already have.
Step 3
Prove — Measured against where you started
Before we call it done, it’s live and measured against your baseline: booked jobs, response time, hours back. Then you decide: expand, adjust, or stop.
Step 4
Compound — After Going Live
An agency’s work depreciates. An operating system compounds — if someone keeps tuning it. Some clients run theirs entirely in-house on the training and documentation we hand over. Others keep us in the room. What that looks like lives on the what happens after the build page. We discuss the support you need and agree on its scope separately.
Whichever step you’re on, the ask stays small: a working session up front, your sign-off before anything gets built, and almost nothing while we’re building it. You keep running your business — the system is what changes.
We don’t make guesses. We diagnose, build, and prove it moved the number.
In writing, right now
We won’t quote a build on a pricing page. Here’s what we will put in writing:
1
Scope and access first.
Ownership and ongoing care are separate. Deliverables, account access, third-party dependencies and ongoing support depend on the agreed scope.
2
We measure it.
Agree on a baseline and the measures relevant to the work: response time, booked jobs, revenue or hours saved. Reporting should answer an operational question.
3
Agree on acceptance.
Define the deliverables, acceptance checks and change process before work begins. Hosting, software, maintenance and fine-tuning have ongoing costs.
4
Plan for failure.
Discuss where human review, logging and fallback behavior are needed. Those safeguards must be designed and verified for the particular workflow.
And we never discount. The price is the price for everyone, so nobody who moved faster than you got a better deal.
Before you hire anyone
Ten questions to ask any AI partner. Here are our answers.
The questions a careful buyer should ask every agency or AI firm. We’d rather answer them up front.
01What do you think our biggest constraint is, and what’s your evidence?
We won’t guess on a first call. We ask about lead flow, response times, who handles what and where the owner gets pulled in, then tell you what we’d look at first and why.
02Show me a comparable client: where they started, what changed, how long it took, what it earned.
A Mid-Atlantic glass and door fabricator. Nine hand-offs on a whiteboard became one job pipeline, at 86% less over five years than the Salesforce quote for the same scope.
03What will be live at day 30, 60 and 90?
Discuss delivery phases, dependencies and acceptance checks during scoping. Dates and deliverables depend on the work agreed, not a universal 30/60/90-day promise.
04What do you need from our staff, and what happens if they don’t adopt it?
A working session up front, sign-off before we build, and the people who’ll use it in the room while we build it. Software built next to a workflow gets ignored, so we build inside it.
05What do we own from day one?
Clarify the deliverables, access, licensing and third-party accounts in the agreed scope. Ownership does not remove ongoing hosting, software, maintenance or fine-tuning costs.
06What happens when the AI gets it wrong?
Identify the human review, logs, alerts and fallback paths that the workflow needs, then verify them. Do not assume every system has the same safeguards.
07Does the dashboard connect activity to booked jobs and revenue?
That depends on the available data and integrations. Agree which outcomes the reporting can support and verify those connections.
08What are the all-in costs?
Scoped before any work starts: the build, software, ongoing support, and what counts as a change. You approve the number before we begin.
09What’s out of scope?
Written down in the scope, not discovered on the invoice.
10If we stop working together in six months, what keeps working?
Review the handover, licences, account access and ongoing operating costs before work begins. What continues and who supports it depend on the agreed scope and third-party services.
Straight answers on cost.
“Just give me a ballpark.”
The cost depends on what you need built, what you're already using, and how much needs to connect. Start with a 30-minute conversation about your priorities and constraints. If there's a fit, we'll define the scope before quoting the work.
“Why won't you just publish the prices?”
The work varies by business. Connecting two existing tools is different from building a new system around your team. We'd rather understand the job and give you a quote tied to a clear scope than ask you to choose a package that may not fit.
“Is there any obligation after the call?”
No. The introductory call is free, and there's no obligation to buy anything. It's a chance to talk through what you need, ask questions, and decide whether another conversation makes sense. Any proposed work and price are agreed before we start.
“What if I already know what I need built?”
Bring your idea, the tools it needs to work with, and any budget or timing constraints. We'll talk through what you're trying to accomplish and what we'd need to understand to scope it. You don't need to buy a diagnostic before speaking with us.
“I'd rather just talk to someone.”
Book a 30-minute call to tell us what's getting in the way and ask your questions. We'll discuss whether we can help and decide on a useful next step together. No obligation.
Let’s talk about what you need.
Thirty minutes to discuss the problem, answer your questions, and decide on a useful next step. No obligation.