DPS Protection

Turbos, injectors, and fuel pumps are the parts that kill a trucker's month — expensive, failure-prone, and uncovered once the factory warranty lapses. DPS Protection wanted to sell coverage for them as a subscription, which makes the software the whole business: recurring billing, policy issuance, and a claims lifecycle nothing off-the-shelf models — replacement shipped out, failed core shipped back, deposit refunded on verification.

• Full policy lifecycle: a multi-step application wizard creates a Stripe subscription and a server-issued policy per truck; claims run submitted → approve/deny → shipped with tracking → core returned → refund, with core-deposit accounting at every step and automatic refunds on denial.
• Fleet checkout: a fleet operator adds N trucks to one application, each with its own plan tier and covered parts — one signature, one payment, one policy per truck. All-or-nothing billing with compensating refunds, so a partial card failure can never charge for truck A and silently drop truck B.
• Admin-managed catalog instead of hardcoded plans: pricing tiers and covered-part products live in the database; price changes mint immutable Stripe Prices and existing subscriptions migrate at renewal. Referenced products archive, never hard-delete.
• A 20-page admin panel — claims review, customers, policies, payments, analytics and reports, coupons, customer reviews, homepage/terms/privacy content editing, and team management with email invites — plus a separate support-ticket workspace.
• Serverless deployment on Netlify: the React SPA ships as static assets and the entire Express 5 API bundles into a single function, with Neon Postgres and drizzle migrations applied at deploy time. Strict CSP, rate limiting, and the Express-on-Lambda edge cases (body parsing, real client-IP restoration) handled properly.
• Multi-language customer portal (English, Spanish, Chinese) with dashboard, policies, invoices, claims, and notifications.

In production at dpsprotection.com, taking real Stripe payments. Claims move from submission to core-deposit refund entirely through the admin panel, and pricing, coupons, and site content are self-serve — the client runs day-to-day operations without a developer in the loop.