We can run it after we build it.
Retained operation of what we shipped, fractional CTO/CMO across the stack, turnarounds, and build-operate-transfer. The exit is written in from day one.
- Diagnostic
- Structure
- Operate
- Transfer or continue
Plenty of good builds decay because nobody was staffed to run them. If you don't have the team yet, handing you a beautifully engineered system is a way of creating a problem rather than solving one.
So we'll run it — the product, the media and the measurement under one accountable party — until you're ready to take it. The default is still that you own and operate everything; this is the option, not the pitch.
Concretely, what you get.
Retained operation
We run what we built — deploys, incidents, iteration — reported weekly against the numbers that matter.
Fractional CTO / CMO
A senior operating seat across product, engineering, media and data, with a team behind it rather than a monthly advisory call.
Turnarounds
Diagnostic on a stalled property, then hands-on: fix measurement, cut what's losing, rebuild what's broken, scale what survives.
Build-operate-transfer
We build it, run it to a defined milestone, then transfer it to you or to a hire we help you make.
Portfolio operations
For multi-brand owners: shared infrastructure, one measurement spine, build-once-deploy-everywhere.
A written exit
Every retained engagement specifies how it ends, from day one, for both sides.
- 01
Diagnostic.
Two weeks, paid, on the asset and the numbers. Either side can walk afterwards.
- 02
Structure.
Fee, revenue share or a blend, sized to who carries which risk. Written plainly.
- 03
Operate.
Weekly reporting against the P&L, not against activity.
- 04
Transfer or continue.
Hand over at the milestone or keep going. The agreement says which up front.
Four ways in. Pick by what you need holding.
Most firms make you book a call to learn what it costs. Here are the ranges, the timelines, and what comes out the other end — so the first conversation can be about your project.
- 011 week
Scoping engagement
You have an idea, a prototype, or a stalled project and need a real plan with a real number.
from $15,000- → Written scope: what ships, what doesn't, what it costs
- → Architecture sketch with the cost-per-request model
- → Eval plan — how we'll know it works
- → Fixed price or rate-plus-ceiling for the build
Start with a scopeusually leads to product build - 026–16 weeks
Product build
You know what you need built and you want it running in production, in your repository, on a date.
$60,000 – $250,000- → A live system: web, native mobile, or agent — typed end to end
- → Thin slice in production by week three
- → Evaluation harness you can run yourself
- → Runbooks, a working local environment, a named handover
Scope a buildusually leads to retained operation - 038–20 weeks
Platform & infrastructure
The attribution spine, the data layer, or the multi-surface system the rest of the business stands on.
from $150,000- → First-party click tracking on your domains, server-side postbacks
- → Warehouse model reconciled to finance
- → Shared engines every property inherits
- → Integrity monitoring on the whole chain
Scope a platformusually leads to retained operation - 04Monthly, 3-month minimum
Retained operation
You want what we built to keep improving, with one accountable party and a weekly number.
from $12,000 / month- → Deploys, incidents, and iteration against the eval harness
- → Weekly one-page readout: what moved, what changed, what's next
- → Cost-drift and quality monitoring
- → An exit written into the agreement from day one
- Minimum
- Minimum engagement is $25,000. Below that, a senior build team rarely pays for itself and we will say so.
- Ranges
- Ranges, not quotes. The scoping week is what turns a range into a number, and it is credited against the build if you proceed.
- Ownership
- Every tier creates repositories, cloud accounts and domains in your name from the first commit. Nothing is held.
Asked and answered.
- Do you take equity instead of fees?
- Rarely, and usually as a blend. Pure equity only makes sense when we genuinely control the outcome, so we say no often.
- Is this different from an agency retainer?
- The reporting is. If a monthly deck is a list of tasks completed rather than a number that moved, you're paying for motion.
- Can we take it in-house later?
- That's the expected path. Runbooks, documentation and a working environment are produced throughout, not at the end.
- What if it isn't working?
- The exit is specified from the start. We'd rather end an engagement cleanly than defend one that stopped making sense.
Need operations?.
Two honest paragraphs beat a ten-page RFP. We answer inside one business day, and the first call is 45 minutes with someone who can scope it.
Or write directly — t@moher.ai