Engineering Standards
The rules our engineers work to, and what each one leaves behind that you can check.
Every project goes through the same six steps. At the end of each one you get something you can look at and check, so you always know where your website or app stands.
When a project starts without a written brief, set points where you check the work, or a plan for going live, nobody is sure what is being built. That is hard on you, and on the people building it.
Our one rule
Every step ends with something you can check. We don’t move on until you have.
The steps are the same on every project. A small job gets a short version of each one.
We learn what you want to achieve, who will use it, what you already have and what limits we have to work within.
What we do
You get
A written brief you can read and correct: your goals, your users, how the work flows, what we assumed and the risks.
Your part
Tell us what a good result looks like, and let us talk to the right people and see the tools involved.
We plan how it will be built and in what order. Where there is a choice, we show you what each option gains and costs.
What we do
You get
A proposal: what is included, notes on how it will be built, the stages, the test for “done” at each stage and the price.
Your part
Look at the options and approve what is included before we build anything.
We build in stages you can look at. Every change is recorded, so we can always see who changed what and when.
What we do
You get
Something working that you can click through at every review, and a written update every two working days.
Your part
Join the reviews, answer our questions and tell us if your priorities have changed.
We test what we built against what you approved.
What we do
You get
Test results set against what you approved, with any open issues listed.
Your part
Try it yourself on the private test copy and tell us in writing that you’re happy.
We put it live step by step, and hand over everything you need to own it.
What we do
You get
Your live website or app, your own access to it and the written notes on how it works.
Your part
Approve the go-live date and confirm who holds each account.
We look after it and improve it under a support plan, if you choose one.
What we do
You get
A support plan that says in writing what is covered and how quickly we respond.
Your part
Choose a support plan, or run it yourself with the handover pack.
Each one is written for you, the person who approves the work. You don’t need to be technical to read them.
Your goals, your users, how the work flows, what we assumed and the risks, in plain words.
What you get, the stages, the test for “done” at each stage, the price and who is responsible for what.
What could go wrong and what we don’t know yet. Each item has a named person and a plan.
What we tested, what we tested it against and what is still open.
The steps, the backups and the way to undo it, for each release.
The written notes, your access and a record of the main decisions.
We use AI tools where they make the work faster and better. They never approve their own work.
Our engineers work with Cursor and models from OpenAI, Anthropic and Google, under a written policy.
AI tools work inside your project’s own code, so what they suggest fits what is already there.
AI tools never hold the logins to your live site or app. They never approve a change or put it live by themselves.
One engineer answers for every change, and a second engineer reads it.
Passwords, keys and personal data never go into any AI tool.
You can ask us not to use AI tools on your project.
You always know who to talk to, what has been done and what happens next.
What this way of working can’t promise
No way of working removes every issue. Ours makes problems rarer, easier to spot early and cheaper to fix. The checks we run are matched to the size of your project and written into your agreement.
One named contact. One named person is responsible for the result and for answering you.
Regular written updates. What we did, what comes next and any open questions, every two working days.
Hours when we are both online. At least 4 hours a day overlap with UK and US East Coast working hours.
A review at the end of each stage. You see it working and decide what happens next.
Changes in writing. Want a change? We tell you what it adds to the work, the time and the price. We start once you approve it.
You know who you are signing with. Our team manages the work from Pakistan. Your proposal names the company you contract with.
Yes, where it helps. The AI tools work inside your project’s code with limited access, and an engineer reads and tests every change.
We work out what the change adds to the work, the time and the price, and send that to you in writing. We start once you approve it.
Yes, but each step gets smaller. A small fix still gets a short brief, a review, a test and a careful go-live.
Yes. We can work in your code storage, your task tracker and your review steps. Where your rules are stricter than ours, yours apply.
In Pakistan. Our engineering and project work is managed from there for clients in other countries. Your project documents name the company you contract with.
Tell us about your project. Within one business day we’ll show you how these six steps would apply to it.