Website Project Brief Small Business: Don't Pay Twice

Opening answer (BLUF)

You pay twice when the first invoice buys a homepage that nobody agreed on, and the second invoice buys it again after the owner, the office manager, and the cousin who "does marketing" finally say what they actually meant. A useful website project brief small business owners can send before they hire anyone is not a mood board. It is a short written record of the job the site must do, who it is for, which pages are in, which pages wait, what content you already have, who has the last word, and what "done" means in plain language.

This is a buying-process piece, not a refresh-versus-redesign checklist. Either path still fails if the brief is a vibe. We ask for this packet on every first call. The shops that write it down spend the build on pages people will use. The shops that skip it spend the build arguing about pages they already paid for.

Write the problem, not a page list

Most briefs start with a wish list: new homepage, about page, services, blog, booking, shop, member login. That list is a solution. It is not the job.

Nielsen Norman Group treats discovery as the early phase where you research the problem, name it, and gather enough evidence to decide what to do next. Their 2020 definition (last reviewed in 2024) is blunt: moving forward on assumptions is risky, because the team can spend time, money, and effort solving a problem that does not matter.[1] A site project is the same trap in smaller clothes. "We need a new website" is not a problem. "Callers keep asking which services we still offer, and the current site lists work we stopped doing two years ago" is a problem.

Write a problem statement before you write a sitemap. NN/g's 2021 guidance is to keep it short, focused on one problem, and free of a baked-in solution.[2] Use the five questions: who is affected, what is going wrong, where it happens, when it happens, and why it matters.[2] A decent first draft looks like this:

> Homeowners in Mecklenburg and the surrounding counties call us after they have already hired someone cheaper. They cannot tell from the site what we include, where we work, or how long a typical job takes. That costs us the jobs we want and fills the calendar with the jobs we do not.

Notice what is missing: "redesign the homepage," "add a chatbot," "move to a new platform." Those can come later. If the statement already names the page, you skipped the problem.

The US Digital Service playbook starts the same way. Play 1 tells teams to begin by naming primary users, the need the service will address, and why those people want it, then to write the findings down so later people can still find them.[3] You do not need a federal-size process to steal that habit. One page is enough.

Name who the site is for (and who it is not)

SBA's planning guidance says to be specific when you name your target market, because the business will not be for everybody.[4] A website brief that says "everyone in Charlotte" is not a brief. It is a way to buy five pages that try to please five different people and help none of them.

Write three audiences at most:

1. The person you most want to hear from this year.
2. The person you already serve well, if that is a different group.
3. The person you want the site to politely turn away.

For each one, add where they live or work, what they are trying to get done, what they already tried, and what they need to believe before they call. SBA's market-research questions are a clean starter: is there demand, who would be interested, where do they live, what else can they buy, and what do they already pay for the alternative.[4] You do not need a consultant to answer those. You need last year's invoices and ten minutes of honesty.

Then write the jobs the site has to do for those people. Call. Book. Request a quote. Find the service they already searched for. Confirm you work in their town. See a real project that looks like theirs. Download a spec sheet. Those jobs are the brief. Pages exist to finish those jobs.

If two owners disagree about the audience, do not paper over it. NN/g's 2022 stakeholder-interview guidance exists because people with a stake in the project often hold different goals, different history, and different ideas of success.[5] They recommend covering success metrics, current priorities, what has been tried, and how each person wants to stay involved.[5] Do that conversation once, on paper, before you pay anyone to design. If you skip it, you will pay for the page the first owner wanted, then pay again for the page the second owner wanted.

List the must-have pages, then the later pile

Once the jobs are clear, list pages in two columns: must ship, and can wait. Must-have is the smallest set that lets the right person finish the job. Later is everything that is true, nice, or "we should have that someday."

A typical local service brief we see, when it is honest:

• Home
• One page per service you actually sell
• Service area or locations
• About
• Proof (projects, reviews you can stand behind, or both)
• Contact, with hours and a real next step

A typical later pile:

• Blog, unless you already have writers and a reason
• A shop, unless you already sell products
• A client portal
• A second language
• A careers page for jobs you are not hiring

Information architecture is the expensive part to get wrong, because every later page hangs on it. NN/g's 2023 tree-testing article is useful here even if you never run a formal study: you can test a proposed menu as a simple hierarchy before anyone writes copy, draws a layout, or writes code.[6] Their phrase is the right warning. If you are not checking, you are guessing.[6]

You do not have to hire a lab. Print the proposed menu. Ask two real customers (not your sister) where they would click to request the job you most want. If they hesitate, the label is wrong. GSA's human-centered design methods make the same point with card sorting: group the information the way the people who use it think, not the way the org chart is drawn. They also warn that if you do not have the back-end system a feature needs (someone to process form requests, a way to keep listed prices true, a person to answer the chat), stop and re-scope instead of designing a product the business cannot support.[7]

That last line is how owners buy the same page twice. They pay for a "Get a quote" form nobody monitors, then pay again for a phone number and a promise to call back. They pay for a blog homepage with no posts, then pay again to hide it. They pay for a shop that never gets inventory, then pay again to take it down.

Write the owner of each must-have page in the brief. Not the designer. The person inside your shop who will give facts, photos, and a yes. If that name is blank, the page is not a must-have. It is a hope.

Bring examples you like, and say why

"Make it modern" is not a brief. "We like how this plumber lists three services, shows a real truck, and puts the phone number on every page" is a brief.

Collect five live sites. They do not have to be in your trade. For each one, write two sentences: what works, and what you do not want copied. Useful notes look like this:

• Clear service names a customer would actually search
• Photos of the real crew or the real shop, not a stock handshake
• Hours and a next step above the fold on a phone
• Proof next to the claim, not in a buried trophy case
• A contact path that matches how you actually answer (call, form, or booking)

Useless notes look like this:

• "Clean"
• "Bold"
• "Like Apple"
• "Lots of white space"

If you cannot say why you like a page, we cannot price or plan from it. Bring the why. Our public web design portfolio is one place to see how we treat services, proof, and contact. Use it the same way: point at a specific page and name the job it does.

Examples are not a contract to copy another business. They are a way to show taste, reading level, photo style, and how hard you want the next step to work. They also surface fights early. If one partner loves a long story and the other wants a short service grid, that is a decision. It is cheaper on paper than in the third round of homepage revisions.

Inventory what you already have

A surprising amount of "we need new copy" is really "we never collected the facts." Before you hire, dump the following into a shared folder:

• Current site URL and any pages you still like
• Legal name, doing-business-as name, address, phone, email, hours, service area
• The three to seven services you actually sell, in the words customers use
• Three recent jobs you are proud of, with what was included and (if you are willing) a range or starting point
• Photos and video you own the rights to: people, place, trucks, finished work
• Reviews or quotes you can use, plus whether the person was paid, related to you, or given a discount
• Logos, colors, fonts, and any brand rules
• Forms, booking tools, or email lists you already pay for
• Who hosts the domain, who can log into email, and who can change DNS

SBA lists "making a website" as a startup cost next to licenses, insurance, and marketing materials, which is a useful reminder: the site is an operating expense with inputs, not a poster you order once.[4] If the inputs are missing, the build stalls, and stalled builds get rewritten. That rewrite is the second payment.

Content you do not have should be marked as a task with a name and a date, not as a designer mystery. "We will send About copy in two weeks" is a plan. "You can just write something" is how you buy a page, hate the voice, and buy it again.

Decide who approves, and what "done" means

Unclear approval is the other way you pay twice. Five people "have input." Nobody has a pen. Every draft comes back with a new color, a new headline, and a new page that was never in the first list.

The US Digital Service playbook puts a single product owner on the work, with authority to decide features and be accountable for whether the service meets the people it is for. Their checklist is simple: name the person, make sure everyone agrees that person can decide, and write down what it takes to add or remove a feature.[8] For a small shop that person is usually the owner, or one partner with a written mandate. "We both have to like it" is fine if you put a deadline on disagreement. It is not fine if it means every heading goes to a group text.

NN/g's 2024 discovery tips add two habits that save money on a small project too: agree on roles and working norms before the work starts, and put a timebox on the early research so the planning fallacy (the habit of underestimating how long tasks take) does not eat the calendar.[9] USDS discovery sprints are often two to four weeks and are meant to find root causes, not to rebuild the product in that window. They interview people at every level, look at how work actually happens, and write down what to do next.[10] You can steal the shape without the federal label: one short discovery, written findings, then a build against that list.

Write "done" as a checklist, not a feeling. A practical done list for a marketing site looks like this:

• Every must-have page is live at the agreed URL, with the agreed next step working
• Names, hours, phone, address, and service area match the rest of your public listings
• Forms go to a monitored inbox, and someone is named as the person who answers
• Photos and claims on the page are ones you can defend
• The site can be used by people with disabilities at least as well as you serve people in the shop (the US Digital Service playbook calls this out as a basic "make it simple" check: follow accessibility practices so people succeed the first time)[11]
• You know who holds customer data from the forms, how you get it back, and what happens if the mailbox or host is compromised (NIST's Cybersecurity Framework 2.0, published in February 2024, starts small businesses with Govern, Identify, and Protect: know the risk, name who is responsible, and put basic safeguards on the data you collect)[12]
• You have logins, a handoff note, and a named person who can change a phone number next month without calling the original designer

If "done" is "we'll know it when we see it," you will see it twice.

USDS also tells agencies to put research and discovery in the budget, and to structure the contract around frequent deliverables rather than one giant milestone months out.[13] That is good buying advice for a private shop too. Ask for a written sitemap and a first homepage draft you can reject before anyone builds twenty pages on a guess. Frequent checkpoints cost less than one late surprise.

SBA's hiring guidance is worth a line here. An independent contractor operates under their own business name and invoices for completed work. You still have to decide, in writing, what "completed" means, or you will argue about it later.[14] The brief is that writing.

Only ask the site to say what you can prove

A brief that asks for "the best roofer in Charlotte" or "results our customers typically see" is asking the designer to print a legal problem. The Federal Trade Commission applies the same truth-in-advertising rules online as it does on a billboard: the claim must be truthful, not misleading, and, when it is the kind of claim that needs proof, backed by evidence.[15] FTC business guidance puts it even plainer. Claims must be truthful, cannot be deceptive or unfair, and must be evidence-based.[16]

That belongs in the brief as a claims list:

• Claims you can prove (license numbers, years in business, cities you serve, materials you use, a warranty you actually write)
• Claims you will not make
• Reviews or quotes you want on the page, plus the relationship behind them

FTC endorsement guidance (updated in 2023) says a testimonial has to be the honest opinion of the person who said it, and you cannot use that person to make a claim you could not make yourself. If there is a connection a customer would not expect (family, employee, a discount given for the quote), say so clearly.[17] Bring the real quotes. Do not ask us to invent a five-star paragraph in the owner's voice.

SBA's own marketing-plan notes remind owners that the federal government regulates advertising, so the plan has to stay legally compliant.[14] The website is advertising. Treat it that way in the brief, and you will not pay to rewrite a homepage after someone in the office gets nervous.

A one-sitting brief you can send

You can write this in an hour. Paste it into a document and send it with the folder of files.

1. Problem. One short paragraph. Who is stuck, what is going wrong, why it matters this year.
2. Audiences. Three groups, including the group you do not want.
3. Jobs. The five things a visitor must be able to finish.
4. Pages. Must-have versus later, with an owner name on each must-have.
5. Examples. Five URLs and a why for each.
6. Assets. What you already have, and what is still missing with a date.
7. Approver. One name, plus who may comment.
8. Done. The checklist above, in your words.
9. Claims. What the site may say, what it may not, and which quotes are real.
10. Constraints. Launch window, languages, integrations you already pay for, and anything the site must not break (current email, current phone tracking, a form you still need).

If a vendor cannot bid from that packet, they are not bidding the same job you think you are buying. If two vendors return wildly different page lists, your later pile leaked into the must-haves. Tighten the list and send it again.

We use a version of this when someone fills out our marketing website estimate. The form is faster than a blank email. The thinking is the same.

Practical takeaways

• Write the problem before the page list. A sitemap is a solution. Solutions that skip the problem get rebuilt.
• Name who the site is for, and who it should turn away. "Everyone" is how you buy five average pages.
• Split must-have pages from later pages, and put an internal owner on each must-have.
• Bring examples with a why, not adjectives.
• Inventory copy, photos, proof, logins, and tools you already pay for. Missing inputs stall the build, and stalled builds get rewritten.
• Name one approver. Write what "done" includes: working next steps, true facts, claims you can defend, a usable site, and a handoff you can maintain.
• Ask for frequent, reviewable deliverables (sitemap, first pages) before a long silent build.
• Do not ask the site to print a claim you cannot prove.

How we can help

We plan and build marketing sites for small businesses, from the Charlotte, NC area and for owners we serve nationally. The first thing we want is the brief above, not a pile of screenshots with no decisions attached.

On a web design project we turn that packet into a page list, a sitemap, and a first homepage you can approve or reject before we build the rest. If you already have the facts and just need a scoped number, use the estimate form. If you want to see how we treat services and proof, start with the portfolio. If you would rather talk it through, contact us and bring the problem paragraph, the must-have list, and one example you like. That is enough for an honest first conversation, and it is how we keep you from buying the same page twice.

Citations

1. Nielsen Norman Group, "Discovery: Definition" (March 15, 2020; last reviewed August 2, 2024). https://www.nngroup.com/articles/discovery-phase/
2. Nielsen Norman Group, "Problem Statements in UX Discovery" (August 22, 2021). https://www.nngroup.com/articles/problem-statements/
3. US Digital Service, "The Digital Services Playbook," Play 1: Understand what people need. https://playbook.usds.gov/
4. US Small Business Administration, "Plan your business." https://www.sba.gov/counseling/plan-your-business/
5. Nielsen Norman Group, "Stakeholder Interviews 101" (October 23, 2022). https://www.nngroup.com/articles/stakeholder-interviews/
6. Nielsen Norman Group, "Tree Testing: Fast, Iterative Evaluation of Menu Labels and Categories" (August 6, 2023). https://www.nngroup.com/articles/tree-testing/
7. Digital.gov (GSA), "Methods" (Human-Centered Design Guides, Design Operations). https://digital.gov/guides/hcd/design-operations/methods
8. US Digital Service, "The Digital Services Playbook," Play 6: Assign one leader and hold that person accountable. https://playbook.usds.gov/
9. Nielsen Norman Group, "7 Tips for Successful Discoveries" (September 27, 2024). https://www.nngroup.com/articles/7-tips-discovery/
10. US Digital Service, "Discovery Sprint Guide." https://sprint.usds.gov/
11. US Digital Service, "The Digital Services Playbook," Play 3: Make it simple and intuitive. https://playbook.usds.gov/
12. National Institute of Standards and Technology, "Take A Tour! NIST Cybersecurity Framework 2.0: Small Business Quick Start Guide" (May 1, 2024). https://www.nist.gov/blogs/cybersecurity-insights/take-tour-nist-cybersecurity-framework-20-small-business-quick-start
13. US Digital Service, "The Digital Services Playbook," Play 5: Structure budgets and contracts to support delivery. https://playbook.usds.gov/
14. US Small Business Administration, "Manage your business." https://www.sba.gov/counseling/manage-your-business/
15. Federal Trade Commission, "Truth In Advertising." https://www.ftc.gov/news-events/topics/truth-advertising
16. Federal Trade Commission, "Advertising and Marketing." https://www.ftc.gov/business-guidance/advertising-marketing
17. Federal Trade Commission, "FTC's Endorsement Guides: What People Are Asking" (revised 2023). https://www.ftc.gov/business-guidance/resources/ftcs-endorsement-guides-what-people-are-asking