How every claim on this site is defined, measured, and labeled.

Every factual claim on this site is classified into one of three tiers before it renders:

The revenue leak calculator on the homepage produces a modeled estimate. It calculates a hypothetical figure from the inputs the visitor enters (inquiry volume, close rate, average job value) and a disclosed time-to-response assumption.

The output is labeled as an estimate. It is not a projection of what ShiFt will deliver, a guarantee of revenue recovery, or a measurement of any actual client result. It is a calculation from the visitor's own inputs, shown to illustrate the math behind response-time economics.

The assumptions behind the calculator are: (1) buyers who receive a response within the first few minutes are more likely to remain engaged than buyers who wait hours — this is a documented behavioral pattern in inbound sales, not a proprietary ShiFt finding; (2) the visitor's stated close rate and job value are taken as accurate inputs; (3) no adjustment is made for seasonal variation, market conditions, or buyer intent quality.

Claims about speed-to-lead response (such as "answers in seconds") describe the designed behavior of the system ShiFt builds — not a guaranteed outcome in every deployment. The system is designed to respond to inbound inquiries via AI-powered automation within seconds of receipt.

Actual response speed depends on: (1) the client's phone and messaging infrastructure; (2) integration configuration; (3) internet and carrier latency; (4) whether the inbound channel is connected to the system. ShiFt makes no representation that every possible inbound channel will be connected or that system latency will be zero in all conditions.

When this site states that clients "own" the system, this refers specifically to the assets listed in the ownership handoff document delivered at engagement completion. The handoff document specifies which automations, integrations, data exports, and playbook documents transfer to the client.

Ownership does not mean the client owns third-party software licences (CRM platforms, messaging tools, etc.) that the system is built on. Those platforms have their own licence terms. What transfers is the configuration, playbooks, data, and the documented architecture — not the underlying SaaS subscriptions.

Any metric in a ShiFt case study is labeled with its evidence status at the metric level. A verified metric means the figure was measured by an auditable method and the client has authorized its publication. A modeled metric means the figure was calculated from disclosed inputs.

No case study metric is rounded up or softened. No client is anonymized in a way that makes them identifiable. No result is characterized as "typical" unless it comes from a set of verified results across multiple clients — which, as of this version of the methodology, ShiFt does not yet have.

The performance of any system ShiFt builds depends substantially on factors the client controls: the quality and volume of their inbound, the clarity and competitiveness of their offer, the pricing and availability of their service, their team's ability to handle the appointments the system books, and market conditions.

ShiFt is responsible for the quality of what it builds. It is not responsible for the client's execution, market position, or business fundamentals. A system that answers in seconds cannot compensate for an offer buyers do not want.

The IntentOS™ Map renders storm activity and licensed contractor density sourced from public-record data: NOAA storm event records and state contractor licensing registries. Both sources are federal or state public-record data. No proprietary or scraped data is used.

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