Your first release, built and launched. One team, one fixed quote.

A deployed first release in accounts you own, where one agreed core journey works end to end: for example, a customer signs in, submits a request and sees its status. Every build includes UX for that journey, frontend, backend and the data storage it needs, sign-in and permissions where the product needs them, the integrations listed in the scope, tests on the agreed critical paths, error monitoring, handover documentation and 30 days of defect fixes after launch. Payments and billing, AI features, native mobile apps, data migration and complex or custom integrations depend on scope and are priced in the quote.

Hosting, AI usage, third-party subscriptions and app-store developer accounts are billed directly to your own accounts, not through us. We estimate them during scoping, so you know the running costs before the build starts.

The scoping call is free, and straightforward products get a written scope and fixed quote at no cost. Products that need deeper discovery start with a $500 Scope Sprint: in 3–5 business days after we receive the information we need, you get the core journey, included features, exclusions, integration dependencies, acceptance criteria, build plan, timeline and a fixed build quote. It is paid upfront once the deliverables are agreed, credited in full against the build, and the documents are yours whether or not you continue. Extensive technical investigations, prototypes or detailed screen designs are quoted separately.

40% when you approve the scope, before the build starts; 30% when the core journey is demonstrated on staging; and 30% after production deployment and handover. Before launch there is an acceptance review window, agreed in the scope, where you check the release against the written criteria. A Scope Sprint fee is credited once against the total.

In writing, before the build starts. The approved scope fixes the core journey, features, exclusions, dependencies, acceptance criteria, build plan and schedule. Payment follows three milestones: 40% when you approve the scope, 30% when the core journey is demonstrated on staging, and 30% after production deployment and handover. Before launch you review the release against the written acceptance criteria, in a review window agreed in the scope. You own the code, designs, documentation and the accounts it runs in.

In the approved scope. It assumes your decisions arrive within the review times we agree, and that outside dependencies such as app-store review, API access or payment-provider approval arrive on time. If one of those slips, we tell you as soon as we see it and what it moves.

Tell us. Changes to the agreed scope are written up and quoted before we do them, so you decide whether they go into this release or the next one. Nothing is added silently.

For 30 calendar days after launch we fix delivered functionality that does not meet the agreed requirements, at no cost. New features, changed requirements and third-party changes are scoped separately, and you can continue with engineers by the month.

Not necessarily. The case studies show how our team owns and coordinates delivery. Your price and schedule come from your own scope.

We cannot promise that, and nobody honestly can. We deliver the agreed software and can help you measure how people use it. Whether customers want it is what the first release is for testing.

Your delivery lead is backed by our engineering team in Lahore, Pakistan, working with you remotely through regular demos and an agreed channel.