Workflows Write a Business Proposal with AI
business Intermediate 9 min · 2 steps

Write a Business Proposal with AI

Turn a vague client brief into a scoped, professional proposal — clear deliverables, explicit exclusions, and a defined revision policy.

ICP Definer Scope Definer
Start with step 1

Why this workflow

Proposals get rejected for being vague, not for being expensive. This workflow turns a fuzzy client brief into a document that's easy to sign: first you pin down who the client really is and what they actually need, then you turn that into a scoped statement of work with clear deliverables, explicit exclusions, and a defined revision policy.

What you'll walk away with
A sharp profile of the client and the real problem behind the brief
A complete scope of work — deliverables, exclusions, and timeline
A revision policy and assumptions that prevent scope creep
STEP 1

Define what the client actually needs

Skill ICP Definer

Before writing a single deliverable, get specific about who this client is and the real goal behind their brief — not just what they asked for.

ICP Definer 774 characters
Before defining the ICP, ask me these questions one at a time. Wait for my answer before moving to the next.

1. What is your product or service?
2. What is the core problem it solves?
3. Who are your best current customers — describe the people or businesses that get the most value? (If none yet, say so.)

Once I've answered all three, give me 2–3 ideal customer segments ranked by likelihood to convert. For each segment include:
- Job title and company type
- Company size (headcount or revenue range)
- The specific pain that makes them ready to buy
- The buying trigger — the event that makes them ready to act now
- Where they spend time online
- What would disqualify them as a customer

Be specific — no vague terms like "decision maker" or "growth-stage company."

A clear read on the client's real pain — context for the scope.

STEP 2

Write the scope of work

Turn that understanding into a clean, client-ready scope that leaves no room for misinterpretation.

Project Scope Definer 1,052 characters
Ask me these questions one at a time. Wait for my answer before moving to the next.

1. What type of project is this? (e.g. website redesign, brand identity, content strategy)
2. What did the client tell you? (paste or summarize their brief)
3. What do you plan to deliver? (your current understanding of the deliverables)
4. How long will the project take?
5. How many rounds of revisions are included?
6. What does the client need to provide, and are there any conditions this scope depends on? (e.g. final copy, brand assets, access, sign-off deadlines)

Once I've answered all six, write a structured scope of work with:
1. Project overview (2–3 sentences)
2. Deliverables (bulleted list of exactly what is included)
3. Exclusions (what is explicitly not included — to prevent scope creep)
4. Timeline (phase breakdown with approximate dates)
5. Revision policy (what counts as a revision and what triggers a change order)
6. Assumptions (any conditions the scope depends on)

Use clear, professional language suitable for a client-facing document.

A scoped statement of work you can paste into a proposal.

Or run all 2 steps in one session

Short on time? Paste this single prompt and your AI will walk through every step in order, pausing for your input as it goes.

Full workflow — one paste 2,044 characters
You are running a 2-step chained workflow. Complete each step in order, label your output clearly, and use each output as context for the next step.

━━━ STEP 1: ICP Definer ━━━
Before defining the ICP, ask me these questions one at a time. Wait for my answer before moving to the next.

1. What is your product or service?
2. What is the core problem it solves?
3. Who are your best current customers — describe the people or businesses that get the most value? (If none yet, say so.)

Once I've answered all three, give me 2–3 ideal customer segments ranked by likelihood to convert. For each segment include:
- Job title and company type
- Company size (headcount or revenue range)
- The specific pain that makes them ready to buy
- The buying trigger — the event that makes them ready to act now
- Where they spend time online
- What would disqualify them as a customer

Be specific — no vague terms like "decision maker" or "growth-stage company."

━━━ STEP 2: Project Scope Definer ━━━
Ask me these questions one at a time. Wait for my answer before moving to the next.

1. What type of project is this? (e.g. website redesign, brand identity, content strategy)
2. What did the client tell you? (paste or summarize their brief)
3. What do you plan to deliver? (your current understanding of the deliverables)
4. How long will the project take?
5. How many rounds of revisions are included?
6. What does the client need to provide, and are there any conditions this scope depends on? (e.g. final copy, brand assets, access, sign-off deadlines)

Once I've answered all six, write a structured scope of work with:
1. Project overview (2–3 sentences)
2. Deliverables (bulleted list of exactly what is included)
3. Exclusions (what is explicitly not included — to prevent scope creep)
4. Timeline (phase breakdown with approximate dates)
5. Revision policy (what counts as a revision and what triggers a change order)
6. Assumptions (any conditions the scope depends on)

Use clear, professional language suitable for a client-facing document.