Web Development Company in Pune: Website Content Readiness — Who Writes the Copy, Who Supplies the Photos, and How to Stop Content Delaying Your Launch
Most website projects that run late are not delayed by code. They are delayed by content: the page text that was promised for week two and arrives in week eight, the photographs that turn out to be 400-pixel WhatsApp forwards, the logo that exists only as a screenshot, and the approval that needs three partners who never see the same draft at the same time. If you are briefing a web development company in Pune, the single most useful thing you can do before the contract is signed is decide who will write, gather and approve every piece of content, and by which date. This guide sets out how to do that in plain steps, with a content inventory you can copy, a realistic schedule, and the questions to ask a developer about content so that the launch date is a real one.
It is written for owners and marketing managers of small and mid-sized businesses, clinics, schools and professional firms who are about to commission a new website or a rebuild, and who have never run a website project before. It does not assume any technical knowledge.
Why Content, Not Code, Usually Decides the Launch Date
A designer and a developer can build page templates in a predictable amount of time because the work is within their control. Content is different, because it sits with you. Someone inside the business has to explain what the company does, choose which services to feature, find photographs, collect testimonials with permission, and confirm that the prices and addresses are correct. All of that competes with the day job.
Three patterns cause most of the delay:
- Nobody owns it. The owner assumes the agency will "write something", the agency assumes the client will send material, and the project stalls at the first handover.
- Content arrives in the wrong shape. Text pasted into a chat message with no headings, product details spread across ten PDFs, or photographs saved at low resolution all need rework before they can go on a page.
- Approval is serial instead of parallel. One person reviews, sends comments, the next person reviews the same page, and each round takes days.
None of these is a technology problem. All three can be settled in a single planning meeting at the start. If you also want to fix the structure of the site before content is written, read our guide to planning your website structure and sitemap first, because you should not write pages you may not need.
Step One: Decide What Each Page Is For Before Anyone Writes It
Content is easiest to write when the page has one job. Before drafting, write one sentence per page in this form: "This page helps [type of visitor] decide to [one action]."
- Home page: helps a first-time visitor understand what we do and choose the right next page.
- Service page: helps a buyer compare our approach and decide to enquire.
- About page: helps a cautious buyer decide whether we are trustworthy.
- Contact page: helps a ready buyer reach us by their preferred method.
If you cannot finish the sentence for a page, the page may not be needed, or it may be two pages trying to be one. Dropping a page at this stage saves far more time than writing and later deleting it.
Match the page to a real search or enquiry
Where a page targets something people search for, say so in the brief. For a service business in Pune, that usually means the service name plus the city or area. Your developer or SEO lead can then check what customers actually type. Our guide to keyword research and search-intent mapping shows how to do this without paid tools.
Step Two: Build a Content Inventory
A content inventory is a simple spreadsheet. One row per page, and for each row these columns:
| Column | What goes in it |
|---|---|
| Page name and web address | e.g. "Dental implants — /services/dental-implants" |
| Purpose sentence | From step one |
| Text owner | One named person, not a team |
| Photos and video needed | List each, with who supplies it |
| Proof elements | Testimonials, certificates, licences, case notes |
| Facts to verify | Prices, timings, addresses, registration numbers |
| Draft due date | A real date |
| Approver | One named person |
| Status | Not started, drafting, in review, approved, published |
The inventory does two jobs. It makes the work visible, and it makes the schedule honest, because it is obvious when forty rows have no owner. Ask your agency to supply a template on day one. If an agency does not use something like this, ask how they track content, because the answer will tell you how they handle the rest of the project.
Separate "needed to launch" from "can follow"
Not every page has to be ready on launch day. Divide the inventory into two groups:
- Launch set: pages that a buyer needs to contact you or trust you. Usually the home page, main service pages, about page, contact page and legal pages.
- Phase two: blog posts, extra location pages, resources, secondary services, gallery expansion.
Launching a clean, complete core site in six weeks is generally better than waiting twelve weeks for a larger site that is half-filled with placeholder text. A page that reads "coming soon" or contains dummy text hurts trust more than a page that does not exist.
Step Three: Decide Who Writes the Copy
There are four realistic options. Each has a cost in money or in time, and you should choose deliberately rather than by default.
Option A: You write, the agency edits
You know the business better than anyone. Write in plain language, in headings and short paragraphs, as if explaining to a customer across a desk. Ask the agency to edit for clarity, structure and search. This costs you time and costs the agency the least. It works best when you are willing to commit a few hours per week and can write.
Option B: The agency interviews you and writes
The agency holds a structured interview of an hour or two per service area, records it with your permission, and drafts pages from it. This is a common arrangement for busy owners. It costs more than Option A but usually reads better and arrives faster. You must still review for accuracy, because the agency cannot know your technical detail.
Option C: A specialist writer, or your in-house marketing team
A medical, legal, financial or engineering business may need a writer who understands the subject. Ask who is accountable for factual accuracy and who will sign it off. For regulated fields, a qualified person inside the business should always approve claims.
Option D: Generated or templated text
Software that drafts text can speed up a first draft, but it does not know your prices, your licences, your service area or your tone, and it can produce plausible-sounding statements that are wrong. If you use it, treat the output as a rough draft from a stranger: every fact must be checked by a person who knows the business, and the text must be edited until it sounds like you. Google's published guidance says it focuses on the helpfulness of content, not on how it was produced; the practical point is that unhelpful or inaccurate pages hurt regardless of origin. See Google Search Central's guidance on generative AI content in the sources below.
Whichever option you choose, write it into the contract: who produces the first draft, how many revision rounds are included, and what happens if content is late (for instance, the launch date moves day for day).
Step Four: Write Copy That Visitors and Search Engines Can Use
You do not need to be a professional writer. These habits cover most of the quality gap.
Lead with the answer. The first paragraph of a service page should say what the service is, who it is for and how to start. A visitor who has arrived from a search wants confirmation that they are in the right place within a few seconds.
Use the words customers use. If customers say "tooth replacement" rather than "prosthodontic rehabilitation", use their words and mention the technical term once. Read your enquiry emails and WhatsApp messages for phrasing.
Be specific. "We deliver quality work on time" says nothing. "We give a written quote within two working days and a fixed completion date" says something that can be checked. Where you cannot back up a claim, leave it out.
Give real numbers only if you can stand behind them. Years in business, number of projects, price ranges and delivery times are all useful, but each must be accurate on the day it is published. Do not copy figures from competitors or from other sites. If a figure is not certain, give a range or leave it for a later update.
Write headings that describe the section. A heading such as "How a typical installation works" is more useful than "Our process". Headings also give search engines a clear outline of the page.
Keep paragraphs short and avoid walls of text on mobile. Most visitors to a local business website arrive on a phone. If a paragraph runs to eight lines on a desktop screen it will run to twenty on a phone.
Step Five: Photographs, Video and Logos
Photography is the second most common cause of delay, and the one that most visibly affects how professional the site looks.
What to supply
- Logo: ask your designer or printer for the original vector file (usually SVG, AI or EPS) and a PNG with a transparent background. A screenshot of a logo cannot be enlarged cleanly.
- Team and premises photographs: real photographs of your people and your premises build more trust than stock images, which visitors tend to recognise. Book a half-day with a photographer rather than relying on phone snaps, where budget allows.
- Product or work photographs: consistent background, lighting and angles matter more than a high-end camera. For online stores, read our guide to preparing product catalogue data, which covers naming, sizes and variants.
- Video: short clips hosted on a video platform and embedded are usually kinder to page speed than large video files uploaded to your own server. Ask the developer how video will be loaded.
Ask for originals, not forwards
Messaging apps compress images heavily. A photograph forwarded on a chat app can lose most of its detail. Share originals through a shared drive folder, a file-transfer link or email, and keep one folder structure that mirrors the site's pages.
Rights and permissions
You need permission to use every image. Stock images need the correct licence. Photographs of identifiable customers, patients, students or beneficiaries need their consent (and a parent or guardian's for children). Photographs taken by a previous agency or freelancer may belong to them unless your contract says otherwise. Check before you reuse. Our guide to website handover and ownership explains why ownership of assets belongs in the contract.
Step Six: Testimonials, Reviews and Proof
Proof is the content that visitors trust most and that businesses have the most difficulty collecting.
- Get permission in writing. An email reply saying "yes, you can use my comment with my first name and city" is enough for most purposes.
- Use real words. Do not rewrite a customer's testimonial into marketing language, and never invent one. Fabricated testimonials are an offence under consumer-protection rules in many jurisdictions and destroy trust when discovered.
- Link to the original where possible. A review on your Google Business Profile, for example, is stronger than a quotation you typed.
- Include certificates and registrations. Professional registration numbers, licences, awards and memberships should be accurate, current and in a form a visitor can check.
- Do not claim awards or rankings you cannot evidence.
If you have few testimonials today, launch with what you have and add more over time. A short, genuine set is better than a long, doubtful one.
Step Seven: Legal and Policy Pages
Several pages are not marketing at all, but must exist before launch and always take longer than expected, because they need a decision rather than a draft.
- Privacy policy. It should describe the personal data the site collects (contact forms, analytics, cookies, WhatsApp click-to-chat), why, how long it is kept and how a person can contact you about it. India's Digital Personal Data Protection Act, 2023 is relevant to how businesses handle personal data; confirm your obligations with a qualified adviser rather than copying another company's policy.
- Terms and conditions, where you sell online or take bookings.
- Refund, cancellation and shipping policy, for stores.
- Cookie notice, if you use analytics or advertising tags that set cookies.
Ask your adviser, not your developer, to approve the wording. The developer's job is to place the pages in the footer and link them from forms.
Step Eight: Approvals Without Endless Rounds
A review process that works looks like this:
- One approver per page, named in the inventory. Others may comment, but one person decides.
- One consolidated set of comments per round. If three partners have opinions, one person gathers them into a single document before it goes to the agency.
- A fixed number of rounds. Two rounds per page is a common allowance in agency contracts. Check the number in yours.
- A deadline for each review. Agree on, for example, three working days for a review. If no feedback arrives, the page is treated as approved for launch, with changes possible later.
- Review on a staging site, not in PDFs or screenshots, wherever possible, so that you see the page as a visitor will on a phone as well as on a computer.
Our guide to brief and approval checkpoints with a website designer covers how to build approval gates into the design stage, which is the companion to this content process.
A Realistic Content Schedule
Every project differs, so treat these as planning ranges, not promises. The shape matters more than the numbers.
| Stage | What happens | Typical range for a small business site |
|---|---|---|
| Planning | Page list, purposes, inventory | 1 week |
| First drafts | Home, main services, about, contact | 2 to 4 weeks, running in parallel with design |
| Photography | Shoot or collect and sort originals | 1 to 3 weeks, booked early |
| Review rounds | Two rounds on each core page | 1 to 3 weeks |
| Legal pages | Drafted and approved by your adviser | 1 to 2 weeks, in parallel |
| Load into the site | Developer places content, checks layout | 1 to 2 weeks |
| Final checks | Links, forms, mobile, speed, tracking | 1 week |
Ask the agency to show how content dates connect to design and build dates. If content is late by a week, a good project plan shows what moves. Our guide to a pre-launch testing checklist for online stores describes the final checks in more detail for e-commerce sites, and most of it applies to any site.
Questions to Ask a Web Development Company in Pune About Content
Use these in your first meetings. The quality of the answers is informative.
- Who writes the first draft of each page, and is it included in the quote?
- How many revision rounds are included and what is the charge beyond that?
- Do you supply a content inventory template and a content schedule?
- What happens to the launch date if our content is late?
- Who owns the photographs and text you produce, and when does ownership transfer?
- What format do you need for logos, photographs and documents?
- Will you add alt text, page titles and descriptions, or do we?
- Who sets up redirects from old pages if this is a rebuild? (This matters for search traffic. See our guide to fixing broken links and redirect chains.)
- How will we edit the text ourselves after launch, and is training included?
- Do you place content in the site or do we enter it?
Our wider article on questions to put to a web development company before you shortlist it covers technical and commercial questions as well.
Common Mistakes
Starting design before text exists. A layout designed around imagined headlines often breaks when real text arrives. Where possible, supply at least draft headings and key paragraphs before visual design is signed off.
Copying text from competitors or other websites. It is a copyright risk and it makes your site look like everyone else's. Search engines may also treat copied pages as duplicates of the original.
Writing for yourself rather than the customer. Lists of internal achievements read as boasting. Describe what the customer gets and how you solve their problem.
Treating the launch as the end. A site needs updates. Agree who will review content every quarter, and book the review in the calendar.
Leaving the contact page for last. It is the page that produces enquiries. Check phone numbers, addresses, opening hours, map links and form destinations early, and test the form by sending a message to each recipient.
Where to Start This Week
- List every page you think the site needs and write a purpose sentence for each.
- Cut the list to a launch set and a phase-two set.
- Create the inventory spreadsheet and name one owner and one approver per page.
- Gather originals of your logo, photographs and certificates in a shared folder.
- Ask each customer you would like to quote for written permission.
- Ask your adviser to start the privacy policy and terms.
- Put review dates into the calendar before the project begins.
Frequently Asked Questions
How long does it take to write the content for a business website?
For a small site of five to ten core pages, expect roughly two to six weeks of calendar time for drafting and review, with the actual writing effort being a few days spread across that period. The range depends mainly on how fast the business can answer questions and approve drafts, not on how fast anyone types.
Should the web development company write my website content?
It can, but it is a separate service from design and development and is often priced separately. Check whether the quote includes writing, interviews and revisions. Even when the agency writes, someone in your business must verify every fact, price and claim.
Can I launch a website with some pages unfinished?
Yes, if the unfinished pages are not essential to a buyer. Launch the core pages complete and leave the rest for a second phase. Avoid publishing pages with placeholder text, as they undermine trust and can be indexed by search engines.
What size and format should website photographs be?
Ask your developer, because the answer depends on the design. As a general approach, supply the largest original you have and let the developer resize and compress it for the web. Sending small, already-compressed copies limits what can be done, and your developer should deliver modern, compressed formats so pages load quickly.
Who owns the website content after the project?
That should be stated in your contract. Ownership of text and images you supplied normally remains with you. For content the agency created, the contract should say when ownership or a licence passes to you, often on final payment. Check the position for stock images and fonts, which may be licensed to the agency rather than to you.
Sources and Notes
- Google Search Central, guidance on using generative AI content: developers.google.com/search/docs/fundamentals/using-gen-ai-content
- Google Search Central, creating helpful, reliable, people-first content: developers.google.com/search/docs/fundamentals/creating-helpful-content
- W3C Web Accessibility Initiative, images tutorial (alternative text): w3.org/WAI/tutorials/images
- Ministry of Electronics and Information Technology, Digital Personal Data Protection Act, 2023: meity.gov.in
The schedule ranges in this article are planning estimates based on typical small-business projects, not measured industry statistics. TODO: if a published benchmark for content-related project delay is added later, cite the specific source and date.
Working With Govindani Infotech on Content-Ready Website Projects
Govindani Infotech is a website design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009. On our website creation projects we agree a page list and a content owner for each page before design begins, and our SEO team helps set page titles and headings once the text is drafted.
If you are planning a new site or a rebuild and want to talk through the content plan first, message us on WhatsApp at wa.me/919201958278 or use our contact page. Pricing is confirmed by the team once the page list is known.
About the author: written by the Govindani Infotech web development team in Pune, drawing on our experience of launching business, e-commerce and NGO websites.