How we work
From brief to production in four moves.
The same four steps for every engagement, whatever the engine. The scope is written down before anything is built, and you see working software every two weeks.
- 01typically one to two weeks
Discover
We read your brief, ask the awkward questions and write down what we would build.
- A working session with the people who own the problem
- Constraints, integrations and risks listed before any design
- A scoped proposal in writing: what, how, and what it depends on
- 02typically two to four weeks
Design
Architecture, data model and a clickable prototype you can put in front of users.
- System design reviewed with your engineers, not handed to them
- Interfaces and contracts agreed before the build starts
- A prototype that settles the questions a document cannot
- 03scoped per project, agreed in writing
Build
Two-week sprints, a working demo at the end of each, and the code in your repository throughout.
- Senior engineers only; the people who scoped it build it
- Tests where failure would be expensive, observability from the first deploy
- A demo every sprint and a written status note you can forward
- 04ongoing, on your terms
Run
Hand-over with documentation and runbooks, or managed operation by us for as long as you want it.
- Runbooks, architecture notes and an onboarding session for your team
- A warranty period for defects at no additional charge
- Optional managed operation with an agreed response time
Engagement models
Three ways to work with us.
Every engagement is scoped in writing. The shape depends on how clear the problem is and how fast your roadmap moves.
Fixed-scope build
A defined deliverable, a written scope and a date. Best when the problem is clear and the outcome is a product.
Embedded team
Agatech engineers working inside your team and your process for a period. Best when the roadmap is moving.
Build and run
We build the platform and operate it with you afterwards, with agreed response times. Best when you want the outcome without the headcount.
Principles
What every engagement is built on.
- Platforms, not prototypes
- Everything we ship is typed end to end, tested where it matters, observable and documented.
- Agents with guardrails
- Evals on every change, explicit tool permissions, a human in the loop where it counts, an audit trail always.
- Your stack, your IP
- Code in your repository from the first commit, no proprietary runtime, hand-over included, NDA by default.
Tell us what you need built.
A short brief, a real engineer reading it, and a scoped answer within a few business days.