The Story
It starts at Ball State University, where two mirror twins earned landscape architecture degrees before pivoting — together — to Computer Science. They taught the same grad-level courses as assistants while finishing their Masters. It was the first version of a pattern that's defined their careers ever since: same path, same instincts, same problems catching their attention.
From Ball State, the path wound through an architecture firm, then Ontario Systems, then J2 Interactive doing healthcare consulting, and eventually enterprise health networks in New York. Two decades of learning how complex systems actually behave — not in theory, but in production, under pressure, with real consequences. Along the way they learned something most integrators never do: the technical problem and the design problem are the same problem.
The Problem They Solved in Healthcare
Healthcare is unforgiving — not just technically, but architecturally. A hospital has 50 different systems holding different pieces of the same patient story. Getting them to work together isn't just a plumbing problem. It's a design problem: how should information flow? What shape should the system take? Where does it need to be simple, and where does it need to be precise?
For two decades, Jerry and Jeff answered those questions in one of the most demanding environments on the planet — where a poorly designed integration doesn't just create bad data, it creates patient risk. They led Epic migrations. They built frameworks routing millions of records in real time. They designed systems clinical staff could actually use. Precision at scale, with a design standard most technical teams never think to apply.
The Insight That Sparked JumboTonic
After years in healthcare, the pattern became obvious: every organization has a version of the same problem. The systems don't talk to each other. The workflows are manual. The data is scattered. And the reason is almost always the same — nobody designed the system. They just added to it.
Your CRM doesn't talk to your operations system. Your team is manually moving data between applications that should be connected. You're paying people to be human data routers. That's not an IT problem. It's a design problem that was never addressed.
JumboTonic exists to address it. To bring the same design-first, build-to-last approach that Jerry and Jeff developed in healthcare to every business that's ready for it. If we can design and build correctly for an environment where failure costs lives, we can do it for yours.
How Their Twin Partnership Works
Two minds. One vision.
Jerry — Architect & Design
Strategic vision & architectural leadership
Jerry thinks in systems and shapes. The landscape architecture degree wasn't a detour — it was the foundation. It gave him a way of seeing how things should connect before anyone touches a line of code. Twenty years of enterprise integration later, he applies that lens to health systems handling millions of patients, workflows that can't afford ambiguity, and data architectures that need to hold up under real-world pressure. At Jumbotonic, he designs the solution first — and it shows in how well it holds together.
Jeff — Technical Lead & Execution
Deep technical expertise & flawless delivery
Jeff builds what Jerry designs — and has spent 20 years making sure what gets built actually works in production. Deep expertise in HL7, FHIR, and enterprise integration platforms, with a hard-won instinct for what breaks under load and why. The landscape architecture degree he shares with Jerry shows up differently in him: less in how he envisions systems, more in how he finishes them — with the same attention to the last detail that a good building requires.
The Mirror Twin Advantage
They don't need to translate for each other. When Jerry designs a system, Jeff already understands the intent — not just the spec. When Jeff hits a production constraint, Jerry sees the design implication without being briefed. That saves more time than it sounds. More importantly, it produces work where the architecture and the implementation are genuinely unified — because they were conceived by the same mind, working in two bodies, in parallel.
The result: unusually tight execution, and solutions that hold together long after the engagement ends.
Why Mirror Twins Matter
Shared vision. Complementary execution. Zero misalignment.
Mirror twins — literal mirror images of each other. Same problems catch their attention. Same opportunities stand out. Same instinct for what matters and what doesn't. There's no negotiation between different worldviews, no gap between what gets promised and what gets built. Just two people with identical vision and complementary skills, working the way they've always worked: together.
Most co-founder relationships involve compromise. Theirs involves alignment.