Separate writing from filling a layout
A writer working from approved positioning and complete product facts has a different assignment from one who must interview the team and clarify the offer. Record what already exists: audience research, product specifications, customer evidence, brand guidance and approved claims.
Then identify the deliverable. A document with text, a CMS-ready page with metadata and a fully published page with images are different scopes. Content entry and technical implementation should not become surprise work at the end.
Group pages by the effort they need
| Page type | Questions to settle |
|---|---|
| Home and main offer | What is the central message and next action? |
| Service pages | Which facts and examples differ between services? |
| About | Which relevant credentials can be verified? |
| Product pages | Is the source data complete and reusable? |
| Case studies | Are results evidenced and publication rights cleared? |
| Help and support | Which real customer questions must be answered? |
A shared layout can reduce formatting work. It does not make every service description interchangeable. Avoid purchasing a large batch of near-identical pages merely because they are priced cheaply.
Estimate the work before choosing a billing model
Consider a fictional project: 4 hours for interviews and research, 3 for the homepage, 2 hours each for four service pages and 5 for revisions and content entry. The total is 20 hours. At an assumed $60 per hour, the labor allowance is $1,200 before tax, photography and translation.
These inputs are an example, not a market benchmark. A fixed project price can be convenient when the source material and review process are defined. Hourly work can accommodate uncertain research needs, but it still needs a spending limit and regular review.
For a per-word quote, ask whether interviews, fact-checking, revisions and metadata are included. Word count is a unit for billing, not a sufficient description of the work or the quality of the result.
Write a brief that prevents avoidable rework
Provide the intended reader, the question each page answers, the required next step, approved facts, prohibited claims and examples of an appropriate tone. Name one person who consolidates feedback and specify the included revision rounds.
Ask for evidence before publishing numerical claims or customer results. If you do not have permission or supporting data, use an explicitly hypothetical example instead of inventing a case study.
Add the agreed content budget alongside the small-business website estimate. SiteCost's development calculation does not automatically include article writing, interviews or translation.