Five commitments on every project.
A small team can carry a large scope only if nothing is left to memory. This is the discipline we work to.
- 01We agree the design with you in writing before we build.
You approve what is built, and each design. We decide how it is built.
- 02Every change is tested by machine, and the tests are yours.
Automated tests run on every change. They are handed over with the code, so they keep working for you.
- 03You always know where it stands.
A regular plain-English report: what was delivered, what got in the way, and the decisions we need from you.
- 04Security is designed in, and independently tested where it matters.
What a person can see and do is decided on the server, never by hiding things on the screen. Where the risk calls for it, the system is penetration-tested by an independent firm.
- 05You own it.
Code, tests, pipelines and documents, in your repository, with a paper saying what it takes to support.
A tool in a senior engineer's hands.
We use AI tools to help write and check code, tests and documents. They make an experienced engineer faster. They do not replace one.
- A named senior engineer designs every change.
- The same engineer reviews it and answers for it.
- Nothing ships until it passes its automated tests.
- Every release goes through the same pipelines.
What if your engineer is unavailable?
It is the first thing to ask a small firm, and the answer is in how the work is kept. The state of a project lives in records, not in one person's head.
- The design is written down and approved.
- The tests say what the system is meant to do.
- The pipelines say how it is released.
- The code and documents are in your repository.
- There are two directors.
The system we run delivery on.
Atlas is our own system for running a project. Every piece of work has an owner, a design approved by a person, checks it must pass, and a record. A board shows progress, what got in the way, and the decisions waiting for you.
About Atlas →What you are given at the end.
All of it, in your repository, with its history.
The automated tests, ready to run on your next change.
The build and release pipelines, so releases carry on the same way.
The specification, the architecture, the security model, and what it takes to support.
Start with a delivery health check.
One to two weeks on your Dynamics 365 or Power Platform estate, ending in a written report and a costed plan.