SOFTWARE PROPOSAL COMPARISON
Horizon Dynamics | Planning worksheet | 5 October 2026
Use the same release boundary and operating period for every supplier.
This worksheet does not contain a quotation or client information.

1. SHARED COMPARISON BASIS
Business process and intended outcome:
First users/team/location:
Included workflows and exceptions:
Existing systems retained:
Data history to migrate:
Operating period after launch (months):
Currency and tax treatment:
Client decision owner:

2. WORKED SCOPE ROW — CUSTOMER IMPORT
Outcome: import customer C-104 and its agreed order history once.
Source rule: use the agreed source identifier; flag uncertain matches.
Business owner: client data owner approves matching and source cleanup.
Supplier work: mapping, import, visible exceptions and reconciliation.
Pricing treatment: state whether covered by a module allowance or separately priced.
Acceptance evidence: import the same sample twice; one customer remains,
with the expected order links and a reviewed exception log.
Open assumption: source quality remains unconfirmed until a sample is reviewed.
Decision: review source sample before committing to a fixed migration scope.

3. COPY THIS ROW FOR EACH WORK ITEM AND EACH SUPPLIER
Supplier:
Work item and intended outcome:
Included / client-owned / separately priced / unresolved:
Responsible person or role:
Source evidence or assumption:
Deliverables and exclusions:
Acceptance scenario and expected result:
Who accepts it:
Amount or range, currency and pricing model:
What changes the price:
Decision needed and owner:

4. CHECK THE SAME WORK AREAS
- Discovery and detailed design
- Shared foundation and selected modules (deduplicate dependencies)
- Source-specific integrations, retries and reconciliation
- Data mapping, cleanup, migration rehearsals and cutover
- Reporting definitions and source checks
- Permissions, agreed security requirements and release validation
- User preparation, documentation, rollout and recovery
- Warranty defect terms (separate from paid support and new work)
- Support coverage, response expectations, team and billing
- Hosting, licences, paid APIs and monitoring ownership

5. COMPARE TOTALS WITHOUT HIDING UNKNOWNS
Build total = included supplier build work + separately priced build work.
Operating total = support + hosting + licences + paid APIs + other agreed
operating charges over the SAME stated period. Separate one-time charges.
State taxes, contingency, client staff effort and any exclusions explicitly.
Do not turn an unresolved item into zero. Do not count a module allowance
and the same implementation task twice. Do not add another multiplier when
a line already contains the full-period operating total.

6. DECISION RECORD
Proposal compared:
Confirmed differences in outcome or responsibility:
Unresolved items preventing a fair comparison:
Evidence needed before commitment:
Decision and next review date:

Complete locally. Share only a non-confidential summary with an enquiry.
https://www.horizon-dynamics.tech/blog/custom-software-development-cost