Proof / Built in Production
Built in production, not in a sandbox.
These six systems were designed and implemented inside a real, operating organization — a multi-site healthcare organization — to solve problems that were already costing it money, time, or staff hours. They are not demos, pilots, or hypotheticals. They run today, inside daily operations, built to a standard set by a business with no tolerance for something that almost works.
Production and The Lab prove different things. Production is commercial judgment — building the right thing, inside real constraints, for a business that depends on the outcome. The Lab is capability — skills kept current on systems built independently, on my own time. Production is the stronger evidence, and it leads. The Lab is more credible for being kept clearly separate from it.
01 / Patient Access
Customer experienceWhat if every call got answered?
The problem. A multi-site healthcare organization runs on inbound calls — patients scheduling, rescheduling, asking questions — and every front desk has a ceiling on how many it can handle at once. Calls during lunch, after hours, or when two lines ring together go to voicemail, and a missed call is often a lost appointment, not a delayed one.
What I built. An AI virtual assistant that answers inbound calls, handles the caller conversation, and schedules appointments directly — working across the organization's locations rather than serving a single office.
Why it matters. A call that gets answered is a problem solved on the spot, without asking a caller to wait, call back, or leave a message and hope. Any business where the phone is the front door is carrying the same ceiling.
02 / Systems Integration
SystemsWhat if your systems actually talked to each other?
The problem. The organization's EMR/EHR and its other software tools were built by different vendors for different purposes, with no connection between them. Staff re-entered the same information more than once, and information that existed in one system stayed invisible to the next person who needed it.
What I built. An integration layer connecting the EMR/EHR to third-party tools that previously couldn't exchange data, so information and workflow move between systems instead of stopping at their edges.
Why it matters. Every business running more than one system pays a hidden tax in double entry, delay, and the errors that live in the gap between two tools that don't talk. Closing that gap gives staff their time back and gives the business one version of the truth.
03 / Business Systems
Cost & operationsWhat if the software fit the business, instead of the other way around?
The problem. The organization was paying for multiple enterprise platforms to handle customer management, sales, and financial transactions — broad, general-purpose tools built for a generic business, not this one. Roughly 60% of what those platforms offered went unused, and staff spent real effort bending how they worked to fit software that was never built for them.
What I built. A CRM and ERP designed and built from the ground up around how the business actually operates — handling customer management, sales orders, financial transactions, and more, in one system shaped to the workflow instead of the other way around.
Why it matters. A purpose-built system that replaces multiple paid platforms removes the ongoing cost of licensing tools nobody fully uses, and it removes the daily cost of a team bending its process to fit software that was never built for its business. Any operator paying for an enterprise platform they've had to configure around, rather than one built around them, is looking at the same trade.
04 / Internal Operations
Internal productivityWhere does an employee go to find anything?
The problem. New employees didn't know where to find basic resources. Existing employees didn't know where the current version of a document lived. Every department had its own scattered answer to "where's the link for that" — and none of it needed artificial intelligence to fix. It needed one place that didn't exist yet.
What I built. A single company dashboard: internal links, employee resources, new-employee onboarding, and department resources, all in one place.
Why it matters. Not every operational problem needs a sophisticated system, and not every valuable fix needs AI. Sometimes the highest-value move is the simplest one — give people one place to look instead of five. Every growing organization eventually strands its own information across departments; someone still has to build the front door.
05 / Marketing Operations
MarketingWhat if content didn't wait on someone to start it?
The problem. Producing regular social content — posts, images — competed for time against everything else on a marketing team's plate, and consistency suffered because someone had to sit down and start from a blank page.
What I built. A system that generates social posts and images automatically, with a mandatory human verification step before anything publishes. Nothing goes out without a person checking it first.
Why it matters. Automation removes the blank-page problem without removing judgment from the process. The system produces a starting point; a person still decides what represents the business. That balance — machine drafts, human accountability — is the right shape for any content produced at pace.
06 / Business Development
RevenueWhat if you knew who to call before they knew they needed you?
The problem. Finding potential customers in a given area meant someone manually searching, visiting websites one at a time, and hand-collecting contact information — slow, inconsistent, and dependent on whoever had the spare time that week.
What I built. An automated engine that finds potential customers in a geographic area, gathers the information needed to reach them, and crawls their websites for specific data and contact details. Built first for one clinical specialty, it's configurable to any industry or keyword.
Why it matters. A prospecting process that used to depend on one person's spare time becomes a system that runs on its own, at a pace and consistency manual search can't match. Any business that grows by finding the right prospects in a defined market has the same bottleneck this replaces.
Capability, kept separate
Production is the stronger evidence
The Lab proves capability — systems built independently, on my own time, to keep skills current. These six prove commercial judgment inside a real organization with a real budget and no tolerance for something that almost works. Both matter; they're kept deliberately separate.