Import a CCC ONE estimate
Upload a CCC ONE estimate PDF, an insurer's for example, and get an editable estimate. Run the audit on it to build your supplement.
Photos, a VIN or fault codes in; an itemized repair estimate out, priced on your own labor rates. Then a built-in audit checks every line for the work estimates usually leave off.
No card to start: create and edit estimates free, pay only when you send one.
Missed operations are money a shop has already earned. These features look for them.
78 built-in rules, drawn from the SCRS Guide to Complete Repair Planning, DEG rulings and the estimating systems' own not-included notes, check every line for commonly missed operations: scans, calibrations, blends, R&I for access, refinish prep, fluids and small fees.
Each suggestion is priced on your rates and says why it's owed.
It suggests; your technician picks what goes on. Nothing is added by itself.
Every estimate with a VIN is checked against NHTSA's recalls, manufacturer service bulletins and special coverage. The ones that touch a line you're repairing come first, flagged on the part.
The sample HHR shows 4 recalls, among them GM's ignition-switch recall, plus 8 special-coverage programs and 21 bulletins.
Upload a CCC ONE estimate PDF, an insurer's for example, and get an editable estimate. Run the audit on it to build your supplement.
The vision model finds damaged parts, severity and repair or replace, with a cropped evidence photo on every line.
Price from DTCs when there's no visible damage, or write a manual or paint-only estimate.
Year, make, model and trim, plus the factory ADAS and safety equipment, so calibrations aren't a guess.
Set your body, paint, frame, mechanical and diagnostic rates once; every estimate prices on them.
Pair a phone to the desktop and take the photos with it; they land on the estimate.
Each technician gets a login that sees only your shop's estimates, and signs off the estimates they review.
An itemized, claim-ready report with labor, parts, ADAS lines, photo evidence and your logo.
A customer who started an estimate online gives you its Ref # or VIN and their phone number; you open it in the shop.
A free, no-signup estimate widget for your own website; the leads come to your shop.
Free to generate & edit — pay only when you're ready to download a PDF or mark an estimate reviewed.
A set number of estimates each month for one flat rate, for shops running estimates every day.
Switch between plans anytime from your own Billing settings.
Photos, VIN, or fault codes — whatever the vehicle gives you.
AI identifies damage and severity; you confirm and refine.
The audit lists what's commonly missed; you pick what belongs.
A signed, itemized PDF ready for the customer or the claim.
Pricing is pay-per-estimate, or a flat monthly subscription that covers a set number of estimates each month — see the Pricing section above. There's no setup fee, and you can switch between plans anytime from your own Billing settings.
Yes — once you register your shop, you can add technician sub-accounts from My Technicians. Each technician gets their own login and only ever sees your shop's own estimates, never another shop's data.
No — Estigator is focused specifically on generating itemized, priced repair estimates from photos, VIN, or OBD fault codes. Many shops run it alongside their existing management software just for estimating.
The vision model identifies damaged parts and prices them against real state labor rate cards and live parts sourcing — a strong first-pass estimate. Every estimate is fully editable, and a technician can add, remove, or correct any line before it's finalized.
Yes — the PDF report is built in a claims-familiar format (vehicle & claim information, labor rate card, itemized damage assessment, parts & paint materials) and can be reviewed and signed off by a licensed technician before it goes out.
Ask where to find a setting, why an estimate looks a certain way, or which estimate type to use.
| Shop | Generated | Paid | Unpaid | Last generated |
|---|
Once you've changed something here, use Regenerate Estimate in the bar at the bottom of the screen.
Every estimate is stored permanently, so it can be found and reopened at any point — most importantly for the supplement workflow: a fault-code-only estimate can sit for days waiting on a technician's physical diagnosis while other vehicles are worked on. Find it, open it, confirm the diagnosed codes, and save.
| Estimate ID | Vehicle | Claim / VIN | State | Grand Total | Status | Source | Last Updated | |
|---|---|---|---|---|---|---|---|---|
|
Search for an estimate
Click Search to browse everything, or filter by ID, vehicle, or
state.
|
||||||||
A towing company, glass shop, attorney, or other referral source. Each partner gets a unique link and QR code that drives traffic to the self-service wizard — estimates generated through it are attributed back to this partner.
How much a referral partner earns for the paid estimates their link/QR code generated. Exactly one mode is active at a time — switch the dropdown below to change which. The computed amount shows in the Referral Partners table underneath.
Loading…
A workshop-management platform embedding Estigator's estimation as a plugin inside its own product — its own client orgs and end users, not a `users` account here. Identified by an API key instead of a slug; the raw key is shown exactly once right after creation (or after a rotate), never again.
Loading…
The software's own name, logo, and browser-tab icon — shown across the Workshop header, login screen, landing page, and (once you configure the same via customer-portal-web) the public wizard. Distinct from PDF Branding, which is your shop's own business identity printed on the generated estimate document itself.
The public FAQ shown on Estigator's own landing page (before anyone logs in) — a prospective shop owner's questions ("what does it cost," "can my techs have logins"). Distinct from Workshop Help Guide Content below, which is staff-only and shown after login.
FAQ, Getting Started guide, Terms, and Privacy content shown to shop staff (any logged-in role) in Workshop's own Help tab — a genuinely separate content domain from the customer portal's own Site Content, which customers see on the self-service wizard, not staff.
Estigator's own From Address, support routing, and (optionally) a fully separate mail server or Resend account for Workshop tenant emails (account verification, technician invites) — separate from the Customer Portal's own Email & Notifications settings, which are EstiNow's. Leave the SMTP/Resend sections below blank to keep sharing Customer Portal's provider — only fill one in if the From Address above uses a domain that provider isn't authorized to send as (see the note below). If both SMTP and Resend are filled in, SMTP is used first.
Estigator's own Stripe/PayPal credentials and pricing for Workshop tenant billing (per-estimate charges, credit packs, subscriptions) — separate from Customer Portal's own Payment Providers, which are EstiNow's. Register each webhook address below in the matching Stripe/PayPal dashboard — shown here whether or not it's configured yet, so you can double-check an already-registered endpoint points at the right place.
Estigator's own Google OAuth Client ID for the "Sign in with Google" button on Workshop's registration/login screens — separate from Customer Portal's own Client ID (Customer Portal → Payment Providers), which powers a genuinely different consent screen. Use a Client ID from an OAuth consent screen configured with Estigator's own app name and logo, not EstiNow's.
Estigator's own default company details, logo, and regulatory IDs shown on a Workshop-generated PDF — only used when a self-registered shop tenant hasn't configured its own branding under My Workshop. Separate from Customer Portal PDF Branding below, which is EstiNow's. Watermark text, legal disclaimers, and footer text are shared platform-wide policy, not brand identity — edit those on Customer Portal PDF Branding regardless of which surface generated the document. Public Base URL below is NOT shared with Customer Portal's own copy — Workshop is reachable at a genuinely different domain, so it needs its own value here.
Configure the company details, logo, and watermark that appear on every self-service wizard (Customer Portal / EstiNow) PDF estimate — separate from Workshop PDF Branding above, which is Estigator's own. Watermark/disclaimer/footer text here also apply platform-wide (shared policy, not brand identity), regardless of which surface generated the document.
| State | Rate Status | Body $/hr | Paint $/hr | Mech $/hr | Supplies $/hr | Parts Tax % | Source / Date | |
|---|---|---|---|---|---|---|---|---|
| Click Refresh to load | ||||||||
| Username | Role | Contact | Status | Created | |
|---|---|---|---|---|---|
| Click Refresh to load | |||||
Actual Cash Value lookups (used for the total-loss threshold) fall back through three tiers: paid vendor APIs below, then a generated depreciation table, then a static estimate. Vendor API keys are never displayed once saved — only a short suffix, so you can confirm one is set.
Replacement-part price lookups (the eBay-sourced quote on REPLACE lines) are gated per calling surface the same way ACV Tier-1 is — a shop can allow a paid parts vendor for Workshop estimates while keeping the Public kiosk on the free vendor. Only eBay has a live backend today, so both toggles currently have no effect — they're ready for when a paid vendor (e.g. a dedicated used/LKQ or OEM-dealer-network API) is added.
VIN decoding runs through a local NHTSA vPIC-backed microservice. It decodes locally first and falls back to a configurable third-party vendor when needed. The connection settings below are this app's own — the vendor's own API key/URL live on the decoder service itself.
Which vision model answers a damage-analysis request (photo intake — Photo Analysis mode, and the self-service wizard). Scope is damage analysis only — part-crop photo grounding always stays on the local GroundingDINO pipeline and is unaffected by this setting.
The Audit estimate button (estimate edit view → Technician-Added Items) checks every line of an estimate, including estimates imported from a CCC ONE or Mitchell PDF, against these rules and suggests the operations that are missing. Each rule reads: when the estimate has this, it usually also needs that. The built-in rules are starting figures: change their hours and prices to your shop's, switch off the ones you don't use, and add your own.
A rule has three parts: when it applies, unless the estimate already covers it, and what line it suggests.
windshield, front bumper, frt bumper. Add the short forms
estimators type (Frt, Rr, LT, RT, Qtr, Bpr): imported estimates use them.door, but not
handle, mirror, glass.urethane, adhesive kit. List every way people write
it, or the audit will suggest work the estimate already has.Matching: capital letters and punctuation are ignored, and a word matches from its
start, so calibrat matches "calibration" and "calibrate", and door doesn't
match "indoor".
Example: when parts = windshield, windscreen and
operations = replace, unless urethane, adhesive kit, add a part cost of
$65: "Urethane / adhesive kit".
Use Try on an estimate in the editor to see what a rule finds before you save it.
Shop/insurer business rules for estimate money math — applies to every estimate on every surface (Public kiosk and Workshop alike), not gated per surface like ACV/Parts.
Controls how confident the grounding model (GroundingDINO) must be before a per-part AI-cropped photo is shown on an estimate. Real-world testing found no single value cleanly separates correct crops from wrong ones — a low floor lets some confidently-wrong photos through, a high floor can suppress nearly all crops. Tune this based on real estimates as they come in; takes effect on the very next estimate generated, no restart needed. Not gated per surface — applies identically to Public and Workshop.
Stripe and PayPal configuration for the separate customer-portal (Angular + Node) app — this app never stores these values itself; every save here is proxied live to customer-portal-api over the internal service network. Takes effect on that service's very next request, no restart needed.
How and where this app sends customer/admin email — provider config, the shared From Address, link-building base URL, and support routing. Proxied live to customer-portal-api, same as Payment Providers above.
Pay-per-estimate and subscription pricing for the self-service consumer wizard, both admin-configurable. Proxied live to customer-portal-api, same as the other Customer Portal tiles. For what a registered workshop tenant pays instead, see Workshop Pricing under Pricing & Vendors.
Webhook signature failures, fulfillment errors after a payment already succeeded, and synchronous PayPal-capture failures — recorded with enough detail (event/order id, the affected estimate, a truncated stack trace) to actually debug, not just "something failed".
Customer-reported issues — exhausted regenerate attempts, general "Report an Issue" submissions, plain data-error reports, and generation failures — each carries a tracking code and, for a guest, a contact email. Processing a refund (generation failures only) charges nothing new; it reverses the original report-unlock payment via Stripe/PayPal directly.
Browse past vision-sourced estimates — photos, VIN/vehicle specs, OBD fault codes, and per-part damage/disposition labels — to curate a dataset for fine-tuning the vision model. Select rows and export a zip (original photos + a manifest.json of the labels). Filter to "Reviewed only" for technician-corrected labels, the higher-value signal.
Sends a message that appears in every recipient's notification bell — and, for Maintenance/Urgent severity, also as a one-time banner across the top of their screen.
Name/logo/favicon shown to customers on the self-service wizard (customer-portal-web, estinow.com) — separate from App Branding's Workshop-internal identity (estigator.com).
On/off switches for optional customer-facing features, plus Google Sign-In — folded in here rather than given its own tile since it's a single field, not really payment/email/ pricing. Toggles below are proxied through a curated view of the Customer Portal's own config (not a second copy); Google Client ID is saved via the same general settings endpoint the other Customer Portal tiles use.
Edit the text shown on the public FAQ, Terms of Service, Privacy Policy, and Refund
Policy pages — changes go live immediately, no deploy needed. This is a plain text
editor, not rich formatting: for Terms / Privacy / Refund Policy,
start a new section with a line beginning ## (e.g. ## 1.
Refunds), and separate paragraphs with a blank line. For FAQ,
start each entry with a line beginning Q: and its answer on the next
line(s) beginning A: (an answer can span several lines — the next
Q: line starts a new entry). Reviews is a real list
editor below instead of raw text — add/remove entries directly, each with a name,
star rating, and comment. Manually-entered reviews here are shown, with the name as
typed, alongside real customer feedback in the landing page's "Reviews (N)" dialog —
a real customer's own submitted feedback shows their own typed name if they gave one,
otherwise "Verified Customer".