ChiefOSby ConversintStart free
Menu
← Back to the library
Sales and customer relationships

Proposal scoping

Scope Conversint client engagements from transcripts, notes, emails, research, or an existing proposal. Use for fixed-fee project proposals, retainer proposals, proposal revisions, and the paired internal scope and fee decision memo.

Works with the context you provideVersion 2.0.1Historical revision

# Scope Engagement

Turn incomplete client inputs into a concise client proposal and an internal commercial decision memo. Push back on scope that is too broad, distinguish confirmed facts from assumptions, and surface only the questions that could change scope, timing, or fee.

Required Context

Read `./references/dependencies/conversint-current/references/client-deliverable-standards.md` and `./references/dependencies/conversint-current/references/output-paths.md`. Follow their rules for source capture and inline citations, client-context integrity, attribution, filenames, commits, and Drive handoff.

Load the common references required by `client-deliverable-standards.md`, including `./references/dependencies/conversint-current/references/org/pricing.md`, plus `./references/dependencies/conversint-current/references/sales-playbook.md` and `./references/dependencies/conversint-current/references/sales-evidence.md`. The selected value hypothesis determines the pricing frame. The internal profitability rate and role split must never appear in client-facing copy.

Ask once for the client proposal format: Branded DOCX, Markdown, or Both.

Use joint attribution to Patrick Saul and Daniel Nfodjo by default without asking an attribution question. Ask about the preparer only when the user requests solo attribution or an approved source artifact specifies a different preparer; otherwise use the shared joint-attribution preset.

The internal output is Markdown by default regardless of the client format. Create an internal DOCX only when Patrick explicitly requests one; do not add an internal-format question to the default picker.

Select The Proposal Model

Classify the request before drafting:

  • **Fixed-fee project:** a discrete project with a start, bounded deliverables, completion, and handoff. Read `./references/proposal-sections.md` and `./references/fixed-fee-proposal-example.md`.
  • **Retainer:** an ongoing monthly relationship, service-module package, website management arrangement, or marketing operations support. Read `./references/retainer-proposal-model.md`; read its service-menu reference only when modules or tiers are needed.
  • **Revision:** read the current proposal and internal memo first. Also read `./references/fixed-fee-proposal-example.md` for revision discipline, then load the fixed-fee or retainer model that governs the existing proposal.

Do not blend the fixed-fee and retainer structures. If the engagement type is unclear, ask whether the work ends with a handoff or continues as a recurring operating service.

Protect Existing Revisions

Before editing an existing proposal or memo, inspect both unstaged and staged changes:

```bash git status --short -- "customers/<Company Name>" git diff -- "<proposal path>" "<internal memo path>" git diff --cached -- "<proposal path>" "<internal memo path>" ```

Treat every pre-existing hunk as user-owned. Preserve wording and changes outside the sections Patrick asked to revise, even when regeneration would be easier. Apply localized edits, re-read the complete affected sections, then inspect the working diff again to confirm unrelated content did not move. If a requested change conflicts with an existing user edit, stop and ask which version controls.

Reconcile The Value Hypothesis

Identify the customer and use case, then locate prior Proposal Value Analysis (PVA) artifacts:

```bash rg --files "customers/<Company Name>" | rg ' - Proposal Value Analysis\.md$' ```

  • If multiple PVAs could apply, ask Patrick to select one.
  • If one clearly matches, read it and name it at the checkpoint.
  • If one exists but its use case does not clearly match, ask whether to use it, ignore it, or change the scoped use case.
  • If none exists, run `./references/dependencies/conversint-source/.claude/skills/proposal-value-analysis/references/value-anchor-framework.md` inline. Use current public sources when wage, vendor, agency, or benchmark assumptions materially affect the fee.

Reconcile rather than blindly reuse the selected PVA: state what changed in the use case, buyer goal, evidence, scope, effort, assumptions, pricing frame, fee, or risk. Decide whether to reuse, adjust, or rerun the value analysis. If an inline analysis should become a durable PVA, ask before saving it and use the canonical PVA path and commit helper.

Draft In Decision Order

  1. Draft the internal memo using `./references/internal-value-sizing.md`. Resolve the commercial recommendation, fee, pass-through costs, duration, effort margin, assumptions, guardrails, dependencies, and delivery sequence first.
  2. Draft the client proposal body using the selected proposal model.
  3. Write the client opening last so the Overall Summary and Commercial Summary reflect the final scope and fee.
  4. Re-verify every URL-to-claim pairing and confirm that no internal rate, margin, role split, or internal uncertainty leaked into the client proposal.

Checkpoint Before Files

Before writing files, run the Client Context Integrity audit and present:

  • Project name and proposal model.
  • Intended outcomes and one-line scope.
  • Fee, client-paid pass-through costs, and duration.
  • Selected PVA and whether the recommendation was reused, adjusted, or rerun.
  • Two or three material assumptions, open decisions, or scope risks.

Ask: "Ready to build both documents, or would you like to adjust anything first?"

Outputs

Produce two durable artifacts in `customers/<Company Name>/`:

  1. **Client proposal:** `<Company Name> - Engagement Proposal.md` and/or `.docx`, following the chosen client format. Fixed-fee proposals use the exact ordered structure in `./references/proposal-sections.md`; retainers use `./references/retainer-proposal-model.md`.
  2. **Internal scope decision memo:** `<Company Name> - Engagement Scope (Internal).md`, 700-900 words using `./references/internal-value-sizing.md`. Generate the paired `.docx` only when explicitly requested, using the internal cover, header, and footer conventions.

Use the shared branded DOCX helper when DOCX is requested. Commit each Markdown artifact through `./references/dependencies/conversint-current/scripts/commit-md-to-main.sh` with:

  • `Update Engagement Proposal: <Company Name>`
  • `Update Engagement Scope (Internal): <Company Name>`

Return the helper's GitHub URLs and any generated DOCX paths. Drive upload is user-driven through `/gdrive`; do not invoke it automatically.

Verification

Before reporting completion:

  • Verify the fixed-fee headings, order, opening word limits, 3-5 deliverables, concrete Assess/Build/Operate actions, and Sources section.
  • Verify the internal body is 700-900 words and contains the PVA reconciliation, full commercial model, material assumptions/open decisions, guardrails/dependencies, delivery sequence, and references without repeating the PVA's benchmark catalog.
  • For revisions, inspect the final scoped diff and confirm pre-existing user changes outside requested sections remain intact.
  • Run `./references/dependencies/conversint-current/scripts/audit-skill-conventions.py` when this skill itself is materially changed.

Useful evaluation prompts:

  • Scope a fixed-fee implementation from rough meeting notes with one matching PVA and client-paid software costs.
  • Turn an ongoing website and campaign support request into a FACCorp-style retainer without importing fixed-fee headings.
  • Revise only the pricing and discovery sections of an existing proposal that already has unstaged user edits elsewhere.

CRM Handoff

After returning the URLs, offer the approval-gated CRM handoff in `./references/dependencies/conversint-current/references/crm-handoff.md`: draft the activity and proposed opportunity changes, then ask before writing.