download dots

📜 Write a Statement of Work

Turn the way you already price work into an app that sends, chases, and closes quotes on its own. These prompts build the whole estimate loop: a price book you control, a builder that does the arithmetic, a link the customer accepts with one tap, and the follow-up that happens whether or not you remember.
  • Tested prompts
  • Edit for your use case
  • Works across models
  • Save in Taskade
Write a Statement of Work

Copy

Every project I run ends in an argument about what was included. Build me a statement of work app. Take an accepted quote and produce a scope document holding the deliverables, an acceptance criterion for each one so we both know what finished means, the schedule, the things I need from the client and by when, the assumptions I am working under, and a short list of explicit exclusions. Give the client a public page where they read it and sign off, and record the date and name of whoever signed. Add an AI agent that drafts the scope and the acceptance criteria from the accepted quote in plain language, and that flags any deliverable described too vaguely to be accepted cleanly. Automate a reminder if a statement of work is unsigned three days after being sent, and a scheduled weekly check for client dependencies that are now overdue. Two logins: a project lead who drafts, and a client who reads and signs only their own.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Write a Statement of Work

Turn an accepted quote into a scope document with deliverables, acceptance criteria, dependencies, exclusions, and sign-off.

// the spark catches · intelligence awakens · the answer unfolds

The argument in month two is always about scope. This writes it down while everyone still agrees, in language a customer will actually read.

What's Included

  • Deliverables with acceptance criteria so done is a fact rather than an opinion.
  • Dates and dependencies including what you need from them and by when.
  • Explicit exclusions which are the most valuable lines in the document.
  • An assistant that drafts the scope from the accepted quote.

How To Use

  1. Write acceptance criteria for every deliverable. Vague ones become disputes.
  2. Name what you need from the client. Most delays start there.
  3. Keep exclusions short and specific rather than long and defensive.
  4. Get it agreed on a link before work starts, not alongside the first invoice.

Handle the extras through the change order tracker, and run the delivery with project management prompts.