A CRM for selling vehicle service contracts, with the consent trail attached.

The warranty and service contracts pack

What the pack adds

None of this exists yet. It is written down so you can judge whether it is the product you want before you spend a minute on it.

• Contract register

  In build

  Contracts as records with term, deductible, vehicle and mileage, priced once and never recomputed from the browser.

• Installment schedules

  In build

  A 24, 36 or 48 month contract billed on a schedule, with what has been collected reported as revenue on the date it landed.

• Expiry and renewal triggers

  In build

  The expiring contract is the next sale. Triggers ahead of the date, born switched off, deduplicated per contact.

• Seller scorecards

  In build

  Contracts sold, value and close rate per seller against a goal, from the same rows the revenue report reads.

• Consent and STOP records on the contact

  In build

  What each contact agreed to, when, and through which form — displayed on the record rather than buried in a log, because this is the part that gets audited.

Without the pack

Available today on the platform

These are live today, and they are described in the words this trade uses rather than rebuilt for it: the platform every workspace runs on, not the warranty and service contracts pack. The pack is the list above and none of it exists yet.

• Cost per sale, against the spend you enter

  Live

  Enter what each source cost you in a month; the marketing report sets it against the leads, the customers and the revenue that source actually produced, pro-rating the month still running rather than pretending it is over. A channel that produces calls and no sales shows up as exactly that.

• What the buyer actually submitted, kept unedited

  Live

  Every form submission and inbound delivery is stored exactly as it arrived — fields, source, campaign and landing path — beside the lead it became. The lead row is edited by people; that record never is. Deliveries that were refused are listed too.

• A priced quote accepted, and the agreement signed online

  Live

  Packages and add-ons become a branded page the buyer accepts, and the acceptance is what generates the agreement to sign and the payment link. It is your agreement, not a service-contract register: term, deductible, vehicle and mileage as fields are in the pack.

• Pipeline and CRM

  Live

  Every prospect in one board from first contact to sold, with the buyer, the notes and the source that produced them on the record. Nothing here dials anyone.

• Invoices and Stripe pay links

  Live

  A down payment or a paid-in-full sale becomes a Stripe pay link, confirmed by Stripe's webhook rather than by the buyer's browser reaching a success page. Installment schedules are a pack surface and are listed above as unbuilt.

• Client portal under your name

  Live

  One private page per buyer for their paperwork, invoices and status, carrying your name rather than ours.

• Follow-ups that run without you

  Live

  Rules and templates on a nightly engine, not a dialer: a prospect who has gone quiet is nudged at two, five and ten days and closed at fourteen, and an unanswered quote expires. Same input, same message, every time.

• Unsubscribe, consent and suppression

  Live

  Every commercial email carries a working unsubscribe link and your postal address. One click writes three things — a suppression on the address, a revoked consent record naming the method and the evidence, and a flag on the contact itself — and every send checks the suppression before it goes. This is the part that gets audited.

• Reports that reconcile

  Live

  What was collected, net of tax, on the day it landed in your workspace's timezone — one definition of revenue, read by every report that says the word.

• Where the work comes from

  Live

  Nightly rollups attribute leads and revenue back to the source that produced them, first touch and last, so a channel that produces calls and no contracts shows up as exactly that.

Questions

What buyers ask

Is there an incumbent CRM for this?

Not for small sellers. Agency CRMs assume carriers and policies, and generic CRMs have no idea what a term or a deductible is. That gap is the reason for the pack.

Is there a dialer?

No. No dialer, no power dialer, no purchased lists, and none planned. Outbound is a source in the pipeline and a compliance surface. A dialer is a different product with different obligations and it is not this one.

How do you handle TCPA and 10DLC?

Consent state per contact, STOP honoured across every send path, a working unsubscribe link and a postal address on every commercial email, and a suppression list that no automation can route around. Carrier registration for texting is yours; until it exists, texting stays off.

Do the numbers reconcile with what actually landed?

That is the design. Revenue is what was collected, net of tax, on the day it was collected in your workspace's timezone — the same definition the seller scorecard and the source ROI report read. One number, one source.

When does it ship?

Phase 4, alongside the insurance pack. No date promised. The waitlist gets the build notes first.

What can I use today?

The general platform listed above — pipeline, invoicing, portal, follow-ups with unsubscribe and suppression, reports and attribution — plus cost per sale against the spend you enter, the raw submission kept beside every lead, and a priced quote the buyer accepts and signs online. The contract, installment, expiry and seller surfaces are not built yet.