Case Study · Consulting

Let Claude draft a proposal from past work and team profiles — with pricing left to a partner.

Claude drafts the proposal from approved past work and team profiles. The pricing section is left for a partner, and the proposal is sent only after the partner approves it.

Example implementation A designed Kroy workflow showing how this can be set up. It is not a customer result.

The workflow

Watch this workflow run through Kroy.

  1. The request.

    “Draft Proposal”

  2. Who is asking.

    Kroy identifies the person in business development and Claude acting for them, within the delegation they gave it.

  3. Only what the task needs.

    Kroy retrieves the opportunity and the prospect’s brief (Salesforce), past proposals cleared for reuse (SharePoint) and team profiles and availability (KroyDB) from SharePoint, Outlook and Salesforce.

  4. Excluded by design.

    Day rates and margin, Confidential client deliverables not cleared for reuse and Staff appraisal records never reach Claude. That boundary is Kroy’s, not an instruction to the AI.

  5. The proposed action.

    Permitted: read the opportunity (salesforce.opportunity.read), read cleared proposals (sharepoint.file.read) and create the draft proposal (artifact.create).

  6. What Kroy refuses.

    Refused: read day rates, send the proposal (outlook.mail.send) and reuse client material not cleared for reuse.

  7. A person decides.

    A partner sets pricing and approves the proposal.

  8. State changes. Everything is recorded.

    The work is updated in Kroy, and every request — allowed or refused — is written to the audit trail.

Claude
Business development
Kroy
SharePoint
Outlook
Salesforce
✓ Read the opportunity
✕ Read day rates
! Approval
AUDIT · STATE

Retrieved

  • ✓The opportunity and the prospect’s brie…
  • ✓Past proposals cleared for reuse (Share…
  • ✓Team profiles and availability (KroyDB)

Excluded

  • ✕Day rates and margin
  • ✕Confidential client deliverables not cl…
  • ✕Staff appraisal records
Claude
Business development
Kroy
SharePoint
Outlook
Salesforce
✓ Read the opportunity
✕ Read day rates
! Approval
AUDIT · STATE

Retrieved

  • ✓The opportunity and the prospect’s brie…
  • ✓Past proposals cleared for reuse (Share…
  • ✓Team profiles and availability (KroyDB)

Excluded

  • ✕Day rates and margin
  • ✕Confidential client deliverables not cl…
  • ✕Staff appraisal records

What the AI can and cannot do

Data accessed

  • ✓ The opportunity and the prospect’s brief (Salesforce)
  • ✓ Past proposals cleared for reuse (SharePoint)
  • ✓ Team profiles and availability (KroyDB)

Data excluded

  • ✕ Day rates and margin
  • ✕ Confidential client deliverables not cleared for reuse
  • ✕ Staff appraisal records

Actions permitted

  • ✓ Read the opportunity (salesforce.opportunity.read)
  • ✓ Read cleared proposals (sharepoint.file.read)
  • ✓ Create the draft proposal (artifact.create)
  • ✓ Create an Outlook draft (outlook.draft.create)

Actions refused

  • ✕ Read day rates
  • ✕ Send the proposal (outlook.mail.send)
  • ✕ Reuse client material not cleared for reuse

Human approval required

  • A partner sets pricing and approves the proposal

Business situation

A London management consultancy has been invited to propose for an operating model review at ABC Limited. A consultant needs to pull together the approach, relevant experience, a proposed team and a timeline. Pricing is set by a partner.

Why existing tools alone are insufficient

An AI can draft a good proposal if it can see past proposals and team profiles. But the consultancy’s proposal library contains day rates and margins, and past deliverables include confidential material for clients who have not agreed to be referenced. A general AI with folder access cannot tell those apart.

Systems involved

  • Salesforce — the opportunity and the prospect’s brief.
  • SharePoint — past proposals, some cleared for reuse.
  • KroyDB — team profiles, availability and which past work may be referenced.
  • Outlook — where the covering email is drafted.

Kroy architecture

Claude connects to Kroy. Salesforce and Microsoft 365 are connected to Kroy by the consultancy. The Draft Proposal Skill may read the opportunity, past proposals marked Cleared for reuse and team profiles. Rate fields are in a partner-only projection. Sending is not in the Skill.

Workflow

  1. The consultant asks Claude: “Draft a proposal for the ABC Limited operating model review.”
  2. Kroy checks the consultant, the agent and the Skill, and returns the brief through salesforce.opportunity.read, cleared proposals through sharepoint.file.read and team profiles from KroyDB.
  3. Claude drafts the approach, relevant experience and a proposed team, and saves it with artifact.create.
  4. The consultant asks: “Add our usual day rates.” Kroy refuses: rates are not in the consultant’s projection. Claude leaves the pricing section marked for the partner.
  5. The consultant asks Claude to include a case example from a recent retail engagement. Kroy refuses: that engagement is not cleared for reuse.
  6. The partner adds pricing and approves the proposal.
  7. Claude creates a covering email with outlook.draft.create. A request to send it is refused; the partner sends it.

Agent permissions

Claude acts under the consultant’s delegation and within the Skill. It sees only material cleared for reuse and cannot see rates or send email.

Human permissions

Consultants draft proposals. Partners see rates, set pricing and approve proposals.

State changes

  • A proposal Artifact is created and moves from Draft to Approved.
  • The Salesforce opportunity is linked to the proposal.
  • The proposed team is recorded against the opportunity.

Audit outcome

Kroy records each read, the draft, the refused rate request, the refused reuse request, the partner’s approval and the covering email draft.

Security considerations

  • Commercial terms are protected by the projection, not by instructions to the AI.
  • Reuse clearance is a field in KroyDB, enforced on every request.
  • Credentials for Salesforce and Microsoft 365 stay in Kroy.

Setup requirements

  • Team profiles and reuse clearance recorded in KroyDB.
  • Salesforce and Microsoft 365 connected to Kroy.
  • Claude connected to Kroy.
  • The Draft Proposal Skill enabled, with rates in a partner-only projection.

Try this with your own systems.

Join the waitlist