The prompt
Score 10 of 10, Excellent
Use it when You have had a first call with a prospective client and need a written scope with deliverables, exclusions and assumptions before you quote.
- {{client}}
- {{call_notes}}
- {{my_standard_scope}}
- {{how_i_work}}
Full prompt and why it works
Prompt
Turn my notes from a discovery call with {{client}} into a scope of work I can price and send with my proposal. The client should be able to read it and confirm "yes, that is what we want", and I should be able to price it without carrying hidden risk. Most freelance disputes start from things both sides assumed and nobody wrote down, so the assumptions matter as much as the deliverables. My call notes, including anything the client said about goals, deadlines, budget and who decides: """ {{call_notes}} """ What I usually include and exclude in this kind of project: {{my_standard_scope}} How I work (revision rounds, the feedback turnaround I need, tools, how I deliver files): {{how_i_work}} Write the scope with these headings: 1. The goal: what the client wants to achieve, in their words where the notes have them, in two or three sentences. 2. Deliverables: a table with the columns Deliverable, What it includes, Format, Rounds of revisions. 3. Not included: specific items the notes suggest the client might expect, such as copywriting, stock images, hosting or ongoing maintenance, each stated plainly. 4. Assumptions: what my price depends on, written so the client can confirm each, for example "You will supply final text for all pages before design starts." That example shows the form only. 5. What I need from the client, and by when: content, access, approvals and one person who gives feedback. 6. Phases or milestones, if the work splits naturally, with what the client approves at each. 7. How changes are handled: anything outside sections 2 and 4 is priced and agreed in writing before I start it. Then, separately for me: - Questions to send the client before I price, five at most, about the gaps that most affect cost. - Risks to the price, such as an unclear number of pages or a decision maker who was not on the call. Keep the scope under 700 words, in plain language without legal terms. Do not add deliverables, dates, prices or extras that are not in my notes, and do not turn a "nice to have" into a commitment. If the notes are unclear on what the client wants, put it under Questions rather than choosing for them.
Variables
- {{client}}
- The prospective client, for example "a family-run hotel".
- {{call_notes}}
- Your notes from the discovery call, as written.
- {{my_standard_scope}}
- What you normally include and leave out for this kind of project, for example "two design concepts; no copywriting".
- {{how_i_work}}
- Your revision rounds, the feedback time you need, your tools and how you deliver files.
Why it works
- Who it's for. The scope is written for the client to confirm and for you to price, which is why assumptions get their own section.
- An example. A sample assumption shows the form: something the price depends on, worded so the client can agree to it.
- If unsure. Anything the call left unclear becomes a question for the client instead of a deliverable the AI chose for them.