Skip to content
bizurk
← ALL CASE STUDIES

THE OPERATOR STACK/2021 to 2026/NDA client

Five years inside one company.

The role started in creative direction, picked up the storefront, then the martech pipeline, the integration estate, the regulated compliance platform, and the recovery when an integration layer went silent. Eleven disciplines under one login.

48h

Server-side conversion build

Hours

Diagnosis to full recovery

0

Data loss on the primary path

A decade of context in five chapters.

  • YEAR ONE2021

    Voice documentation shipped

  • YEAR TWO2022

    First server-side container live

  • YEAR THREE2023

    Compliance platform launched

  • YEAR FOUR2024

    Asset hub built and deployed

  • YEAR FIVE2025

    Cloud incident, recovered same day

What the scope looks like from the inside.

A regulated healthcare DTC company with a storefront on one side and a payer integration on the other. The creative direction expanded into full-stack web build, server-side martech, regulated platform engineering, design ops, and cloud incident response because the work compounds when the same operator owns brand and infrastructure together. Voice documentation and a deployment hygiene runbook can land in the same week because neither waits on a handoff.

Two custom platforms shipped from zero. An integration outage diagnosed and recovered the same afternoon. Hundreds of API routes and a four-figure test suite, all owned end to end. This page is the index to the fourteen chapters that prove each claim.

Twelve chapters across five disciplines. Each one owned end to end.

Brand and voice/creative direction

THE STOREFRONTpublic surface

Where the company meets buyers.

Server-side tracking, in motion.

iOS 14.5 broke browser-only pixel tracking across the category. The fix is a server-side container fronted by a first-party loader, with event_id deduplication and external_id hashing so the platform can deduplicate browser and server fires. The visualizer below toggles between browser-only and server-side modes so you can see what the lift looks like.

Conversion event capture

BrowserClient tag fires
LoaderFirst-party endpoint
Platform APIConversions endpoint

Events captured

62

Reaches the platform via the client only.

Events lost

38

~ blocked, ITP, ad-blockers.

Recent events

  • Waiting for events.

// runs locally on this page · no fetch · transform and opacity only

TRACKING SCOPE

Built tracking pipelines like this. The full engagement scope is on the contact page.

Start a conversation

THE PLATFORMregulated compliance system

A member system you can audit.

The calls a small team cannot answer.

A small clinical team cannot pick up every inbound call, schedule every check-in, and chase every resupply window in real time. The dispatcher routes calls into a queue, hands them to a voice agent when the team is full, and records the transcript for follow-up. Click any call to see what the transcript pane looks like.

QUEUE8 calls

Use j / k or arrow keys to walk the queue.

CALLPatient (Pt-0001)Intake / INBOUND
queued0:00
Agent:
Caller:
Agent:
Caller:
Agent:

// 8 mock calls · pre-allocated transcript rows · prefers-reduced-motion honored

Compliance sits under everything. It is the floor.

Field-level encryption on the columns carrying member health data, row-level security across the data layer, and audit logging across administrator actions. A data-export endpoint and a deletion routine that wipes a member's record atomically.

Authentication runs short-lived session cookies with strong defaults, rate-limited credential paths to contain stuffing, and time-based one-time passcodes on the roles that touch sensitive data. Integrations expose BAA-swappable abstractions from day one so the architecture is ready when the business decides it needs them.

The architecture states its limits and overbuilds where the data is sensitive.

ARCHITECTURE

Architecture questions land cleanest before the engagement starts.

Get in touch

THE RECOVERYinfrastructure incident

The day the silence ended.

Outage to full recovery, same afternoon.

An integration layer had gone quiet. A downstream consumer surfaced the stale data and the diagnosis followed. The host’s outbound network stack had wedged after a reboot. Recovery was a snapshot, a clean reboot, a credential rotation across the function fleet, and a series of clean post-patch runs to verify end-to-end. The timeline below walks each phase.

INCIDENT RECOVERY

Outage to recovery

Conceptual reconstruction. No real infrastructure references.

Phase 1 of 8Silent failure
SILENT FAILURE
ElapsedT+0h

An integration layer stopped exchanging data. The signal was application output, not host health, so the standard runbook checks did not surface it.

// click a phase · arrow keys cycle · narrative announces on phase change

The work compounds when one person owns it.

Most companies that sell direct to consumers staff brand and infrastructure as separate disciplines, with one person on voice and another on the cloud. The handoff between them is where work disappears.

The argument of this engagement: when one role owns brand and code, the artifacts compound. A voice document and a deployment hygiene runbook get written in the same week, by the same person, with the same eye on the company. The translation step disappears.

Five years of one role, and the artifacts line up.

Eleven disciplines owned end to end. Two custom platforms shipped from zero. An integration outage diagnosed and recovered the same afternoon with zero data loss on the primary path. Five years, one role.

The chapters that make up the arc.

If your work looks like this, let’s talk.

> Start a conversation Or buy a product