Commercially clear from the start.
OpsForm is a UK custom software business based in Brighton. Custom software is scoped around the workflow and risk involved. These figures help establish likely investment before discovery.
Discovery & solution planning
Requirements, workflow mapping and a practical technical/delivery plan. For qualifying new-build projects, paid discovery is credited in full against the agreed build when you proceed with OpsForm.
Starter MVP
A focused first release built around the highest-value workflow, with enough foundation to operate reliably and extend later.
Support & improvement
Lightweight ongoing maintenance arrangements can be agreed around the live system and required response level.
| Service | Indicative price | Typical fit |
|---|---|---|
| Ad-hoc development / changes | £36/hour | Small changes, investigation and support |
| Half-day development | £130 | Up to 3.5 hours focused development |
| Full development day | £255 | Up to 7 hours focused development |
| Discovery & solution planning | From £235 | Requirements, workflow mapping and technical plan; credited against qualifying builds when you proceed |
| Minimum fixed-price project | From £760 | A tightly scoped first phase with a clear outcome |
| Prototype / proof of concept | £760–£1,600 | Validate one workflow, rule set or product idea before a wider build |
| Starter MVP | £2,500 | Core journey, database, user access and practical administration |
| Larger custom business system | From £4,000 | Multiple workflows, roles, reporting and operational rules, usually phased |
All prices are indicative launch rates. Final pricing depends on agreed scope. OpsForm is not VAT registered. Third-party subscriptions, infrastructure and pass-through provider charges are separate unless expressly included.
The number of screens is rarely the main factor.
Business rules
Complex pricing, eligibility, approval and exception logic takes more care to model and test.
Integrations
Payments, messaging and external APIs introduce provider dependencies, authentication and failure cases.
Roles & permissions
Customer, staff, manager and administrator experiences can each require distinct access rules and actions.
Data migration
Cleaning and importing historic spreadsheets or legacy-system data can be a project in itself.
Operational risk
Systems handling money, compliance or time-critical work need stronger safeguards and testing.
Launch requirements
Hosting, environments, domain setup, monitoring and production migration affect delivery effort.
Reduce scope before reducing quality.
If the full idea is above budget, the better answer is a smaller first release—not forcing the same workload into a lower price.
How a smaller first phase works
- Choose one high-value workflow or bottleneck
- Keep the minimum roles, records and rules needed to operate it
- Move nice-to-have modules into a later release
- Keep testing, security and maintainability standards intact
- Use real feedback from phase one to decide what deserves investment next
Example: a £1,500 budget should fund a focused £1,500 phase—not a £4,000 system squeezed into the same budget.
Scope first, price second.
A fixed price only works when both sides know what is included. Larger or uncertain work therefore starts with discovery rather than a guess.
Typically included in a build quote
- Agreed features and workflows
- Development and internal testing
- Reasonable review/fix cycle against scope
- Production setup explicitly listed in the proposal
- Handover information agreed for the project
Typically separate unless quoted
- Third-party provider fees
- Paid licences and messaging charges
- Major new scope after approval
- Large data cleansing/migration exercises
- Ongoing support after any included warranty period
Need a firm quote?
Send the workflow, current tools and desired outcome. If the scope is uncertain, discovery is the right first step.