Warranty Readiness Report shareable
What this book supports, as a one-page report you can send: indicative price ranges, the revenue opportunity across attach scenarios, and a data-quality read. Per-unit rates stay behind the program agreement.
Book risk model inputs concentration · tail · exposure — from your imported repair history
Geographic concentration
Correlated-failure concentration
Aggregate loss exceedance (EP curve)
Active risk signals
Concentration flags from the imported repair history.
Exposure by system
Share of incurred cost in the training history.
Program inputs
Coverage and payment switch instantly — no refit.
Recommended premium
This is your internal number. The quote card is what the homeowner sees — your business name, term options, plain-English coverage, sized for a phone at the kitchen table.
Catastrophe / tail risk §4e
Your whole book’s bad-year risk (not one contract). A Monte-Carlo of annual portfolio losses: expected loss = a typical year’s claims; 1-in-100 cap = the loss exceeded only 1 year in 100; risk margin = the average loss inside that worst 1% minus the typical year — the capital cushion you’d reserve or reinsure against.
Rate-sheet matrix
Labor-only vs bumper-to-bumper premium across every system & brand — grouped by system type.
Upload your book
Your own service history — an export from ServiceTitan, or a spreadsheet. Books accumulate: add equipment first, then repairs, and they link across uploads.
……Manufacturer part-warranty terms
Bumper-to-bumper covers parts only after the OEM's part warranty ends — and that term varies by brand.
Book batches
Every import, with its data-quality read-out.
Warranty analytics BETA
Operational metrics over your live book — contracts in force, claims filed, cost and denial rates. Lights up as real claims arrive.
Warranty cost trend
Cost breakdown
Claims breakdown
Claims frequency by policy
Claims opened per contract in force, by policy.
Covered equipment
Where the loss comes from model input
Decomposed from the imported repair history that trains the model (§4e).
Exposure by category
Share of incurred cost by system type.
Claim mix
Incurred cost by component.
Portfolio & risk
Pick which book to view: the preliminary model (fitted from imported repair history) or your actual book of contracts sold.
Consent pool
Submit experience & consent, then build the shared pool (admin, §4e).
Methodology & model fit §4f · exportable
A full, citeable methodology paper for your book — the actuarial method woven with your actual fitted numbers. View here, or export to share with an actuary, counsel, or a client.
Backtest — predicted vs. actual out-of-time
Fit the model on your history up to a cutoff, then check its predictions against the claims that actually came in after. The strongest proof the model works: it being right on data it had not seen.
Whole-unit lifespan replacement survival
A second install at the same address means the old unit died and was replaced — an observed lifespan. This fits the long-tail ages (10–20 yr) the repair-based curve is thinnest on. Needs a multi-year install history to have replacements to fit.
New contract sell from the book
The model prices the equipment in front of you — brand, capacity, ZIP, age. A SKU is optional: it fills in defaults and shows what your book would have charged, so you can see where the two differ.
Contracts book of business
File a claim against a policy
Pick the policy (type the customer name), describe the problem and its cost. It enters the workflow as Submitted.
Claims adjudication
Submitted → in review → approved / denied → paid → closed. Approved claims feed the model as experience.
Customers
Held from contracts and CRM imports.
Complaints consumer-trust KPI
Complaints arrive by phone, DOI inquiry, or AG referral — channels that leave no trace in the claims table. Log them as they happen: the rate cannot be reconstructed later, and complaints per 1,000 in-force contracts is the first number a state examiner asks for.
Price book contract types & SKUs
The products you sell: family × capacity × efficiency × term, each with its price and the admin/reserve cost split. Contracts are written against a SKU, so premium follows the book instead of being retyped.
Import SKU-based contracts
One row per covered component — several rows share a contract. They're grouped into a contract plus its equipment list, and priced from the book by SKU.
Recognised income & outstanding obligation
Money collected up front is not income up front. Each contract earns along its own expected-loss curve, so this is what you may actually book — and what you still owe in future repairs.
Month-end reserve close what you can take as income
Of the funds you hold, how much must stay reserved for future repairs and unpaid claims — and how much of this period's earnings you may recognise as profit. Decision support, not a statutory reserve; moving money is a separate, human-approved step.
Recognisable over the next 12 months
Book status
What is on risk, and what needs attention.
Contracts that cost more than they brought in
Claims paid against the price collected — the renewal and re-pricing list. Claims are actuals; earned and unearned are modelled, so they are never netted together.
All contracts
| Report Name | Module | Type | Date Range | Created By | Last Run | Rows | |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Go-live readiness checking…
first real sale: sell → collect → claimThe full sell → collect → claim flow is wired. These are the credentials & DNS to switch it on — the unmet items are things to supply, not code to write.
Manage Users & Roles permissions
Define roles with granular permissions, then assign one to each teammate. Members with no role assigned keep full access.
| Name | Description | Edit |
|---|---|---|
| Loading… | ||
They get a link to set their own password. It expires in 14 days.
Your environment public surfaces
Each company has its own branded, tokenized surfaces. Embed the contract form on your website so homeowners can enroll, and share the claim portal link so they can look up their coverage — both land in your workspace.
Security two-factor
Add a second step at sign-in with an authenticator app (Google Authenticator, Authy, 1Password…). Strongly recommended for admins.
Coverages & failure points catalog
The covered-component vocabulary claims are filed against, by equipment class. This drives the claim form's component picker and the failure-point analytics.
Coverage questions service tech
What a technician is asked when filing a claim. Leave the equipment class blank to ask it on every claim.
Email templates notifications
The copy sent when a lifecycle event fires. Edit any of them, or leave the shipped default. A workflow rule with its own wording still overrides both. The contract document email is generated separately — its disclaimer language isn't editable.
Claim workflow lifecycle
The claim status lifecycle and the exact transitions the system enforces — from a new filing through review to approval/denial, payment, and close.
Business profile branding
Your company details — shown on your public forms, emails and invoices.
Localization
Default timezone for dates across the dashboard.
Tax
Whether policies are taxable in your jurisdiction.
Contract configuration
Claim configuration
Provider email notifications
Who receives contract and claim event notifications.
Workflow rules automation
Automate a notification when something happens — e.g. email your ops inbox whenever a claim is denied. Rules fire on lifecycle events.
| Rule | When | Notify | Status | |
|---|---|---|---|---|
| Loading… | ||||
System types lookups
Curate the option lists your team draws from — payout, commission and claim-payment types, and service categories.
Labor rate affects pricing
Your hourly labor rate. A warranty prices the labor you’d pay out, so this scales every model-suggested premium.
Pricing policy affects pricing
Set your markup and how bumper-to-bumper is handled. These apply to every quote — no refit needed for the markup.
Account
Your sign-in and plan.
Payments Stripe Connect
Connect your Stripe account so clients pay you for warranties — funds go straight to you, never through Astrolabe.
Sending contracts to clients (Amazon SES).
Team users & invites
Who can access this workspace. Invite teammates by email — they get a link to set their own password and join.
Access log who did what
Every change made in this workspace, and every time Astrolabe staff opened it. Staff can act inside any account — that is how support and onboarding work — so the control is this record, not the door.
System status platform
What the app can report about itself and the fleet. Server/DB metrics & uptime alerts live in CloudWatch.
Create a company
Provision a new tenant and (optionally) invite its owner — the safe way to onboard a contractor, since open signup is first-come.
Accounts admin
Every company on the platform — its data, contracts, claims, and model status. Switch into any account to work inside it, invite an owner, or grant/suspend access.