Try SpecBot free — keep your deliverables and exclusions in your offers, reused in every proposal.
More client disputes trace back to vague deliverables than any other single cause. When both parties have different mental pictures of what “done” looks like, the project ends with someone disappointed.
The fix isn’t more communication during the project — it’s better deliverable definition before the project starts. Here’s how to do it.
What a deliverable actually is
A deliverable is a specific, tangible output you produce for a client. It’s what they receive when work is complete.
The key word is specific. “A website” is not a deliverable. “A 7-page Webflow site (Home, About, Services, Case Studies, Blog index, Contact, and a single Blog Post template), with responsive mobile design, deployed to specbot.dev” is a deliverable.
The difference matters: the first description could mean anything. The second description leaves no room for misinterpretation.
The anatomy of a well-defined deliverable
A fully defined deliverable answers five questions:
- What — what type of output is it?
- How many — what’s the quantity?
- What format/platform/specs — in what form will it be delivered?
- What’s included — what’s specifically part of this deliverable?
- What’s excluded — what’s explicitly NOT part of this deliverable?
For example, a content deliverable fully defined:
Monthly blog content package
- 4 long-form articles per month (1,500–2,000 words each)
- Topics: provided by client via monthly brief (due by 1st of the month)
- Format: published directly to WordPress, or delivered as Google Docs if CMS access isn’t available
- Includes: research, writing, 1 round of revisions per article, basic on-page SEO (title tag, meta description, internal links)
- Excludes: images/graphics, social media promotion, article briefs, content strategy
This description leaves nothing ambiguous.
Why the exclusions list matters more than you think
When you write deliverables, clients mentally fill in gaps with assumptions. If you don’t name what’s NOT included, they assume it is.
A web design proposal that says “5-page website” doesn’t answer:
- Does it include copywriting?
- Does it include photography or stock images?
- Does it include ongoing hosting or just launch?
- Does it include SEO setup?
- Does it include a blog or e-commerce capability?
The client assumes yes. You assumed no. The dispute happens when work starts.
A scope exclusions list prevents this entirely. It’s not adversarial — it’s protective for both parties. The client benefits from knowing exactly what they’re paying for and what they’ll need to arrange separately.
Deliverable definitions by service type
Web design & development
Typical deliverables to define:
- Number of pages (list them specifically if possible)
- Platform (Webflow, WordPress, Shopify, custom code)
- Responsive design (desktop + mobile only, or tablet too?)
- Integrations (CRM, email, analytics — which ones specifically?)
- Revision rounds (typically 2 for design, 1 for development)
- What “launch” includes (domain setup, DNS, SSL)
Common exclusions to name:
- Copywriting (unless it’s in scope)
- Photography or stock images
- Ongoing hosting or maintenance
- Content migration from old site
- Additional pages beyond the agreed count
- Third-party plugin licenses
Content & copywriting
Typical deliverables to define:
- Number of pieces (articles, pages, emails)
- Word count range per piece
- Who provides the brief/topic (you or client)
- Format of delivery (Google Doc, CMS, Word)
- Revision rounds
- SEO optimization (if included: what level — just titles and meta descriptions? Full on-page?)
Common exclusions to name:
- Graphic design or images
- Social media distribution
- Email formatting or campaign setup
- Translation or localization
- More than the agreed revision rounds
SEO
Typical deliverables to define:
- Keyword research (number of keywords, format — report vs. spreadsheet vs. brief)
- Technical audit (what’s reviewed, what’s the output format)
- Content production (if included — how many pieces, what length)
- On-page optimization (how many pages, what specifically — title, meta, H1, internal links?)
- Link building (how many per month, what type — guest posts? HARO? digital PR?)
- Reporting (monthly report, what metrics, what format)
Common exclusions to name:
- Content implementation (if you deliver content but client implements)
- Technical fixes implementation (if you audit but they fix)
- Paid search or PPC
- Social media
Brand design
Typical deliverables to define:
- Logo package (how many concepts, how many rounds of revisions, file formats — SVG, PNG, PDF at minimum)
- Color palette (primary + secondary with hex codes)
- Typography system (which fonts, which weights, where used)
- Brand guidelines document (what’s in it — typically 10-20 pages covering logo usage, color, typography, photography style, do’s and don’ts)
- Application files (any additional mockups or asset types)
Common exclusions to name:
- Website design
- Print collateral (business cards, letterhead — unless specified)
- Social media templates
- Motion/animation
- Photography direction
Strategy & consulting
Strategy deliverables are the hardest to define because the output is often a document or recommendation rather than a tangible product.
Typical deliverables to define:
- Report or deliverable type (competitive analysis, go-to-market strategy, content calendar, etc.)
- Length/depth (e.g., “20-30 page report,” “prioritized recommendation matrix”)
- What’s included in the analysis (data sources, methodologies)
- How recommendations are presented (written report + 60-minute walkthrough call)
- Number of revisions or iterations
Common exclusions to name:
- Implementation (strategy engagement typically excludes executing on recommendations)
- Ongoing advisory beyond the defined scope
- Primary research if only secondary research was scoped
The deliverable definition workflow
Before writing your proposal:
-
List everything the client expects to receive. What are the tangible outputs when this project is done?
-
For each deliverable, answer: what, how many, what format, what’s included. Be as specific as the project warrants.
-
Identify the adjacent work clients might assume is included. Write those as exclusions.
-
Review with a second pair of eyes. Ask: if I read this and had never been on the discovery call, would I know exactly what I’m getting?
A 5-minute deliverable definition exercise before writing a proposal saves an hour of scope dispute conversation during a project.
Start free on SpecBot — SpecBot turns your offers into proposals clients accept in one click, with a signed PDF for both sides. Free is 3 proposals a month with every feature; Pro is unlimited proposals at €12/month, or €9/month billed yearly. Write them in the web app, by voice, or inside ChatGPT and Claude.