Ten steps from a free call to a system you own. You can stop after any of them.
Nothing here is a surprise on purpose. Every step names what you receive, what you owe, and what happens next, so the next invoice is never news.
- 01
Free AI Revenue Roadmap
A 30-minute call. You describe how work moves today; Surge identifies the three highest-value opportunities to increase revenue, improve conversion, or recover time. You receive a one-page roadmap and keep it either way.
You provide 30 minutes and honest answers. No preparation required.
- 02
Written scope document
If you want one of the opportunities built, you receive a written scope: what gets built, which systems connect, where a person approves, what happens when something fails, what done means, and what it costs.
You provide Access details for the systems in scope, so the scope is checked against reality before you sign.
- 03
Fixed project price
The scope carries one number. It changes only if the scope changes, and a scope change is quoted in writing before any work on it starts.
- 04
50% deposit to begin
The deposit starts the build. Payment in full upfront is available and costs less overall.
You provide The deposit and a named person on your side who will own the system.
- 05
Build in your environment
Everything is built inside accounts in your name: your CRM, your phone system, your automation platform. No Surge-owned middle layer you would have to keep paying for.
You provide Admin access where the scope says so, granted through your own accounts.
- 06
Testing and your approval
Tested against your real jobs and real edge cases before a customer sees anything. You approve every message that goes out in your name, and the acceptance checks in the scope are run with you.
You provide An hour or two of review time, spread across the build.
- 07
Remaining 50% at delivery
Due when the definition of done is met and you have approved the system in production.
- 08
Loom walkthrough and written handoff
A recorded walkthrough of the working system plus a written handoff: how it works, how to change it, how to turn it off, and who to call at each vendor.
- 09
You own the completed system
The workflow, the accounts, the documentation, and every transferable asset are yours. If Surge disappeared tomorrow, it keeps running and someone else could maintain it from the handoff.
- 10
Optional support, no forced retainer
Every build includes a 30-day window for correcting defects against the written scope. After that, monitoring, optimization, and continued-build plans are available month to month, and none of them is required.
Twelve sections. If a question about the build is not answered in it, the scope is not finished.
The scope is the contract in plain language. It is written after the Roadmap call, checked against your actual systems, and signed before a deposit is requested.
- 01
What Surge will build
The workflow or system, described in plain language and in the terms your team uses.
- 02
Systems being connected
Every tool in the path, the account it runs under, and whether the connection is native, through a connector, or custom.
- 03
Workflow trigger and actions
What starts it, what it reads, what it does, and what it produces, step by step.
- 04
Human approval points
Exactly where a person reviews, approves, or takes over. Every workflow has at least one.
- 05
Exceptions and failure handling
What happens on bad data, a vendor outage, an unexpected reply, or a missing field, and who is told.
- 06
Client responsibilities
Access, approvals, a named owner on your team, and the decisions only you can make.
- 07
Definition of done
Observable acceptance checks. The final payment is gated on them, not on a feeling.
- 08
Timeline
Kickoff, build, test, and delivery dates, with the dependencies that could move them.
- 09
Fixed price
One number for the scope as written.
- 10
Vendor and usage costs
Any third-party fees the build will create or increase, estimated monthly, paid to the vendor.
- 11
Ownership
Confirmation that the workflow, accounts, documentation, and assets are yours.
- 12
Support window
The included 30-day defect window and the optional plans available after it.
- No hourly billing for scoped builds. You buy a defined outcome at a fixed price.
- No required monthly Surge license. Nothing you own depends on paying Surge to keep running.
- No forced maintenance retainer. Support after delivery is optional.
- You own the completed workflow, the relevant accounts, the documentation, and every transferable asset.
- Third-party tools may still charge hosting, messaging, API, CRM, or usage fees. Those are disclosed before you sign, and they are paid to the vendor, not to Surge.
- Every build includes a 30-day window for correcting defects against the written scope.
- New features or scope changes are quoted separately, in writing, before work starts.
Optional monitoring, optimization, and continued-build plans are available after delivery, priced to scope and cancellable any month. Pricing →
Find, build, prove, run.
01
Find
Count what is leaking before touching anything. The Roadmap call is where this starts.
02
Build
Inside the software you already own, at a fixed price agreed before work starts.
03
Prove
Tested on your real work, approved by you, and measured against the baseline we froze.
04
Run
Handed off with documentation so it keeps working, with optional support if you want it.
Prove is the word that matters. Before the final payment, five real drafts go in front of you with one question each: would you send this as written? Three yes is a pass. Fewer and Surge tunes for another week or says honestly that the scope should shrink. Every automation starts with a person reviewing each message and earns autonomy on measured accuracy, never on a promise.
How long does the whole thing take?
The roadmap arrives within two business days of the call. A written scope follows within a week if you want one. Single automations ship in one to two weeks from deposit; multi-tool builds in two to three. Custom systems get a timeline after the feasibility review.
How much of my time does a build take?
A few hours total: the roadmap call, access setup, one or two review sessions, and approving the messages that go out in your name. Surge is built to spend as little of your live time as possible.
What if it does not work?
The definition of done in the scope is a list of observable checks, and the final payment is gated on them. If they are not met, you do not pay the balance. After delivery, the 30-day window covers defects against the scope.
Can I stop after the roadmap?
Yes. Most people should read the roadmap and decide on their own time. Some of what it recommends is a setting in software you already own, and the roadmap says so.
What do you refuse to build?
Anything that moves money, posts publicly, files insurance claims, or contacts strangers without a person. Anything that sends patient information to a model without the right agreements. The trust page has the full list of what Surge does not claim and does not automate.
Step one is free and takes 30 minutes.
Book the Free AI Revenue Roadmap call. You leave with a one-page document naming your three highest-value opportunities, whether or not you go to step two.
Find out where the revenue and the hours are going.
Thirty minutes on a call. A one-page roadmap with your three highest-value opportunities, reviewed by Austin before it is sent. Yours whether or not you hire Surge.