01
New projects
A paragraph about the problem is enough to start. We reply within two working days, usually with questions rather than a quote.
How we work Five ways to engage, and what each one costs you in effort.
Every model below states the team, the timeline, the shape of the commercial arrangement, and what we need from you. Pick the one that matches the decision you are making.
Engagement models
Product build
A fixed scope, a fixed team, and a working product at the end of it.
- Best for
- A first version that has to prove something, or a defined piece of work with a date attached.
- Team
- Tech lead, two to four engineers, designer as needed
- Timeline
- 8–12 weeks to a first release, then iterate
- Pricing
- Fixed scope, milestone-based
- You provide
- A decision-maker who can answer questions inside a day, and access to the systems we integrate with.
Dedicated engineering pod
An embedded team working in your repo, your rituals, your definition of done.
- Best for
- A roadmap that outgrew the team, where the work is ongoing rather than a project.
- Team
- Three to six engineers with a lead, scaling by quarter
- Timeline
- Rolling, minimum one quarter
- Pricing
- Monthly per-seat retainer
- You provide
- Repo access, a product owner, and a seat in your planning cadence.
Modernization audit
A written assessment of what you have, what it costs you, and what to do first.
- Best for
- Legacy systems, an inherited codebase, or a rewrite decision nobody wants to make blind.
- Team
- Two senior engineers, one architect
- Timeline
- 2–3 weeks to a written report
- Pricing
- Fixed fee, credited against a build that follows
- You provide
- Read access to the codebase and infrastructure, and an hour each with the people who run it.
Fractional CTO
Senior technical judgement on call, without the cost of hiring it full time.
- Best for
- Funded teams between technical leaders, or founders who need a second opinion that has shipped before.
- Team
- One principal engineer, named and consistent
- Timeline
- Rolling, one to three days a week
- Pricing
- Monthly retainer by day rate
- You provide
- A standing slot in your leadership cadence and visibility into the decisions being made.
Security review
An adversarial read of the code before someone else does it for free.
- Best for
- Contracts before deploy, agents before they get tool access, platforms before an enterprise review.
- Team
- Two reviewers, independent findings, one reconciliation pass
- Timeline
- 1–3 weeks depending on surface area
- Pricing
- Fixed fee by scope, re-review included
- You provide
- A frozen commit, the threat model as you understand it, and someone who can answer design questions.
The same six steps, whichever model you pick
- 01
Discovery
Constraints, users, and what is actually being decided.
- 02
Architecture
Written down and reviewed before anyone opens an editor.
- 03
Build sprints
Two-week cycles, demoed, with the branch always deployable.
- 04
Audit & QA
Adversarial review, load, and the failure cases nobody asked about.
- 05
Deploy
Staged rollout, monitoring in place before traffic arrives.
- 06
Support
A named engineer, an agreed response window, and a handover that works.
06 / Let’s build
Bring us the difficult problem.
02
Careers
Engineers, designers and researchers who like systems that are hard to get right. Send something you built and what you would change about it now.
03
Studio
Based in India and working remotely, with overlap hours agreed up front so your team always has a time to reach us.
04
Read
Guides on AI agents, RAG, MCP, tokenization and chain abstraction, written by the engineers who build them.