You do not need to know every technical term to choose a provider. You need to understand what you are ordering, who is responsible and how the work will proceed. Proposals become easier to compare when they describe a similar scope.
What the proposal includes
The page count is a starting point. Ask about content, design, features, checks and launch too. Find out who prepares copy and photography and what needs to be ready before development. A design without real content may need more work later.
- Which pages and features are included in the price?
- Who prepares the assets and approves them?
- When will you see the design and give feedback?
Who works on the website
Working directly with one person and working with a larger team involve different communication. Neither is automatically better. Ask about responsibilities, your contact person and how decisions pass from design into development.
What remains after launch
- Who manages the domain, hosting and access?
- How will you change the content?
- What does handover and documentation include?
- How are further changes priced, and who handles maintenance?
The answers should make sense without a technical dictionary. If you mainly need new content or a repair to one part, you do not necessarily need a whole new website. Agreement on the problem matters more than the size of the proposal.
Before work begins, confirm the scope, price, timeline and approval process. That reduces ambiguity and gives both sides the same understanding of when the project is finished.
First published .