Approach
Look first. Then build. Then leave.
How every engagement runs, and the principles behind it. We build towards being unnecessary, so your team ends up owning what we deliver.
Look
Two weeks, fixed price. We map what you have, what it would take, and what it is worth. You keep the written assessment whether or not you continue with us, and it is written so another supplier could act on it.
Build
Delivery in increments you can see running, not a six-month silence ending in a demo. Every piece ships with tests, source-to-target reconciliation counts, and documentation written for whoever inherits it.
Hand over
Your team runs it. Runbooks, a knowledge transfer document, and a defined period where we are on call while they take the controls. Support afterwards is available, never required.
Principles
What we will not trade away
These survive deadline pressure. When something has to give, it is scope, not these.
- Every number traceable back to the source it came from
- Reconciliation counts produced automatically, not on request
- Documentation written for the person who inherits it
- No proprietary lock-in we could hold over you later
- Your team keeps full access to everything we build
- We will tell you when the answer is to do nothing
- Estimates include the risks we can see, not just the happy path
- Work we would not want to inherit does not get shipped
Working together
Practical things worth knowing
The questions that usually come up in the second conversation, answered here instead.
Remote, with time on site
Most delivery is remote. Discovery, workshops and handover go better in person, and we plan for that rather than pretending otherwise.
We work in your tooling
Your repositories, your ticketing, your review process. Bringing our own would only mean handing over something unfamiliar at the end.
Fixed price where scope allows
Assessments are always fixed. Build work is fixed once scope is settled, and time and materials only where genuine discovery remains.
Small teams, no bench
The people you meet do the work. Nobody is substituted after signature for someone more junior.
We say no
If a piece of work sits outside what we do well, or the sequencing is wrong, we say so. Declining work that fits poorly is better for everyone than delivering it below standard.
Knowledge transfer is scheduled
It is a planned phase with its own time, not an afterthought squeezed into the final week.
Sound like a fit?
Tell us what you have in mind and we will be straight about whether we can help.