Evaluation / compare
A comparison sheet that does not grade its own homework.
There is no competitor logo wall here. Use these questions with JTF and every other vendor; keep the answers, evidence and exceptions in the same column.
Vendor-neutral worksheet · claims require inspectable proof
Decision register
The questions that expose where work breaks.
| Ask this | JTF design target | Final-beta check |
|---|---|---|
| Where is the property identity established? | Establish it once, then reference it from each participating system. | Try a correction and verify that no vendor or module creates a competing customer, lead or job copy. |
| What happens when facts disagree? | Keep the source and handoff inspectable; treat disagreement as review work. | Create a disagreement and identify who reconciles exports, integrations and copied fields. |
| Can incomplete work advance? | Require human and evidence gates that can refuse the transition. | Remove required evidence and verify whether a stage change still advances. |
| Does the buyer see maturity? | Publish a declared review status and its boundary for each system. | Require evidence that separates design, prototype, final beta and release-ready operation. |
| Does the site work without spectacle? | Keep buying-critical content in semantic DOM that survives Tier D. | Disable animation and scripts; verify whether the product argument remains. |
Buying rule
Do not accept a green check without its boundary.
“Has an integration,” “uses AI,” “secure,” and “automated” are incomplete sentences. Ask what data moves, which direction, under whose authority, what fails closed and how the claim was verified.
Final beta · applications open
Join the final beta round before production release.
We are accepting roofing operators who will test one real workflow, tell us where it breaks, and help shape the production release.