About
How we work, and what we won't do.
How we work
Every engagement is structured around defined deliverables, published pricing, and a scope both sides sign. It starts with a scoping call. Then a flat-fee design phase: an operational audit of the teams and duties the work touches, a specification tailored to your organization, and a firm fixed price. If you proceed, the design fee is credited in full against the build. Build follows the Springbrook framework. You approve the testing plan before testing starts, and testing gates go-live. Invoices are triggered by your sign-off, not the calendar. Support continues after go-live. Everything is documented in plain English, and all of it carries a one-year warranty.
What we guarantee, and what we don't
We guarantee technical outcomes: configuration that works as specified, measured directly, attributable to the build. We don't guarantee financial outcomes under a fixed fee. The gains are real, but they usually arrive as higher collections, and collections move for too many reasons to attribute honestly to one build. Adoption matters too: a build nobody uses returns nothing. Financial results get reported honestly. They don't go inside the warranty.
Honest measurement
"$3M of AR released" doesn't mean $3M of value was created. Automation replaced the labor that would otherwise have worked that AR; the honest value is that labor cost, plus whatever would actually have been lost. Attributing gross throughput to a tool is a habit across this industry. We don't do it, and we publish technical and labor measures instead.
How value is realized
When automation frees staff hours, those hours usually go to accounts that never got worked, and collections rise. That gain is real and nearly impossible to prove. Here is how to make it land on a line you control: hire permanent staff until marginal cost approaches marginal benefit. As it does, keep about 10% of revenue cycle staffing outsourced. When automation frees capacity, that buffer is what gets retired - not the permanent jobs of people who were hired expecting a career. It's also the honest answer to where the ROI comes from: a specific line item you control, not a number we invented.
Who we work with
Healthcare in this country is funded largely by public money, and the people who manage it owe something to patients and taxpayers, not just the board. We measure honestly because of that, and we'll tell you the real number even when the inflated one would sell better. If that's what you want from a vendor, we'll get along.
Transparency
We donate 2% of all revenue to organizations serving those with the least.
Consultant compensation is tied to deliverables, not hours.
Founder
Aaron Flenar
Principal Revenue Cycle Solutions Architect
Fourteen years in Epic revenue cycle, including three at Epic in Technical Services, where he co-developed the internal Claims and Remittance certification. Certified Resolute PB. Enterprise Claims and Remittance lead through a multi-state health system merger.
The architect designs it and signs off on every phase.
The design phase is where the fixed fee becomes firm.