What is real, what is estimated, and what depends on you.

No client testimonials, reviews, ratings, review counts, customer counts, client names, logos, awards, certifications, office addresses, statistics, benchmarks, or "as seen in" placements exist on this site that are not supported by a verified, auditable, client-authorized record with a named source and date.

This is not a legal hedge. It is a design rule. Any proof element on this site either has a source recorded in the ShiFt evidence inventory or it does not appear.

A claim labeled or treated as verified means: it is supported by a named, auditable source; it was recorded at a specific date; and the party whose data is used has authorized its publication. Verified claims render with their source and date visible on the page.

As of July 2026, the one published verified case study on this site is the Titan engagement. That engagement's metrics are the only client-specific performance figures currently published.

A modeled estimate is a figure calculated from disclosed assumptions. The calculator and any projected figures on this site are modeled estimates. They are not measurements of actual outcomes. They render with "(modeled)" or "(estimate)" inline on the same line as the figure — not only in a footnote or fine print.

The assumptions behind each modeled figure are disclosed in the methodology page. Any reader can reproduce the calculation from those assumptions.

ShiFt is designed to improve speed-to-lead response, lead qualification, appointment booking, automated follow-up, and revenue attribution. Whether those improvements translate into more revenue depends substantially on factors outside ShiFt's control:

• The quality and competitiveness of the client's offer
• The volume and intent quality of their inbound
• The client's ability to deliver on booked appointments
• Pricing, availability, and service area coverage
• Market conditions and competitive dynamics
• The client's execution of the handoff playbook after transfer

ShiFt does not guarantee any specific revenue outcome. The system is designed to improve the mechanisms listed above. Actual results vary.

The IntentOS™ Map uses two live data layers: storm event data from NOAA (federal public-record) and licensed contractor counts from state licensing registries (state public-record). Both sources are public domain. No scraped, purchased, or proprietary data is used.

Storm data trails approximately 75 days from event to public record. Contractor counts reflect registry status at the last ingest date, not real-time licensing activity. The map renders county- and ZIP-radius-level aggregates only. No per-address data is generated or displayed.

When this site states that clients "own" the system, this refers to the assets listed in the ownership handoff document delivered at engagement completion. It does not mean ownership of the third-party software platforms the system runs on. Those platforms have their own licence terms. What transfers is the configuration, playbooks, data exports, and documented architecture.