Ask for a scope you can compare
Two quotes for a website or application can cover very different work. Compare the pages or workflows, user roles, integrations, content responsibility and review milestones. A useful quote says what is included, what is separate and which assumptions affect the price.
Identify the work that adds uncertainty
Clean content and a simple enquiry form are different from a complex product catalogue, online payments or a migration from several old systems. Integrations depend on API access and documentation. Existing data may need cleaning before it can be imported. New user roles and approval exceptions also need design and testing.
Separate build costs from running costs
Domain renewal, hosting, platform licences, payment fees, AI usage and ongoing support may continue after launch. Request a list of recurring costs, who pays each provider, and what happens if usage changes. A maintenance plan should explain its coverage and limits.
Make feedback and changes explicit
The schedule depends on access, approved content and timely decisions as well as development. Nominate one person to consolidate feedback. Ask how new requests are estimated and approved, and what counts as a defect against the signed scope.
- Which deliverables are reviewed at each milestone?
- What is required before work can start?
- How are extra requests priced and approved?
- What tests must pass before delivery is accepted?
- What warranty applies to defects?
- What support is available after the warranty?
Bring enough context to the first conversation
Share the problem, the people affected, a sample workflow, any deadline and a rough budget if you have one. You do not need a technical specification to start. A concrete example of what is not working is more useful than a long list of desired features.
Prepared by Articcus as general project-planning guidance. Your proposal should reflect your own requirements and dependencies.