Skip to content
ZunovAIBuild | Design | Grow
Process

What a scope document should contain before you pay

Twenty headings that turn a conversation into something both sides can hold each other to.

5 min readZunovAI
Showtime Crew CRM, built to a written scope

Most project disputes are scope disputes wearing a different hat. Somebody assumed something was included; somebody else assumed it was not; neither wrote it down.

A proposal that prevents that argument has a predictable shape.

The headings that matter most

Every section earns its place, but four of them do the real work:

  • 01Number of pages or screens — the baseline everything else adjusts.
  • 02Exclusions — what is explicitly not included, written before work starts.
  • 03Client responsibilities — content, approvals, access, and by when.
  • 04What happens when scope changes — the mechanism, agreed in advance.

The exclusions list is the one people skip and the one that saves the relationship. Domain, hosting, premium plugins, paid apps, stock imagery, third-party subscriptions and ongoing SEO are separate unless a proposal says otherwise — stating that plainly costs nothing and prevents an awkward conversation in week six.

Next step

Planning a project like this?

Get a scope-based estimate in about a minute, then a formal quotation within one business day.

Response within one business day

Let's build something your business can grow on.

Tell us what you need. You will get a clear scope, a realistic price and a formal quotation — usually within one business day.

  • A written scope before anything is built
  • A published starting price, not a mystery
  • A formal quotation inside one business day
CallWhatsAppEstimate