How a project actually runs
Every project runs the same way, whatever it is building. Working software on staging every two weeks, decisions in writing, and everything in your name from the start.
Two-week cycles, always
Every fortnight there is something running on staging that you can use. This is the single most important thing about how we work, because it means a wrong direction costs two weeks rather than six months, and you can stop at the end of any cycle keeping everything delivered.
Timezone overlap
We work Indian Standard Time and hold a guaranteed overlap window. For US Eastern that is four hours in your morning. For Europe it is most of your afternoon. Urgent items raised in the overlap get an answer the same day rather than the next.
- US Eastern: four hours of overlap, your morning
- US Pacific: two hours, arranged early in your day
- Europe: most of the working afternoon
- India: full working day
Decisions in writing
Anything agreed on a call is written up the same day and sent to you. Not minutes, just the decisions and who owns what. Verbal agreements across a timezone gap and a language boundary are where projects quietly diverge from what the client thought they were getting.
What we need from you
Projects stall on decisions far more often than on engineering. Four things prevent nearly all of it.
- One named person who can approve without convening a committee
- Feedback on each staging build within three working days
- Content, credentials and access before the work that needs them starts
- An early warning when something changes at your end
What you own at the end
Everything. Source code in your repository, infrastructure in accounts in your name, documentation written for whoever maintains it next, and a recorded handover session. There is no licence, no lock-in and no fee for leaving. We would rather be kept because the work is good.
Questions we get asked
That is expected, and the two-week cycle exists for it. Changes inside a cycle are usually absorbed. Anything adding a screen, an integration or a data model is written down and estimated in days, and then either replaces something planned or extends the date. You choose which, and nothing starts before you do.
Roughly two to four hours a fortnight for the named decision-maker, concentrated around each staging review. More at the start during discovery, less once the pattern is established. Projects where the client cannot find that time take noticeably longer, and we will say so early rather than let it drift.
Say so at the staging review rather than waiting. Every cycle ends with something you can use precisely so dissatisfaction surfaces in week two. If the problem is ours we fix it at our cost. If we cannot get it right, you stop at the end of a cycle and keep what has been delivered, in your repository.
Either. We have a standard agreement that covers IP transfer, confidentiality and payment terms, and we are equally happy to work under yours. Enterprise clients almost always use their own, and we read it properly rather than signing and hoping.
What clients say on Google
Unedited, pulled live from our Google Business listing.
Loading reviews from Google - read them on Google.
Sound like a way you could work?
Book a call and we will walk through what the first two cycles would cover.
- USD
- EUR
- GBP
- CHF
- SGD
- AUD
- CAD
- AED
- SAR
- QAR
- JPY
- INR
Card, netbanking, wallet and UPI through Razorpay, which is what our checkout runs on, so anything it accepts we accept. Bank transfer, SEPA, Wise and Payoneer for invoices that prefer it.
NDA before the first call. Full IP assignment on delivery. Contracts under Indian, English or Delaware law.