From an incoming brief to a considered proposal.

The operating challenge

A consultancy receives inquiries through its website, referrals, and email. Partners repeatedly summarize discovery notes, find past material, and chase missing information. Proposal preparation competes with delivery work.

A good proposal reflects the client’s actual request, current capacity, and approved commercial terms. The workflow must preserve unknowns and confidentiality while avoiding invented credentials, pricing, or promises.

A workflow with a clear next step

01 / Capture and match

Create an inquiry record and check for existing contacts and organizations. Potential duplicates wait for review.

02 / Structure the brief

Extract explicit requirements, timeline, stakeholders, and stated budget. Mark missing information as unknown.

03 / Check fit

Apply service and capacity rules. Prepare a short list of questions for the discovery owner.

04 / Assemble a draft

Select approved service modules, rate cards, deliverables, and genuinely authorized evidence.

05 / Partner review

A partner approves scope, fees, staffing, claims, and terms before external delivery.

06 / Prepare the handover

After a verified acceptance, create onboarding tasks and the agreed delivery brief.

Architecture & controls

Website or email intake → HubSpot or another CRM → permissioned document library → document-generation service → review workflow. Postgres retains proposal versions and approval records.

• Confidential proposals cannot enter another client’s context.
• Only approved service descriptions and rate cards are used.
• Drafts are visibly identified and never treated as contractual acceptance.
• The partner reviews every external proposal and commercial commitment.

When things do not go to plan

Missing rate-card data blocks fee generation. Duplicate contacts are flagged rather than merged automatically. During a CRM outage, jobs queue and the coordinator receives an alert. Retries respect API limits.

The automation boundary: The workflow prepares proposals. It cannot agree fees, sign terms, invent experience, or commit the team’s availability.

Evaluation, before expansion

Evaluate 30–50 de-identified inquiries and proposal outlines. Include conflicting requirements, unavailable services, duplicate contacts, confidential attachments, and prompts asking the system to fabricate experience. The proposal owner signs off on the rubric.

Targets are agreed with the process owner after measuring representative current work. A pilot also records error rates, review effort, operating cost, and exceptions. Released staff capacity is not automatically a cash saving.

Rollout & handover

Move through offline evaluation, shadow mode, and operator-assisted work before considering a limited automatic path. Each phase has a named owner, stop conditions, and a manual fallback. The approved scope determines the delivery schedule.

What the engagement would deliver

• Structured intake and CRM routing
• Approved content-library structure
• Versioned proposal assembly
• Commercial review checklist
• Onboarding handover and editing guide

The final handover includes client-owned access, configuration or source, known limitations, evaluation cases, and recovery instructions. Third-party subscriptions and ongoing support are agreed separately.