Background
Why Michael Is the Person Building This
Michael's career has been a straight line from data infrastructure to commercial software for life sciences, at the firms that defined each of those categories in turn. He has built the kind of platform LoxaNova requires before, and he has watched what happens when life sciences companies do not own their own technology.
Michael was the CEO of the first biotech firm to implement Snowflake, back in 2017. Most of the life sciences industry is still relying on system integrators like ZS Associates and Accenture to retrofit AI and LLM capabilities onto legacy platforms, and the result is a locked-in chatbot or proprietary add-on that does not scale. Michael's stance has been the opposite from the start: use Snowflake as the foundation and follow its trajectory as a category-defining company. That position has proven correct.
Michael's earlier career was in Accenture's data management practice. The exposure to enterprise data programs across regulated industries is the foundation everything else is built on, and it is the reason Michael is candid about why pharma keeps getting locked into the same recurring consulting cycles.
At Accolade, a patient services firm using behavioral economics to influence how health plan members use their benefits, Michael took the explicit position that the company would build its own technology rather than lock into Salesforce or Microsoft Dynamics. The reasoning was straightforward: owning the software and harnessing the data was the differentiator, and it preserved acquisition optionality. That same philosophy applies directly to LoxaNova. We build it ourselves, we own the IP, and that is what makes the eventual exit clean.
Veeva is the world leader in customer relationship management and other software for life sciences, including CRM for field sales and CRM for med tech. Michael led US data strategy and data science there and worked directly with the product owners and strategy leaders building those CRM tools. He knows what an effective life sciences engagement platform looks like from the inside, and he knows what a team has to do to build one.
At Intarcia, a Boston biotech, Michael was CDO and CIO during development of an osmotic mini-implantable pump (the ICA 650) that delivered a microdose of a GLP-1 to type 2 diabetics over a ninety-day period. Because it was a REMS product, Intarcia had to train and certify the clinical staff at endocrinologist offices and surgical centers on how to use the kit and place the device subcutaneously, covering scalpel, sutures, depth tool, the entire procedure. The training-and-certification problem Michael solved there is structurally identical to what LoxaNova has to solve for arthroscopic surgeons and OR staff using Daniel's devices. It is on the roadmap by design.
The Core Insight
Michael Already Built This. For Pharma.
Loxalytics handles pharma-scale operations: over a billion patient records on Snowflake Business Critical, HIPAA BAAs already in place, NVIDIA compute already provisioned, and life sciences commercial data models already built. LoxaNova is not a greenfield build. It is Loxalytics' existing commercial data platform extended into orthopedic surgical device sales, with a new field-facing mobile layer and an inventory module pharma doesn't need.
Revised Tech Stack
Enterprise Architecture
The entire data model lives here. HCP data, territory structures, sales activity, inventory movements, OR case records, patent-linked product catalog, Sunshine Act reporting tables. Michael has already configured this environment for sensitive healthcare data.
$0 incremental, existing accountOwner: Michael
NVIDIA Spark handles local inference for anything touching sensitive data. Snowflake Cortex runs ML directly on warehouse data without moving it. OpenAI handles non-sensitive tasks like rep coaching prompts, device recommendation narratives, and sales insight generation.
$0 incremental on existing hardwareOwner: Michael + Jason
Streamlit in Snowflake builds dashboards that run directly on warehouse data. Sales manager territory views, Sunshine Act compliance dashboards, inventory reconciliation reports, pipeline analytics, and AI-generated forecasts all live here.
$0 Streamlit nativeOwner: Michael
Michael does not like calling it a CRM. It is a healthcare provider engagement tool: collaboration across accounts, contacts at those accounts, territory performance, ASC and group-practice consignment activity, and surgeon onboarding. Softr is the current implementation. It is a no-code environment that gives the team a working engagement layer in front of the Snowflake data model fast, so the May 12 demo is a functioning system the team can actually click through, not a scaffold or a screenshot. Softr is the bridge. We use it to validate the workflow and the data model, then pivot to owned IP.
Rapid prototyping in productionOwner: Michael
Once the workflow is validated in Softr, the platform pivots to Node.js, React, and React Native, frameworks that produce IP the entity owns outright. This is the same philosophy Michael set at Accolade: do not lock into Salesforce or Microsoft Dynamics. Build it, own it, and the acquisition stays clean.
Owned source codeOwner: Michael
Auth0 handles rep and manager login, territory-based role permissions, and enterprise SSO for hospital system integrations. When an acquirer's IT team wants to integrate LoxaNova into their SSO environment, Auth0 makes that a configuration change rather than a rebuild.
$0 free up to 7,500 usersOwner: Michael
The Agentic CRM Vision
Stop Asking Reps to Enter Data
Most CRMs and engagement tools, including the ones at Veeva, still ask territory managers and area VPs to hand-enter accounts, contacts, calls, and consignments. Next-best-action engines have been around for a while and do not solve the actual problem. Rep time is the bottleneck, not recommendation quality. LoxaNova's engagement platform is being designed to flip that model entirely. The machine does the CRUD operations. The person has a better interface and a better way to do analytics.
A rep on a phone or tablet says something like: "Create a new account for Mayo Clinic at 123 Main Street, add Dr. Michael Barrett as an orthopedic surgeon, Mayo is his primary place of surgery, add them into my territory." The agent listens, distills the prompt into a set of create / update / delete operations, and applies them to the engagement tool. No more clicking "add new account," no more searching menus. The rep talks, the system records.
"What HCP did I call on the most last month?" The rep stops searching through reports and views. The bot reads the data and answers. Embedded directly in the same engagement surface so the experience stays in one place.
The bulk of LoxaNova's data (sales, claims, Medicare, CMS, whatever else gets layered in) stays in Snowflake rather than being copied into the engagement layer. Snowflake Cortex is effectively a coding agent plus the ability to run natural language queries against a semantic layer that Snowflake lets us build without writing code. We expose Cortex as an agent inside the same React / Node framework, so the rep gets analytics in the same interface as the engagement workflow. Asking "Show me my territory totals" or "Who is the next doctor I should talk to" happens in the same place, with one interface and one experience.
There is a company called Hex (H-E-X) doing exceptional work on natural-language-to-visualization. You ask a question and get an answer plus the chart that supports it, without ever opening a report. LoxaNova's engagement platform should be a small, med-device-shaped version of that idea. No more paging through Excel, Tableau, or Power BI to figure out how you are doing. You ask, and the system answers contextually and visualizes alongside.
Platform Roadmap · Medical Education & Certification
Training and Certifying the People in the OR
The next major addition to the platform roadmap is medical education and rep certification, and it is informed by direct experience.
At Intarcia, the ICA 650 implantable pump was a REMS product. Michael's team had to train and certify the clinicians at endocrinologist offices and surgical centers on how to use the kit (scalpel, sutures, the placement tool that set the pump at the correct subcutaneous depth), then attest that they had completed the certified procedure. That training-and-attestation infrastructure is structurally the same thing Daniel's devices will need in the OR for arthroscopic procedures.
Loic has worked with a company called Acto at a customer who is using LLM and avatar-based training with their sales reps. Approved, medically and legally reviewed materials get delivered conversationally. Reps interact with an avatar instead of paging through hundred-page PowerPoints, ISI documents, and three-page FDA labels. The result is faster ramp, current information, and an audit trail of who has consumed which approved content. This is a strong model for how LoxaNova handles rep enablement, change management, and onboarding as we scale.
The training problem in med tech is broader than the sales team. The surgical team using Daniel's devices needs documented training and proof of certification on the procedure itself. Building that capability into the LoxaNova platform (scalable, auditable, tied to the device and to the case) is the long-arc addition to the roadmap that ties directly back to the work Michael did at Intarcia.
Pre-May 12 · Michael's Directives
What Needs to Be Built Before Dallas
LoxaNova needs its own isolated Snowflake database within the Loxalytics account. This protects existing client relationships and creates a clean IP boundary for the eventual acquisition.
Create LOXANOVA database with its own schema namespace, and do not commingle with any Loxalytics client databases
Set up role-based access (REP, MANAGER, ADMIN, EXECUTIVE) to mirror the territory hierarchy
Confirm Business Critical tier is active and HIPAA BAA is in place, then document this for the acquisition data room
Enable Snowflake audit logging on the LoxaNova database from day one
The nine core tables: ACCOUNTS, CONTACTS, PRODUCTS, INVENTORY_ITEMS, ACTIVITIES, OR_CASES, OPPORTUNITIES, PREFERENCE_CARDS, TERRITORIES. Every table needs created_at, updated_at, and created_by fields. The PRODUCTS table has a patent_id field linking everything back to Worrel IP, and that field is sacred.
Build all 9 tables using the schema Jason sends, and do not deviate from field names
Add Sunshine Act fields to ACTIVITIES (transfer_value, transfer_category, hcp_npi). Make transfer_value required when activity_type is food, education, or consulting
Seed 5 to 10 dummy Texas accounts, contacts, and products for the demo. No blank tables on May 12
Add one dummy product per Suremka patent category with real patent numbers from the status chartRetractable Cannula · Surgical Devices & Methods · Graft Compression · Suture Shuttle · Deployment Apparatuses
We need something visual on a screen at the meeting. Three views minimum: Accounts by territory, Pipeline by stage, Product lookup by patent category. Connect to seeded dummy data with real rows, not screenshots.
Build Streamlit app with three views: Accounts by territory, Pipeline by stage, Recent activities feed
Add a product lookup: select a patent category, see matching Suremka devices with patent numbers
Connect to seeded dummy data. The demo must show real rows, not placeholder screenshots
The May 12 deliverable is no longer a hand-passed React Native scaffold. It is a functional Softr prototype wired into Snowflake (accounts, contacts, territory views, surgeon onboarding flows) with real Medicare and CMS data already loaded behind it. The owned-IP React / React Native build comes after the workflow is validated. For Dallas, we need a system Daniel can click through, not a sketch.
Stand up the Softr app and connect it to the LoxaNova Snowflake database
Load representative Medicare and CMS data structured around arthroscopic procedure codes
Build the core engagement views: accounts, contacts, territory performance, consignment status
Have it running on a laptop and a phone for the room, then pass it around the table
Jason writes the prompt. Michael wires the OpenAI API call. Input is surgeon specialty and procedure type. Output is a recommended Suremka device with its patent number and a one-paragraph clinical rationale. It does not need to be smart, just exist and look intentional.
Set up OpenAI API key in a secure environment variable, never hardcoded
Build API endpoint: POST surgeon specialty + procedure type → OpenAI call → device name, patent ID, rationale
Surface output in the Streamlit dashboard as an "AI Device Recommendation" panelJason will send the final prompt by May 9
Suremka LLC · Patent Portfolio
Seed These Into the Products Table
These are the real patent numbers from Zach Hilton's May 4 status chart. Do not use placeholders. Every product record in Snowflake maps to a patent number, and that linkage is the entire IP commercialization story.
| Patent / App No. |
Device Name |
Status |
Next Deadline |
| 8,777,902 | Retractable Cannula (Gen 1) | Issued 2014 | Jul 15, 2026 · $3,528 ⚠️ |
| 10,258,368 | Retractable Cannula (Gen 2) | Issued 2019 | Oct 16, 2026 · $1,616 |
| EP15806528.4 | Retractable Cannula, UK, France, Germany | Issued 2020 | Jun 30, 2026 · ~$2,250 ⚠️ |
| 10,342,577 | Surgical Devices and Methods | Issued 2019 | Jan 9, 2027 |
| 10,687,846 | Surgical Devices and Methods (Div.) | Issued 2020 | Dec 23, 2027 |
| 11,607,246 | Surgical Device Deployment Apparatuses | Issued 2023 | Sep 21, 2026 · $860 |
| 11,607,322 | Graft Compression System | Issued 2023 | Sep 21, 2026 · $860 |
| 12,427,039 | Graft Compression System (CIP, Newest) | Issued 2025 | Mar 30, 2029 |
| 11,627,985 | Surgical Devices & Deployment Apparatuses | Issued 2023 | Oct 18, 2026 · $860 |
| 18/355,936 | Surgical Devices & Deployment Apparatuses | Pending | Awaiting examiner action |
| 18/336,287 | Knotless Suture Shuttling & Anchoring System | Pending | Final office action, imminent response |
| 18/295,414 | Surgical Devices & Deployment Apparatuses | Pending | Awaiting examiner action |
| 19/252,607 | Surgical Devices & Deployment Apparatuses (Newest) | Pending | Filed Jun 2025, awaiting exam |
Urgent: IP Maintenance Deadlines
June 30, 2026: European patent maintenance fees ~$2,250. Zach Hilton needs Daniel's instructions by mid-June. Recommendation: pay them. European coverage adds acquisition value.
July 15, 2026: US Patent 8,777,902 final maintenance fee $3,528, non-extendable. This is the 2012 cannula, the oldest in the portfolio. The call needs to be made intentionally before the deadline, not by default.
September 21, 2026: Two patents due simultaneously, 11,607,246 and 11,607,322, $860 each.
October 2026: Two more fees, 10,258,368 ($1,616) and 11,627,985 ($860).