The Pair
Both of us, on your backlog.
Some companies do not need a discovery process. They need two people who can build, who have shipped in production before, and who can start on Monday. The Pair is us inside your team: your repo, your standup, your backlog, moving at the speed you actually work at.
- Time
- Month to month, 30 days notice either way
- Terms
- MonthlyBoth of us. One of us part time, quoted lower
A week
Both of us, every day.
A real week. Both of us on your backlog, in your repo, in your standup.
Included
Everything you keep.
- 01
Both of us, on your backlog
Product and architecture in the same pair. Mayank on what to build and whether it pays, Atul on making it survive production. No account manager between you and either of us.
- 02
Your repo, your standup, your tools
We work inside your workflow rather than exporting you into ours. Every commit is in your repository under your history.
- 03
Shipping weekly
Something in a reviewable state every week. We would rather ship at eighty percent and iterate than present a plan for a month.
- 04
AI-native throughput
We build with agents rather than talking about them, which is most of why two people can carry the load of a larger team. It is also why the security discipline is not optional.
- 05
Documented as we go
Runbooks and decision records written during the work, not promised at the end. This is the answer to what happens when we leave: nothing breaks, because the knowledge was never only in our heads.
- 06
A hard stop when you want one
Month to month. When your own team can carry it, we hand over and go. Several engagements have ended exactly that way and that is a good outcome.
Do this if
- You have more roadmap than engineers and hiring takes three months
- You have a prototype that works and needs to become a product
- Your team is strong but has never shipped an agent into production
- You want people who will argue with the spec, not just implement it
Do not, if
- You need five engineers. We are two, and we will say so on the first call
- You want staff augmentation billed by the hour. We do not sell hours
- The work is maintenance on a stack neither of us knows. We will pass
The Pair / questions
What people actually ask.
You are two people. Is that not a risk?
It is a risk if the knowledge lives in one head. Ours does not. Both of us are across every engagement, everything is documented while we build it rather than afterwards, and the code and accounts are yours from the first day. What you are actually buying is the thing an agency structurally cannot sell you: the two people who pitched are the two people who build.
Do you subcontract?
Not silently. If a piece of work needs a specialist neither of us is, we say so and you decide. When a build genuinely outgrows two people there is a Delhi team we have worked with for years, and that is scoped, quoted and named in writing before anyone touches your systems. It is never folded into our fee.
How many clients do you take at once?
Three active engagements, maximum. That is the real limit and we would rather publish it than discover it with you.
Which stacks?
TypeScript and Next.js, Python, Postgres, the major clouds, and the current agent tooling. Atul carries fifteen years of solutions architecture and DevOps across a wider range than that. If it is a stack we would be slow in, we will tell you rather than learn on your budget.
What does your team still do by hand?
Thirty minutes. No deck. Sometimes the answer is that you do not need us, and that is a short call.
Book thirty minutes3 engagements at a time