Three choices.
One fixed number.

Yes. Public pricing, product pages, and interactive demos are available before you speak to us. AI Architect can recommend a route and price band. A call is optional when you want to discuss fit, not a gate placed in front of basic information.

Product prices and hosting terms are published on the site. A Build Sprint is fixed-price and scoped in writing before work starts; the signed sprint plan or order form is the binding number. No hourly meter and no surprise change order.

Per sprint, not per week or per month. You buy a fixed-scope sprint at a fixed price agreed before work starts: a deposit to begin and the balance on delivery and handover (the Pilot Week is paid upfront). The weekly rate is only how the fixed number is calculated — it is not a subscription, so there is no meter and no retainer. Need more than one sprint? The next one is scoped and priced separately. Ongoing help afterwards is an optional flat add-on, never a default.

For a Build Sprint, the repository, deployment assets, and work-product IP described in the signed scope are handed over to you. Pre-existing ResoluteX products keep the licence stated on their product page, and managed services remain services. We make that boundary explicit before payment.

Often, yes. Customer-hosted products and custom builds can run in your infrastructure with your keys. Managed products have their own hosting and data terms. The product page and order form state the deployment boundary so self-hosted and managed offers are never presented as the same thing.

We prefer customer-controlled repositories and infrastructure, grant the minimum access needed, and remove access at handover. Security, retention, residency, backups, and incident responsibilities are documented for the actual deployment. NDAs and data-processing terms can be included where the engagement requires them.

A focused scope can usually be shaped within one business day, and most Build Sprints start within a week of sign-off. Your start date, milestones, and handover date are written into the sprint plan rather than left as a verbal estimate.

A missed item already inside the agreed scope is ours to finish. A genuinely new request is priced and scheduled separately before anyone starts it. That keeps the fixed price honest without pretending that new work is free.

Yes. A sprint can cover one risky workflow, integration, migration, release pipeline, AI layer, or internal tool. We begin with the smallest boundary that can ship safely and prove value, then expand only when the next scope is clear.

Every Build Sprint ends with code, deployment assets, documentation, and a handover. Ongoing hosting, maintenance, or a managed capability is optional and priced separately. You do not need a permanent retainer for the software to keep working.

Delivery is organised from our India and UK presence with planned overlap for the customer team. Written updates, visible work, and clickable demonstrations reduce status meetings; the overlap window and meeting cadence are agreed in the delivery plan.