DentStream
The acquisition layer of a larger Vertical SaaS platform. DentStream gives any independent collision shop a branded digital presence — capturing estimate leads, digitizing customer intake, and eliminating the phone-tag bottleneck. It's designed to connect downstream to BayOS, an AI-powered shop management layer, completing the loop from lead capture to job completion.
Problem Statement
The Problem
A missed call at 7pm is a lost customer by 8am.
Independent collision shops are built around the bay, not the inbox. When a potential customer tries to reach out after hours, there's nowhere for that intent to land — no intake form, no booking flow, no record the inquiry ever happened. The shops know they're losing business. They just can't see how much.
Existing solutions exist — but they weren't built for this problem specifically. Standalone website and digital intake options run $350–$700 per month, locked inside platforms designed for shops that already have the infrastructure to support them. For an independent operator just trying to stop losing inbound leads, that's the wrong tool at the wrong price.
DentStream was built for the shops left out of that equation — a branded digital presence with self-serve estimate intake, live in under 24 hours, at a fraction of the cost. So the next inquiry has somewhere to land.
Approach
What I Built
Designed and shipped DentStream end-to-end — from concept to live deployment — as a solo PM building with AI-assisted tooling. First shop live in Houston, TX. Currently collecting data — results to be posted soon.
Each shop gets a custom-branded page — their name, colors, and contact info. No generic templates, no shared subdomain.
Customers submit estimate requests with vehicle details, damage photos, and a preferred drop-off date — then receive an on-screen confirmation that the shop will follow up. Closed-loop intake, no phone call required.
Shop owners receive instant email alerts on every new submission. No dashboard login required to get started.
One codebase serves unlimited shops. Onboarding a new tenant takes under 24 hours with zero developer involvement.
Outcomes
Results & Impact
Reflections
What I Learned
- ◆Shops don't have IT teams — zero-friction onboarding is the product.
If setup takes more than a few steps or requires any technical knowledge, independent shop owners won't do it. The product had to be operable by someone who manages vehicles for a living, not software.
- ◆The first real customer teaches you more than any user interview.
Deploying with the first shop surfaced edge cases, workflow gaps, and notification timing issues that no research phase would have caught. Shipping early — even with rough edges — was the right call.
- ◆Multi-tenant from day one forces every decision to be scalable.
Building for one shop is simple. Building so that the second, fifth, and fiftieth shop work the same way — without touching code — required architectural thinking up front that saved significant rework later.
Next Project
BayOS →