Pilot
Sixty to ninety days on one stream
A Fromenance pilot puts communication provenance on one live communication stream for 60 to 90 days, for a fixed fee of $10K to $15K that is credited to your first annual contract. You get onboarding help, a weekly review, and a written report of verification volume, verdict distribution, campaigns discovered, intelligence yield, and the operational numbers you care about.
Timeline
Step 1: Week 0
Contract and DPA signed, tenant created, TXT published, redirect rule live, forwarding test passed in the wizard.
Step 2: Week 1
One stream registered, footer deployed to that template, reply identity live. First verifications arrive.
Step 3: Weeks 2 to 12
Run. Interim reports from the Overview export at day 30 and 60. Day 90: pilot report, Authoritative Mode readiness review, proposal.
What you provide
Deliberately small. The setup wizard walks through the six steps and refuses go live until the forwarding test passes.
One TXT record
_fromenance.yourdomain.com with the token from the setup wizard. Polled every 60 seconds until it resolves.
One mailbox and one redirect rule
verify@yourdomain.com redirected (not forwarded) to your tenant inbox. Guides for Google Workspace, Microsoft 365, Proofpoint, Mimecast, and Cisco Secure Email.
One stream registered
Fraud alerts or transaction alerts. An ESP webhook, an SDK call, or a journal BCC. The footer snippet pasted into that template.
A reply identity
A DKIM signed subdomain such as verify.yourdomain.com (three DNS records), or our reply domain with your display name and logo for the pilot only.
Baseline numbers
Contact center 'is this real' call volume and abuse mailbox volume on the pilot stream for the period before, so the report has a before and during.
Thirty minutes a week
A weekly review of Submissions and Indicators with your fraud lead. We watch coverage and trust rejections daily from our side.
What you get
Every number is captured by the product. The report is a dashboard export, not a spreadsheet exercise.
Verification volume
Attempts split by forward and web, and verdict distribution: Verified, Not verified, Known fraud, and replay flags.
Campaigns and lookalikes
Unique phishing campaigns discovered, time from first submission to analyst confirmation, and lookalike domains found from customer forwards.
Intelligence yield
Indicators not present in your existing feeds, verified by your team. Exportable as CSV or STIX 2.1.
Operational deltas
Call volume, abuse mailbox volume, analyst triage time per week, and account takeover events traced to the pilot stream, before and during.
Coverage and readiness
Registered volume versus your stated volume per source, trust check rejection rate, and an Authoritative Mode readiness review at day 90.
A proposal
The annual contract for your band, with the pilot fee credited, and a plan for the second stream.
Product health targets we hold ourselves to during the pilot
| Metric | Target |
|---|---|
| Reply time, inbound to reply sent, p95 | under 10 seconds |
| Web verify, submit to verdict, p95 | under 3 seconds (text), under 15 seconds (screenshot) |
| Verify code found rate on forwards | above 85 percent with the footer deployed |
| Match rate on legitimate submissions | above 95 percent |
| False Verified (overridden to fraud) | zero tolerated; each one is an incident |
| Registration API p95 | under 150 ms |
| Trust check rejection rate, healthy tenant | under 1 percent |
| Coverage per registered stream | above 90 percent |
Start the conversation
Tell us which stream you would register first and what you would want the pilot to prove.