Pricing
A quote based on the work your product needs.
Choose an engineering review, a defined build, or ongoing support. We discuss the scope before quoting a fee or delivery schedule.
The ladder
Three ways in
Start here
Build Audit
Scoped quote
Review scope agreed first
Understand an inherited or stalled build before committing to the next phase.
- Codebase and architecture review
- Prioritised findings
- Repair or rebuild options
- Review of the proposed next steps
Product Build
Project quote
Based on requirements and dependencies
Build a product or a defined part of one, with the deliverables and milestones agreed together.
- Product and technical scope
- Implementation milestones
- Testing and deployment plan
- Handover requirements
Ongoing Engineering
Custom scope
Capacity and cadence agreed together
Get engineering support for an existing product and an evolving roadmap.
- Prioritised backlog
- Agreed engineering capacity
- Progress reviews
- Support and ownership boundaries
Fees, payment stages, and delivery dates are confirmed in your proposal.
Disqualifiers
Choose the right kind of help
The shape of the problem matters as much as the technology.
- A permanent role may suit work that needs continuing ownership inside your company.
- A small, well-defined task may be a good fit for an individual specialist.
- An unclear codebase benefits from a review before a large build commitment.
- A new product needs a clear user problem and priorities before a delivery estimate can be useful.
Billing
What your proposal should settle
These details are agreed in the proposal before work starts.
- Scope
- Deliverables, exclusions, and assumptions
- Price
- The fee and currency for the agreed work
- Schedule
- Milestones, dependencies, and availability
- Billing
- Payment stages and any agreed expenses
- Changes
- How changes to scope, fees, or timing are agreed
- Handover
- Access, documentation, and support requirements
Before you commit
Decide with the scope in front of you
A website cannot price an unfamiliar codebase accurately. Share the product, the blocked work, and your constraints so we can determine what needs reviewing.
Any payment, cancellation, support, or ownership terms belong in the written proposal and engagement agreement. Review those terms before proceeding.
FAQ
Pricing questions
Can you quote before seeing the code?
An initial conversation can establish fit. A reliable estimate for existing software may also require an agreed review of its architecture, dependencies, and current behavior.
Is the initial inquiry a paid commitment?
No. Sending an inquiry asks us to discuss your project. It does not purchase an audit or start an engagement.
How are changes handled?
The proposal should identify how new requirements affect the scope, cost, and schedule. Ask for any change to be recorded before it is implemented.
What determines the cost?
The current codebase, required behavior, integrations, data migration, testing, and handover needs all affect the work. Include any fixed budget or deadline in your inquiry.