Business·April 3, 2026

47-Page Brief. Proposal Due Friday. The Freelancer's Playbook.

TL;DR

New client. 47-page brief. Proposal due Friday. Here's the freelancer's playbook to turn a dense brief into a first proposal draft, the clarifying questions to send, and a risk list to price in.

A freelancer's workspace in a sunlit cafe — a laptop showing a clean proposal draft alongside a PDF brief with highlighted sections and margin questions, a small notebook with scope and pricing jotted down, a cold coffee cup, AirPods on the desk, a printed one-page SOW template, afternoon light through a window

It's 3 PM Tuesday at your usual cafe. New prospect, referred by a past client. They sent a 47-page brief Monday night with the subject line "quick look?" You opened it at lunch. It is not, in fact, a quick look.

Page 1: a company overview. Page 7: a vague "success criteria." Page 14: an exhaustive list of "questions we'd want answered," most of which contradict the success criteria on page 7. Page 28: a timeline that starts next Monday. Page 41: a note that a competitor's previous contract "did not work out." Page 47: a polite request for your proposal by Friday EOD.

Your current reality: a Tuesday client call in ninety minutes, a Thursday deliverable for your biggest retainer, two kids at home, and a coffee that has been cold for some time. The old version of this story ends with you writing the proposal Friday at midnight, under-scoping the project out of exhaustion, winning it anyway, and spending the next six weeks regretting your own pricing.

The brief is not the problem. The problem is that reading 47 pages carefully enough to quote against them is a twelve-hour job, and you don't have twelve hours.

The move: turn the brief into a proposal draft, step by step

Drop the PDF in. Get a summary, the clarifying questions the client left out, a scoped deliverables list, a risk register, and a draft proposal to edit. Send the questions first, then write the proposal from the answers.

The playbook

Tuesday afternoon: load the brief

Open CorpGPT. Create a collection in My Documents: "[Prospect] — [Project]." Drop in:

  • The 47-page brief.
  • Any prior emails with the prospect.
  • Your three most similar past proposals that you won.
  • Your standard SOW template and rate card.
  • The prospect's public website, About page, and recent blog/LinkedIn posts.

Now the brief and your own past work sit in one collection.

Tuesday evening: the brief diagnostic

Use the Make pane ("Make from these sources") for the summary and the risk register, and ask Chat for the rest:

  • A brief summary (Summary) — what they actually want, in plain language.
  • A contradictions list — where the brief says two different things.
  • A clarifying-questions list — the specific questions you need answered to quote responsibly (aim for 6-10 sharp questions, not 40 lazy ones).
  • A deliverables breakdown — what you'd actually produce, with rough effort estimates.
  • A risk register (Risk check) — specific things that will go wrong if the client doesn't clarify them up front.
  • A red-flag note — anything in the brief that reads like scope creep bait, budget misalignment, or prior-contractor trauma.

What you have now: a map of the brief, the questions to send, and the risks to price in.

Wednesday 9 AM: send the clarifying questions

Do not write a proposal yet. Send the 6-10 clarifying questions. Short, professional, numbered, with context per question. Frame it as "so I can get you a proposal that's actually useful, a few quick questions first." Clients love this. It signals care. It surfaces the unspoken budget. It filters out tire-kickers.

Wednesday afternoon: draft the proposal

Answers come back. Paste them in, then ask Chat to write a draft proposal using:

  • Your three prior winning proposals as voice and structure references.
  • The brief + the clarifying answers as scope.
  • The SOW template as format.

Output: a draft with your positioning, your scope, your deliverables, your assumptions, your risk notes, your pricing placeholders, and your call-to-action.

You do not ship the draft. You edit it into your voice, delete the fluff, sharpen the value prop, and — critically — set the price yourself based on value and calendar, not on the tool's hour estimate.

Thursday morning: the pressure-test

Before you send, upload the draft and ask Chat:

  • "What's the weakest part of this proposal from the client's perspective?"
  • "What's the single line a competitor would use to beat me on this deal?"
  • "Where am I under-scoped? Where am I over-scoped?"
  • "If I were the client reading this, what objection would I have?"

Fix the three things that come back. Send it.

Then: send the proposal

You have a proposal built from the brief, the client's answers and your own best past work — edited into your voice and priced by you. You have shown up with clarifying questions (a signal of craft).

Now go do the Thursday deliverable.

Friday: kickoff call prep

If they want to meet Friday to walk through the proposal, ask Chat: "Given this prospect's brief, their company, and their public posture, what are the five hardest questions they'll ask me on Friday?" Draft one-paragraph answers. You walk in prepared.

Beyond the one proposal

Your proposal archive compounds

Every proposal — won or lost — goes into a separate "Proposal Archive" collection. Year three, you are not writing from scratch anymore. You are editing what already worked.

Client onboarding, in one move

Once the SOW is signed, use the Make pane for a kickoff meeting agenda, and ask Chat to draft a project plan skeleton, a communication cadence doc, and a risk/change-order template — all in your voice. You look organized because you are.

Weekly status updates your clients actually read

Feed your weekly work into the collection. Ask Chat to draft your Friday client update — specific, short, and drawn from your notes. Retention clients stay retention clients because they feel informed.

Scope-creep defense

When the client asks for "just one more thing" in week three, ask Chat: "Is this in the SOW? If not, what's the smallest fair change order?" You have a cited answer to check, not a week of resentment.

The quarterly self-review

Every quarter, ask Chat: "Across my last 10 proposals, which patterns correlate with wins vs. losses? What clients match my best outcomes? Which projects should I say no to next quarter?" Chat reads the passages that best match, so treat the answer as a lead to check, not a full audit. Running your own book better is how freelancers get to the point where they can charge more and work less.

The features doing the work

Make pane — brief summaries, risk registers (Risk check), kickoff meeting agendas, saved to Things I've made.

Chat across everything — clarifying questions, draft proposals and SOWs, weekly updates, pressure-testing, cross-proposal pattern recognition, scope-creep defense, and finding the prior proposal, the prior clarification, the rate that worked.

Record audio — your own notes right after a prospect call (it records your device's microphone, not the call), or upload the audio file (MP3, M4A…) your meeting tool saved (audio up to 50 MB, not video files); the Transcript tab shows who spoke → action-item recaps and follow-up drafts while the call is fresh.

What this can't do

It does not know which prospect is going to ghost you. It does not know when your gut is telling you the client is trouble — listen to your gut; it is usually right. It does not negotiate your rate; you negotiate your rate. It does not do the thing you were hired for. It helps you prepare the proposal.

The bottom line

New client. 47-page brief. Proposal due Friday. Coffee cold — fine, that part is on you.

Send sharp questions. Draft from what the brief says. Price it yourself.

Open CorpGPT. Load the brief. Ship the proposal.

Keep reading

Ready to try it yourself?

Upload any document and see it in action. Free to start, no credit card.

Start My Free Workspace