How to Write a Project Brief Vendors Can Actually Quote

If you've ever posted a job and gotten back three quotes that ranged from $800 to $9,000, the problem usually isn't the vendors. It's the brief. When a request is vague, every vendor fills the gaps with their own assumptions, and you end up comparing guesses instead of bids.

A good project brief does one thing above all else: it lets a competent vendor estimate the work without a phone call. That doesn't mean it has to be long. Most strong briefs fit on a single page. It means it has to answer the questions a vendor would otherwise have to ask — or worse, not ask.

Here's how to write one, section by section.

Start with the outcome, not the task

Most people open a brief with the task: "I need a new deck built" or "I need a logo." A better opening describes the outcome you're paying for.

Compare these two:

• "I need my kitchen painted."
• "We're listing our house in August and want the kitchen to read clean and neutral for showings — walls, ceiling, and cabinet faces."

The second version tells a painter the deadline pressure, the quality bar (good-enough-for-photos versus good-enough-for-a-decade), and the actual scope. Same project, completely different quote.

One or two sentences is enough. The point is to give the vendor a reason behind the work so they can flag things you didn't think to mention — like the fact that cabinet painting is a different process and price than wall painting.

Define scope by listing what's in and what's out

Scope is where most quote disputes are born, so spell it out in both directions:

• In scope: the specific deliverables, rooms, pages, features, or items the vendor is responsible for.
• Out of scope: the things a vendor might reasonably assume are included but aren't — or that you're handling yourself.

If you're hiring a landscaper and you plan to buy the plants yourself, say so. If you're hiring a web designer and the copywriting is already done, say so. Every excluded item you name is one fewer assumption baked silently into a price.

A useful test: read your scope list and ask, "Could two different vendors interpret this differently?" If yes, tighten it. "Refinish floors" can mean screening and recoating or full sanding and staining — hundreds of dollars apart per room.

State your constraints early

Constraints are the conditions that shape how the work gets done, and vendors price them whether you mention them or not. The difference is that unmentioned constraints get priced after the contract is signed, as change orders.

Common ones worth stating:

• Access: Can crews work weekdays only? Is there an elevator? Parking? An HOA with quiet hours?
• Occupancy: Will you be living or working in the space during the project?
• Materials or brand requirements: Do you require a specific product line, or are equivalents fine?
• Approvals: Does anything need permits, landlord sign-off, or a board review?
• Existing conditions: Old wiring, prior DIY work, files in a legacy format — anything that makes the starting point messier than it looks.

You won't know every constraint, and that's fine. Listing the ones you do know signals to vendors that you've thought about the job, which tends to attract more serious bids.

Share a budget range — yes, really

This is the section people resist most, so let's address the fear directly: "If I tell them my budget, they'll just quote the whole thing."

Here's what actually happens when you hide your budget:

• Vendors guess, and they guess defensively. Without a number, an experienced vendor pads the quote to cover unknowns, because vague buyers are riskier buyers.
• You get quotes for different projects. One vendor assumes the economy version, another assumes premium. Now your three bids aren't comparable at all.
• You waste rounds of back-and-forth discovering that your $5,000 budget and their $20,000 approach were never going to meet.

A budget range — not a single number — solves this. "We're hoping to stay between $4,000 and $6,000" tells vendors which tier of materials, scope, and finish to design for. Good vendors will tell you honestly if the range is unrealistic, which is information you want before anyone starts work, not after.

If you genuinely don't know what things cost, say that too: "We don't have a firm budget yet — please quote the standard approach and note where we could trim." You can also browse services to see typical package pricing for the kind of work you need before you commit to a range.

Give a timeline with the why attached

"ASAP" is not a timeline; it's a stress signal. Useful timeline information includes:

• A target completion date, and whether it's a hard deadline or a preference
• Why the date matters (a move, an event, a product launch) so vendors can suggest what to fast-track
• Your own availability for decisions — if you take three days to answer questions, that belongs in the schedule too
• Any blackout dates when work can't happen

If the deadline is genuinely tight, expect that to show up in the price. Rush work costs more everywhere, and a brief that acknowledges this reads as realistic rather than naive.

Define what "done" looks like

Success criteria are how you and the vendor will both know the job is finished. Without them, "done" becomes a negotiation. With them, it's a checklist.

Make them concrete and checkable:

• "All punch-list items resolved and final walkthrough completed"
• "Site loads in under three seconds on mobile and passes our accessibility checklist"
• "Two rounds of revisions included; final files delivered in editable format"

Notice these double as acceptance terms. When the proposal comes back, you can ask the vendor to reference them directly — which makes approving milestones and releasing payments much cleaner down the road.

Attach the things that remove guesswork

Photos and documents do more work per minute than anything else in your brief. Depending on the project, attach:

• Photos of the space, including the problem areas you're tempted to crop out
• Measurements or floor plans, even rough ones
• Inspiration references — and a note about what specifically you like in each
• Existing brand files, prior contracts, inspection reports, or spec sheets
• For digital work: logins you'll provide, platforms in use, examples of work you admire

A vendor who can see the cracked subfloor in your photo will price it. A vendor who discovers it on day two will change-order it.

A one-page template you can copy

Pulling it together, your brief should cover:

1. Project summary — what you want and why, in two or three sentences
2. Scope — what's included, what's explicitly excluded
3. Constraints — access, occupancy, materials, approvals, known conditions
4. Budget range — a low and high you're comfortable with, or an honest "guide me"
5. Timeline — target date, hard or soft, and the reason behind it
6. Success criteria — the checkable definition of done
7. Attachments — photos, measurements, references, relevant documents
8. Logistics — how you prefer to communicate and how fast you can make decisions

That's it. If a vendor can read those eight sections and produce a number, you've written a quotable brief.

Put the brief to work

A brief only earns its keep when vendors actually see it. Once yours is drafted, post a job with the brief as the body of your request, or send it directly to a few providers you've shortlisted from the vendor directory. Either way, you'll notice the difference immediately: faster responses, sharper questions, and quotes that are close enough together to actually compare.

And when the proposals do come in, the brief becomes your measuring stick. Any quote that ignores your stated scope or skips your success criteria has told you something useful about that vendor — before you've spent a dollar.