SITEBORNE SIGNAL MODULE
LeadBrief — structured inquiry intelligence
Converts a long inquiry into a structured internal brief without making protected or binding decisions.
BUSINESS OUTCOME
What this capability changes.
- Faster follow-up
- Consistent lead records
- Visible missing information
Best for
Service businesses, Agencies, Professional firms
From $1,000
Module-only monitoring: from $100/monthA narrow add-on scoped to this module alone—checking its allowance, fallback, and failure state. It is separate from and smaller than a full Care plan, which covers the whole website.
PLAIN LANGUAGE, TECHNICAL PROOF
What LeadBrief does.
Turns a long inquiry into a clean internal summary of the goal, timing, budget, constraints, and missing information.
The business can respond faster and more consistently without assigning sensitive or discriminatory lead scores.
Example workflow
A paragraph about a slow website, an October launch, and a $12,000 budget becomes a reviewable brief with open questions clearly marked.
FOR TECHNICAL READERS
How the control model works
Validated fields provide the source of truth. Deterministic extraction works without AI; optional AI may improve phrasing but cannot change protected facts or make acceptance decisions.
Failure path: Deterministic extraction from structured fields plus the original inquiry.
INTERACTIVE WALKTHROUGH
Use LeadBrief before discussing it.
Paste a realistic, non-sensitive project inquiry and inspect the structured result.
The interaction uses your input and identifies whether it runs locally, checks this live site, or previews a production control. It does not disguise seeded output as intelligence.
System view
Required
Cloudflare Workers, Cloudflare D1, Resend, Cloudflare Queues
Optional
Cloudflare Workers AI, Cloudflare AI Gateway
Fallback
Deterministic extraction from structured fields plus the original inquiry.
Cloudflare Workers, Cloudflare D1, Resend, Cloudflare Queues, Cloudflare Workers AI, Cloudflare AI Gateway
2026-08-02
Provider limits, terms, model availability, and pricing may change. Production accounts remain client-owned.
Data classification
- Inquiry text
- Contact details
- Project metadata
LAUNCH ALLOWANCE
Structured data
Low-volume SQL storage for leads, metadata, and module state.
View all referenced allowances
- Structured data: 5M rows read/day, 100K rows written/day, 5 GB account storage, up to 10 free databases, 500 MB/database, seven-day point-in-time recovery.
- Asynchronous workflow: 10,000 operations/day and 24-hour message retention; a typical successful delivery uses three operations.
- Transactional email: 3,000 emails/month, 100/day, one custom domain, one webhook endpoint, 30-day retention.
- AI governance and routing: Core features free; up to 10 gateways and 100,000 stored logs across the account.
- Low-volume inference: 10,000 neurons/day; model availability varies and some models require Workers Paid.
Upgrade triggers
- email/day — 75%. Queue and review paid email tier.
- AI unavailable — any. Use deterministic summary template.
View implementation proof
Decision rationale
The implementation favors semantic HTML, static rendering, typed content, and isolated on-demand routes. Optional AI never controls pricing, eligibility, or emergency routing.
Controls
- WCAG 2.2 AA target
- Provider-neutral adapters
- Usage caps and kill switches
- Client-owned production accounts
- Conventional fallbacks
Verified evidence
- The browser demonstration runs from a clean clone without a paid credential.
- Kill switch and allowance states are typed configuration.
- Primary navigation and contact paths remain independent of this module.
Known limitation
External provider allowances and production behavior require owner accounts and deployment-time verification.