Field note / Buyer guide
How to make a software vendor prove the sentence after “integrates”
Five questions that turn a logo-wall claim into an inspectable operating contract.
Published 2026-08-15 · public evaluation material
Section 01
A connector name is not a behavior
Ask which record moves, which direction it moves, how quickly it moves, which system remains authoritative and what the user sees when it fails. A credible answer names all five.
If the answer is “two-way sync,” ask how conflicts are resolved. Two systems cannot both be authoritative when they disagree.
Section 02
Test the negative path
Disconnect a credential, remove a required field or present a duplicate. The important behavior is not the happy-path transfer; it is whether the job stops visibly or continues with missing and contradictory data.
Final beta · applications open
Use the note on one real job.
We are accepting roofing operators who will test one real workflow, tell us where it breaks, and help shape the production release.