How we work
How an engagement actually runs
Four stages, in the order you experience them. We publish this rather than a portfolio because the way the work runs is what you are buying, and because a gallery of finished screens tells you nothing about what it is like to work with us.
Discovery
We find out what actually happens, not what the manual says happens.
Every operation has a documented process and a real one, and the gap between them is where the cost hides. We sit with the people doing the work, follow a job from end to end, and put numbers on each step — how long it takes, how often it is redone, how many times the same information is entered. It ends with a map your own team recognises and a redesigned flow you approve before anything gets built.
What happens
- Watching the work happen, on the floor rather than in a meeting
- Interviewing the people who run it daily, not only the people who own it
- Timing and counting each step, so the findings carry numbers
- Redesigning the flow and agreeing it with the people it affects
What you receive
- A measured map of the process as it runs today
- Findings ranked by what they cost you
- A redesigned process, agreed before anything is built
- A specific estimate for whatever you decide to do next
What we need from you
A few hours from the people who do the work, and one session to review the findings. You end this stage able to act on the map whether or not you continue with us.
Development
Short cycles, each ending with something you can use rather than read about.
We build in cycles measured in weeks, not months. Each one ends with the work on an environment you can log into and try, so you judge progress by using it rather than by reading a status report. What we build first is whatever removes the most pain, so the earliest cycles are usually the ones you feel.
What happens
- Building in short cycles, highest-pain first
- Automated tests written alongside, not afterwards
- A weekly call and a shared channel for anything between them
- Re-estimating before any change of scope, never after
What you receive
- Something usable at the end of every cycle
- An environment you can log into that is always current
- A test suite that grows with the system
- A revised estimate before scope changes, never after
What we need from you
One call a week and whatever questions arise in the shared channel. Priorities can move between cycles at no penalty — that is what the cycles are for.
Updates
Changes reach you on a rhythm, and you always know what changed.
Releases are routine rather than events. Each one arrives with a plain description of what changed and why, so nobody has to read a commit log to find out. Nothing goes out that has not run in an environment you could have looked at, and anything that turns out to be wrong can be rolled back rather than patched under pressure.
What happens
- Releasing on a predictable rhythm rather than when something is finally ready
- Writing what changed in language the people affected can read
- Rehearsing anything that touches live data before it touches it
- Keeping a way back from every release
What you receive
- A release note per update, written for the people who use it
- A rollback path for anything that touches live data
- Training or a walkthrough when a change alters how someone works
What we need from you
You decide when a change reaches the people using it. We never surprise an operation with its own software.
Improvements
We measure the new process against the old one and keep going.
Launching is not the end of the work; it is the first time the process meets real load. We watch how it behaves, measure it against the numbers we took during discovery, and fix what only real use exposes. From there the same loop continues at whatever pace suits you — the next thing worth improving is usually obvious once the first one stops hurting.
What happens
- Measuring the new process against the discovery baseline
- Watching monitoring and alerts through the first weeks of real load
- Fixing what only real traffic exposes
- Agreeing what is worth improving next, or stopping cleanly
What you receive
- A before-and-after against the numbers taken in discovery
- Monitoring, alerting and backups you own
- A runbook and handover documentation
- A support agreement, or a clean handover and training
What we need from you
As much or as little as you want. Some clients keep a standing cycle; others take the handover and run it themselves. Both are normal endings.
How we work
What stays true at every stage
These do not change between engagements, and they are the parts clients tell us they had not had before.
You can always see the work
An environment you can log into that is current, not a demo scheduled for Friday. Progress is something you use, not something you are told about.
Estimates move before the work does
Anything that affects the schedule gets a revised estimate before we do it. The surprise arrives while you can still act on it.
Everything has a way back
Nothing reaches live data without a rehearsed path to undo it. Cutover is a decision you make, not a risk you accept.
You own it as it is built
The maps, documentation and systems live in your accounts from the first day. Leaving costs nothing but the decision.
Questions
Asked before you ask
It depends on the scale of the operation, which is why we do not publish a single number. A focused workflow is measured in weeks; something covering several sites or departments is measured in months. Discovery takes two to four weeks and ends with a specific estimate for your project — and we would rather estimate long and deliver early than the reverse.
Close, and that is the point of paying for discovery before committing. We estimate after understanding the work rather than before, we deliberately estimate on the conservative side, and when something does move you hear about it in the week it happens rather than at the deadline.
It usually does, and priorities can move between cycles at no penalty. Anything that affects the schedule gets a revised estimate before we do the work, never after — so the surprise arrives while you can still act on it.
You do, from the first day. The process maps, the documentation, the systems and everything they run on live in your accounts and stay there. There is nothing licensed back to you and nothing held back, so leaving costs you nothing but the decision.
Specialists in exactly the kind of work your project needs — mapping the process, redesigning it, automating it, and building whatever runs it on web, mobile or desktop. Every discipline an engagement takes sits under one roof, so nothing waits on an outside party and nobody is put on your project to learn on it.
Tell us what needs fixing.
Describe the problem in a paragraph. Someone who does the work reads every message and replies within one business day — no call required to get a straight answer.