Pricing
How we quote, and what moves the number
We do not publish a rate card, because the same one-line brief can mean four weeks or six months. We do publish exactly how we price, what drives cost, and what is included every time.
In short
KriyaXlabs works on five engagement models: fixed-scope projects, four-to-eight week MVP sprints, retained monthly capacity, embedded engineers and product partnerships. Every engagement starts with a free discovery call and a written scope, and you own the code from the first commit.
Five ways to engage
Fixed-scope project
When it fits
The requirement is clear and you want a number before you start.
Typical work
Defined platforms, migrations, integrations, redesigns.
How it runs
We scope it in writing, quote a fixed price and a fixed date, and carry the risk of our own estimate. Change requests are quoted separately rather than absorbed silently or refused.
MVP sprint
When it fits
You have an idea and need something real in front of users quickly.
Typical work
First versions, funding demos, market tests.
How it runs
Four to eight weeks, fixed scope, weekly demos and a staging deploy you can use. We cut features rather than dates, and we tell you which ones on the call before we start.
Retained capacity
When it fits
The work is continuous and the roadmap changes faster than a scope document.
Typical work
Live products, ongoing feature work, long roadmaps.
How it runs
A monthly retainer buys a fixed amount of engineering capacity. You direct it sprint by sprint. Unused capacity does not roll over, which keeps both sides honest about the size of the commitment.
Embedded engineers
When it fits
You have a team and a gap rather than a project.
Typical work
Scaling an existing team, specific stack expertise.
How it runs
Our engineers join your standups, your repository and your review process. You manage the work; we manage the people. Minimum three months, because anything shorter costs more in onboarding than it returns.
Product partnership
When it fits
You want a studio that owns the outcome, not just the tickets.
Typical work
Founders without a technical team, new product lines.
How it runs
Strategy, design and engineering under one roof, with a longer horizon and shared accountability for what the product does in the market. Structured case by case.
What actually drives cost
Six things move a quote more than anything else.
How many surfaces
One web app is not the same as a web app, an admin console and two mobile clients. Surfaces multiply design, testing and release work more than they multiply back-end work.
Whether it is multi-tenant
Serving one organisation and serving a hundred are different products. Row-level isolation, org-scoped roles and audit logging are worth building early and expensive to retrofit.
Integrations and identity
Payment gateways, single sign-on, SCIM provisioning and third-party APIs each carry their own failure modes, sandbox quirks and certification steps.
AI, and how sure it has to be
Calling a model is cheap. Verifying its output, grounding it in your content and controlling its cost at volume is the actual work, and it is what separates a demo from a product.
Compliance and procurement
If an institution's procurement committee will review this, the audit trails, data handling and documentation are part of the build rather than an afterthought.
The state of what exists
Taking over a codebase is sometimes faster than starting fresh and sometimes much slower. We do a paid architecture review first rather than guessing, and you keep the findings either way.
Included in every engagement
- 01A written scope before anything is billed
- 02Weekly demos on a staging environment you can use
- 03Source code in your repository from the first commit
- 04Infrastructure as code, deployed into your accounts
- 05Handover documentation and a walkthrough at the end
- 06No lock-in: nothing we build depends on us staying
Getting a number
- 01Book a free thirty-minute discovery call.
- 02We reply within one business day to confirm it.
- 03You get a written scope and a fixed quote within two business days of the call.
- 04If the scope is not knowable yet, we propose a paid architecture review instead, and you keep the findings.
Not sure which model fits? Start with the services or tell us the problem on the call and we will recommend one.
Questions about cost
PricingHow much does it cost to build an app with KriyaXlabs?
It depends on scope, and we quote rather than publish a rate card, because the same sentence from two founders can mean a four-week build or a six-month one. What we can promise is a written scope and a fixed number before you commit anything. Book a thirty-minute call and you will have a detailed proposal within two business days.
PricingDo you charge for the first call or the proposal?
No. The discovery call is free and so is the proposal that follows it. We charge for architecture reviews of existing systems, because that is real work with a written deliverable you keep whether or not you hire us.
PricingDo you work fixed-price or time and materials?
Both, and we will tell you which one fits. Fixed price when the scope is genuinely knowable, which suits defined projects and MVP sprints. Retained capacity when the roadmap will change, because pretending otherwise leads to change requests instead of progress.
PricingWhat is the smallest engagement you take?
An MVP sprint, or a paid architecture review. Below that the coordination cost outweighs what we can usefully deliver, and we would rather point you somewhere better than take the work.
PricingWho owns the code?
You do, from the first commit. Work happens in your repository or is transferred to it, infrastructure is deployed into your accounts, and handover includes documentation and a walkthrough. Nothing we build is designed to keep you dependent on us.
PricingDo you offer maintenance after launch?
Yes, as a monthly retainer sized to the product. Some clients take a small retainer for security updates and incident response; others keep a larger one for continuing feature work. Neither is compulsory.
Get a fixed number
Thirty minutes on a call, a written scope within two business days, and no obligation to go ahead.
30 min · No obligation · Reply within one business day