Proposal Drafting with Claude Projects

Most residential and commercial proposals coming out of a small BC architecture firm are 70% the same document. The scope language, the fee structure, the exclusions, the payment schedule — those repeat. What changes is the project description, the site address, the client name, and two or three scope items specific to this job. Claude Projects turns that repetition into a system you build once and run forever.

The stack

Two tools carry this workflow:

• Claude Pro ($20 USD/user/month) — one Project per proposal type. Projects hold persistent context: your firm voice, standard scope sections, fee structure, and three past proposals as style reference. You never re-explain yourself.
• Granola ($14 USD/user/month) — meeting notes without a bot in the call. It records locally and outputs a structured summary with decisions, scope items, and follow-up dates.
• Monograph (~$35/user/month) — fee engine and e-signature at the end of the process, once the draft is where you want it.

How it gets wired

Set up one Claude Project for each proposal type you write regularly: residential addition, tenant improvement, multi-family, interior. Inside each Project, drop:

• A system prompt defining your voice, your standard exclusions, your boilerplate liability language, and your fee structure
• Three finished proposals from past projects in that category, stripped of client identifying details
• Your current schedule of values or unit-rate fee table

When a new inquiry comes in, you paste the client brief or the Granola meeting summary into that Project and ask for a draft. Claude returns a structured proposal — scope narrative, fee schedule, payment milestones, exclusions — at roughly 80% completion. You review, adjust the project-specific scope, confirm the fee numbers, and export to Monograph for the fee engine and e-signature.

Total time per proposal: 25–35 minutes from brief to client-ready document.

The setup investment is building the prompt library — one afternoon to load your best past proposals, write the system prompts, and test each Project against a real brief. After that, the overhead per proposal is a review pass, not a writing session.

Compliance posture

Client briefs and meeting notes contain project addresses, budget discussions, and sometimes sensitive owner information. Keep that data inside Claude’s Projects context, not in shared chat threads or forwarded emails. Claude Pro operates under Anthropic’s standard commercial terms; uploaded files in Projects are not used for model training. Verify your firm’s engagement letter covers AI-assisted document preparation — most standard AIBC contracts don’t prohibit it, but your professional liability carrier may have language worth checking.

Proposals generated this way are drafts, not final deliverables. You review and own the output. That review step is also your professional liability protection: Claude does not carry E&O coverage; you do.

IP in your past proposals — scope language, fee structure, project descriptions — stays yours. You’re using it as style reference for a tool running on your own account. No shared workspace, no third-party firm access to your prompt library.

Common pitfalls

Loading too many past proposals into a single Project degrades output quality. Three well-chosen examples per type outperform ten mediocre ones. Pick proposals where the final scope matched what was actually built.

Granola summaries from short calls sometimes miss fee discussions or skip scope items mentioned verbally. Review the summary before pasting it as the brief source, and add any gaps manually.

Monograph’s fee engine expects specific line-item format. If you let Claude auto-format the fee schedule in a free-form narrative style, you’ll spend time reformatting before import. Set a fee table template in your Project system prompt that matches Monograph’s expected structure.

Claude Projects context is per-account. If a second architect at the firm needs access to the same Projects, they need their own Claude Pro seat with a duplicate Project setup — there’s no shared Project access in Claude Pro today.

When this is worth the setup

This workflow pays off if you write four or more proposals per month and spend two or more hours on each. At that volume, the time savings cover the combined Claude Pro and Granola cost in the first week of the month.

For firms writing one or two proposals per month, a simpler shared template library in Google Docs may be sufficient. The Projects setup is specifically valuable when proposal volume is high enough that the prompt library maintenance cost (updating scope language, refreshing style references annually) is clearly offset by drafting time saved.

If your proposals are highly bespoke — unusual site conditions, complex phased fees, joint ventures — the 80% draft still helps, but the editing pass gets longer. The workflow still saves time; the ratio just shifts.