Bay 028 projects · 7 articles

Forward Deployed Engineering.

Embedded with doctors, finance, and ops.

As the only engineer at a dental implant company, I sit with the person who has the problem, ship into their tools, then train them.

Scroll to walk the bay

How I work

  • No one writes tickets. My users are surgeons, a VP of finance, treatment coordinators, an operations lead and the lab.
  • Discovery is the work. Requirements live in their spreadsheets, meeting transcripts and workarounds, so that is where I dig.
  • Build where they work. The planner started from the operations lead's own workbook, and the doctor portal from the lab lead's own mockup.
  • Fix the data first. Fixing the broken patient to lead join linked almost every patient to a lead.
  • Ask, then ship. Six apps share one feature request list, and a request filed on October 28 was live 19 minutes later.
  • The honest no. My CRM blueprint tells leadership plainly: without funded engineering, stay on the current vendor.

What I bring

Find the real problem, ship into their workflow, teach them to run it.

  • Discovery from primary sourcesRequirements from real exports, transcripts and mockups: eight data problems catalogued with row counts.
  • Ship into existing workflowsMonday boards for leadership, a web page for finance, email reports for doctors.
  • Enablement and trainingTraining and office hours that get nontechnical teams to confident AI use.
  • Honest scopingBuild versus buy analyses with real costs, including the ones that say don't build.
In production

Patient Dashboard

One row per patient, with linked records one click away, in a practice where every system named patients differently.

  • Patients, intake surveys, manual intake, patient experience, estimates and consultations in one place
  • Records now join on the Denticon id, and a person's link decision always beats the matcher
  • The Denticon mirror went from 6.0 days behind to 2.6 minutes behind once the sync ran on a timer
In production

Capacity Planner

Replaced a workbook of twenty pasted weeks with one forward view of demand and capacity across three offices.

  • Started from the workbook itself, including the fixed ranges that undercounted without a warning
  • Burnout treated as a design goal: proposed defaults flag three heavy days in a row
  • Cover suggestions explain themselves: five ranked keys, every reason traced to its rule
Prototype

Doctor Portal

The lab's own doctor portal, where the Rx joins the case the scanner made. Live on sample data.

  • Built from the lab lead's own July mockup
  • Top priority to a working live link in 3.7 hours
  • Every release note lists what is still pretend; real data waits on a vendor license
In production

Launchpad

Every Hybridge app on one board, the work in progress for four leaders, and one feature request list six apps share.

  • A working live board 78 minutes after the first commit
  • 38 projects on one board on Oct 29, 22 of them live, with every edit logged
  • A request filed in the Cowork Dashboard on October 28 was live 19 minutes later
In production

Cowork Dashboard

The operations dashboard for leadership: Monday.com boards turned into a full funnel view.

  • One definition per metric since the September rebuild, so a card and its drilldown cannot disagree
  • Fixing the join left 23 patients with no lead, mostly retreatment cases filed without a Lead row
  • Ambiguous patient to lead links cut from 31% to 5.8% with first name checks, recorded per row
Program

AI Lab & Office Hours

AI Power Hour sessions and open office hours for seven nontechnical departments, built from a needs survey.

  • Curriculum built from a structured needs survey across seven departments
  • Decks generated from a build script, versioned like code
  • Plain language, no jargon, no code
Design complete

Hybridge CRM blueprint

A ready to build architecture for moving our patient records off Monday.com, with a marketing firewall around patient data.

  • The PRD says it plainly: without funded maintenance, don't build this
  • Human in the loop dedup; reversible merges; an audit log that captures reads as well as writes
Offline

Accounting automation platform

Our controller's nine accounting scripts on one page behind IAP: upload, answer one form, download. Built in an evening.

  • 26 prompts across the nine old scripts, now asked up front in one form
  • The browser editor our controller asked for was live 3.7 hours after the first commit