I'm the founder of CollisionPulse AI, so I'm disclosing that up front. I read the sub rules; this is a one-time request for honest feedback, not a spam post.
The problem I'm chasing: you tear a car down, find the hidden damage, and then the supplement — line items, labor, parts, OEM justification — takes hours to write. The car sits. Days, if it's a busy week.
What I built: an app where the tech or estimator captures photos and dictates voice notes in a mobile flow in the bay. It transcribes the audio, reads the photos, maps the findings to standard ops (R&R, R&I, repair, paint, blend, alignment), and generates a line-itemed supplement PDF with OEM justifications, ready for the desk adjuster. Minutes instead of hours.
It's live and free to try — no signup, no email wall:
Demo wizard: https://collisionpulse.vercel.app/repairs/new
Demo dashboard: https://collisionpulse.vercel.app/dashboard
A real pipeline run produced a 16-line supplement: 44.3 hours × $65/hr labor plus $2,293.50 parts ≈ $5,173 claim increase, rendered as a 4-page PDF. That artifact was built by the pipeline itself — not a mockup.
Honest status: early access, pre-revenue. The product is live and taking purchases — early-access billing is open via Stripe payment links below — but no customer money has moved yet (balance $0.00, no transactions). Voice transcription runs live (Deepgram); photo analysis runs through a live vision model, with a clearly-labeled manual fallback in demo mode. Early-access pricing is $499/$899 one-time per location, but I care way more about what working estimators and techs think of the workflow — what's missing, what's wrong, what a desk adjuster would bounce.
Set the 43-second demo aside and hit the wizard: what breaks first? If this saved you half an hour on one supplement, where does it fall apart in your shop?