How We Work: Process, Pricing, and Ownership

Every project starts with a call about your product, your goals, and your constraints. Within 48 hours you get a written proposal with a scope, a timeline, and a recommended set of tools.

To get a useful proposal fast, tell us what you're building, who it's for, and any deadline you're working against. Rough is fine. On the call we sketch your idea on a shared online scratchpad, so you can see what we've understood and correct us while it's still a drawing.

When the scope is clear, the proposal is a statement of work (SOW): what will be built, what won't, the timeline, and the tools. When you're still working out what you need, we work in sprints, which are short, fixed stretches of work, and agree the next few weeks together. Either way, you approve the SOW or the sprint plan in writing before we start building.

We agree on the engagement model during the first call. Each one fits a different situation.

We don't quote before we understand the project, because the number depends on a few things you can't see from the outside. The biggest are the number of user roles, how many third-party systems we integrate with, how much of the product is custom versus standard, and how much design work is involved.

Once those are clear, you get a proposal you can plan around. If you need a budget range earlier, ask on the call and we'll tell you what we can.

Before we write code, we plan how the system fits together, how its parts will talk to each other, and sketch the screens where it matters. Then we build in short stretches of work and show you the progress on a video call: every week on a full-time engagement, every two weeks on part-time work. Our founder joins the call, walks you through what has changed, answers your questions, and takes your feedback there and then.

Between calls we stay in touch on a message channel you agree with us, so the work doesn't stall waiting for an answer. If something is blocking the work, we ask for a quick call instead of waiting for the next one. That rhythm means no long blackout and no surprises at delivery. If something is off, you'll see it while it's cheap to change.

It happens on most projects, because you learn what you need as you see it working. We map the new request against the work already done, see what has to be redone, and adjust the timeline, the budget, or both. You hear about that before we go ahead, not afterwards.

We put the product on your own hosting, or set it up for you. You get the logins, a walkthrough and a training call for your team, and the technical documentation for whoever looks after it later. Automated releases (CI/CD) are in place so you can publish updates on your own.

Every project includes a post-launch support window, 15 days as standard, and we're open to extending it. After that, most clients choose a monthly maintenance retainer for bug fixes, dependency updates, security patches, and small features. You're never locked into a contract just to keep your own product running.

You do. All code, assets, and intellectual property belong to you on project completion and final payment. The cloud accounts and infrastructure are yours from day one, because we don't build on anything only we can access. NDAs and IP assignment agreements are standard.

Typically within one to two weeks of a signed agreement, depending on project complexity and team availability. For urgent work, we can sometimes begin within days.

Our founding team leads every project from discovery to delivery and stays your point of accountability. Specialist contract engineers join for the parts of the project that need them. We work remotely across India, the United States, the United Kingdom, France, the Netherlands, and Australia, so there is almost always overlap with your working day. You can meet the team on our About page.