How an engagement works
The same six steps every time. You know what happens next, and what you hold at the end of each one.
Discover
A short intro call about what you run and what you want changed. Then a written proposal with a fixed price.
- What you get
- A written proposal: scope, deliverables and a fixed price
- What we need from you
- 30 to 60 minutes with someone who knows the system
- Typical duration
- Proposal within a week of the intro call
Assess
Day 1: access agreed, read-only. We review the code, infrastructure and processes in scope.
- What you get
- Written findings, risks and options by the end of week 1
- What we need from you
- Read-only access to the systems in scope
- Time with your engineers
- Typical duration
- Week 1
Design
We agree the target design, the order of work, and how we'll know each part is done. You decide what comes first.
- What you get
- Architecture and a prioritized plan
- Acceptance criteria for each milestone
- What we need from you
- Someone who can make trade-off decisions
- Typical duration
- Agreed in the proposal
Build
We implement the plan in your repositories and accounts, in small changes your team reviews.
- What you get
- Changes merged through your review process
- What we need from you
- Access scoped to the work
- Code review from your team
- Typical duration
- First month fixed; the rest agreed in the proposal
Hand over
We document what we built and walk your team through it. Done means your team can run it without us.
- What you get
- Documentation and runbooks
- A handover session
- What we need from you
- The people who will own the system
- Typical duration
- First handover by week 4
- Optional
Operate
Optional. We stay on for changes, upgrades and incident support, alongside your team, on agreed terms.
- What you get
- Agreed response times and a regular review
- What we need from you
- A support agreement
- Typical duration
- Month to month
Support terms
- Duration
- Month to month. Cancel with 30 days' notice.
- Response
- Next business day for normal requests. On-call cover for critical incidents on the Premium support plan only, with agreed response times.
- Review
- A short monthly review of changes and open issues.
- Price
- Agreed in a written proposal.
- Hours
- A retained block of hours, set in the support agreement.
- SLA
- Response targets are written into the support agreement.
Ways to engage
Start with an assessment, or go straight to a build when the scope is clear. Ongoing support after handover is optional.
Assessment
A fixed-price review of what you run today. You get a written report and a prioritized plan.
Build
We implement the plan with your team, in your repositories and accounts, and hand it over documented.
Ongoing support
Optional, after handover: a retained block of engineering time for changes, upgrades and incidents.
Access and credentials
We work inside your systems. How we handle access matters as much as the work.
- We ask for the least access the work needs. Read-only while assessing.
- Access goes to named people, through your identity provider where possible.
- Credentials never travel over email or chat, and never leave your systems.
- Access is removed when the engagement ends, and we confirm it in writing.
Tell us what you're running.
A few lines about your stack is enough. We'll reply to set up a short intro call, then send a written proposal with a fixed price.
