ABOUT PEARLY
Pearly is a high-growth B2B SaaS and payments company at a critical inflection point. With deep product-market fit and over 3,000 dental offices across DSOs, groups, and private practices on the platform, we're now looking for builders to help shepherd the next stage of growth.
Because we're lean, you won't be inheriting legacy process or systems debt. You'll be building from a clean slate: leveraging process, technology, and AI in smart, creative ways to accelerate growth and productivity across dental billing, payments, and engagement.
We are a team of high-talent, high-integrity people who genuinely enjoy the art of building and competing; honing our craft and getting better each day, both as individuals and as a team. We care deeply about good outcomes, but just as much about how we get there with smart, passionate people who hold each other to a high standard, move fast, and take pride in the work.
That's what makes Pearly feel different. The caliber of the people and the intentionality behind how we operate.
THE ROLE
You'll own Practice Experience: the app the practice team works in every day, the workflows inside it, and the experience around it from onboarding to daily use. Your users are the people responsible for a practice's financial performance, some living in Pearly for hours a day working a queue of accounts, others, like an owner or a CFO, checking in weekly and needing to know where things stand without digging. And it isn't one customer. It's the single-location office running its own billing, the group or DSO standardizing across dozens of locations, and the outsourced billing company working on behalf of hundreds. You own that arc for all of them without building three versions of the product.
The problems are concrete. A new customer should get live and start collecting in days, not weeks. An RCM manager should be able to set up a payment plan in under a minute without calling support. A balance sitting 60 days past due shouldn't wait for a person to decide to chase it. And a DSO rolling out location 41 shouldn't need the hand-holding location 1 did. Some of those are workflow problems, some are product we haven't built, and some are automation that should have replaced the work entirely. All of them compound directly into collections.
Part of your roadmap exists to win customers and part exists to keep them, and you should know which is which. The metrics you'll answer for are listed below. Senior here means you own it end to end, from discovery through release, without day-to-day direction. The lines around your area are thin on purpose. With a lean product bench, breadth matters, and you'll own features that reach into Payments, Onboarding, and Integrations.
WHAT YOU'LL OWN
Getting Live and Getting Unstuck. Onboarding and support are product surfaces, not someone else's problem. Own what gets configured versus defaulted, how fast a new customer connects their PMS and reaches value, and the in-product guidance that replaces a training call.
Own what staff see when a sync breaks or the data looks wrong, and treat recurring support volume as a product signal to remove the cause.
The Daily Workflow, and Automating It Away. How staff find an account, understand a balance, decide what needs attention today, take action, and trust what they see. The job underneath it is chasing money that's owed across thousands of accounts, usually while the phone is ringing. Make that work faster where a person has to do it, and build the automation and the new products that mean they don't.
One Product, Several Operating Models. A single office, a group standardizing across locations, a DSO with centralized RCM, and an outsourced billing company all need different permissions, reporting, and defaults. Own what generalizes, what stays configurable, and what we decline to build.
Discovery, Craft & Adoption. Run discovery with the people doing the work and the people answering for the numbers. Sit in enough deals…