Referral Signal

Agentic Commerce Enablement

Paid merchant audit for ACP/AP2/agent-search readiness.

Shopify, WooCommerce, BigCommerce, and direct-to-consumer merchants.

Validation Terms

Monetization path: Paid audit, setup fee, retainer, integration fee, or transaction fee

Primary channel: Founder-led merchant interviews and approved B2B audit offers.

Delivery workflow: Audit catalog, policy, checkout, product feed, and agent visibility readiness; produce implementation packet.

Required gates:

  • No production checkout changes without approval
  • No merchant claims without evidence

Submitted signals are stored with this server-side offer snapshot for operator review only.

Commercial Validation Options

Primary signal: paid audit pilot interest

Suggested amount reference: $250

Signal willingness to approve a paid merchant audit for agentic commerce readiness after separate payment approval.

  • Written buyer commitment for a paid audit pilot.
  • Setup or retainer interest if the audit finds actionable gaps.
  • Implementation intro interest after merchant review.

This is not an invoice, contract, charge authorization, or payment collection. Live payment or success-fee collection requires separate approval.

What Can Count After Review

Public submissions create operator-review candidates only. A signal can count later only after production launch, approval gates, verified live or operator-reviewed proof, and guarded recording rails.

Validation Evidence Types

  • payment_or_deposit
  • paid_pilot
  • success_fee_authorization
  • signed_loi_or_written_buyer_commitment
  • real_recovery_or_savings_event
  • affiliate_or_transaction_conversion
  • reviewed_buyer_interview_with_willingness_to_pay
  • reviewed_public_or_consented_external_proof_reference

Monetization Evidence Types

  • live_payment_provider_webhook
  • production_paid_pilot_payment
  • production_success_fee_payment
  • affiliate_or_transaction_revenue
  • proof_backed_written_payable_commitment

Validation Must Include

  • production launched lane
  • review grade public signal or verified provider event
  • real buyer or user context
  • source date channel offer segment context
  • objections delivery burden and next action context
  • approved follow up or proof gate when required

Money Must Include

  • production launched lane
  • live payment runtime or proof backed written payable commitment
  • approved payment or success fee gate when required
  • positive amount cents
  • provider webhook or operator verified payable commitment proof
  • guarded monetization recording rail

This board does not approve follow-up, launch lanes, create checkout, collect payment, collect artifacts, record proof, count validation, count monetization, or complete the goal.

Offer A Consented Intro

Use this page when you can introduce a buyer, budget owner, operator, partner, or internal sponsor who may care about this lane.

  • Share only your own consented context and public company/site information.
  • Describe why the intro is relevant, who owns the decision, and what outcome would make the offer worth considering.
  • Do not paste third-party private contact details unless you have permission to share them.
  • Do not submit credentials, payment details, receipts, bills, claims, disputes, regulated documents, or account access.

This records an operational referral review signal only. It does not authorize Foundry follow-up, send outreach, schedule an interview, collect payment, collect artifacts, record proof, or count final validation evidence.

Review-grade required for buyer_interview_request: problem, commitment_statement, urgency, decision_authority, decision_timeline, willingness_to_pay_terms, requested_next_step.

Review-Grade Packet

operator review only

Complete these fields to make the signal review-grade on the first submission. It still does not authorize outreach, payment collection, proof recording, validation credit, monetization credit, or final-audit credit.

Required

  • ProblemDescribe the money leak, recovery, revenue lift, or workload that made this urgent.problem
  • Commitment statementSay what you would buy, pilot, approve, authorize, interview about, or introduce.commitment_statement
  • UrgencyExplain why this matters now and what timing pressure exists.urgency
  • Decision authorityState whether you approve, recommend, influence, or know the approver.decision_authority
  • Decision timingGive the real decision window, such as this week, this month, or before renewal.decision_timeline
  • Willingness-to-pay termsState acceptable payment terms, such as pilot fee, success fee, deposit, or savings share.willingness_to_pay_terms
  • Requested next stepAsk for the concrete next operator action, such as send pilot packet or review intro context.requested_next_step

Stronger If Included

  • Amount in centsUse the actual pilot, fee, success-fee, savings, or recovery amount you would approve.amount_cents
  • Budget ownerName the role that can approve the spend or success fee.budget_owner
  • Payable commitment termsState the exact pilot, fee, success-fee, savings-share, or retainer terms that could become payable after approval.payable_commitment_terms
  • Payable triggerName the event that would make the commitment payable, such as recovered money, delivered audit, qualified lead, or approved packet.payable_commitment_trigger
  • Payable timingGive the decision, invoice, or success-fee timing without submitting payment details.payable_commitment_deadline
  • Signer titleGive the title or approval role for the person who can sign or approve.commitment_signer_title
  • Signer organizationName the buyer entity, household, merchant, creator business, or team behind the commitment.commitment_signer_organization
  • Commitment authorityState whether you can approve, sign, route, or verify the payable commitment.commitment_authority_attestation
  • Commitment proof channelName the non-sensitive channel where an operator can verify the written commitment later.commitment_proof_channel
  • Success criteriaDefine what would make the pilot, success fee, interview, or delivery worth approving.success_criteria
  • Availability windowsGive safe scheduling windows only; this still does not schedule a meeting.availability_windows
  • Company or site URLUse a public URL only; do not submit logins, private records, or customer data.company_or_site_url
  • External proof referenceShare only a public or explicitly consented non-sensitive URL/reference for operator review.external_proof_uri
  • External proof summaryExplain what the reference supports without pasting private documents or artifacts.external_proof_summary
  • External proof permissionState your authority or permission to share the reference for operator review only.external_proof_permission
  • ObjectionsName the one issue that could stop approval or purchase.objections

Payable Proof Context

  • NoneNo extra field is required for this signal.none

Safe Preflight

Check server readiness before submitting this public signal.

No lead, payment, proof, validation credit, monetization credit, outreach, or live action is recorded by this check.

    Boundary

    Referral signals help prioritize operator review and lawful acquisition planning only. They are not lead-source approval, outreach approval, validation evidence, monetization evidence, or final-audit credit.

    Controls

    Medium: payment, merchant claim, and checkout changes require approval.