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 sells 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. Then the business model changed mid-build, from annual prepay to monthly coverage, and the platform had to change with it without breaking a single money path.

• The monthly coverage model: a recurring coverage fee per truck plus a fixed claim charge per replaced component, capped per 12-month term. Contract terms are frozen onto the policy at purchase — editing a plan never reprices a live agreement — with a 15-day grace period, 30-day termination, and admin reactivation that restores the original term so lapsing can never be used to unlock fresh coverage.
• Full claims lifecycle with money-safe gates: submitted → approved → claim charge and core deposit collected → shipped with tracking → core returned → deposit refunded. Every charge, refund, penalty, and credit is a ledger row; the shipment-release gate reconciles the invoice against the ledger before anything leaves the warehouse.
• Fleet checkout: N trucks in one application, each with its own plan and covered parts — one signature, one payment, one policy per truck, all-or-nothing with compensating refunds on partial card failure.
• Admin-managed catalog: plans, per-plan claimable parts, core deposits, coupons, and a fee-credit switch, all database-driven. Price changes mint immutable Stripe Prices; existing subscriptions migrate at renewal. Referenced products archive, never hard-delete.
• A 20-page admin panel (claims, customers, policies, payments, analytics, coupons, reviews, homepage/terms/privacy editing, editable email templates, team invites), a support-ticket workspace, and customer notifications over email and Twilio SMS.
• Serverless on Netlify: React SPA plus the entire Express 5 API as a single function, Neon Postgres with Drizzle migrations applied at deploy time, strict CSP, rate limiting — with the Express-on-Lambda edge cases (body parsing, real client-IP restoration) handled properly. Customer portal in English, Spanish, and Chinese.

Live at dpsprotection.com on real Stripe billing. The model migration shipped behind a test suite of 2,301 assertions with zero failures and a full end-to-end QA pass against real data on a dev environment before promotion. Pricing, coupons, claimable parts, notification templates, and site content are all self-serve — the client runs day-to-day operations without a developer in the loop.