A system name or screen count is not enough for a responsible custom software estimate. Two employee-portal briefs can differ substantially in permissions, data migration, integration and operation. Instead of publishing an unsupported price range, this guide identifies what makes a quote comparable and what can be deferred to narrow the first release.
Describe complexity through decisions and data
Similar fields can carry very different complexity. An amount field may change an approval chain, connect to a cost center and trigger reapproval when edited. Define each process by its start, end, roles and exceptions. Separate work performed inside the system from dependencies on external systems: API access and data quality affect the estimate.
- List processes, request states and accountable owners.
- Define roles for viewing, editing, approval and export.
- Provide non-sensitive sample data with estimated volume and duplication.
- Name integration systems, API owners and available test environments.
Separate implementation from operating costs
Ask for separate lines for discovery, design, implementation, testing, migration and training. Then clarify hosting, licenses, messaging, third-party services, support and updates. Proposals may include or exclude these items; compare the same period and support scope. The word support alone does not define duration, coverage hours or included changes.
- Which costs recur and which are one-time?
- Who owns subscriptions and accounts after handover?
- Which assumptions would change the price?
- How are additions priced after scope approval?
Define a first release that can be accepted
Illustrative scope: start with a purchase request from submission to decision, including a record, permissions and basic status reporting. Defer supplier comparison or accounting integration if the first workflow can operate without them. Do not defer data protection or access controls as cosmetic improvements. Attach acceptance tests to deliverables: an employee cannot see another department's request, an edited request returns to the correct reviewer, and integration failures are visible.
A brief to complete before requesting a quote
Copy the following fields into one document and review it with the process owner and IT. Write unresolved where an answer is unknown: hiding uncertainty does not remove its cost. Ask suppliers to distinguish confirmed scope from conditional items and tie the schedule to agreed deliverables and dependencies.
- Current problem and impact; desired outcome and how it will be measured.
- Users, roles, languages, and required phone/browser use.
- First-release workflows and explicit exclusions.
- Data, integrations, hosting and an owner for each decision.
- Acceptance tests, handover, support and unresolved dependencies.
What makes two quotes incomparable?
| Item | Narrow scope | Broader scope to disclose |
|---|---|---|
| Approvals | A fixed route and one reviewer role | Delegation, escalation and amount-based routing |
| Data | Start with new records | Clean, migrate and reconcile legacy records |
| Integration | Standalone entry | External API, failure monitoring and reconciliation |
| Operation | Defined handover | Hosting, monitoring and updates under an agreement |
The next step
Before pricing, aim for an agreed brief, a defined first release and explicit assumptions. Share these to begin a scope discussion with VANTERA.