For agencies, consultants and fractional CTOs
Your client built AI for their business.Now someone else wants it.
When a client’s internal software becomes something other businesses in their industry want, the next stage is not more features. It is platform engineering, and it is a different job. We take that stage. You register the client, keep the relationship, and take a share of what follows.
Two ways in
Most of the time, an introduction is the whole job.
You do not have to deliver anything, front any cost, or learn how any of it works. The client buys, you get paid, and the relationship stays yours.
You spotted it. We take it from there.
- You register the client before anything is scoped
- We run the Readiness Review and the build
- You keep the relationship and stay in the loop
- A share of the review, and a share of the build
- Nothing to deliver, nothing to fund, nothing to maintain
Or keep it under your brand.
- The system ships as yours, not ours
- We build, integrate, monitor and cover out of hours
- You set the client price and keep the spread
- Suits an established firm with repeat demand
- The model below, in full
Either way, the client is registered to you before scoping starts — and stays yours for the life of the agreement and twelve months after it ends. How that works.
Who tends to see it first
You are usually the only person who notices.
The moment rarely announces itself. It shows up as an offhand comment from a client, and the person closest to their operation is the one who hears it.
Fractional CTOs
You are already in the architecture conversation. You will see this before anyone, and it is the one thing an advisory engagement cannot deliver.
AI agencies and consultants
You built the thing that now works. When another company asks for it, that is a different engagement from the one you signed.
Dev shops and MSPs
You maintain it, so you know what would break with a second tenant. Usually before the client does.
“Could we sell this to others in our industry?” · a competitor of theirs asks to use it · they ask about separate logins for another company · they want to charge someone for access.
The agency bottleneck
Building is the easy part. Supporting it is the business.
Every deployment adds a codebase, new integrations, and another reason the founder stays trapped in delivery. The knowledge and the software both end up living with one engineer, and nobody can say who owns it.
And when the AI you recommended breaks three weeks in, it isn’t the vendor’s name on it — it’s yours.
Before you file us somewhere
What this is not.
Three things we are not, stated up front because the category is crowded: not an agency, not staff augmentation, and not another tool your client has to log into and then ignore.
Not an agency
No campaigns, no sites, no hourly retainers.
Not staff augmentation
You are not renting a developer by the month.
Not another tool
Nothing new for your client’s team to log into and ignore.
What your client is weighing
The alternative is payroll.
This is the arithmetic your client runs the moment their software starts getting asked for. Hiring the capability costs roughly $360,000 to $450,000 a year fully loaded, because it takes two people minimum — an engineer who can ship and someone who can hold the architecture — plus a recruiter fee of 20 to 25% per hire and two to three months to fill before either starts. Knowing that number is usually what makes the introduction land. The full breakdown.
Two people, minimum
US market rates, fully loaded
- AI / backend engineer who can actually ship it$145k–$185k base$185k–237k
- Solutions architect — scoping, integrations$136k–$166k base$174k–212k
- Payroll tax, benefits, equipmentin the above
- Recruiter fee, per hire20–25%
- Time to fill, before ramp-up2–3 months
- Out-of-hours cover — one person is not a rotaa third hire
- What happens when one of them leavesstart again
No headcount at all
The same capability, rented
- Architecture, build, integrations, rolloutincluded
- Monitoring, escalation, out-of-hoursincluded
- Documentation, versioning, rollbackincluded
- Recruiting, onboarding, ramp-upnone
- Time before your first client is liveweeks
- Cost when a client leavesit stops
- You keep the margin above what you’re chargedyours
Partner rates sit below retail, so the spread is yours. You set the client price. Build fee and monthly both carry a partner rate. We quote on the first qualified client.
US market medians, 2026 — Built In, Glassdoor, ZipRecruiter. Loaded cost adds roughly 28%. Deliberately conservative: it assumes two hires, and most agencies need a third for cover.
Ownership
You own the market. DWOS owns production.
The split is fixed and written into the agreement. You bring niche knowledge, lead generation, client discovery and first-line support. We bring architecture, build, integrations, monitoring and out-of-hours cover. The client relationship is yours for the life of the agreement and twelve months after it ends.
Market & relationship
- Niche knowledge and positioning
- Lead generation and sales
- Client discovery and communication
- Adoption and first-line support
Building it, and keeping it running
- Architecture, build and integrations
- Ships the same way every time, and rolls back when it doesn’t
- Written down, so it isn’t in one person’s head
- We watch it, and we answer the pager
The core engine
DWOS owns and runs it. Built once, improved for every client.
The vertical layer
Configured once per niche, then reused across every client in it.
Their edge
Their data, prices, customers and voice. Walled off, exportable any time.
One shared engine. Every client’s edge stays theirs. Reusing the core never touches it, and white-label delivery never transfers the core.
How “you own the client” is a mechanism, not a promise
You register the client before scoping starts. For the life of the agreement, plus twelve months after it ends:
- DWOS does not approach, market to, or solicit that client
- DWOS does not accept direct work from them — enquiries come back to you
- Support lands in your inbox, and outbound email goes out from your address
- If the partnership ends, the client relationship stays yours
This is in the partner agreement, not just on this page.
The partner delivery model
Qualify → Scope → Build → Operate.
Four stages, in that order. You lead the business conversation at every one and we lead the technical one, with the support boundaries agreed in writing before any build starts.
Qualify
An established business, a clear workflow, an accountable owner, usable data.
Scope
You lead the business conversation. We turn it into a contained production design.
Build
Architecture, integrations, testing and rollout, while you manage the relationship.
Operate
You keep first-line comms. We keep it running, inside boundaries written down before launch.
Workspaces
Role-based access and a live health view per deployment.
Versioning & audit
Who changed what, when and why. Rollback ready, runbooks written.
Every issue gets sorted
Triaged the same way every time, so nobody argues about who pays.
White-label, and reused
A working system starts the next one in hours. Under your brand, on one core.
Before you get in touch
Questions partners ask
Who owns the client relationship?
You do, and it is a mechanism rather than a promise. You register the client before scoping starts. For the life of the agreement and twelve months after it ends, we do not approach, market to or solicit that client, enquiries come back to you, and support lands in your inbox. This is in the partner agreement, not just on this page.
What happens if the partnership ends?
The client relationship stays yours. That is the point of registering it at the start rather than negotiating it at the end.
Is our client's data mixed with anyone else's?
No. Their data, prices, customers and voice are walled off and exportable at any time. The shared part is the engine; reusing the core never touches their data, and white-label delivery never transfers the core.
How is this priced?
Per client, per month, at a partner rate below retail so the spread is yours. You set the client price. The build fee and the monthly both carry a partner rate, and we quote on the first qualified client.
Do we need technical staff on our side?
No. You keep the business conversation, the account and first-line support. We take architecture, build, integrations, monitoring and out-of-hours cover. That division is what makes it work without you hiring engineers.
How does the first one start?
You name one client. We work out with you whether they are actually at this stage, and register them to you before scoping. Most introductions do not turn into anything, and that costs you nothing.
The first one
Start with one client you already have in mind.
No programme to join and nothing to commit to. Tell us what they built and who has asked to use it, and we will tell you whether it is real. If it is, the client is registered to you before anything is scoped.
- You own acquisition and account management
- DWOS scopes, builds, deploys and stabilises
- Economics and support boundaries in writing
- Documented, reusable learning after launch
