Ask three developers to quote for "a website" and you'll often get three documents that are hard to compare: a single price on one page, a long feature list with no timeline, and a detailed plan that costs more than the others. Choosing on price alone is tempting. It's also the most common way projects go wrong.
This guide shows you how to read a website development proposal properly: what it should contain, which questions reveal the real differences, who ends up owning the work, and how to compare offers on a fair scorecard.
What a complete proposal includes
A good proposal answers four questions: what you'll get, how it will be built, when it will be ready, and what happens after launch. Check for each of these:
Scope
- The pages or templates included, and the number of products if it's an online store
- Features, named specifically: contact forms, booking, payments, logins, integrations
- Who provides the content (text, images, product data), and whether writing or photography is included
- How many design revision rounds are included, and what counts as a revision
Approach
- The platform or technology, and why it suits your needs
- Whether the design is custom or based on a ready-made theme
- How the site will be tested: devices, browsers, forms, payments, speed
Timeline
- Milestones (design approval, development, testing, launch) with dates or durations
- What the timeline depends on from your side, such as content and feedback within a set number of days
Commercials
- An itemised price, with GST stated as included or extra
- The payment schedule, tied to milestones rather than paid entirely upfront
- What's excluded, and the rate for extra work
After launch
- How long support or bug-fixing is included
- Maintenance options and what they cover
- The handover: logins, documentation, training
If a proposal is silent on any of these, ask. The answer, or the lack of one, tells you a lot.
Who owns the website when it's finished?
This is the question most people skip, and the one that matters most when you change providers later.
Under India's Copyright Act, 1957, the author of a work is generally its first owner. There are specific exceptions, such as work made by an employee under a contract of service (Copyright Act, 1957, s.17 (opens in a new tab)). An outside developer or studio isn't your employee, so ownership of the code and design generally transfers to you only through an assignment. An assignment is valid only if it's in writing and signed, and it should identify the work, the rights assigned, and the duration and territory. If the duration isn't stated, the law presumes five years (Copyright Act, 1957, s.19 (opens in a new tab)).
In practice, look for a clause stating that ownership of the website's code, design and content passes to you, for example on full payment. Make sure your domain, hosting and other accounts are registered in your business's name. Webnetic's own terms, for instance, state that all website content and code developed for the client become the client's property once full payment is received.
This is general information, not legal advice. For significant projects, have a lawyer review the contract.
Freelancer, agency or founder-led studio?
Each can deliver excellent work. The differences are in who does the work, how it's managed, and what happens when something goes wrong.
| Freelancer | Larger agency | Founder-led studio | |
|---|---|---|---|
| Who builds it | One person | A team, often split by role | The founder, sometimes with specialists |
| Your main contact | The developer | An account or project manager | The person building your site |
| Process | Varies by person | Formal and documented | Structured but direct |
| Capacity | Limited; depends on one person | High; can run several workstreams | Focused; a limited number of projects at a time |
| Cost structure | Lean | Includes management overheads | Senior-level work without agency overheads |
| Continuity risk | Higher if the person moves on | Lower, though staff can change | Depends on documentation and ownership |
Whichever you choose, ask: Who exactly will work on my project? What happens if they're unavailable? Will I receive documentation and all the logins at handover?
Questions that reveal the real differences
Ask every provider the same questions, and compare the answers side by side:
- Can I see two or three live websites you've built that I can test on my phone? Screenshots aren't enough.
- What's included in each line of your quote, and what isn't?
- Which parts depend on me, and what happens to the timeline if I'm late?
- How do you handle requests that fall outside the agreed scope?
- How will the site be optimised for speed and search, and how will you check it?
- What exactly do I receive at handover? Code, logins, documentation, training.
- What support is included after launch, and for how long?
- If we part ways in two years, what do I take with me?
Specific answers are a good sign. Vague ones ("we'll handle everything") deserve a follow-up.
Is the timeline realistic?
A credible timeline:
- breaks the project into stages, with design approval before development starts
- includes time for your review and feedback, not only the developer's work
- allows time for testing before launch
- states its assumptions, such as "content supplied before development begins"
Be cautious about timelines that promise a complex site very quickly without listing what they depend on. Delays usually come from unclear scope and late content, so a proposal that addresses both is more realistic than one that simply quotes a short time.
Red flags
- A single price with no breakdown of what's included
- No mention of revisions, testing or post-launch support
- The domain or hosting registered in the developer's name, not yours
- Full payment demanded upfront
- No clear answer on who owns the code and design
- No live work you can check, or reluctance to share references
- "Unlimited" pages or revisions with no definition
A simple scorecard for comparing proposals
Before you read the proposals, decide what matters most to you and give each area a weight. Then score each proposal out of 5 in each area and multiply. The weights below are an example; adjust them to your priorities.
| Area | Example weight | What a 5 looks like |
|---|---|---|
| Clarity of scope | 25% | Every page, feature and exclusion listed |
| Relevant live work | 20% | Comparable sites you can test |
| Process and timeline | 15% | Clear stages, dependencies and testing |
| Ownership and handover | 15% | Written transfer; accounts in your name |
| Support after launch | 10% | Defined period and maintenance options |
| Price and payment terms | 15% | Itemised, GST stated, milestone payments |
How to use it: a proposal that scores 4 on scope (× 25% = 1.0), 5 on live work (1.0), 3 on process (0.45), 5 on ownership (0.75), 4 on support (0.4) and 3 on price (0.45) totals 4.05 out of 5. Compare the totals, then read the comments behind them. The cheapest proposal often scores lower once scope and ownership are counted.
For online stores, our ecommerce cost guide explains how to compare running costs, not just build prices.
What we include in ours
At Webnetic, our proposals:
- list the scope and what's excluded
- give a fixed price
- set out a staged timeline
- explain what happens after launch
Work starts with a 25% advance, two rounds of revisions are included unless agreed otherwise, and ownership of the code and content passes to you on full payment, as set out in our terms and conditions. Explore our website development services or our website maintenance services for support after launch.
Frequently asked questions
Should I always choose the cheapest website quote? Not on price alone. Compare scope, ownership, support and process too. A lower quote that excludes content, testing or support can cost more by the end of the first year.
Who owns my website's code if I hire a developer? Under the Copyright Act, 1957, the author is generally the first owner, and an assignment must be in writing. Make sure your contract states that ownership passes to you, and that your domain and accounts are in your name.
How many design revisions are normal? It varies by provider. What matters is that the number is stated and defined. "Unlimited revisions" without limits often leads to disagreements later.
Is it safer to hire an agency than a freelancer? Not automatically. Ask who will do the work, how the project is managed, and what you receive at handover. Documentation and ownership protect you more than the size of the provider.
What payment schedule is reasonable? An advance to start, then payments tied to milestones such as design approval and launch, is common and protects both sides. Be wary of paying everything upfront.
Want a proposal you can compare easily?
Tell us about your business and what your website needs to do. We'll send a clear, itemised proposal: scope, timeline, price and handover, all in writing.
Request a proposal · Explore our website development services
