Gravity Group Logo

Website development proposal: example and 12 questions

Filip Ivanović

November 16, 2026

Filip Ivanović/Software Engineer

A website development proposal should clearly connect the price to the scope of work: the pages and functions provided, who prepares content, when the project starts and what you receive at handover. Comparing two proposals requires more than checking the final amount. You need to establish whether they cover the same work and which costs remain after launch.

For example, one proposal may include writing copy, entering content and a CMS for future editing. Another may assume you will supply every item ready for publication. If that difference is unclear before acceptance, comparing prices will not show how much of your own time you will need to invest in the project.

This guide provides a sample project brief, 12 questions for your developer and handover checks. It is intended for small businesses and sole traders who need a business website to present services and receive enquiries. A webshop with payments, inventory and business integrations needs additional scoping and its own assessment of the work involved.

What should a good proposal include?

A good proposal helps you understand what you are ordering before work begins. It should describe the project outcome, price and payment arrangements, timetable, responsibilities and the process for additional requests. It does not need technical vocabulary that nobody will use during the collaboration. It does need enough detail for both parties to check whether the agreed work is complete.

Instead of an item labelled "modern website development", a description of the homepage, services page, business information and contact page with a form is more useful. If individual services need their own pages, specify how many and who prepares their content. Photographs, additional languages, a blog and integrations should also have a defined scope.

The proposal should distinguish what is included, what can be added and what you pay another provider. A domain requiring registration or renewal is one example. A paid service you want connected to the website is another. If an item is still unknown, recording what needs checking is more helpful than implying that everything is already included in the quoted price.

A sample project brief to send to a developer

You do not need a technical specification for your first enquiry. A short description of your business, visitors and the action you want them to take is enough to start. The following example is fictional and is intended to help prepare an enquiry. It is not an actual Gravity Group proposal and does not determine your project's price or terms.

Item
Business
Sample project brief
Garden maintenance business serving Zagreb and nearby areas
Item
Website goal
Sample project brief
Receive relevant enquiries for regular and one-off maintenance
Item
Visitors
Sample project brief
Private homeowners and smaller commercial buildings
Item
Pages
Sample project brief
Home, services, about the business, gallery and contact
Item
Contact
Sample project brief
A form covering service type, location and a description of the request
Item
Content
Sample project brief
A logo exists; copy needs preparing and photographs need selecting
Item
Editing
Sample project brief
The owner wants to change copy and add photographs independently
Item
Existing website
Sample project brief
A domain exists; access and business email need checking
Item
Special requirements
Sample project brief
Croatian initially; an English version may be considered later
Item
Preferred timing
Sample project brief
Agree on the start, proposal review and public launch date

You can copy this outline and replace the entries with your own information. If you do not know an answer, say that you need a recommendation. That is more useful than choosing a function in advance that you may never use. For an initial assessment, identify the main action you want visitors to take: enquire, call, book an appointment or order a product.

Add a few example websites and briefly explain what you like about each. One may present services clearly, another may have a straightforward form, while a third may show completed projects well. These examples provide direction for discussion. Another business's copy, photographs and design should not be treated as ready-made content for your own website project.

12 questions before accepting a proposal

1. Exactly which pages and functions will I receive?

Ask for a list of pages and their main functions. "Five pages" may mean five straightforward layouts, or it may include a gallery, filtering and a specialised form. The number alone therefore does not provide enough information. Describe what each page displays and what a visitor should be able to do when they arrive there.

If you need bookings, customer sign-in, search, a catalogue or several forms, mention them at the start. Distinguish a contact form from a system that checks available appointments and confirms a booking. Before accepting, check whether those requirements are included in the agreed price or assessed separately. For basic package comparisons, see our website development offering.

2. Who prepares copy, photographs and other content?

Ask whether the proposal covers entering supplied material or preparing content as well. This affects your workload, the schedule and the final appearance of the site. Also agree on who checks service information, prices, contact details and claims before publication. A developer can prepare the wording, but you need to confirm that it accurately describes your business and what customers can expect.

At Gravity Group, we prepare the structure, copy and suitable photographs and visuals if you have no planned content, within the agreed project scope. Dedicated photography of premises, people or products should be specified separately where required. Selecting a suitable existing photograph and organising a photography session are different items and should be described accordingly in the proposal.

3. Can I edit the website myself through a CMS?

A CMS is a content management system. It allows you to edit the parts of the website designed for that purpose, such as copy, photographs and articles. Ask which content you can change, how you receive access and whether someone will demonstrate the process. The phrase "CMS included" alone does not describe how independently you can manage everyday updates.

Our websites allow you to edit content through a CMS. Content editing should be distinguished from developing a new function or changing an entire page layout. Updating a service description may be a routine content change, while adding a booking system requires separate development. During scoping, explain which changes you expect to make most often and who will be responsible for them.

4. What does design include, and how do we agree on revisions?

Check whether the design is prepared for your business, what you will receive for review and how you should submit comments. It helps to nominate one person to gather feedback. If several colleagues send conflicting instructions, decisions about copy, structure and appearance can remain unresolved even after several reviews and create uncertainty about which version has actually been approved.

Ask how revisions within an agreed direction are distinguished from new requests. Rewording a heading and adding a completely new page involve different amounts of work. The number of review rounds, the approval process and how previously accepted decisions are handled should be agreed in your proposal. Do not assume unlimited revisions unless the document explicitly provides for them.

5. When does the timeline start, and what counts as completion?

Ask for a clear start point and the conditions needed before work begins. These may include accepting the scope, paying a deposit, completing an information form and providing domain access. Also agree on the difference between a version ready for review and a publicly launched website. Final publication may depend on your approval of the content and the availability of the necessary access.

For website projects up to €500, Gravity Group's timeline is 5 working days, subject to the agreed prerequisites. A webshop usually takes around 10 days, depending on complexity, and is assessed separately. Larger projects and integrations are also assessed according to scope. Our guide to how long website development takes explains preparation in more detail.

6. Are hosting, the domain and business email the same item?

These are separate services and should be clearly distinguished in the proposal. A domain is the site's address, hosting enables the website to run, and business email has its own configuration and terms. If you already use email on your domain, tell the developer before settings change. The launch plan should check whether publication affects that existing email service.

Hosting is free with Gravity Group. This does not automatically include domain registration and renewal or every external application. Ask who manages the domain, whose name it is registered under and where access is held. As the business owner, you should understand how you could continue working with another provider if you need to do so in the future.

7. What exactly does SEO mean in this proposal?

Ask for a list of tasks rather than a general promise of "SEO optimisation". These might include page structure, headings, meta descriptions, links, image preparation and checks that search engines can access the site. Ask whether keyword research, additional articles and subsequent monitoring are included. Initial website preparation and ongoing content work are different services and should have separate descriptions where appropriate.

No provider can responsibly promise first place on Google for every query. Google's guidance on choosing an SEO provider warns about guarantees of first position. A proposal should therefore identify concrete tasks and how the work will be assessed. A clearly described deliverable is more useful than an unverifiable promise about future search positions.

8. Can we track visits and genuine enquiries?

Ask what will be measured and how you will access the information. Viewing a page, clicking a telephone number and successfully submitting a form are different actions. If your objective is enquiries, check whether successful submission can be recorded and whether the information reaches the agreed address. A visit to the contact page alone does not confirm that someone has contacted you.

If you need analytics, advertising or CRM connections, identify the systems and expected actions. Agree on who creates the accounts, grants access and checks test results. Measurement needs to work with your website's consent and privacy settings. Installing a tracking tag and analysing the quality of received enquiries also involve different responsibilities, which should be clear before the work is accepted.

9. What is the price, and how are additional costs approved?

Check the final amount, charging method, VAT treatment stated in the proposal, deposit and balance arrangements. If an item is priced separately, ask why and when its cost will be known. For basic packages, compare the same scope. For requirements that are not yet defined, agree on a clear assessment process rather than assuming an unspecified allowance covers every possibility.

A useful arrangement is to describe and estimate an additional request before approving it for implementation. Examples include deciding to add an English version, a new gallery or a connection to an external application. Such changes may affect the timetable as well as the price. Written confirmation of scope helps both parties avoid discovering different expectations at the end of the project.

10. Is maintenance compulsory, and what does it cover?

Ask how content editing, technical support and future additions are distinguished. An owner who changes photographs through the CMS may not need the same service as a business wanting regular help with technical changes. The proposal should explain what you can do independently, when to contact the developer and how additional work is assessed and approved.

At Gravity Group, maintenance costs €50 per month and is optional. We agree on the support scope without assuming that the monthly amount includes every new function or unlimited changes. Free hosting and CMS access do not depend on purchasing maintenance. Our website maintenance guide explains the distinction between these services and their responsibilities in more detail.

11. Which access details and instructions will I receive?

Handover should provide the access required for your agreed way of using the website. This may include the CMS, domain and external service accounts you manage. Ask which accounts belong to you, how you change collaborator permissions and who to contact if you need new access. Passwords and sensitive information should be shared through an agreed secure channel.

Agree on brief instructions or a demonstration of the most frequent updates. Ideally, change a piece of copy or a photograph yourself during handover. If the website includes custom-developed code or external licences, usage terms, source-code access and transfer options should be described explicitly. Do not infer those terms simply from the fact that you have paid for the website.

12. How do we check delivery, and what happens after launch?

Before acceptance, agree on checks related to the proposal's scope. For a straightforward business site, these may include the agreed pages, contact information, mobile layout, links and form. Analytics and integrations should also be checked if included. Each test needs an expected result, rather than ending with a general statement that the website looks good on the reviewer's screen.

Record where to report a problem after launch and how a correction to an agreed function differs from a new request. For example, a form that does not deliver its message needs checking against the accepted function, while an additional CRM connection may be new scope. Check response arrangements and support terms in the actual proposal rather than relying on assumptions.

How do you compare two proposals for the same website?

Place them side by side and turn unclear items into questions. Do not automatically assume a more expensive proposal includes more or that a cheaper one is incomplete. Compare the deliverables, your responsibilities and subsequent costs. The following table helps review the relevant items without relying on invented market prices or suggesting that one price level suits every business.

Area
Scope
What to check in each proposal
The same number and type of pages, languages and functions
Area
Content
What to check in each proposal
Copy and image preparation or only entering supplied material
Area
CMS
What to check in each proposal
What you can edit and which instructions you receive
Area
Timeline
What to check in each proposal
Starting conditions, design review and final publication
Area
SEO and measurement
What to check in each proposal
Specific tasks, account access and event checks
Area
Costs
What to check in each proposal
Development, domain, external services and future additions
Area
Support
What to check in each proposal
Whether it is optional, its scope and how problems are reported
Area
Handover
What to check in each proposal
Access, demonstration and checks of the agreed delivery

If a proposal does not mention copy or domain renewal, ask for clarification. The absence of an item does not reliably establish whether it is included or excluded. The objective is a sufficiently comparable description to assess overall value and responsibilities. You can then choose the working arrangement that fits your business and the amount of involvement you want.

An example of comparing more than the final amount

Imagine two proposals for a business wanting to present its services and receive enquiries. The first expects the owner to supply finished copy, prepared photographs and the final content structure. The second describes preparing those materials as part of the project. If the owner has no time to write, that is a meaningful business difference even when both proposals list the same number of pages. Establish how much preparation the developer handles, what remains your responsibility and how final content is approved. This is a hypothetical example, not a description of two actual market proposals.

Next, consider what happens after launch. One proposal may expect you to send every change to the developer, while another enables independent editing through a CMS. Assess either approach against your needs. If you update content frequently, request an editing demonstration. If you prefer someone else to do it, ask how support is arranged. Include changes you expect over the next few months, such as adding a service or a new project photograph. This helps you select a workable arrangement and understand additional costs before the first update feels like an unexpected new order.

What should you check before final handover?

Prepare one realistic visitor scenario. Open the website on a phone, find a service, check the contact details and submit a test enquiry using fictional test information. Then establish whether the enquiry reached the person responsible for processing it and whether the message clearly explains what the visitor needs. This checks the complete process rather than the appearance of the form alone.

Check
Content and contacts
Example of an expected result
Accurate business name, services, phone, email and address
Check
Form
Example of an expected result
Successful submission and delivery to the agreed address
Check
Mobile layout
Example of an expected result
Readable copy and accessible main buttons
Check
Links
Example of an expected result
Agreed pages open at the correct addresses
Check
CMS
Example of an expected result
You can make and save the intended content update
Check
Analytics
Example of an expected result
Agreed actions have been checked with test events
Check
Access
Example of an expected result
You know where to manage the site, domain and connected accounts

Record outstanding items and who will resolve them. If something belongs to a later stage, identify it as a later stage and describe the scope. Public launch should not silently become acceptance of a function that has not yet been developed. A well-run handover makes the website easier to operate and gives later support discussions a clear starting point.

How do we prepare a proposal at Gravity Group?

Start by describing your business, intended outcome and whether you need a new website or changes to an existing one. We then define pages, functions, content and responsibilities. After you pay the deposit, we send you a short form to complete so we can gather the necessary information and materials. This brings the essentials together and makes it easier to confirm what we are preparing for publication.

If you do not have prepared copy and photographs, we handle their preparation within the agreed scope. You confirm the actual business information and approve content before publication. Answering customers' questions clearly matters more than increasing the amount of text alone. Google's helpful content guidance likewise emphasises content that serves people and their needs.

For websites up to €500, the timeline is 5 working days with the prerequisites confirmed, hosting is free and you can edit content through the CMS. Maintenance is optional at €50 per month. Special functions and larger projects are scoped before the price and schedule are confirmed, so the proposal does not depend on unstated assumptions about what will be delivered.

Frequently asked questions

What should a website development proposal include?

The proposal should describe pages and functions, content preparation, CMS, pricing and payment, timing and prerequisites, external costs, support and handover. It should distinguish included work from possible additions. This helps you check whether two proposals cover the same scope and how much preparation you will need to handle yourself before development can proceed.

Can I get a proposal without copy or photographs?

Yes. Explain what you already have and where you need help. Gravity Group prepares the structure, copy and suitable visuals within the agreed scope. After you pay the deposit, we send a short form to gather the information required. Dedicated photography and specialised materials are arranged according to project requirements and should be described separately where needed.

How long does website development take at Gravity Group?

For websites up to €500, the timeline is 5 working days, subject to agreed prerequisites. We confirm the start and final publication arrangements within the project. A webshop usually takes around 10 days, depending on complexity. Larger projects and special integrations are assessed separately according to the scope of the work required.

Do I have to purchase maintenance to use the website?

No. Gravity Group maintenance costs €50 per month and is optional. Hosting is free, and you can edit content independently through the CMS. Technical support arrangements and possible future additions are agreed separately from everyday editing of copy and photographs. The maintenance subscription should not be confused with the ability to access and use the website.

Is choosing the cheapest proposal enough?

First establish whether you are comparing the same scope. Compare pages, functions, content, CMS, timelines, access, support and later costs. A lower price may suit a simpler project, but does not by itself explain how much work is included. Ask for clarification of unclear items before accepting and deciding which proposal best suits your business.

Send a project description for a clearer proposal

To begin, explain what your business does, what the website should achieve and whether you already have a site, domain or materials. Add the functions you need and your preferred timing. If some decisions are still open, we can clarify the scope together before confirming implementation, rather than asking you to prepare every technical detail on your own.

Send us a website development enquiry and mention whether you need help with content. Using your requirements, we can prepare a proposal with pricing, timing and responsibilities that are understandable before work starts.

06Newsletter

Free tips to grow your business

Practical tips for tradespeople and small businesses - how to get a website, attract clients, and more. No spam.