Most software companies treat pricing as a negotiation asset. We treat it as a conversation that has to start with the scope, because a number without a scope is a guess dressed up as a commitment.
Why we do not publish a fixed price list
Two projects with the same one-line description routinely differ by a factor of four. A payments integration behind an existing, documented API is not the same job as the same integration into a system nobody has touched since 2016. Publishing a single figure would mean padding every quote to survive the worst case — and you would pay for that padding.
What actually moves the number
- Scope clarity. A written backlog costs less to deliver than a conversation, because nobody is paying for rework.
- Integration count. Every external system adds a protocol, an owner and an unreliability of its own.
- Compliance load. MiCA, MDR, PSD2 and HIPAA add documentation that is real engineering work, not paperwork.
- Seniority mix. A senior engineer costs more per hour and less per delivered feature.
- Operational commitment. A 24×7 SLA is priced separately from building the thing.
How we get to a number
We run a discovery sprint first: stakeholder interviews, a domain model, an architecture sketch and a backlog with three-point estimates. Only then do we quote — as a range, with the assumptions written down next to it. If the assumptions change, you can see exactly which line moved.
What we will not do
We will not quote a firm price from a one-page brief, and we will not discount testing, code review or documentation to make a number look smaller. We will happily reduce scope. Tell us the budget you are working with and we will tell you honestly what fits inside it.



