The system a home warranty company runs its sales floor on, from the first call to the agent’s commission.
A multi-tenant CRM and contract platform for a home and auto warranty seller: lead intake, qualification, plan pricing, card and financed payments, verification, partner transmittals, commissions and payroll. It replaced a legacy CRM and is in daily production use.
- Category
- Sales and contract operations
- Platform
- Web, desktop-first
- Scope
- Leads to payroll
- Status
- In production, daily use
What we built.
The client sells warranty contracts over the phone. Every sale runs through a chain most CRMs do not model: an agent claims a lead, captures the home and its appliances, configures a plan with coverage items and surcharges, takes a down payment on a card or sets up financing, hands the contract to a verifier, and only then does a commission exist. The legacy system held that chain together with habits. We rebuilt it as one system.
Neeka Studio designed the architecture, the permission model and the payment system, and built it. The first production release went live with the legacy data imported, and it has shipped continuously since: more than 900 migrations, 300-plus tables, over a thousand pull requests.
The first sales team runs on it today while the last integration lands, ahead of a rollout to around fifty agents across California and Texas, plus the finance, admin and customer service operators behind them.
The hard parts are the ones you cannot see in a screenshot. Money is stored in cents, never floats. Every payment operation is idempotent behind a lock. Card processing routes across multiple merchant gateways with automatic failover, because one processor is a single point of failure for this category of business. Commission and bonus calculation moved out of database triggers into explicit, testable server actions once triggers proved impossible to debug. Row-level security enforces an organization, sub-organization and team hierarchy with per-user overrides, so a superadmin, a finance clerk and a sales agent each see exactly what they should.
- Lead intake from CSV import, ads, referrals and inbound calls
- Home and appliance inventory on every customer record
- Plan pricing with coverage items, surcharges and discounts
- Cash and financed deals with down payments and payment schedules
- Direct card processing across multiple gateways with failover
- PIN-verified contract verification workflow
- Commission matrix, volume bonuses and payroll export
- Automated transmittals to finance and fulfillment partners over SFTP
- Next.js on AWS Amplify
- Postgres on Supabase: row-level security, GraphQL, job queues
- Deno edge functions for SFTP transmittals and scheduled runs
- First Data and Authorize.Net merchant gateways
- Bank account validation and card tokenization
Still shipping. Still theirs.
This was never a 30-day proof and was never sold as one. It is an ongoing engagement, priced monthly, where the client has owned the repository, the infrastructure and the data from the first commit. That is the same deal on every engagement, whatever its size.
- A multi-tenant web application with role-based access and row-level security
- A payment system with idempotent operations, card tokenization, void and refund
- Contract PDF generation and purchase confirmation email
- Bank account validation and routing-number lookup
- A public REST API with an OpenAPI spec for partner integrations
- Admin tooling: plan management, commission rules, payment providers, access logs, exports
- Edge functions and scheduled jobs for transmittals, financing runs and exports
Ready to run on a system that fits?
If you have crews, customers, and a process that off-the-shelf keeps fighting, let's talk. One call. Thirty minutes. We'll tell you straight whether a 30-Day Proof is the right fit, or whether an off-the-shelf tool is.