What you receive in each engagement
Four engagements, each with a stated price, a time frame, and a list of what you keep. Start with the smallest one that answers your question.
How an engagement runs
The $1,500 triage fee is credited toward a sprint that starts within 30 days.
- 1
Fit call
Fifteen minutes to establish the problem, the urgency, and who decides. It is free.
- 2
Written scope and fee
Scope and fee are agreed in writing before work starts. Every recommendation and decision is a document you keep; calls explain documents and do not replace them.
- 3
Work
A triage, an audit, a bounded sprint, or ongoing fractional work, in your repository and your environment.
- 4
Handoff
You receive the documents and, for a sprint, a runbook and walkthrough. Any engagement can end with a recommendation to stop.
Production Triage
The smallest engagement that can reduce your uncertainty.
What we need from you
- A read-only repository invite for the one system in scope.
- One architecture conversation.
What you receive
- Architecture review. How the system works, verified from code, including where your docs disagree with it. PDF and an editable diagram.
- Prioritized risk map. Every material risk, ranked by blast radius and tied to a specific component. PDF.
- Remediation plan. The top risks as bounded work items with acceptance criteria that a senior engineer could carry out. PDF.
- 45-minute walkthrough. A live call with your team, recorded if you want it, ending in a recommendation: build, audit deeper, or stop.
What happens next
You can name your highest-leverage technical move and defend it to your own team. The $1,500 fee is credited toward a sprint that starts within 30 days.
Production Audit
For systems where the risk surface needs more than three days, or where you want specs your team can execute alone.
What we need from you
- Repository access and an architecture conversation, as for a triage.
- A scope agreed in writing before work starts.
What you receive
- Everything in a triage, at full depth.
- Code-level findings. Annotated references into your repository covering contracts, data flow, failure modes and release discipline. Written report.
- Implementation-ready specs. Acceptance criteria, migration and rollback notes, and test expectations for each work item.
- AI evaluation notes, when in scope. How your prompts, retrieval and tool use behave under real inputs, with an eval harness you keep.
- Sequenced roadmap. Now, next and later, with dependencies and rough cost. One page.
What happens next
Your team can start any recommended item without a clarifying meeting. If you want us to build it, the next step is a sprint scoped in writing.
Build or Rescue Sprint
Hands-on delivery against one bounded production outcome.
What we need from you
- Access to your repository and CI.
- One outcome, agreed in writing, that the sprint is meant to deliver.
What you receive
- Working code in your repository, through reviewed pull requests rather than a zip file.
- Tests that guard the outcome. The behavior you bought is the behavior that is tested, and the suite runs in your CI.
- Weekly written status. Shipped, in progress, blocked, and decisions needed.
- Decision log. Each non-trivial choice recorded with its context, in markdown in your repository.
- Handoff package. A runbook with deploy, rollback and known failure modes, an updated diagram, and a recorded walkthrough.
What happens next
The outcome is live and your team can operate and extend it. Anything shipped comes with its limits and rollback path documented.
Fractional engineering
Ongoing senior ownership without a full-time hire.
What we need from you
- An agreed slice of your system to own.
- Priorities set together each month.
What you receive
- A named owner for that slice, including its incidents and its roadmap. Set out on a one-page charter.
- Shipped work every month, under the same pull request and test discipline as a sprint, with a demo.
- Monthly engineering report. What shipped, system health, and accumulating risks. One to two pages.
- Current docs. Decision log and runbooks kept up to date.
What happens next
Each month: the report is sent, the demo happens, and the docs reflect the system as it is. The engagement runs month to month with 30 days notice.
Start with fifteen minutes.
A free call to see whether the triage fits your system. No preparation needed.