Skip to content
Start a project

FAQ

Answered properly, not evasively.

Every one of these is a question someone has opened a contact form to ask. If yours is not here, send it — we would rather have the difficult conversation now than three weeks into a build.

21

Questions answered

1h

Reply to anything else

The things people ask first.

If the awkward question is not here, send it. We would rather have the difficult conversation now than three weeks into a build.

Ask us directlyOne reply, from whoever would build it

21 answered in full

Our packages start at ₹70,000 plus GST: MVP ₹70,000 to ₹1,50,000, Full-fledged ₹1,50,000 to ₹3,50,000 and Growth and Scale priced after scoping. Where a project lands inside its range depends on how many templates, integrations and content types are involved. We quote a fixed number after a scoping conversation, and once it is agreed it does not move.

As a planning range, a marketing site usually takes three to six weeks, a mobile app eight to fourteen and custom software ten to twenty. You get a date in the proposal, and we renegotiate early if it is ever at risk rather than quietly missing it.

Yes. What we will not do is take a cheque for a full build when the honest answer is that you need a landing page and four customer conversations first. If that is the situation we will say so — it costs us the project and saves you a quarter.

Yes. We are based in Noida and can invoice in INR, AED or USD. We work async-first with a daily overlap window, so a different time zone does not have to slow a project down.

Yes, and it is part of every build rather than a separate line item. We design in components with real content and real edge cases — empty, loading, error, overflow — because those are the states that decide whether software is actually usable. We design the screens with our own tools and show them to you in a PDF to approve.

Usually, after a paid technical audit so we can tell you honestly what shape it is in. Sometimes the finding is that maintaining it costs more than replacing one part of it, and we would rather establish that up front than discover it three months in.

Always, and from the first commit rather than the last. We work inside your GitHub organisation and your cloud account. There is no licence, no proprietary platform and no clause that makes leaving expensive.

You get a bug-fix warranty, included in the price: 30 days on MVP and 90 days on Full-fledged and Growth and Scale. That covers defects in our work; new features get quoted like any other work. After the warranty, monthly care plans cover upkeep: Starter Care ₹4,999, Essential Care ₹11,999 and Priority Care ₹24,999 a month, plus GST.

There are 3 monthly plans, billed per month plus GST: Starter Care ₹4,999, Essential Care ₹11,999 and Priority Care ₹24,999 a month. They include up to 4, 10 and 20 hours of support a month, in that order. The hours are inside the monthly fee. They do not roll over to the next month, and we never bill by the hour. Work beyond the hours is quoted as a fixed-price change order, in writing, before anyone starts it. A care plan starts after the warranty ends.

We set hosting up in your own account — Vercel, AWS or whatever fits — so the bill and the control are yours, and you are never in a position where leaving us means losing your infrastructure. Ongoing care after launch is on the pricing page, as monthly care plans.

Payment is split into milestones tied to delivery, and each is invoiced when its stage is reached. MVP: 20% onboarding advance (when the deal is signed), 50% MVP ready (when the build is delivered for testing) and 30% completion (when you sign acceptance); Full-fledged and Growth and Scale: 20% onboarding advance (when the deal is signed), 20% designing (when you approve the design), 40% MVP (when the build is delivered for testing) and 20% completion (when you sign acceptance). Nothing starts before the advance clears — that is a gate in our own system rather than a policy we try to remember. Prices exclude GST.

Yes, and we will sign yours rather than insisting on ours. We also work under DPAs where a project touches customer data, and access to your systems is time-boxed to the engagement and revoked at handover.

Yes, on every build, included in the price: 30 days on MVP and 90 days on Full-fledged and Growth and Scale, counted from launch. If something we wrote is broken, we fix it at no cost in that period. That is in the statement of work, not a goodwill gesture.

SaaS is the right choice for generic functions like accounting or email marketing. However, when your workflow is your core business differentiator, when monthly user-seat licenses create an expensive growth penalty at scale, or when off-the-shelf tools require fragile third-party integrations, building an owned custom platform delivers far better unit economics, data sovereignty, and operational control.

Every build begins with an agreed Technical Project Requirements Document (PRD) and a deterministic Done-When checklist. Scope is locked during the design phase. If you need new capabilities during the build, we quote them as formal written change orders with fixed costs and adjusted dates rather than silently absorbing them, so neither the budget nor the deadline slips.

You own the custom source code, repository history, database schemas, and documentation. We build directly inside your GitHub organisation and cloud accounts from the first commit. Under our terms, complete IP ownership is assigned to your business upon milestone payment with zero proprietary lock-in.

An MVP build includes the primary user transaction flow, authenticated database models, production cloud deployment, and automated testing delivered in a focused 8-to-12 week cycle. We help founders trim non-essential complexity so they can validate their business hypothesis in the real market without budget overruns.

A desktop application is the right choice when your software requires direct hardware integration (such as thermal printers, biometric scanners, or industrial serial ports), offline operation without internet connectivity, local file processing with zero cloud latency, or dedicated background system services. For collaborative workflows, customer-facing portals, and multi-device access, a modern web application is the standard choice.

Traditional agencies often use senior engineers to sell the engagement and then delegate delivery to junior staff or offshore subcontractors with layers of account management. A software studio is compact: the senior engineers who scope your system are the ones writing your commits and deploying your infrastructure. We quote fixed scopes, defend realistic dates, and maintain direct technical communication.

Growing SMBs often hit operational bottlenecks when managing critical workflows across disconnected spreadsheets, manual reconciliation, and email threads. Custom automation tools unify inventory, orders, customer communications, and financial reporting into an internal control panel with role-based permissions, automated audit trails, and zero per-seat licensing penalties.

Software projects fail primarily due to ambiguous scope, unmanaged mid-sprint changes, and misaligned delivery criteria. We prevent this by establishing a Technical Project Requirements Document (PRD) before writing code, defining exact Done-When acceptance criteria for every screen, and maintaining strict change control where any new scope is quoted in writing with date impacts.
Start here

Tell us what you want to build.

One call, a deterministic technical scope, and a 100% fixed price. From architecture to launch, we engineer software that drives real business results.

Contact UsChat on WhatsApp