Pricing
Price the work it takes to make the software useful.
Screens and features are only part of the investment. The estimate should include the rules, integrations, data, testing and rollout the business depends on.
Discuss your project
What the work includes
What shapes the estimate
The delivery scope
The workflows, users, rules, exceptions and acceptance criteria included in the release.
The existing environment
The condition of the software and data, integration constraints and migration work.
The responsibility after launch
Training, handover, hosting responsibilities, support coverage and further development.
Agree a model that fits the work
A defined scope
For work with clear boundaries and acceptance criteria, we can discuss a fixed-price engagement with an agreed approach to changes.
A question that needs investigation
When material unknowns affect the estimate, an initial assessment or discovery can create a sounder basis for the next commitment.
Ongoing development and support
For continuing work, agree capacity, priorities, coverage and review points around the needs of the product.
Questions before we start
Can you estimate from a short brief?
We can discuss the likely scope and identify what is missing. A delivery commitment needs enough detail about dependencies, data, responsibilities and acceptance.
Why not publish a single price per screen?
Similar screens can hide very different rules, integrations and migration needs. A useful estimate explains those differences and what is included.
Bring the problem. Let’s work out the next step.
An idea, a plan, or software that needs to change — tell us where you are and what you want to achieve.