Status: implemented locally, not deployed. Scope: B2B inbound enquiries, especially demo or contact requests arriving after a new website launch.

The Sales category starts with three reusable Crew capabilities: Lead Intake & Qualifier, Account Researcher, and Sales Follow-up Coordinator. Each installs a project-local skill plus a nine-check chat setup list. A Crew may carry more than one capability; a new Crew is proposed only when the owner, data access, or review boundary makes it useful. The creation picker and Builder both use the same versioned first-party catalog.

The Inbound Lead-to-Meeting Review Automation Playbook proposes two required Crew slots (Qualification and Follow-up) and one optional Research slot. Installing it copies guidance and a ten-check setup record into the Workflow. Builder chat inspects current Crews, website lead source, booking route, channel and customer direction, then proposes concrete steps. Selection does not create Crews or start a run. The first route remains manual until actual source access, policy, validator steps, and an owner-reviewed result are verified.

1. Qualification reads one authorized inbound enquiry or export, checks duplicate scope, applies owner-defined fit criteria, and creates lead-qualification-brief/v1 with source IDs. Unknown fit signals stay unknown. A not-fit, possible duplicate, or contact-blocked lead receives an internal disposition and does not advance to an outbound draft.
2. Optional Research uses a resolved company domain and approved public or customer-provided sources to create account-research-brief/v1. It labels observed facts, owner-provided facts, and hypotheses.
3. Follow-up reads only the validated lead brief and optional validated research, checks current prior contact and policy, and creates sales-followup-draft/v1 with send_state: not_sent, owner approval, claim references, a verified booking URL, and next-check time.
4. When the customer has connected an authorized email route and approved the exact message, a separate action rechecks suppression, reply, duplicate and meeting state, sends once, and records a real provider ID in sales-delivery-receipt/v1. A later calendar or CRM observation records sales-meeting-outcome/v1 only after the event exists. The optional route is blocked if a connector, booking URL, owner decision or current source check is missing.

The bundled validator checks each artifact's shape, source references, lead/domain binding, duplicate and contact-state gate, exact approved draft fingerprint, and provider receipt links. It blocks the consumer step on failure. A human verifies source truth and customer contact permission; valid JSON alone cannot establish either or prove a send or booking.

An export or file is sufficient for the first read-only result. During setup, ask for the authoritative form/CRM account, ideal-customer rules, lead owner, suppression policy, approved offer, prior-contact scope, booking URL/provider, and calendar outcome source. HubSpot and Salesforce are provider examples; this package does not assume either is connected. Existing authenticated webhooks can start asynchronous intake. A customer can use a verified Gmail/Google Calendar connection or approved MCP for delivery and observation; the chosen Crew must have actual read/write grants. A meeting counts only when an authorized calendar or CRM source confirms it. Instant on-page calendar display needs a separate synchronous website integration; the existing Workflow webhook cannot provide that response.

The product choice follows the existing small-business sales workflow of capturing leads, recording activities and follow-ups, and tracking pipeline outcomes; see HubSpot lead pipeline automation and Salesforce small-business lead management. These references explain market context, not a claim of AgentWorks integration.

• All three Crew templates install with an uncompleted nine-check list and no selected account, trigger, schedule, or outbound route.
• The Playbook installs with two required and one optional slot and an uncompleted ten-check setup record.
• The valid fictional qualification, research, draft, delivery, and meeting artifacts pass the local contract validator; a bad source reference, blocked contact, possible duplicate, another lead ID, changed approved message, previous reply, or a claimed sent state in a draft fails.
• Builder can create a Sales Crew from the trusted template ID with its local skill selected and an idempotent receipt.
• Frontend and Go tests cover catalog visibility, setup, Playbook installation, and Builder creation. A real customer setup, provider send and observed booking remain pending until that customer supplies authorized records, connected accounts, booking route and decisions. The current package is not a live instant-booking widget.