Separate the client outcome from the requested solution
Begin with what the client needs to achieve. A request for an app may actually be a need to give customers easier access to information. A dashboard may be a response to inconsistent reporting. Understanding the outcome allows the team to recommend the right scope rather than price an assumption.
Map the central workflow
Document the event that starts the process, the users involved, the information captured, the decisions made and the result that ends the journey. Include important exceptions, but avoid attempting to specify every future possibility before the main process is clear.
Where several departments or client stakeholders disagree, treat alignment as discovery work rather than expecting development to resolve it later.
Confirm users, roles and access
Permissions can materially affect design and effort. Clarify whether the solution serves public visitors, client users, managers, administrators or several customer organisations. Ask who can view, create, approve, edit, export and delete information.
Identify the hidden parts of delivery
The visible interface is only one part of a software project. The scope may also include data migration, integrations, hosting, backups, notifications, document generation, audit history, security controls, testing, deployment, training and post-launch support.
These responsibilities should appear in the estimate or be explicitly excluded. If they remain implied, the agency and development partner may price different projects while using the same feature list.
Ask for the evidence behind integrations
Do not assume that an existing product can be connected because the client uses it. Confirm whether an API exists, whether access is included in the client’s subscription and whether technical documentation or a test environment is available.
When an integration cannot be verified before quoting, state the assumption and describe how a discovery stage or change process will handle it.
Agree how the partnership will operate
- Who owns the client relationship and leads meetings?
- Will the development partner be visible, introduced as part of the team or remain entirely behind the scenes?
- Who collects feedback and confirms decisions?
- Who provides design, content, testing and acceptance?
- Whose environments, accounts and repositories will be used?
- Who provides support after launch?
These are delivery questions, not administrative details. Unclear ownership creates delays and can make the client feel that no one is accountable.
Choose the right quoting method
A fixed quote is most credible when the central workflows, responsibilities, dependencies and acceptance conditions are understood. Where important uncertainty remains, the agency can quote a paid discovery stage, provide a range based on stated assumptions or divide delivery into separately approved phases.
Contingency should cover normal delivery risk. It should not be used to hide a requirement that has not been investigated.
Write assumptions and exclusions in plain language
A proposal should state what has been priced and the conditions on which that price depends. Typical assumptions concern the number of user roles, quality of supplied data, availability of third-party services, volume of content and speed of client feedback.
Clear exclusions are equally important. If copywriting, visual identity, data cleansing, licensing or ongoing hosting is outside the quote, say so before approval.
Frequently asked questions
Can an agency request technical input before winning the project?
Yes. The agency and partner should agree how much presales investigation is appropriate and when deeper discovery becomes paid work.
Should the client know that development is outsourced?
That depends on the agency’s model and the agreed relationship. What matters is that confidentiality, communication and responsibility are clear between the partners.
Who should own the code and hosting?
Ownership and access should be agreed for each engagement. The client or agency should understand where the code, data, domains and service accounts reside, and what handover would require.
Nuvise works behind the scenes with agencies to investigate, scope, build and support software while respecting the agency’s client relationship.
