Custom software pricing depends on agreed functionality and acceptance criteria. The same customer-management screen can require different permissions, approvals, migration and integrations. Start by defining one essential workflow and how you will check that it works.
[01]What changes the scope of a quote?
| Item | What to clarify |
|---|---|
| Business rules | Pricing, discounts, approvals, exceptions and user permissions |
| Integrations | Providers, API availability, plan restrictions and retry handling |
| Migration | Source formats, duplicate and missing records, validation and cutover |
| Quality and release | Acceptance scenarios, supported environments, security, performance and release ownership |
| Operations | Hosting, subscriptions, usage charges, backups and support scope |
[02]How do you make a request specific?
Instead of asking for a CRM, describe a workflow: a salesperson registers a customer and drafts a quote; a manager approves exceptional discounts before it is sent. Add an existing quote template, user roles and current tools. This is an illustrative scope example, not a customer result or a price estimate.
- Included: customer records, quote creation, approval history and an agreed export format.
- Clarify separately: e-signatures, accounting integration, migration and additional reports.
- Acceptance: validate agreed quote calculations and access rules for each role.
[03]How do you compare proposals?
Give each provider the same workflow and materials, then compare included features, exclusions, acceptance and deliverables. A lower total may leave out migration, deployment or support. Clarify applicable tax and external service charges separately.
[04]Project or subscription?
Consider a project when scope and acceptance can be defined. Compare subscription options when requests continue after launch and priorities change. A subscription does not mean unlimited work: agree on monthly scope, request handling and treatment of unfinished tasks.
[05]What should you bring to a consultation?
- The first workflow to improve, with examples of inputs and outputs.
- Current tools, data locations and intended integrations.
- Your target release date, budget range and acceptance owner.
- Mark unknowns as undecided and discuss them during the consultation.
- Software costs
- Comparing proposals




