What working with us is actually like
Including what we need from you, because most project problems come from the client side being unclear about that.
01Discovery
1-2 weeksWe work out what you are actually building and what it will cost. Process walkthroughs, a technical assessment of anything we must integrate with, and a written specification with a scoped estimate.
What you get
A specification, an estimate with a range, and a plan. Yours to keep even if you do not proceed.
What we need from you
Access to the people who do the work today, not only the person commissioning the project.
02Design
2-4 weeksInterface design for the screens people will use daily, reviewed with your actual users rather than only with management. We design the unhappy paths — empty states, errors, permissions — because that is where software usually disappoints.
What you get
Clickable designs you can put in front of your team before anything is built.
What we need from you
Honest feedback early. Changing a design is cheap; changing built software is not.
03Build
The bulk of the projectTwo-week sprints with a working deployment at the end of each. You see progress continuously rather than waiting for a reveal. Priorities can change between sprints — that is the point of working this way.
What you get
A running staging environment from week one, and a demo every fortnight.
What we need from you
One decision-maker who can settle questions within a day or two. This is the single biggest factor in timelines.
04Testing & hardening
1-3 weeksFunctional QA, performance testing at realistic volumes, and a security review. We test with your real data volumes, not a hundred sample records, because most performance problems only appear at scale.
What you get
A test report, known issues documented honestly, and a go-live checklist.
What we need from you
A few of your people to run through real scenarios. They find things we cannot.
05Launch & handover
1-2 weeksDeployment, data migration, training delivered separately per user group, and documentation. Then a support window while your team settles in.
What you get
Source code, documentation, deployment runbook and training. Everything needed to continue without us.
What we need from you
Time from the people who will run it. Training is not optional.
Communication
Most unhappy software engagements are communication failures rather than engineering failures.
Weekly written update
What shipped, what is next, what is blocked, and anything that has changed about the estimate. Sent whether or not there is good news.
Fortnightly demo
A working build, not a slide deck. Thirty minutes, and you can invite whoever you like.
A shared channel
Slack or WhatsApp, with the engineers in it. Not a ticketing queue and not an account manager.
Your tools, where possible
If you use Jira, we use Jira. Asking a client to adopt our tooling for our convenience is backwards.
Common questions
What happens if the project runs over?
You hear about it as soon as we know, not at the deadline. On fixed-scope work, overruns caused by our estimation are ours to absorb; overruns caused by added scope are quoted before the work starts. We do not do the silent-overrun-then-invoice thing.
Who owns the code?
You do, from the first commit. The repository is in your organisation's account, not ours. This is in the contract, and you should insist on the same from any vendor.
What if we want to change direction mid-project?
On a dedicated-team engagement, just change the priorities at the next sprint. On fixed-scope work, we re-scope and re-quote the affected portion. If you expect direction to change, a dedicated team is the honest model and usually cheaper overall.
Do you work with our existing developers?
Frequently, and it usually works well. We agree code ownership boundaries and review conventions upfront. The common failure is ambiguity about who owns what, so we settle that before writing anything.
What time zones do you work in?
IST, with deliberate overlap into European and US morning hours. For US clients that typically means a few hours of live overlap each day, which is enough for standups and decisions if the written updates are good.
Let's talk about what you're building
Tell us what you need and we will come back with a scoped estimate and a realistic timeline — within one business day.