PROPOSALPREPARED FOR

DATE: JUNE 26, 2026

For

Dealer Program Build Proposal

We build the brand, portals, onboarding, and integrations that turn a licensed administration platform into your dealer program — fast, compliant, and on-brand.

See what we build View the timeline

10–12 wks

to launch

portals

admin app

∞

scale ready

01 — The opportunity

Three audiences. One coherent experience.

Launching a franchise dealer program means three audiences need a great experience at the same time. Dealers need to quote and write contracts in seconds. Agents need to recruit dealers and watch their book grow. Customers need to understand their coverage and file a claim without friction.

The regulated core of all this — the rating, the contracts, and the claims — runs on a licensed administration platform. That is the proven, compliant foundation every serious provider uses. Our role is the layer on top of it: the brand, the portals, the onboarding, and the integrations that turn that platform into your program. We build everything you put in front of your dealers, agents, and customers, and we connect it cleanly to the platform that does the rating and pays the claims.

02 — Program structure

Two layers. A clean line between them.

A complete program is really two layers, and keeping a clean line between them is what makes the build fast, compliant, and predictable.

Licensed

The regulated administration core

Rating and quoting, contract issuance, claims adjudication, commissions, and reinsurance accounting. Licensed from an established platform such as TecAssured or PCMI and backed by your insurer or obligor. System of record for anything regulated.

Your cost with the vendor — separate from this build.

Built by us

The experience & go-to-market layer

Your public brand site, the dealer and agent recruitment funnels, the dealer / agent / customer portals, the onboarding automation, your SEO and AEO presence, and the integrations that tie everything to the licensed platform.

The part your audiences actually see and use every day.

We make a proven platform feel like your brand. We do not rebuild the regulated core — which is exactly where past attempts at programs like this tend to fail.

03 — What we build

Eight pieces. One coherent product family.

Marketing website

Fast, search-optimized brand site. Home, a product page per coverage type, partner section with dealer & agent economics, claims info, about & leadership, contact, and the full legal set including state disclosures. Built for AI search and answer engines from day one — not as an afterthought.

Dealer & agent recruitment funnels

The engine that grows the program. A dealer landing page with a multi-step application, and an agent landing page with its own application. Submissions flow into an approval pipeline and trigger automated follow-up so no lead sits unattended.

Dealer portal

Where dealers run their business with you. Rate and quote, issue contracts, see sold contracts and statuses, view what they owe and remittance history, see commissions, and access a co-branded marketing & training center. Principals manage their own staff logins.

Agent portal

Where agents grow their book. Roster of dealers they manage, submit & track new dealer applications, production rolled up by dealer / product / month, override & commission visibility, and recruitment kits to help sign new dealers.

Customer portal

Where customers feel taken care of. View coverage and contract details, file a claim through a guided flow, track claim status with email + text updates, find a repair shop, manage payments. Card data never touches us — payments run through a dedicated provider.

Internal admin application

Your team's back office. Review and approve dealer & agent applications, publish announcements and marketing assets out to the portals, and pull production & pipeline reporting. Keeps your team self-sufficient.

Onboarding automation

The glue that makes growth feel effortless. Applications land in an approval pipeline, agreements and tax forms auto-send for e-signature, approved accounts provision in the admin platform without manual data entry, and welcome & nurture sequences run by email + text.

Integrations

Everything connected. Live connection to your admin platform for rating, contracts, claims, and commissions. SSO across the site and portals. VIN decoding in the quote flow, repair-network lookup, payment-plan provider for customer financing. Email + SMS for lifecycle messaging.

04 — How we build it

Modern, secure, and built so the regulated core stays the source of truth.

The marketing site is built for performance and search, deployed on a fast global platform so pages load instantly and rank well. The three portals and the internal admin app are built as modern web applications that share one design system, so they look and behave like a single product family.

A secure database handles accounts, applications, documents, and a fast local copy of contract and claims data for display — with strict role-based access so a dealer only ever sees their own dealership, an agent only sees their own book, and a customer only sees their own contracts.

A secure middleware layer sits between our applications and your admin platform. Every call for rating, contracts, claims, or commissions passes through it. This keeps your platform credentials protected, smooths over differences in the platform's responses, and lets the portals stay fast and reliable.

Design principle

Your licensed platform always remains the system of record for anything regulated. Our layer delivers the experience and caches data for speed. If our layer ever pauses, contracts still rate and claims still pay.

Onboarding, document handling, and all lifecycle messaging run through an automation backbone connected to your email and SMS tools, so the program scales without adding manual work for your team.

05 — How we deliver it

Three phases. Launch lean, then expand.

Phase 1~10–12 weeks

Launch

Public site, both recruitment funnels, the platform's own portals branded and connected through SSO, live quote and claim entry points, onboarding automation, and the SEO/AEO foundation. This is the point where you can recruit dealers and write contracts. Everything after this is improvement, not a prerequisite to going live.

Phase 2~8–10 weeks after launch

Branded experience

Custom dealer, agent, and customer portals built directly on the platform's API, so the entire experience feels native to your brand rather than a vendor login. Full onboarding-to-provisioning automation, commission and production dashboards, and a complete dealer marketing center.

Phase 3Ongoing

Scale & optimize

An ongoing AEO and SEO content engine, production and performance analytics, customer payment plans, automated remittance, and new product lines or states as you grow. Naturally becomes a continuous roadmap rather than a fixed project.

06 — Timeline overview

From kickoff to writing contracts in about three months.

Phase	Outcome	Duration
Discovery & setup	Platform access, brand assets, products & states confirmed, architecture locked	Week 1
Phase 1 — Launch	Recruiting dealers and writing contracts	~10–12 weeks
Phase 2 — Branded	Fully owned, on-brand portal experience	~8–10 weeks after launch
Phase 3 — Scale	Continuous growth, optimization, and expansion	Ongoing

The single biggest factor in the Phase 1 timeline is access to your admin platform's developer documentation and a test environment. We request these in week one so integration starts immediately rather than waiting.

07 — What we need from you

Five answers turn this overview into a precise plan.

01Which admin platform have you chosen, or would you like help selecting one?
02Which products and which states are you launching with?
03Do you already have a brand and logo, or is that part of the build?
04What dealer volume are you targeting in the first year?
05Are claims and administration handled by the platform, or in-house?

08 — Where our scope stops

So the boundaries are clear and in writing.

Rate tables, contract forms and language, claims adjudication, insurer and obligor backing, reinsurance and DOWC accounting, and state registrations belong to you, your underwriter, and the admin platform vendor.

We build the experience, the funnels, the automation, and the integration layer on top of that foundation. This boundary protects your timeline and keeps the program compliant.

Appendix

Internal build plan

The detail underneath the proposal — architecture, stack, modules, data model, risks. Shared so there are no surprises about how the system fits together.

A1 — System architecture

One regulated core. Three audiences. A clean middleware seam.

                          ┌──────────────────────────────┐
                          │   LICENSED ADMIN PLATFORM    │
                          │   TecAssured (SmartLink API) │
                          │   or PCMI PCRS               │
                          │   rating · contracts · claims│
                          │   commissions · remittance   │
                          └──────────────┬───────────────┘
                                         │ REST API / SSO / webhooks
                  ┌──────────────────────┼──────────────────────┐
                  │                      │                      │
        ┌─────────▼────────┐   ┌─────────▼────────┐   ┌─────────▼────────┐
        │  DEALER PORTAL   │   │   AGENT PORTAL   │   │ CUSTOMER PORTAL  │
        │  React/Vite SPA  │   │  React/Vite SPA  │   │  React/Vite SPA  │
        └─────────┬────────┘   └─────────┬────────┘   └─────────┬────────┘
                  │                      │                      │
                  └──────────┬───────────┴──────────┬───────────┘
                             │                      │
                   ┌─────────▼─────────┐  ┌─────────▼──────────┐
                   │     SUPABASE      │  │  EDGE FUNCTIONS /  │
                   │ Postgres · Auth   │  │ CLOUDFLARE WORKERS │
                   │ RLS · Storage     │  │  (API middleware)  │
                   └─────────┬─────────┘  └────────────────────┘
                             │
              ┌──────────────┼───────────────┐
              │              │               │
     ┌────────▼─────┐ ┌──────▼──────┐ ┌──────▼──────────┐
     │  MARKETING   │ │     AI      │ │  INTEGRATIONS   │
     │     SITE     │ │ automation  │ │ Klaviyo, Twilio │
     │  + funnels   │ │  workflows  │ │ e-sign, CARFAX  │
     └──────────────┘ └─────────────┘ └─────────────────┘

Any of this software or platforms can be switched out. Everything is customizable.

A2 — Recommended stack

Modern and proven in production.

Layer	Technology	Why
Marketing site	Astro on Cloudflare Pages	Static-first for top SEO/AEO performance, schema markup, fast LCP, content collections for products and blog.
Portals (×3)	React + Vite + TypeScript	One monorepo, three apps sharing a component library and design tokens.
Database / Auth	Supabase (Postgres, Auth, RLS, Storage)	RLS gives clean role isolation. Storage handles agreements, W-9s, marketing assets.
API middleware	Supabase Edge Functions / Cloudflare Workers	All admin-platform calls flow through here. Keeps keys server-side, normalizes responses, handles retries, writes the mirror tables.
Automation	n8n (self-hosted)	Onboarding workflows, document chasing, CRM sync, alerting.
Email / SMS	Klaviyo + Twilio	Recruitment nurture, onboarding sequences, claim status notifications.
E-signature	SignWell or Dropbox Sign	Dealer agreements and W-9s embedded in onboarding.
CRM	Supabase-native pipeline or HubSpot Free	Dealer/agent recruitment pipeline; chosen in discovery.
Analytics	Plausible or GA4 + Supabase dashboard	Marketing analytics plus internal production reporting.
Monitoring	Sentry + Better Stack	Error tracking and uptime across portals and middleware.

A3 — Portal modules

Module-by-module breakdown of the three portals.

Launch-tier shortcut: in Phase 1, Rate/Quote and Claims are the platform's own stock screens — branded and SSO-linked. Custom React versions ship in Phase 2, replacing handoffs one module at a time.

Dealer portal

Rate & Quote
Live rates from the admin platform API (pass-through, never cached as authoritative).
Issue Contract
E-contracting, customer info, signature, payment. PDF stored in platform, reference mirrored.
My Contracts
Searchable list, statuses, cancellations — mirrored via webhook or nightly poll.
Remittance
What's owed this period, plus history. Platform API + cache.
Commissions
Earnings statements from the platform with local caching.
Marketing Center
Co-branded collateral, training videos, sales scripts in Supabase Storage.
Users
Dealer principal manages F&I manager logins via Supabase Auth + RLS.

Agent portal

My Dealers
Roster, status, production snapshot for every dealer they manage.
Dealer Onboarding
Agent submits new dealer applications on a dealer's behalf and tracks approval.
Production Dashboard
Contracts sold rolled up by dealer, product, month.
Overrides & Commissions
Override earnings and statements.
Marketing Kits
Recruitment one-pagers, decks, email templates.

Customer portal

My Coverage
Contract details, coverage summary, term remaining, PDF.
File a Claim
Guided intake submitting into the platform claims API.
Claim Status
Live status with SMS/email updates via Twilio/Klaviyo.
Find a Repair Shop
Repair network lookup if the client licenses one.
Payments
Deep-link or embed to the payment provider — no card data on our side.

A4 — Data model

Core tables, with strict role isolation by default.

organizations

Client co, agents-as-orgs, dealerships

users

Auth users with role: admin | agent | dealer_principal | dealer_user | customer

applications

Dealer + agent recruitment apps, status pipeline

documents

Agreements, W-9s, licenses — storage refs + e-sign status

dealers

Approved dealerships, platform_dealer_id link

agents

Approved agents, platform_agent_id link

contracts_mirror

Read-only cache of platform contracts

claims_mirror

Read-only cache of claim id, contract, status, last update

commissions_mirror

Statements cache

assets

Marketing center files with audience targeting

announcements

Admin-published portal notices

audit_log

Who did what, when — required posture for this industry

RLS enforces dealer-only-sees-their-dealership, agent-only-sees-their-book, customer-only-sees-their-contracts. Mirrors are written by service-role Edge Functions, never directly by client apps.

A5 — Security & compliance posture

Built for the regulated reality this program lives in.

All PII encrypted at rest and in transit. No card data ever stored — payment provider handles it.
RLS on every table. Service-role keys live only in Edge Functions, never shipped to browsers.
MFA available for dealer / agent accounts and required for the admin app.
Audit log on contract-touching and document actions.
Document retention per the client's compliance counsel; their underwriter dictates, we implement.
Backups via Supabase PITR plus weekly export to client-owned storage.
SOW boundary in writing: rate tables, contract language, claims decisions, state filings, and obligor obligations belong to the client and platform vendor.

A6 — Critical-path risks

Five things we watch from day one.

01
Platform API quality
Demand sandbox access before signing Phase 1, or carve out integration as T&M. This is where past attempts most likely died.
02
SSO method
If the platform only supports token handoff (not SAML/OIDC), the seamless stock-portal experience in Phase 1 degrades to deep links.
03
Webhook availability
No webhooks means polling — near-real-time, not live. Fine, but set the expectation upfront.
04
Brand readiness
If there's no logo or brand, add a brand sprint to week 1 and price it.
05
Scope creep into the regulated core
Requests to 'just add a rating rule' get pointed at the platform vendor. The SOW boundary is the shield.

A7 — Week-one checklist

The moment you sign, this is what's already in motion.

Platform decision confirmed (or evaluation sprint scheduled): TecAssured vs PCMI
API documentation + sandbox credentials requested from vendor
SSO method confirmed with vendor
Products, rates loaded by vendor; states list confirmed
Brand assets received (or brand sprint added)
Insurer/obligor + payment plan provider relationships confirmed
Domains, Cloudflare account, Supabase project provisioned
n8n instance + Klaviyo/Twilio accounts confirmed

09 — Adjacent capability

We also build custom home warranty platforms.

The same playbook powering your dealer program applies cleanly to a home warranty line — brand site, plan builder, customer portal, agent recruitment, and an internal admin to run the book. Below is a live example we built end-to-end for Rhino HomeGuard.

Case study

Rhino HomeGuard

Public marketing site, tiered plan builder, customer self-service portal, and a full internal admin with orders, CRM, agents, leads, products and commissions.

Rhino HomeGuard — Plan builder — Plan builder
Monthly/annual toggle, three tiers, transparent coverage lists.

Rhino HomeGuard — Customer portal — Customer portal
Policy overview, quick actions, claims — everything in one screen.

Rhino HomeGuard — Internal admin — Internal admin
Orders, customers, agents, leads, CRM, products and commissions.

Consumer-facing

Brand site, SEO/AEO, plan builder with monthly/annual pricing, checkout, and a customer portal for policies and claims.

Operator-facing

Internal admin for orders, customers, agents, leads, CRM, blog, products, and commission tracking — your team runs the business without us.

Built to extend

Same architectural pattern as the dealer program: clean separation between the admin app, the storefront, and the portal so each can evolve independently.