WarmStart

Free operator tool

Project Warmth Audit

Review the public signals and operating controls that keep a project useful. This tool runs entirely in your browser and stores nothing on a server.

Self-assessment, not an automated crawl. Open your own pages and provider consoles, then answer from evidence. The tool never fetches a URL, signs into an account, or claims to verify your answers.
Canonical homepage and primary CTA work while signed out

Open the canonical host in a private session, understand the offer, and complete the primary CTA to a real next step.

Evidence to save: Final URL, title, CTA destination, timestamp, and expected next-screen marker.
Robots, sitemap, canonical, and internal links agree

Verify real text/XML bodies, canonical host URLs, and no HTML catch-all at discovery endpoints.

Evidence to save: Status, MIME, parsed body, canonical tag, and sitemap URL sample.
A clean-session visitor can complete the conversion outcome

Run the path far enough to verify the account, submission, booking, report, or other promised result.

Evidence to save: Controlled input, final artifact or durable record, and completion timestamp.
Source and content context survive through activation

Follow a tagged link and inspect first-party or analytics events at signup and the first meaningful product action.

Evidence to save: Event payload with source, medium, campaign, content, slug, cluster, and activation identity.
The public support path reaches a named owner

Send a safe labeled message from outside and verify arrival, assignment, response ability, and escalation.

Evidence to save: Redacted message or ticket ID, timestamps, owner, and queue state.
Payment and entitlement state reconcile

Use test mode for success/failure and verify signed, idempotent events plus application access.

Evidence to save: Test event ID, processing receipt, application state, and expected entitlement.
The smallest representative task delivers its final artifact

Test the product promise beyond the button click and include a recoverable failure path.

Evidence to save: Input fixture, final artifact or changed state, version, and timestamp.
Critical systems and recurring tasks have primary and backup owners

Cover domains, deploys, payments, support, analytics, email, social, data, and recovery.

Evidence to save: Dated ownership register and controlled access procedure, without copied secrets.
A backup operator can follow a tested recovery card

Rehearse one controlled scenario and confirm detection, decision, safe mode, restoration, and communication.

Evidence to save: Scenario, exercise date, result, gaps, and corrective actions.
Every green status has a current, reviewable receipt

Receipts state check, environment, source, timestamp, expected outcome, observed result, and owner.

Evidence to save: Sample receipts plus exact blockers for failed or unavailable verification.

How the score works

Each check is weighted by consequence and recovery cost. “Yes” earns full weight, “partial or unknown” earns half, and “no” earns zero. The result is a planning aid, not a guarantee of availability, security, growth, or search indexing.

No benchmark claims

Version 1.0, dated July 13, 2026, does not compare your answer with other companies. WarmStart will not publish benchmark bands until there is a documented, privacy-safe sample and methodology.

What to do next

Save a timestamped receipt for every yes. Turn each partial or no into one owner, one next action, one evidence requirement, and one review date. Then add the project to WarmStart if you want the routine visible in LiveOps.

Add the project to LiveOps