AP-059 no-send first-buyer outreach DA packet

Buyer segment hypothesis and disqualifier rules

Buyer segment hypothesis: controller/CFO/AP manager/finance ops/accounting-service buyer hypothesis

• Free checklist/template only.
• No budget influence or buyer sponsor path.
• Wants advice, invoice approval/rejection, payment instruction, ERP record mutation, live/private data before value, or customer delivery before DA.
• Forbidden demand: broad AP automation platform, guaranteed recovery, audit pass, ROI claim, or bespoke reconciliation service.
• Service burden likely red or bounded diagnostic output rejected.

Safe outreach objective and approved source class

safe outreach objective: validate pain and bounded diagnostic value, not sell/collect payment.

approved source class: DA-approved buyer/source class only, without lead list unless separately DA-authorized.

Buyer qualification rubric

• role, budget influence, AP pain, trigger window, bounded-output acceptance
• buyer role fit: controller/CFO/AP manager/finance ops/accounting-service partner
• budget influence: influencer or budget owner path
• AP pain: vendor statement gap, duplicate-risk review, stale aging, PO/receipt/amount mismatch, close delay
• trigger window: 0-90 days or recurring close cycle
• bounded-output acceptance: evidence pack, owner-review routing, hard stops, no advice/no payment/no writeback

Pre-send evidence checklist

• Deployed demo URL loads.
• Sample Diagnostic Report exists.
• AP-058 operations console shows proof status and gates.
• Buyer segment and disqualifier rules are explicit.
• Response taxonomy, objection taxonomy, first-10 score sheet, stop conditions, and authority split are ready.
• No lead list, recipient names, campaign IDs, send buttons, payment/quote wording, or customer delivery promise.

What exact Janez DA would authorize later

• lead_sourcing_DA would authorize only the specific source/lead discovery action named by Janez.
• outreach_DA would authorize only the specific approved message/send action named by Janez.
• quote_DA would authorize only a separately approved quote/price presentation.
• payment_ask_DA would authorize only a separately approved payment ask.
• payment_route_DA would authorize only a separately approved route/link/instructions.
• delivery_DA would authorize only a separately approved customer delivery under safe intake.
• live_data_DA would authorize only the specifically named live/private data action, if ever approved.

What remains separately DA-gated and next-authority gates

• lead_sourcing_DA
• outreach_DA
• quote_DA
• payment_ask_DA
• payment_route_DA
• delivery_DA
• live_data_DA

First-10 interaction score fields

• interaction_id
• source_class
• buyer_role
• buyer_segment
• budget_influence
• pain_trigger
• trigger_window
• bounded_output_acceptance
• forbidden_scope_requested
• price_band_signal
• paid_pilot_intent
• objection_class
• service_burden_estimate
• reply_quality
• next_authority_gate
• payment_ask_status=not_authorized
• payment_route_status=not_authorized
• revenue_amount_eur=0

Response taxonomy

• qualified_pain_signal
• budget_path_present
• bounded_output_accepted
• curiosity_only
• free_template_only
• forbidden_scope_requested
• wrong_role_or_no_budget_path
• service_burden_risk

Objection taxonomy

• is_this_just_file_parsing
• can_it_tell_us_what_to_pay
• can_it_approve_or_reject
• can_it_update_ERP
• can_we_use_live_or_bank_data
• is_this_advice
• can_it_guarantee_duplicates_or savings
• can_you_reconcile_everything_for_us

Safe draft message angle bank

No-send/internal only. These are placeholders only: buyer-pain angles, demo mention variants, boundary-safe snippets, reply-triage prompts, and objection handling notes. No recipient names, no lead lists, no campaign IDs, no send buttons, no Instantly actions, no payment/quote language, and no customer delivery promise.

Subject-line angle bank

Demo-path checklist

• Open deployed entry.
• Open AP-057 Sample Diagnostic Report.
• Open workbench Sample Report and Ops Console tabs.
• Show static/redacted intake, exception summary, owner-review routing, hard stops, and revenue truth.
• Do not send, quote, ask for payment, collect materials, or promise delivery.

Post-reply triage workflow

Practice the synthetic classifier locally: AP-060 synthetic first-10 interaction triage simulator.

• Classify buyer role and segment.
• Record pain trigger and trigger window.
• Record bounded-output acceptance and forbidden-scope request.
• Record objection class, reply_quality, service_burden_estimate, and next_authority_gate.
• Do not advance beyond readiness_only unless Janez grants the next specific DA.

Stop/continue thresholds

continue toward payment-ask DA candidate only if >=3/10 qualified interactions show buyer role, budget influence, urgent AP pain, bounded-output acceptance, no forbidden scope, credible paid-pilot intent, and service burden not red.

• Stop if replies are curiosity/free-template only.
• Stop if buyer asks for advice, invoice approval/rejection, payment instruction, ERP record mutation, live/private data before value, or guaranteed savings/recovery/audit pass/ROI.
• Stop if no budget path, no trigger window, no bounded-output acceptance, or service burden red.