Estimate a project
Four questions, and a number you can take to your board.
No call, no discovery fee. The range is indicative — we will scope it properly before anyone signs anything.
Indicative range
—–—
What are we building?
Pick the closest. We will scope the detail properly on a call.
How much of it exists already?
Rebuilding on something solid costs far less than starting cold.
What does it need to talk to?
Integrations are usually where estimates go wrong, so we ask early.
When does it need to be live?
Compressed timelines mean more people in parallel, which costs more.
Want the breakdown in writing?
We will send what drives that range, what would move it up or down, and two comparable projects. One email, no sequence.
Rather just talk it through?
Book a scoping callOn its way
Sent. Now the useful part.
The breakdown is on its way to. A range is a starting point though — thirty minutes turns it into a written scope and a number, and you keep both either way.
One email, no sequence — exactly as promised. If it has not arrived in ten minutes it is in spam, or you can reach us atcontact@xtenzium.com.
Ranges are based on our last three years of delivered projects and assume a standard engagement. They are not a quote.
What moves the number
Four things, and none ofthem are a mystery.
Most agencies keep this opaque. It is not complicated, and knowing it lets you change the number yourself.
- 01
What it is
A marketing site and a connected-hardware fleet are different orders of magnitude. This sets the floor; everything else scales it.
- 02
What already exists
Designs signed off, or a blank page? Extending a working product costs roughly half what starting cold does.
- 03
What it talks to
Integrations are where estimates go wrong. A standalone app is predictable; one wired into a decade-old ERP is not.
- 04
When it ships
A hard deadline means more people working in parallel. That is the single most expensive constraint you can add.
Always included
In every numberon this page.
Not upsells. If a quote from us does not include these, it is not a quote from us.
- A written scope before anything is built
- Design and build in two-week cycles, with a working link at the end of each
- Source code, credentials and infrastructure in your name from day one
- Documentation written for your team, not for us
- Thirty days of post-launch support
- No mandatory retainer afterwards
Questions
Before you ask.
How accurate is this range?
Four questions cannot produce a quote, and we would rather say so than pretend. Treat it as the bracket we would work within — enough to know whether to keep talking. Our written scope after a call is typically within 15% of the final number.
Do you charge for scoping?
No. The scoping call and the written scope that follows are free, and yours to keep whether or not you hire us. If you take that document to another agency, that is a fair outcome.
Why is hardware so much more expensive?
Because physical iteration has a cost software does not. Every board revision is a fabrication run and a lead time. We front-load that risk with careful design review, but it is genuinely more work than a web build.
Can you work to a fixed price?
For well-defined scopes, yes. For anything exploratory we prefer time-and-materials with a cap, because a fixed price on an unclear scope just means padding it — you pay for our uncertainty.
What if my budget is below the range?
Tell us anyway. Often the honest answer is a smaller first phase that proves the idea, and sometimes it is that we are the wrong team for it. We will say which.
Do you work with clients outside Pakistan?
Most of our work is international — North America, Europe and the Gulf. We overlap several hours with both European and US-Eastern working days and run everything in English.
Next step
Bring us the numberand we will scope it properly.
Thirty minutes with the people who would build it. You leave with a written scope, free either way.