Why I'm the one signing this.
A short, honest letter about what I built, who it's for, and why a solo founder is a feature, not a bug \u2014 as long as you know which risks that trade-off hides and which it eliminates.
I've been building this for eight months. I haven't taken outside money. I haven't hired a sales team. I haven't chased a demo call with a venture-backed DSO platform so I could co-brand in their deck. I'm one person in Orlando who saw a specific, expensive problem inside every dental practice in this country \u2014 a problem measured in lost revenue per month, not abstract pain points \u2014 and I chose to build a tool narrow enough and deep enough to solve it without the usual SaaS tax.
The problem is patient reactivation. The math of it is uncontested: the average US dental practice loses between 8% and 12% of its active patients every year to broken appointments and lapsed recalls. On a 2,000-patient practice, that's ~180 patients a year \u2014 worth roughly $77,000 in unrealized production at a conservative visit multiplier. Multiply that by the 180,000 practicing US dentists. The leak is bigger than the GDP of several countries.
The leak has existed since the recall postcard was invented. Every dental-practice owner knows about it. Most of them try to plug it with some combination of: the front desk making 20 calls between checkout and insurance verification, a generic tool pushing a quarterly "we miss you" SMS, and a yearly postcard mailer in January. These tactics aren't wrong. They're under-engineered for the job.
Reactivation isn't a message problem. It's a sequencing problem. A single SMS reactivates at 1\u20132%. A dedicated multi-touch sequence \u2014 across email, SMS, phone \u2014 reactivates at 8\u201315%. Same list. Same front desk. Six times the result.
So I built the sequence. Then I built the compliance scaffolding around it, because dental outreach sits at the intersection of HIPAA, TCPA, CAN-SPAM, state dental-board rules, and state anti-kickback statutes. Getting any one of those wrong is a felony or a license issue. I built a PHI scrubber enforced at the database query layer. I built TCPA rate limits (1/day, 3/week per patient) enforced at the dispatcher level, not as a policy you could disable in an admin panel. I priced the product as a flat SaaS fee because Florida \u00A7817.505 and the Patient Brokering Act make per-patient referral fees a crime. That wasn't a marketing choice. It was the only model I could defend to an attorney.
01Why a solo founder \u2014 and why that\u2019s deliberate.
Most dental SaaS is sold by a sales rep who won't remember your name in 90 days. Most dental SaaS is supported by a tier-one help desk that can't fix anything \u2014 they escalate. Most dental SaaS is built by a product team five layers removed from the front desk actually running the tool. The output is a product that works 70% of the time, covers 40% of the jobs, and costs 3\u00D7 what it should because every layer charges a margin.
I'm building the opposite version. Here's what that means concretely, whether you like it or not:
- One throat to choke. Something broken? Email me. I'll reply within two business hours or credit the day. No ticket queue, no "we've escalated it," no Salesforce workflow.
- Weekly changelog. I ship every week. Good week or bad. You can read every change at /changelog.
- Product built narrow, maintained deep. I don't ship features I wouldn't personally support forever. If it's in the product, I own it.
- No upsell team. You won't get a call from an "account executive" trying to upgrade you. You'll get emails from me, and they'll usually be about the Friday report.
- No VC clock. I haven't taken institutional money, so I don't have to chase a 10\u00D7 exit on someone else's timeline. That means I can build what actually helps a 4-chair practice, not what helps a pitch deck.
The honest trade-off: if I get hit by a bus, you'd be in a bad spot for 72 hours. That's why the very first thing in the Trust hub is a continuity plan, a data-export SLA measured in minutes, and written disaster-recovery procedures you can audit. Every risk I can mitigate, I have. I don't pretend the solo-founder risk doesn't exist; I designed the product so it doesn't hold your data hostage the day it matters.
Last year an office manager told me her practice had written off the last quarter's broken-appointment list because "Margaret has moved on." Margaret hadn't moved on. Margaret had switched insurance, missed one follow-up call during her son's soccer season, and then felt too awkward to call back seven months later. One well-timed text \u2014 "we kept your chart, want to come back? \u2014 Dr. Patel" \u2014 brought Margaret back. She was worth $1,840 that year. She's worth ~$650/yr for the next decade.
There are a lot of Margarets. They\u2019re not inventory. They\u2019re not a funnel. They're someone who trusted your practice once and needs a graceful reason to come back. That's the job I'm trying to do well.
02What I'll refuse to build.
I get pitched features every week. A fair share of them I decline. Here's a partial list of the things that will not appear in this product while I'm the one signing the code:
- Per-patient pricing or per-rebook success fees. A felony in Florida and a patient-brokering violation in most other states. The pitch is compelling ("align incentives!"). The reality is regulatory disaster.
- AI that auto-sends to a patient without template approval. "Saves time" \u2014 until it generates a HIPAA violation in a reply to grandma about her crown prep. Drafts, yes. Autonomous sends, no.
- Cross-tenant benchmarking that reveals other practices' data to yours. Every tenant\u2019s data is walled off. Permanently. I'll never ship a "practices like yours" feature that requires learning from your patients\u2019 records.
- A mandatory annual contract. Month-to-month forever, cancel in one click. If the tool isn't earning its month, you shouldn't be forced to renew.
- Dark-pattern retention. No friction on cancel. No "three emails to confirm" flow. Click, done, data exported in under an hour.
I'll update this list publicly when I add to it. You can hold me to it.
03What I'll commit to, in writing.
Written into the Service Agreement. Refundable if I miss them.
- Founder response SLA. Email me during US business hours. Reply in under 2 hours or that day's fee comes off your invoice.
- Data portability SLA. Full export (CSV + JSON) emailed to you in under 1 hour, any time. Miss it \u2014 credit a month.
- Price-lock. Your rate is grandfathered for at least one full renewal cycle on any price change. 60-day written notice.
- 30-day money-back pilot. First 10 practices: if we don\u2019t rebook 10 patients in the first paid month, we refund the whole month.
- Quarterly transparency. Starting Q4 2026, I publish uptime, send volume, refund rate, reactivation rate, and every incident \u2014 good numbers or bad.
04Who this isn't for.
I'd rather lose a wrong-fit customer on the homepage than a month in. So, for clarity, usdpr. probably isn't for you if:
- You're evaluating a 20-feature all-in-one platform and reactivation is the fifth-priority checkbox. Buy Weave. They're great at the 20-feature version.
- You need a fully managed service where a human writes each campaign for you. That's a different company \u2014 a done-for-you agency at ~$3k/mo. Email me and I'll introduce you to two good ones.
- Your PMS is something exotic that's not on our roadmap (we ship CSV import for anything, but if your front desk will mutiny over a weekly export, we're not a fit yet).
- You want a per-rebook success fee. Not legal. Not building it.
05What happens next if you start a trial.
Here's the honest choreography of the next two weeks, laid out in advance so nothing surprises you:
- Minute 1. Stripe Checkout (14-day free trial, no card), HelloSign BAA in your inbox. Sign it \u2014 takes 90 seconds. I don't touch any patient data until it's signed.
- Hour 1. Connect Open Dental direct-REST, or upload a CSV from any PMS. Auto column detect. Your list is ingested, segmented, and queued.
- Afternoon 1. You approve templates. Email campaigns go live that afternoon. First replies usually arrive within 2 hours.
- Day 3\u20135. First bookings get warmed-up and handed to your front desk. You see them on the dashboard, with the full conversation trail.
- Day 14\u201321. Twilio's 10DLC carrier approval lands; SMS layers in automatically. Email keeps running the whole time \u2014 you don\u2019t wait on the carrier.
- Day 7 + Day 14. Friday Report. What was contacted, who replied, who booked, who showed up, what dollar production came through. On your dashboard and in your inbox.
If something in this sequence isn\u2019t working by day 30 \u2014 and you're one of the first 10 practices \u2014 I'll refund the paid month. No phone calls, no exit interview. One click, done. I'd rather have ten practices who are raving fans than a hundred who tolerate us. That math doesn\u2019t even require spreadsheet gymnastics: referral revenue from one truly happy practice beats churn from ten indifferent ones, every quarter.
I'm asking you to try the product, not believe it. Day 14 you have data. Day 30 you have revenue \u2014 or your money back.
06The smallest-possible promise.
If you email me right now \u2014 not a form, not a chatbot, my actual inbox \u2014 I'll reply today. If you need the BAA reviewed before you start, I'll send it to your attorney. If your PMS export scares you, I'll get on a screen-share and pull it with you. If you have an objection about the 10DLC wait, I'll explain the workaround we've engineered (email goes live first; SMS catches up). If it's 11pm, I'll reply in the morning. If you're a practice in Florida and want a coffee in Orlando, I'll buy it.
That's the smallest, most honest thing I can promise: a human who is accountable for this specific product, returning your message, today.
Run the numbers, then try it for 14 days.
If the math doesn't hold up, you'll know by day 14. If it does, you'll have a revenue channel that keeps working. Either way, no card required and one-click cancel.