Evaluation / integrations
No logo wall. Bring the systems that have to move data.
An integration name says almost nothing about direction, ownership, freshness or failure. JTF documents the exact handoff before describing it as supported.
No unsupported connector claim · direction and authority are part of scope
Integration register
Every connection answers five questions.
What is the source?
Name the authoritative system and the exact record being transferred.
Which direction?
Read, write or both—and which side can correct a disagreement.
How current?
Real time, scheduled, manual import or event-driven are different operating promises.
Who authorizes it?
Credentials, tenant scope and user consent are part of the connection, not setup trivia.
What happens when it fails?
The job must expose the failure without silently creating a second version of truth.
Bring these
The first map is your current stack.
Lead sources, call tracking, calendars, measurement vendors, accounting, document tools, material systems and any spreadsheet that still owns a critical handoff all belong on the table. Inclusion here is an evaluation category, not a claim that a named connector already exists.
Final beta · applications open
Bring the stack diagram—even if it is a photo of a whiteboard.
We are accepting roofing operators who will test one real workflow, tell us where it breaks, and help shape the production release.