Three pains every sales and BD team hits weekly. Each one is what your reps actually complain about, not what a feature page would call them.
Qualifying every inbound and outbound lead against the ICP takes reps off the phone and onto a spreadsheet.
Deal strategy, pricing, and negotiation playbooks live in one rep's head, not a system the team can reuse.
Partnership term sheets and MoUs sit in a legal queue for weeks before anyone flags the real risk.
Every pipeline below is a shape you wire on the canvas using the crew and tools further down. Not a feature we ship for you, a pattern you configure.
ProspectIntelligence scores inbound and outbound leads against your ICP and reads intent signals from scraped company pages, while AccountManager checks existing-account health in parallel. Both write straight to the CRM.
Once ProspectIntelligence hands off a qualified lead, SalesStrategist designs the pricing model and negotiation playbook for that specific opportunity, logging the deal and its stage in HubSpot as the plan forms.
SolutionsEngineer builds the technical value story for a qualified prospect while ProspectIntelligence keeps feeding fresh signal; free/busy checks and demo bookings run through Calendly and Google Calendar instead of an email thread.
AccountManager watches expansion and churn signal on every existing account; RevenueAnalyst layers in pipeline conversion and CAC/LTV context so a renewal at risk shows up in the weekly report, not the exit interview.
BizDevPartner researches and structures the alliance, then PartnershipLegal reads the MSA or term sheet for commercial risk. The draft goes out for internal sign-off before it reaches the partner's inbox.
useCases.list.sales-bd.workflows.5.body
Real personas from the sales_bizdev crew. Each ships with a tuned system prompt and a default tool allowlist. Swap models per persona on the canvas.
Researches accounts and contacts, gathers LinkedIn, event, and firmographic context, and assembles the dossier every other persona reads.
Picks the angle for each outbound move. Maps the prospect dossier to a play and the play to a message structure.
Scans for ecosystem partners, intro paths, and co-sell angles. Owns the strategic relationships, not the inbox-by-inbox grind.
Owns the existing book. Prepares QBRs, expansion conversations, and renewal nudges from the same dossier the SDR side reads.
Drafts the technical answer for an active opportunity. Reads the prospect's stack from the dossier and shapes the proposal around it.
Compiles stage-by-stage conversion, deal velocity, forecast accuracy, CAC and LTV bands, and the bottlenecks costing the most revenue.
Reviews MoU and partnership terms drafted by BizDevPartner, surfaces revenue-share and exclusivity risk before anything leaves the building.
Synthesizes the rest of the crew into the one revenue narrative the CRO or board reads. Used for QBR prep and forecast review.
Every tool below is a real shared tool from the Melaya bundle. Allowlist per agent; HITL-gate the writes; revoke any of them in one click.
Pull firmographics, news, and event context from public pages. Scoped at the agent level so ProspectIntelligence reaches only what you allow.
Search LinkedIn for the right people at the target account. linkedin_share is gated by HITL on every write.
Read inbound conversation history, prepare outreach, and stage every send for review. gmail_send is HITL by default for this crew.
Drop RevenueAnalyst's Monday pipeline report straight into your team channel. Same audit log as every other write.
Build the per-workflow knowledge store from CRM exports, call notes, won-deal email corpus, and product collateral. Powers all three knowledge layers.
General-purpose research and structured fetch. The fallback when nothing more specific applies.
Every pipeline ships with three layers of knowledge access. Mix and match per agent on the canvas. No shared vector space with another tenant, no surprise reads, no opaque retrieval.
includeContextPer-pipeline documents appended to specific agents' input on every run. The ICP brief, playbook, pricing sheet, or won-deal email corpus. Whatever needs to be there before the agent thinks. You pick which personas get which docs.
rag_retrieveA scoped tool granted per-agent. When the agent decides it needs more depth, it queries the workflow's vector store on demand. Same knowledge base as Static context, accessed only when the model asks for it.
pipeline_memoryPipeline-level state that carries from one run to the next. Yesterday's research is in scope for today's follow-up. The crew remembers what it already prospected, what got approved, what was sent. The audit log is the second-order knowledge base.
Sandbox tier is free with no card. Join the waitlist and we will email you the moment a slot opens.
← Back to every use case