How We Work
How we work: engineered by people, accelerated by AI
AMT runs every project the same way. A senior engineer leads discovery, the work moves through five delivery gates you sign, and an AMT technical lead stays accountable for what ships. Our engineers use AI coding tools, under one written rule: no blind AI-generated code. Every line that reaches your repository has a named engineer who reviewed it.
Schedule Technical DiscoveryYour first conversation will be with a senior technical partner, not a salesperson.
AI-assisted development, with a named human on every line
AI coding tools make good engineers faster. They also make it easy to ship code nobody understands. That is the difference between AI-assisted engineering and what the industry now calls vibe coding.
| Vibe coding | AI-assisted engineering at AMT | |
|---|---|---|
| Who decides the design | The tool's first answer | An engineer, before the tool is opened |
| Who reads the code | Often nobody, if it runs | A named reviewer, on every pull request |
| Tests | Whatever the tool generated | Written against the acceptance criteria, then checked by a person |
| Security-sensitive code | Treated like any other code | Written and reviewed by a senior engineer |
| Who answers for a defect | Unclear | The engineer who approved it, and the technical lead |
The rules our engineers follow
- Design first. The approach is agreed by an engineer before any tool generates code.
- Every line is reviewed by a person before it is merged. The reviewer's name is on the pull request.
- Authentication, authorisation, payments, cryptography and personal-data handling are written or rewritten by a senior engineer, never accepted from a tool as generated.
- Your code stays in approved tools. Engineers use only AI tools on business plans that do not train on your code.
- You can opt out. If your contract or your regulator rules out AI tools, we work without them and say so in the statement of work.
- Generated tests are not proof. A person checks that each test actually tests the requirement.
The five delivery gates
Nothing moves to the next stage until both sides sign the gate. That is how you keep control without managing every ticket.
| Gate | What must be true | Evidence you get | Who signs |
|---|---|---|---|
| 1. Discovery complete | The problem, users, constraints and success measure are written down and agreed | A discovery report with scope, risks and an estimate range | Your sponsor and AMT's senior partner |
| 2. Architecture agreed | The design handles security, data, integration and cost at expected volume | An architecture note and the risks it accepts | Your technical owner and AMT's architect |
| 3. Increment accepted | Each increment meets its acceptance criteria in a test environment | A demo, test results and the release notes | Your product owner, every increment |
| 4. Production ready | Monitoring, rollback, access and runbooks are in place | A production readiness checklist, signed | Your operations owner and AMT's technical lead |
| 5. Handover complete | Your team can run and change the system without us | Documentation in your repository, a recorded walkthrough, access transferred | Your technical owner |
Want the gates applied to your project? Schedule Technical Discovery
Who you work with
- A senior technical partner runs discovery and stays your escalation point for the whole engagement.
- A technical lead owns the quality of what ships and reviews the team's work.
- Engineers who join your tools: your repository, your tracker, your chat.
- Leadership you can name. Aby Varghese (Founder and Managing Director), Roopesh Natarajan (VP Projects) and the rest of the team are on the About page.
How we keep you informed
| What | How often | What it contains |
|---|---|---|
| Stand-up | Daily, inside the overlap window | Progress, blockers, decisions needed from you |
| Demo | Every increment | Working software, not slides |
| Status note | Weekly | Done, next, risks, decisions, budget used |
| Steering review | Monthly | Scope, risk and commercial review with your sponsor |
Working hours overlap with UK and European business hours every day. Overlap with US time zones is agreed per project.
What you keep
- Code and documentation live in your repository from day one, not ours.
- Decisions are written down in the repository, so a change of engineer does not mean a change of memory.
- Access is yours to revoke. We work through accounts you control.
When AMT is the wrong choice
FAQ
Does AMT use AI to write code?
Yes, as an assistant. Engineers use approved AI tools to move faster, and every line is reviewed by a named engineer before it is merged. Security-sensitive code is written or rewritten by a senior engineer.
What is the difference between vibe coding and AI-assisted development?
Vibe coding accepts what an AI tool generates as long as it runs. AI-assisted development uses the tool inside an engineering process: design first, human review on every change, real tests, and a named person accountable for defects.
Can we stop AMT engineers from using AI tools on our project?
Yes. Say so before the work starts and it goes into the statement of work.
Is our code used to train AI models?
No. Engineers may only use AI tools on business plans that do not train on customer code.
How does a project with AMT start?
With a 30-minute technical discovery call, then a discovery sprint of two to three weeks that ends in a written scope, risks and an estimate range.
What happens if an engineer leaves mid-project?
Documentation lives in your repository and the technical lead knows the system, so a replacement picks up from written decisions, not memory.
Tell us what you are building and where it is stuck. A senior engineer will reply within one business day.