Founding Pilot Scope

A controlled first deployment of Revenue Recovery.

The pilot is designed to validate whether Jaynus surfaces useful stalled opportunities inside an operating roofing pipeline—without requiring a CRM migration or immediate automated homeowner outreach.

Current native pilot connector: AccuLynx. Roofing companies using another CRM may still submit digital qualification; connector or approved data-access fit is confirmed before payment.

Included in the pilot

✓
Read-only CRM connectionJaynus monitors supported CRM data without changing customer records during the initial pilot.
✓
Revenue Recovery rulesLead and estimate inactivity thresholds are configured around the contractor's operating process.
✓
Recovery priority queueOpportunities are ranked by workflow urgency, stage, inactivity, observed estimate value, and contactability.
✓
Owner operating viewJaynus Command surfaces exceptions, payment status, onboarding state, and system health for supervision.
✓
Digital onboarding and supportThe normal workflow is online. A sales call is not required to enroll or receive routine support.

Not included by default

—
No guaranteed recovered revenueJaynus prioritizes workflow review; it does not guarantee a close, revenue amount, or conversion rate.
—
No automatic customer messaging on day oneOutbound automation is introduced only after the workflow is validated and approval rules are defined.
—
No forced CRM replacementThe product is designed to sit around the existing system when that system remains the source of truth.

Digital onboarding

Qualification

Submit company and pipeline information online.

Approval and checkout

If the pilot fits the current workflow, the implementation payment path is opened digitally.

Secure connection

The contractor connects the supported CRM through the private credential workflow—not through the public website.

Rule configuration

Jaynus applies initial recovery thresholds and verifies the resulting queue against the real operating process.

Monitoring

The owner supervises exceptions while the system handles repeatable monitoring.