Business software: define a first delivery before requesting a quote

“We need an app to manage everything” expresses a difficulty, but it is not yet enough to compare quotes. Start by choosing one specific workflow and describing what its user must be able to accomplish.

Begin with a working situation

Consider a fictional small business that receives service requests, assigns technicians and wants to track progress. A first delivery could let staff create a request, assign it and view its status. Invoicing and stock management can remain outside that delivery.

The UK government’s service manual describes needs through the user, action and goal, then adds acceptance criteria. This structure focuses discussion on the outcome rather than a list of screens.

Describe the important rules

• Who can create, edit and close a request?
• Which information is required?
• Which statuses exist, and who can change them?
• What happens if a request is entered twice?
• Which data must be imported or exported?

Add working constraints: phone or computer, connection quality and the number of people working together. Offline access must be explicit; it does not follow simply from using a browser-based application.

Prepare three acceptance cases

In our example, a manager creates and assigns a request. The technician sees their assignment and records the intervention. Finally, a person without the required permission cannot close the case. Each case states the expected result.

Use fictional data initially. A paper mock-up or prototype lets people discuss the steps before investing in the full feature set.

Make quotes comparable

Ask for clear inclusions, exclusions, deliverables, data migration, hosting and maintenance arrangements. Agree how new requests during the project will be handled.

The first delivery is ready for pricing when users and the supplier understand the same acceptance cases. Our custom business application service can start with this scoping work.