Pricing and investment guidance

What goes into the cost of custom business software?

The right investment depends on what you need to change, what can stay and how the finished system will be used and supported. These are engagement categories and cost factors, not fixed packages or price quotations.

Discuss my workflow

Ways to scope the work

Three engagement categories

These categories help clarify scope. They do not establish a minimum spend, included feature set or contractual package.

Focused process automation

A defined administrative step, spreadsheet or repetitive workflow needs more consistency or a better handover.

Possible scope

  • One approved form-to-task workflow
  • A limited spreadsheet replacement
  • An existing-system notification or status process

Key discovery question: What triggers it? Who handles exceptions? Which current tool remains the system of record?

Explore the related service

Connected business systems

Several operational spreadsheets, roles or tools need connected records, controlled updates and reporting.

Possible scope

  • Shared job and timesheet records
  • Approved data from multiple workstreams
  • Operational dashboards built from agreed sources

Key discovery question: Which records are authoritative? How will data be cleaned, joined and protected?

Explore the related service

Custom operational platforms

A broader application is required for multiple teams, processes, permission levels and longer-term operation.

Possible scope

  • A service-delivery workspace with assigned roles
  • A tailored field-to-office application
  • A multi-workflow operations and reporting platform

Key discovery question: What is the first usable release? Who owns maintenance, security and future change decisions?

Explore the related service

Cost drivers

What changes the effort and investment?

A small interface can hide complex data or permission rules. A larger-looking form may be straightforward if the process is already well defined.

Workflows and business rules

Number of distinct processes, approvals, exception paths and users involved

Data quality and migration

Duplicate records, spreadsheet formulas, historical imports and reconciliation

Users and access controls

Staff roles, permissions, authentication and privacy needs

Reporting

Metric definitions, filtering, exports and information freshness

Integrations

Current software, supported APIs, vendor permissions and third-party charges

Implementation and training

Prototype reviews, test cases, migration cutover, documentation and handover

Hosting and support

Infrastructure, backups, updates, monitoring and response responsibilities

Future development

Planned changes, ownership decisions and the terms for ongoing work

What a useful proposal should explain

  • The workflows and users included in the first release
  • Explicit exclusions, assumptions and third-party dependencies
  • A practical acceptance and data validation approach
  • Who is responsible for hosting, security and support
  • How training, future changes and exit arrangements are handled

What this page does not promise

There is no fixed price, guaranteed savings figure, promised implementation timeframe, blanket IP ownership term or included support package stated here. These matters must be agreed in the relevant proposal and contract. Keep your current accounting or HR system where practical rather than assuming a replacement is necessary.

Start with the process you need to improve

Use the existing enquiry pathway to tell us which workflows are causing problems. We can discuss the scope and whether a focused improvement, connected system or custom platform is appropriate.

Get my free automation assessment