I called it PharmsNet. The ability for pharmacies to digitally track prescribed medications across a shared network. Patients, doctors, and pharmacies connected. Prescriptions documented on a common digital board. Pharmacists notifying doctors of conflicts. Session timeouts. Encrypted records. Medication data masked except in emergencies, accessible only to authorized users.
I had the architecture. I had the timeline. I had the business plan. I had a meeting scheduled for April 9th with an engineer, kept secret until we filed. The person I wanted to build it with didn't want to.
PharmsNet never got built.
The sell line I wrote in that notebook: Being in the loop will save lives.
I was 26.
Concept · Architecture · Business Plan
Never built
Not in a straight line. Not with a plan. Through the work.
Eat In Chef taught me that technology only works if the surrounding structure can absorb it. I built the matching logic, the onboarding system, the operational layer. I was bartending and serving tables to cover rent while running the company and leading a $3M seed round. The technical co-founder left. I kept building. Four cities. Thirty-six chefs. Three thousand on the waitlist.
I stopped thinking in features and started thinking in flows.
At SiriusXM and Pandora, the variables changed. Two hundred million assets. Seventy million users. A taxonomy that was constraining what the intelligence layer could do. I rebuilt it. Replacing a third-party contextualization system blind. Designing the first structured classification framework. Collaborating with scientists to redefine the schema after a major acquisition brought in a genomic model that was constrained and outdated.
What truly excited me was the data. Modeling on whiteboards. Defining attributes, relationships, clusters, interactions. Mapping scenarios to shape outcomes.
That's where the brains thesis started. Not from a framework. From the work.
Healthcare operations. PHI constraints. Fragmented teams. Ambition without mature infrastructure.
I built the connective tissue. Orchestration layers. Communication backbone across SMS, voice, chat, and telephony. AI routing systems. Governance patterns. Not prototypes. Production systems. The kind that run 24/7 and carry clinical accountability.
The system I built was a direct descendant of what I wrote in that notebook in 2008. Patient records tracked through a network. Pharmacist-to-doctor notification. Prescription conflicts flagged. Confidential, encrypted, session-controlled.
The intelligence layer is always the moat. And it almost always belongs to no one.
Mast Labs is that layer. Seventeen years in the making. mastOS is how we deploy it.
Architecture proven at scale. mastOS is the build.