Our approach
How It Works
Four steps, each one small enough to judge on its own. We map before we build, and we charge before we go deep — both for the same reason.
MaxPower Labs maps a workflow before designing anything. A platform build runs nine to twelve weeks across six milestone phases — discovery and configuration planning, data layer and first board, remaining boards and automation, client testing and sign-off, go-live and training, then post-launch support — and the client signs off on each phase before the next begins.
Process archaeology
Before anything gets built, somebody sits with the person who actually runs the workflow and writes down what they really do.
Not what the org chart says. Not what the process document from 2019 says. What actually happens on a Tuesday when a regional-center referral arrives as a PDF attached to an email from a case manager who has spelled the client’s name two different ways, the authorization number is in the body of the email rather than the attachment, and the only person who knows which supervisor signs off on that report type is on holiday.
We map every stage, every handoff, every approval, every workaround, and every point where the same information gets typed into another system. Then we cost it — in hours, at your loaded rate, using your numbers.
Two things reliably come out of this. First, the operational lead usually says nobody has ever asked them to explain their job before. Second, the money turns out to be somewhere other than where everyone assumed.
Why we charge early
Free is 30 minutes. After that, the first dollar moves before the deep-dive does.
Unpaid discovery sounds generous and works badly. It teaches a prospect two things that are not true — that our time costs nothing, and that the work is easy, because a prototype appeared without an invoice. Then a real number arrives at the end and it reads as a cliff rather than a price.
The ladder removes that. Each step is small, each has a price published on this site, and each earns the next. By the time a large figure appears, you have already seen its components and watched us work twice.
It also protects your time. A paid two-week assessment gets our full attention and a fixed deliverable date. Free discovery gets whatever is left after the paying work is done — that is true of every firm, whether or not they say so.
A $3,000 assessment you decline in week one is a better outcome for both of us than a $60,000 proposal that dies in month four.
A platform build, end to end
Nine to twelve weeks, six phases, you sign off on each
Nothing moves to the next phase until you have accepted the last one. It is not finished until you say it is.
Discovery & configuration planning
We finalise the schema, confirm which workflows are in scope, and agree what “done” means for each one before a line of anything is written.
Data layer & first board
The foundation, plus the flagship workflow that everything else inherits from. You see something real early, because an abstract plan is impossible to give useful feedback on.
Remaining boards & automation
The rest of the workflows, the privacy engine, intake forms, notifications and reporting. Delivered module by module, tested as each one lands rather than all at the end.
Your team tests it
Your people use it against real scenarios and tell us what is wrong. We fix it. Silence is not acceptance — we need an actual yes.
Go-live & training
Your active records move across, staff are trained by role, and we enable an internal superuser so you are not dependent on us for routine changes.
Post-launch support
Two weeks of close attention while real work flows through the system for the first time. Then Platform Care begins.
What makes this different
Three commitments that are unusual enough to be worth naming.
We map before we sell
You get a written picture of your own operation before you are asked for a large decision. If a practice takes the map and fixes things itself, that is a fine outcome and it costs you nothing.
It stays in your tenant
No MaxPower Labs cloud your patient data gets copied into. Your Microsoft 365, your BAA, your admin control, from the first day to well after the last invoice.
Every price is published
You will never receive a quote from us containing a number you have not already seen on this website. The negotiation is about scope, never about what we felt like charging.
Practical questions
How much of our time does this take?
The deep-dive is the heaviest part and it is roughly a day of your operational lead's time, plus short follow-ups. After that we work asynchronously and send a recorded update each week rather than booking a standing meeting. Your team's testing phase needs a few hours across a week. We deliberately design around the fact that nobody in a practice your size has spare hours.
Do we have to change how we work?
As little as possible, and that is a design principle rather than a courtesy. The reason we map before we build is so the new system matches the workflow your team already has in their heads. If we hand you something that requires retraining everyone, we have failed, no matter how good the software is.
What if the roadmap says we should do nothing?
Then it says that, and we will tell you so plainly. You keep the risk analysis, the inventory and the policy, which are worth having regardless, and we part on good terms. We would rather be the firm that told you the truth than the firm that sold you a platform you did not need.
Who actually does the work?
MaxPower Labs is your contracting party and your single point of accountability throughout. Discovery, architecture, requirements and quality verification are ours. Build work is sometimes performed by a subcontractor under a signed BAA, working against dummy data, which we tell you before you ask.
Start with the free half hour
Bring one workflow — the one that annoys you most. We’ll map it on the call and tell you plainly what we’d do, what it would cost, and whether it’s worth doing at all.
30 minutes with Paul Tran, who runs every one of these calls. Evening slots available — we know your day is patients. · paul@maxpowerlabs.ai