The first thing we give you is not a proposal.
It is a plan you own. Two weeks of mapping the process as it actually runs, the architecture decisions written down in language your board can read, and a costed sequence you are free to build with us, with your own team, or with somebody else. We would rather be paid for two honest weeks than win a build we are wrong for.
One call, two weeks, and a decision that is yours
Four ways to work with us, and what each one owes you.
Nearly everything starts with a discovery. What happens after it depends on how much of the work you want to keep in your own team — all of it, none of it, or the one piece nobody wants to own.
Discovery
Where most startWhere nearly every engagement starts. We map the current process, agree what success means in a number, and produce a plan you own.
What you get- A written problem statement, agreed by your side
- An architecture decision record in plain language
- A costed plan with a sequence and a first milestone
- A straight answer on whether we are the right team
Build
Architecture through to launch, with a named delivery lead and a working system you can click from week one.
What you get- A weekly working demo against a shared plan
- A staged environment from the first sprint
- A named lead who is reachable, not a coordinator
- Source and cloud accounts in your ownership
Managed operations
Running what we built, with support scheduled around when the system is genuinely used rather than around office hours.
What you get- Agreed response targets by severity
- On-call cover aligned to real usage windows
- A written post-mortem after any severity-one event
- Continuous improvement against an agreed backlog
One piece
You already have a team. We take the part nobody else wants to own — the AI layer, the operations console, the migration behind a facade.
What you get- A defined slice with its own acceptance criteria
- Your team keeps the domain knowledge in house
- Documentation written for your engineers, not ours
- A clean exit at the end of the slice
Five things that double the value of thirty minutes.
None of these are prerequisites — if you have a problem and no paperwork, call anyway. But a first call that has these in the room usually ends with a real answer instead of a follow-up to schedule another call.
Send it to us insteadThe problem in one sentence
Not the solution you have in mind — the thing that is going wrong. "Passes take three days to approve" beats "we need a workflow platform".
What happens today, including the manual bits
The spreadsheet, the WhatsApp group, the person who checks it by eye. Those are usually where the real requirement is hiding.
Who decides
Name the person who can approve scope and budget. Engagements stall on decision latency far more often than on technical difficulty.
The deadline that is real
A session date, a contract renewal, an audit. A real deadline shapes sequencing; an invented one produces a plan nobody believes.
Any constraint you already know about
Data residency, procurement route, an existing stack you must integrate with, a certification your policy requires. Earlier is cheaper.
When we are the right firm — and when we are not.
Published because it is cheaper for both of us than finding out in week six. If the right-hand column describes you, say so at the first call and we will tell you the same thing in person.
- The system matters — failure would be visible, expensive or on the record.
- You want one team accountable end to end rather than three vendors and an integrator.
- It has to work in real Indian conditions: multilingual, low bandwidth, older devices, field use.
- You can give us access to the people who do the work today, not just to their managers.
- You are buying a system that will run for years, not a demo for a board meeting.
- Your policy requires an ISO 27001 certified vendor today. We are implementing it and do not hold it yet — that is stated plainly on our security page.
- You are optimising for the cheapest quote. We will not be it, and we would rather say so now.
- The scope is a head count of developers rather than an outcome. Staff augmentation is a real business; it is not ours.
- You need it live in three weeks with no discovery. We would be guessing, and you would be paying for the guess.
- Nobody on your side can make a product decision inside a week. That single constraint sinks more projects than any technical one.
The questions we will ask
Published in advance on purpose. A discovery is worth what the answers are worth, and the answers are better when nobody is hearing the question for the first time in a meeting.
Answer them with us- 01What happens today, step by step, including who touches it and when?
- 02What does it cost you when this goes wrong — in money, time or reputation?
- 03Who are the users, and what device and connection are they actually on?
- 04What has been tried before, and why did it not stick?
- 05Which parts are regulated, audited or on the public record?
- 06What must be true on day one, and what can wait until month six?
- 07Where does the data come from, where must it live, and who may see it?
- 08How will we both know, in a number, whether this worked?
The questions that decide it.
- What does a discovery cost?
- It is a fixed price for a fixed two weeks, quoted after the first call once we know the shape of the problem. We quote it before you commit to it, and the output is yours regardless of what you do next.
- What if we stop after discovery?
- Then you keep the problem statement, the architecture note and the costed plan, and you are free to build it with your own team or another firm. That is a legitimate outcome. A discovery that only has value if it leads to a build is a sales exercise, not a discovery.
- Who owns the code?
- You do, along with the cloud accounts. There is no proprietary runtime that only we can operate, and handover to your own team is a defined, priced process rather than a negotiation conducted under pressure.
- Where is your team?
- Hyderabad. The people who scope your work are the people who build it — there is no separate delivery centre that inherits the project after the pitch.
- Can you respond to a tender or an EOI?
- Yes. Send the document with your first enquiry along with any security questionnaire, and entity details and a capability statement come back the same day.
- How quickly can you start?
- A first call within a few days, and a discovery usually within two to three weeks depending on what is already in flight. If we cannot start when you need us to, we will tell you at the first call rather than at the third.
Let’s build what’s next.
Tell us where your business wants to grow. In one conversation we will show you where AI and software will pay back first, and whether we are the right team to build it.
- 30 minutes, free, no obligation
- A clear, practical recommendation
- Your ideas and data kept confidential
Book a free strategy call
We look at your goals, your current systems and your biggest time and cost drains, then recommend the first AI or software move with the fastest payback.
Book my strategy callRequest a briefing
A working session on your requirement, our reference deployments and a capability statement.
Public sector