
CRM KitsAuto glass replacement and repair
Who is driving where today.
A technician run sheet for mobile and in-shop glass work, with the glass part and its state on every row, a calibration that stays visible until it is recorded done, and the insurer or fleet behind the job. Clearview brings the run sheet, the parts and the paperwork into one connected workspace.
Read the day down a technician's column.
Jobs group by technician and then by day, each row carrying a six-pane glass diagram, the part state, the calibration chip and who pays.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Run sheet operating view
- Jobs operating view
- Quotes operating view
- Parts operating view
- Calibrations operating view
- Accounts operating view
- Insights operating view
- Three native form drafts and three editable document templates
- Editable per-job checklists and preserved row history
four pipelines
- Glass jobs · 8 stages
- Quote requests · 7 stages
- Insurance work · 7 stages
- Fleet accounts · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- New quote request
- Quote follow-up
- Part ordered
- Part arrival check
- Day-before confirmation
- Calibration booking
- Calibration outstanding follow-up
- Review request
- Fleet account check-in
Inactive until you review and publish them. None send customer messages.
Forms and documents
- Quote request
- Mobile appointment details
- Job feedback
- Glass replacement quote
- Mobile job prep sheet
- Calibration notice
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore 18 fictional glass jobs across three technicians and four days, with six open quotes, eleven part lines, seven jobs needing a calibration and four insurer or fleet accounts. Sample edits stay in memory and reset on navigation or reload.
No sample customers are added to your CRM.
Setup and source
- Guided setup and compatibility report
- Private rollback receipt
- AI-agent guide for customized installations
- Original editable source, configuration, and tests
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set business name, descriptor and default pipeline name. Then sign in and check the workflows and permissions your team uses.
Technical details and compatibility
Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original backend helpers are required for connected record creation, edits, insurer and fleet account records and resource setup. They preserve native account permissions, unrelated custom fields and row history, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
One contact-linked glass job holds the customer and vehicle, an optional VIN last eight reference, the glass position, the part and supplier with its state and promised arrival, the service mode, area and technician, the job day and time window, the calibration state with its partner label, the payer with a claim reference, recorded quote and deductible amounts and an editable checklist. Insurer and fleet accounts are separate records with their own revision guard, archived rather than deleted.
Parts past their promised arrival, calibrations outstanding, quote age and per-account job counts are derived from what staff record. The kit does not look up parts, decode VINs, file insurance claims, drive calibration equipment, route or track vans, take payments or give safety and drive-away-time advice.
Four optional pipeline templates and nine inactive workflow drafts. 18 fictional in-memory examples.
Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.
Get the Auto Glass Kit

DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 270 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
Already a member? Open your downloads.
Questions
How do I receive the kit?
Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.
Does this include Seedly CRM?
You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.
Is this one connected workspace?
Clearview retains its application frame across the kit views and native CRM tools in the same signed-in account. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.
Can I use it with existing customizations?
Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.
Do I have to import all the starter content?
No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.
Can I remove the examples and starter content?
Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.
Can different subaccounts use different kits?
The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.
More automotive & fleet kits
Browse all 220 kits









