The largest risk in custom software is rarely the hourly rate. It is ambiguity about workflow, scope, ownership, acceptance, security, integration behaviour and support.

1. Procure an operating outcome

Describe the actors, decisions, records and exceptions that must improve. A feature list without a workflow model invites inconsistent assumptions.

2. Require scope boundaries

Ask what is excluded, which systems are authoritative, which data must migrate and which external dependencies can block delivery.

3. Evaluate architecture evidence

The proposal should explain identity, permissions, integration boundaries, environments, backup, recovery and the expected growth path.

4. Define acceptance before build

Each critical workflow needs observable acceptance criteria, including invalid input, permissions, retries and reporting.

5. Clarify ownership and exit

Contract terms should address source code, credentials, infrastructure, data export, documentation and handover support.
Core takeaway
A comparable proposal makes assumptions and evidence visible—not merely the total price.

Next step

Use the checklist in a discovery session with operations, finance, compliance and the technical team. Record disagreements as risks before they become production exceptions.