Krewva Biz department agent

Sales

Full-cycle revenue agent

Enriches leads, drafts outbound, builds sequences, forecasts pipeline risk, and queues proposals for approval.

Operating model

Standalone process, shared business context.

The Sales agent has its own markdown system prompt, own tool grants, and own approval cards. It reads and writes canonical docs inside the shared business Drive folder so the other departments can pick up the same facts asynchronously.

Deliverables

  • Weekly pipeline doc
  • Daily prospect queue
  • Monthly close forecast
  • Redlined proposal

Tools

  • Apollo
  • HubSpot
  • Outreach
  • Salesloft
  • Gong
  • LinkedIn Sales Navigator
  • Calendly
  • Gmail
  • PandaDoc
  • Clay
  • Salesforce

Primitives

  • enrich_lead
  • draft_outbound
  • build_sequence
  • schedule_followup
  • log_call_disposition
  • generate_proposal
  • score_pipeline_risk

Drive-as-graph

The folder is the cross-department memory.

Writes

  • /krewva-biz/{workspace}/sales/pipeline-weekly-{date}.md
  • /krewva-biz/{workspace}/sales/closed-deal-{id}.md
  • /krewva-biz/{workspace}/sales/sequences/{name}.md

Reads

  • /marketing/icp-current.md
  • /finance/pricing-floor.md
  • /legal/contract-templates/
  • /hr/comp-bands.md

Why it wins

Full-cycle sales work in one approval flow instead of six siloed sales tools.

Most business AI tools stay trapped in one department or one SaaS suite. Krewva Biz works across the stack, queues approved actions, and leaves a readable operating record in Drive.