David Tovar · Practical guide
Describe the work the application should support
You do not need to design every screen before requesting a quote. It does help to explain who will use the application, what they do today and what the software should enable them to do. For example, “we need to organise pending services and assign them to an available person” is more useful than “we want a modern dashboard”.
Include the tools your business uses and where information is stored. A fictional spreadsheet or a process sketch can help explain the rules without sharing confidential data.
Prepare a list of priorities
Separate what is essential for launch from improvements that could come later. Describe users and permissions, main operations, integrations and any data that needs to be migrated. If a particular date matters, explain why: it may affect the order of delivery.
This makes it possible to assess a useful first version. It also prevents providers from quoting for different interpretations of the project.
What a proposal should explain
Look for a description of the features and the tests used to accept them. Check which documentation you will receive, how the application will be put into use and what your team is expected to contribute. Repository access, licences, usage rights and maintenance should be covered by the applicable terms.
Read the price alongside those deliverables. Compare recurring hosting and external-service costs, and how later changes will be estimated.
When further investigation is needed
A poorly documented integration, legacy application or data migration may prevent a reliable estimate. In those cases, establish what needs investigation and what that investigation will deliver. Not every project requires a separate analysis stage.
The first conversation should end with a clear next step: preparing a proposal, providing missing information or investigating a specific technical uncertainty.
Discuss your project
I’m David Tovar. If you want to apply these ideas in your business, we can review your requirements and the options for developing a solution.