Thirty minutes on what you’re building.
Then a written scope note.
- No charge
- Not a sales call
- Nothing to sign
You bring the problem and whatever architecture you already have. You leave with an honest read on the shape of it: what we would build first, what we would cut, and the parts that would worry us. Two working days later, that comes back in writing — yours to keep, even if you build it with someone else.
- 30 minutesVideo or phone, your call
- Aryan or PriyanshuDirector and CTO — no handoff
- 2 working daysWritten scope note afterwards
Five things we try to get through, in this order
We do not get through all of it every time. We get through the parts that decide whether the build is sane.
- 01
The problem in your words
What breaks today, who feels it, and what a fixed version looks like to that person. Not the feature list — the failure.
- 02
The system it has to live in
Your stack, where the data actually sits, and which integrations are known to be painful. If there is no system yet, we cover why.
- 03
Where a model belongs, and where it does not
Which steps genuinely need an LLM and which are cheaper, faster and more predictable as ordinary code. Usually fewer than people expect.
- 04
Data and deployment constraints
What can leave your infrastructure and what cannot — and whether that is regulatory, contractual or internal policy. It changes the architecture, not just the paperwork.
- 05
A first cut at scope and sequence
The smallest version worth putting in front of real users, what we would deliberately leave until later, and the parts we would worry about.
A written scope note, within two working days
A page or two written by whoever was on the call, not a proposal document. It is yours either way — if you take it to another team and build it with them, that is a fine outcome.
- The problem as we understood it — in plain language, so you can correct us.
- The shape of the system we would build — the components, where the data moves, what talks to what.
- What we would build first — what we would defer, and why in that order.
- The open questions and risks — the ones that would change scope once answered.
- What we would need from your side — and roughly when.
Book it if there is a decision to make. Skip it if there is not.
We take on few clients at a time, so we would rather be honest about fit up front than spend your thirty minutes finding out.
| Dimension | Book it if | Skip it if |
|---|---|---|
| The problem | Specific, and someone inside your company owns it | Nothing decided yet, nobody owns it, no date |
| The starting point | A system it has to fit into, or a clear reason there is not one yet | You want a written proposal before any conversation |
| The decision | You can say what would make the build worth doing | You are filling seats under someone else’s architecture direction |
| What you want back | A straight opinion, including one that disagrees with your plan | Boxes ticked for a vendor comparison spreadsheet |
The one we turn down mostA written proposal before any conversation. We will not scope a system we have not asked questions about, so the conversation has to come first.
Five fields, read by Aryan and Priyanshu
We reply with two or three times that work, usually within a working day.
- When we are around
- Roughly 09:00–19:00 IST, Monday to Friday. We will happily take a call outside that if your timezone needs it.
- On booking
- There is no public calendar link yet. Rather than fake one, we send back two or three times and you pick. A proper booking link will land here when it exists.
No obligation, and no long-term contract required to work with us.