Client stories
Specific outcomes from LeafHub architecture consultations — including the awkward parts.
Voices from recent engagements
LeafHub forced us to name which parts of our booking system were truly custom and which could stay off-the-shelf. That one distinction saved us three months of side projects.Mara K. — Operations lead, regional clinic network
The health review was blunt about our API sprawl. We did not enjoy hearing it, but the remediation order was clear enough that our contractors stopped arguing and started shipping.Daniel R. — Founder, wholesale inventory app
Our discovery workshop ran long because finance and warehouse disagreed on stock ownership. LeafHub kept the conflict on the board instead of in side chats. We left tired, but with a module map both sides signed.Priya S. — General manager, specialty foods distributor
I wished the advisory had included a sample ticket breakdown for our agency — we had to invent that ourselves. The architecture note itself, though, answered the questions our board kept asking about rebuild risk.Tom H. — Director, community education provider
Extended story: clinic portal rebuild
A multi-site clinic group approached LeafHub after an unfinished patient portal stalled mid-build. Staff had three partial admin screens, two competing identity approaches, and no agreed source of truth for appointments.
Constraints. Budget for one more contractor quarter. No appetite to replace the practice-management system. Patient messaging had to stay inside existing secure channels.
What we did. A three-week architecture advisory: stakeholder interviews, a skim of the incomplete repository, and two diagramming sessions. We recommended treating appointments as owned by the practice-management system, limiting the portal to read models plus a narrow request queue, and deferring payments until identity settled.
Outcome. The clinic paused two half-built features, rewrote the backlog around the agreed seams, and resumed with a single contractor lead. Six months later they reported fewer “which screen is live?” incidents — and noted that early board expectations for a full messaging rewrite had been unrealistic given staffing.
Extended story: wholesale inventory integrations
A wholesaler’s custom stock application had grown five ad-hoc connectors to suppliers. Nightly jobs overlapped; warehouse staff kept paper backups.
LeafHub’s health review ranked connectors by failure impact, proposed a single ingestion boundary, and listed which supplier feeds could wait. The founder later said the mild reservation above still applies elsewhere: teams sometimes want more implementation detail than a review includes. For them, we now flag that boundary in the kick-off so expectations stay honest.
Ready to discuss your application? Request a briefing.