HIRO MINDS — turning fear into confidence,
one therapy session at a time.

Build a clinic, not just a CRM.

HIRO MINDS started with a clear product mandate: most therapy software was either a glorified scheduling app or an enterprise EHR built for hospitals — nothing that fit the modern child-therapy practice. The founders needed an operating system therapists actually want to open every morning.

Triad Global Solutions joined as the technical lead. Aharon Bilenki took the CTO role end-to-end: architecture, build, hiring, code review, technology decisions. The product had to launch fast, scale to multi-tenant from day one, and hold up under real clinical workflows — not demo sessions.

What got built, in plain language.

1. Patient and family management

Every child treated by a HIRO MINDS practice has a structured record covering intake, demographics, parent/guardian relationships, consent, and treatment history. Therapists update notes after every session — and those notes are immediately searchable, timestamped, and audit-logged for clinical review.

2. Session scheduling + reminders

Calendar layer with per-therapist availability, conflict detection, automated SMS + email reminders to parents, and a no-show tracker that helps practices identify families who need extra outreach. Built to take the manual phone-tag out of running a practice.

3. Treatment plans

Therapists author per-child treatment plans that translate clinical goals into tracked milestones — visible to parents, the supervising clinician, and the billing team. The system enforces required fields by jurisdiction so plans pass insurance review without rework.

4. Therapeutic content + games

HIRO's defining feature: a library of therapy-mapped exercises and games that therapists assign to children between sessions, with progress reporting back to the platform. The technology challenge here was content versioning across languages and regulatory regimes.

5. Billing + insurance

Integrated billing layer that produces clinically-coded invoices, tracks insurance claim status, and reconciles partial payments — designed to fit how multi-region clinics actually get paid. The CFO of any practice using HIRO sees A/R live, not at month-end.

6. Multi-language + multi-region

Internationalization wasn't a v2 — it was a day-1 architecture decision. UI strings, content, treatment plan templates, and even legal disclosures localize per region. The same codebase serves practices in different countries without forks.

7. Multi-tenant from day one

Each practice gets its own logical tenant — its own data, its own users, its own settings — running on shared infrastructure. Tenant-level role-based access control prevents cross-practice data leaks. Critical for a healthcare-adjacent product.

Fractional CTO, full responsibility.

Aharon's CTO role at HIRO MINDS is exactly the kind of engagement Triad Global Solutions offers as a service. Day-to-day responsibilities:

• Architecture decisions. Stack selection, database schema, multi-tenant isolation strategy, the in-house vs build-vs-buy calls. All written down, all defensible.
• Hands-on engineering. Critical-path features still get written by the CTO. The role isn't "advisor with opinions" — it's "engineer who can ship the hard parts when needed."
• Hiring and contractor vetting. Tech screens, JD reviews, contractor selection. The team you have determines what you can build; the CTO owns who's on the team.
• Code review on production-bound work. Every PR that touches patient data, billing, or auth gets reviewed before merge. Not optional.
• Founder partnership. Weekly working sessions with the founders to translate product strategy into engineering reality and back.

What we built it on.

The technology choices below weren't randomized — each one was chosen to optimize for the specific constraints of multi-tenant healthcare SaaS: regulatory readiness, multi-region scale, and fast iteration without sacrificing reliability.

What changed for the business.

• Multiple practices live in production, treating real children with real treatment plans — not pilots, not demos.
• Multi-language deployment from day one means the product can expand to new markets without engineering rework — only content + legal localization.
• The CTO role is fractional but full-stack: HIRO doesn't carry the cost or the hiring burden of a full-time CTO, but every architectural decision is owned by someone with a B.Sc. in CS, ten years of full-stack experience, and skin in the company.
• Aharon's continued role as CTO is itself the strongest endorsement: HIRO has the relationship the founders want, on the terms they can afford.