Post-engagement
Technical Stewardship
Ongoing senior attention for software already delivered or already understood — available after an engagement, not as a starting point.
Post-engagement service
Continuity, not a retainer for its own sake
After a recovery or a build, some clients want the person who already knows the codebase to keep an eye on it. That is what this is.
It is deliberately not a starting point. Stewardship of software nobody has examined is just a monthly invoice with good intentions attached — the understanding has to come first, through an engagement.
Who this is for
- Clients who have completed a recovery or build and want continuity
- Businesses without an in-house senior engineer who need periodic review
What you receive
- Periodic review at an agreed cadence
- A defined scope of work each period
- Continuity from someone who already knows the codebase
What this does not include
Stated plainly so there is no ambiguity later. Anything here can be scoped separately if you need it.
- Unlimited support
- 24/7 or on-call incident response
- Fractional CTO responsibility
- A guaranteed response-time SLA unless separately contracted
The outcome
Your software keeps getting senior attention after the engagement ends.
Boundaries
What this is not — stated plainly
Most disappointment with ongoing arrangements comes from an expectation that was never actually agreed. So here it is up front.
Not unlimited support
Each period has a defined scope. Work beyond it is discussed and agreed, not silently absorbed and then resented.
Not 24/7 or on-call
There is no incident rota and no overnight response. If your software genuinely needs that, you need a team, and saying so is more useful than pretending otherwise.
Not a fractional CTO
This is not hiring, strategy ownership, vendor management, or board reporting. It is senior engineering attention on a specific codebase.
Not a guaranteed SLA
A response-time guarantee is a separate commercial commitment. It can be contracted separately; it is not included by default.
Why say all this on a sales page
Because the alternative is you discovering it during an incident. An ongoing arrangement only works if both sides agreed to the same thing at the start, and the honest version is easier to keep than the flattering one.
What it actually looks like
A defined scope, at an agreed cadence
Each period covers an agreed set of work. What that contains depends on the software and what it needs, but typically:
- Periodic review of the areas most likely to drift
- Dependency and security update review
- Small changes and fixes within the agreed scope
- Being available to whoever is doing the day-to-day work
- Keeping documentation current as things change
- Flagging what is accumulating before it becomes urgent
The value is mostly continuity. Someone who already knows why a decision was made can act in an hour where a newcomer needs a day to understand the question.
About this price
From $1,000 / month, with tiers reflecting the amount of work included and the cadence — not a promise of availability.
Priced per engagement, because the right amount depends entirely on what the software is and who else is working on it. Some clients need a quarterly review; some need monthly involvement.
How to get here
Stewardship follows an engagement — usually a Focused App Recovery Sprint or a custom build. By the end of one, the codebase is understood and documented, which is what makes ongoing attention worth paying for.
It is always optional. A recovery that leaves you dependent on the person who performed it has not really succeeded, and the handoff documentation is written so that you can walk away.
Ask about stewardship
Tell us what you are dealing with. If this is not the right fit, we will say so and point you at what is.