Ongoing support
After the build, we keep it running, building, and growing.
$3,500 a month. Only after a First Build. We keep what we built running, and we act as your fractional CTO: every technology decision, AI included, made with someone on your side.
- Price
- $3,500 a month
- Changes
- 8 hours a month
- Our role
- Your fractional CTO
- Term
- 3 months, then monthly
What it buys
Five things, every month.
Everything we built stays running
The server, the data copy, the scheduled syncs, monitoring, backups and security patches. If it stops, we restart it. This never counts against your hours.
Anything we built that breaks gets fixed
No charge, no hours counted. A defect in our work is our problem. There is no cap, because a cap would mean we benefit from building badly.
Eight hours a month of changes and upgrades
A new field, a changed rule, a report that needs different columns, a workflow that needs an extra step. Hours do not roll over.
We act as your fractional CTO
We are your trusted advisor when you decide how technology, AI included, can help your business. We take the vendor calls. We review contracts and quotes, flag renewals, and check new tools before you buy them. You stop making software decisions alone.
A monthly review and planning with you
Sixty minutes. What was built, what broke, what hours were used, what is coming next.
Running while you sleep
What you can count on
Service standards, in writing.
The same standards on every engagement. If we miss one, tell us: it is on us, not on you.
No build yet? You can still have us as your fractional CTO.
How Fractional CTO worksEvery recommendation in writing.
The options, the cost, the risk, our pick and why.
A reply within one business day.
Ask a question, get an answer the next business day at the latest.
No renewal surprises.
A renewal calendar for your software. Every renewal flagged 90 days before its notice deadline.
A written summary within two business days
of every monthly review.
Everything stays in your name.
Documents, accounts, access and the decision log.
The build test
What counts as a new build
Any one of these means a separate scope and a separate price. We apply the test before work starts, not after.
It needs more than the eight monthly hours.
It is a new capability, not a change to something that exists.
It touches a system we have not already connected.
It needs a new vendor, a new contract or a new recurring cost.
It changes which system holds the official record.
It needs more than one person trained to use it.
If someone inside your company owns technology
We work with them, not around them.
Maybe you named someone to lead technology or AI. Maybe they were handed the job. Either way, we are on their side. We advise them, answer their questions and help them make the right calls. They keep the credit and set the direction.
If they want to build the skill themselves, add coaching: five hands-on hours a month, working with them.
How coaching worksIf the month fills up
You always know where your hours stand.
If changes go past eight hours, we check with you first. They can wait for next month, or we can scope them as their own build. Your call.
Every month you get one short note: hours used, hours left, and what's next in line.
Your monthly line · example
- Hours used
- [x] of 8
- Hours left
- [x]
- Waiting
- [items]
What ongoing support doesn't cover
Said up front, so there are no surprises.
New capabilities, moving to a new system, or replacing one. We scope those as their own build.
Systems we didn't build or connect.
Marketing, content, design, SEO and advertising. We stick to software.
Day-to-day task work. Ongoing support keeps your systems healthy and growing; it is not an extra pair of hands.
After-hours work, unless we plan for it together ahead of time.
Term
Three months to start, then month to month. Either of us can stop with thirty days' notice.
Next step
It starts with a build.
Ongoing support picks up where your First Build leaves off.