Pixuntra
Pricing

No price list. No guesswork either.

Software pricing that ignores your requirements is fiction. Instead of a rate card, here is exactly how we arrive at a number — and what would move it.

Get an estimateSee what drives cost
Engagement models

Three structures. Pick the one that fits the risk.

The right model depends on how well-defined the work is. We will tell you which one suits your project, even when it is the cheaper one.

Fixed-scope project

On request
Quoted after a thirty-minute call.

Best when the requirements are clear and the finish line is real.

We do paid discovery, write the scope, then commit to a price. You carry no risk on estimation error — if we get it wrong, that is ours to absorb.

  • Written scope and fixed price agreed up front
  • Milestone-based payment schedule
  • Change requests quoted before they are built
  • Fixed delivery date
Get a quote
Most chosen

Dedicated team

On request
Quoted after a thirty-minute call.

Best for ongoing product work where the roadmap keeps moving.

Senior engineers embedded with your team at a monthly rate. You direct the backlog; we bring the delivery discipline. Scale up or down each month.

  • Senior engineers embedded in your team
  • Minimum three-month commitment
  • Your tools, your standups, your backlog
  • Adjust team size monthly
Get a quote

MVP sprint

On request
Quoted after a thirty-minute call.

Best for founders validating an idea before raising.

Six to ten weeks from brief to launched product. Ruthless scope discipline — one core loop built properly rather than six built badly.

  • Six to ten weeks, brief to launch
  • One core loop, done well
  • Investor-ready demo and technical narrative
  • Direct path into a longer engagement
Get a quote
What drives cost

Five things move the number.

When you ask why one project costs three times another, it is almost always one of these — not the number of screens.

  1. 01

    Integration surface

    Talking to one well-documented API is cheap. Talking to four systems, two of which are undocumented and one of which is a legacy database nobody owns, is not.

  2. 02

    Data and state complexity

    Offline sync, multi-tenancy, permissions, audit trails and reconciliation are where the real engineering time goes. A pretty interface over simple data is fast.

  3. 03

    Compliance and security requirements

    Handling payments, health data or personal data at scale adds design, testing and documentation work that cannot be shortcut.

  4. 04

    Certainty of the requirements

    A clear brief is cheaper than an evolving one — not because change is bad, but because rework is real. Paid discovery usually costs less than guessing.

  5. 05

    How long it has to last

    A campaign microsite and a platform your business will run on for a decade are different products, even if they look similar in a mockup.

Always included

Things other agencies bill as extras.

These are part of delivery, not a line item you find later.

  • Automated tests and type safety
  • Performance budget and Core Web Vitals pass
  • WCAG 2.2 AA accessibility pass
  • Security review before release
  • Technical documentation and runbooks
  • Handover walkthrough with your team
  • Source code and cloud account ownership
  • Defect support window after launch
Pricing questions

The awkward ones, answered.

Why will you not publish a rate card?
Because the honest answer to 'what does an app cost' is 'what does a building cost'. We would rather spend thirty minutes understanding your project and give you a real number than publish one that is wrong for everybody.
Do you charge for the first call or the estimate?
No. The first call and the written estimate that follows are free. Deep technical discovery — where we produce architecture, a data model and a de-risked plan — is paid, and we tell you before it starts.
What if the project runs over?
On fixed-scope work, overruns against the agreed scope are our cost, not yours. That is the point of fixing the scope. If you add to the scope, that is quoted separately before any work begins.
How do payments work?
Fixed-scope projects are billed against milestones, typically an initial payment then staged releases. Dedicated-team engagements are invoiced monthly in advance. Terms are in the contract before you sign.
Are there ongoing costs after launch?
Third-party costs — hosting, domains, APIs — are billed to your accounts directly, so you see them and control them. Our ongoing maintenance is optional and quoted separately.
Can we start small?
Usually the smartest move. A paid discovery or a small first increment lets both sides find out how the other works before anyone commits to a large number.
Next step

Send us the brief. Get a real number.

Written scope, assumptions and price within a week of our first call — in a document you can compare against any other quote.

Request an estimateBrowse services