How we work
No surprises, in either direction
Most bad consulting experiences come from the same few causes: scope that was never written down, a team that changed after signing, and a handover that never happened. Our process is built specifically to remove those.
Ways to work with us
Four engagement models
Most relationships start with a Discovery Sprint, because it is the cheapest way for both sides to find out whether this is going to work.
Discovery Sprint
Fixed fee · one to two weeks
Best for: You know something needs to change, but not what to tackle first — or you need a credible estimate before going to your board.
- Current-state assessment of systems, costs and risks
- Target architecture and prioritised roadmap
- Effort and cost estimate for the recommended work
- Written report that remains yours, whoever you go on to use
Project Delivery
Fixed scope · milestone-based billing
Best for: A defined outcome with a clear finish line — a migration, a new application, a modernisation, an audit-readiness programme.
- Written scope with acceptance criteria per milestone
- Named senior delivery team
- Two-week iterations with working demonstrations
- Quality assurance, security review and documentation
- Structured handover to your team
Dedicated Pod
Monthly retainer · agreed capacity
Best for: Continuous product or platform work over months, where the roadmap will evolve and you want consistent people rather than a revolving bench.
- Senior engineers embedded alongside your team
- Agreed, predictable monthly capacity
- Quarterly roadmap and architecture reviews
- Shared delivery practices and code review with your engineers
- Thirty days' notice either way, with handover included
Advisory Retainer
Monthly retainer · limited hours
Best for: You already have a team. What you need is senior technical judgement available when decisions come up.
- Architecture and design review
- Vendor, platform and tooling evaluation
- Technical hiring and team structure input
- Escalation support when something goes wrong
How we work
Six stages, and you know where you are in all of them
Every engagement runs the same way. You should never have to ask what is happening, what is next, or what it will cost.
- 01
Discover
We map what you have, what it costs you to run, and what is actually holding the business back. This is deliberately short and fixed-fee, so you can find out whether we are useful without committing to a project.
- 02
Design
Target architecture, delivery sequence, risks and a written estimate. The document is written so you could hand it to any competent vendor — not only to us.
- 03
Build
Small senior teams working in two-week iterations. You see working software at the end of each one, receive a written update every week, and always know what is next.
- 04
Harden
Performance testing, security review, monitoring, alerting and runbooks — completed before anything carries real traffic or real data, not after the first incident.
- 05
Hand over
Documentation, architecture decision records, credential transfer and working sessions with your team. The measure of success is that your people can run it without us.
- 06
Support
An optional support or advisory arrangement, sized to what you actually need. You should stay because it is useful, not because leaving is difficult.
Commercials
How we price
We do not publish a rate card, because a rate on its own tells you nothing useful. The same number is a bargain for one piece of work and poor value for another. What matters is what you are committing to and when you find out.
So the commitment we make is about the process rather than the number: you get a written estimate before you commit to anything; discovery is fixed-fee so that assessing us is cheap; project work is billed against milestones you have accepted; and any change in scope is priced and approved by you before the work happens. You will not receive an invoice for something you did not agree to.
What you receive before committing
- A written statement of what we understand the problem to be — so you can correct us before it costs anything.
- Deliverables and acceptance criteria, in plain language.
- A timeline with the assumptions it depends on stated explicitly.
- A cost estimate, and what would cause it to change.
What you can hold us to
The commitments we make before you sign anything
We are a young firm, so we are not going to show you a wall of client logos. What we can offer instead is a set of specific undertakings — the things we think a technology partner should be willing to put in writing.
Senior engineers on your work
The people who scope the engagement are the people who deliver it. No handover to a junior bench after signing.
Written scope before any invoice
Deliverables, acceptance criteria, timeline and cost are agreed in writing first. Changes are priced and approved by you before they happen.
You own everything we build
Source code, infrastructure definitions, documentation and credentials are yours from the first day. No proprietary wrapper, no exit fee, no lock-in.
A named point of contact
One senior person who knows your engagement, is reachable, and does not change without notice and a proper handover.
Weekly written updates
Progress, what is blocked, and what is at risk — in writing, every week, whether the news is good or not.
Handover as a deliverable
Documentation, architecture decision records and working sessions with your team, so that continuing with us stays optional.
FAQ
Working with us, answered directly
The questions prospective clients ask before a first call. If yours is not here, ask it.
How do you price your work?
Discovery work is a fixed fee. Project work is fixed-scope and billed against milestones you accept. Ongoing work is a monthly retainer for an agreed capacity. In every case you receive a written estimate before committing, and any change in scope is priced and approved by you before it happens.
What is the smallest engagement you take on?
A Discovery Sprint, which runs one to two weeks at a fixed fee. It is designed so that finding out whether we are useful to you is a small, bounded decision rather than a large one. Many clients start there and stop there, and that is a perfectly good outcome.
Can you work with our existing in-house team?
Yes, and a good share of our work is mixed teams. We agree code ownership, review practice and working hours at the start so the arrangement adds capacity rather than friction. We are also happy to be the ones who write things down when a team has been moving too fast to document.
Who owns the code and the intellectual property?
You do, from the first commit. Source code, infrastructure definitions, documentation and credentials are yours and live in your accounts and repositories. We do not wrap deliverables in proprietary tooling, and there is no exit fee for leaving.
How do you handle access to our systems and data?
Access is least-privilege, individually named, time-bound, and recorded in writing as part of the engagement. We use your identity provider where you have one, we do not share accounts, and access is revoked at handover as a documented step rather than an assumption.
We are not a technical company. Is that a problem?
No. A significant part of the job is translation — making the trade-offs clear enough that a non-technical owner or board can make the call with confidence. If you cannot follow our reasoning, we have explained it badly, and we would like to know.
Where are you based, and do you work remotely?
We are based in India and work with clients across the country, primarily remotely, with on-site time where the work genuinely calls for it — migration cutovers, workshops and handover sessions being the usual cases. Our working hours are Indian Standard Time.
How quickly can you start?
It depends on current commitments, and we will tell you honestly rather than promise a date we cannot hold. A Discovery Sprint can usually begin sooner than a full delivery team. If we cannot take your work in a timeframe that suits you, we will say so at the first conversation.
Tell us what is not working
A first conversation costs nothing and commits you to nothing. Describe the problem in your own words and we will tell you honestly whether we are the right people for it.