See where your website actually stands—no email, no URL crawl, score in two minutes. Run the free System Review →
Client-owned web systems
Plan my system

SITEBORNE SIGNAL MODULE

IntentPath — guided service matching

Uses deterministic rules to match a visitor with a service, resource, or next action.

Try the demonstrationAdd to a project brief

BUSINESS OUTCOME

What this capability changes.

  • Improve qualification
  • Reduce wrong-fit inquiries
  • Explain next steps

Best for

Service businesses, Cost-conscious businesses, Agencies

AI: optionalProduction pattern: available

From $2,000

Module-only monitoring: from $150/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.

Launch allowance statusAvailable

PLAIN LANGUAGE, TECHNICAL PROOF

What IntentPath does.

A guided set of choices that points a visitor to the service or next step that best fits their situation.

Why it is valuable

It reduces wrong-fit inquiries without hiding the reasoning or letting an opaque score make a consequential decision.

Example workflow

An agency needing overflow campaign capacity is routed to Partner Desk, while a firm with repeated customer questions is routed to Intelligence.

FOR TECHNICAL READERS

How the control model works

Versioned deterministic rules map declared needs to routes. Ambiguous combinations surface alternatives or human review instead of inventing certainty.

Failure path: Static decision tree, service links, and conventional project brief.

INTERACTIVE WALKTHROUGH

Use IntentPath before discussing it.

Choose the outcome closest to your current business problem.

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.

Interactive demonstrationYour input stays in this browser unless the control says “live.”

System view

Required

Cloudflare Workers, Cloudflare D1, Cloudflare Turnstile, Resend

Optional

Cloudflare Workers AI

Fallback

Static decision tree, service links, and conventional project brief.

Provider dependencies

Cloudflare Workers, Cloudflare D1, Cloudflare Turnstile, Resend, Cloudflare Workers AI

Last verified

2026-08-02

Provider limits, terms, model availability, and pricing may change. Production accounts remain client-owned.

Data classification

  • Form choices
  • Non-sensitive project context

LAUNCH ALLOWANCE

Serverless application logic

Workers Free request allocation for dynamic functions.

Current limit
100,000 Worker requests per day; static asset requests should bypass Worker execution.
Expected light use
A static-first marketing site with low-volume forms and optional module requests.
What consumes it
Dynamic Worker or Pages Functions invocations. Static asset requests do not consume this request allocation.
Fallback
Static content and conventional navigation remain available.
Paid successor
Cloudflare Workers Paid
Commercial use
Commercial use permitted under provider terms.
Data warning
Review logs and binding data; do not send unnecessary sensitive data.
Last verified
2026-08-02
View all referenced allowances
  • Serverless application logic: 100,000 Worker requests per day; static asset requests should bypass Worker execution.
  • Transactional email: 3,000 emails/month, 100/day, one custom domain, one webhook endpoint, 30-day retention.
  • 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.

Upgrade triggers

  • submission volume — 75%. Review email and D1 capacity.
  • rule ambiguity — any. Route to human review.
Conventional fallback: Static decision tree, service links, and conventional project brief.
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.