How we deliver
A path with people at every decision
The same six stages apply to a pilot and to ongoing delivery. Each stage ends with something you can inspect.
- 01
Discovery
We learn the outcome you need, the system it lives in and who signs off on the work. We look at repositories, environments and constraints, and agree how access and source handling will work.
Decision Together: whether and how to proceed.
- 02
Scope and acceptance agreement
We break the outcome into scoped work items. Each has acceptance criteria that describe expected behaviour and the important failure cases, before anything is built.
Decision You and our team agree scope and acceptance criteria.
- 03
Implementation
Our engineers and agentic technology implement each item on a separate working branch and open it as a pull request. Tests are chosen for the work.
Decision Our engineers take responsibility for the design and implementation.
- 04
Verification and rework
A verifier, separate from the implementation, runs checks against the delivered code and examines the change and its evidence. Findings go back for rework. Failed checks stay visible.
Decision Our engineers review the outcome before it reaches you.
- 05
Customer review
You inspect the pull request, the test results, the verification findings and the documentation, using your normal review process.
Decision You accept the result or ask for changes.
- 06
Handover and release planning
We hand over code and documentation as agreed, with known limitations and notes. Merge, deployment and operational checks are planned with you; they are separate from verification.
Decision Together: release timing and operational checks.
How you see progress
You should never have to ask what state the work is in.
-
Scoped work items
- Each item has an owner, acceptance criteria and a state, from ready through in progress, waiting for review and verified.
-
Branches and pull requests
- Work arrives as pull requests in your repository, compatible with your review process, so you see changes as they are proposed.
-
Progress reports
- We report against agreed priorities on a cadence we set with you, including what is blocked and what needs your decision.
When scope changes
Change is normal. We make it explicit.
- A change is raised as a new or amended work item, not absorbed silently.
- Acceptance criteria are updated and agreed before the work continues.
- Priority changes are made by you; we explain what they displace.
- Work already delivered stays reviewable against the criteria it was accepted under.
Who owns what
-
What we deliver
- Rights in the code and documentation we deliver to you are set out in your engagement agreement.
-
Our technology
- At the heart of our consulting services is Drover, our proprietary technology platform. Developed in-house and operated by our consultants, Drover enables us to deliver sophisticated solutions without requiring our clients to license or manage the underlying technology.
Who does what
You
- Business priorities
- Domain knowledge and answers to questions
- Access to repositories, environments and people
- Acceptance decisions
Our team
- Scope refinement
- Implementation
- Testing
- Verification
- Progress reporting
- Agreed handover
Together
- Architecture choices
- Source-handling arrangements
- Release planning
Discuss your project
Tell us what you need built, improved or connected. We start with the outcome you want and who signs off on it.