From 0 to 1: Building eApp, WatchTower, SENTRY & FireSpec

From Zero to One: Building Real Products That Solved Real Problems

Most product leaders can optimize what already exists.  Far fewer can take something from nothing, no roadmap, no team, and sometimes not even permission, and turn it into a tool people rely on every day.

Over the past decade, I’ve taken four products from 0 to 1 across government, analytics, and field operations.  Each solved a different problem.  Each required the same foundation: clarity under uncertainty.

Step 1: Start with Pain, Not Permission

Every 0 to 1 product began with pain, not a project charter.

eApp: as Product Manager & System Owner, I led the creation of the federal background investigation platform that replaced e-QIP, scaling from zero to 2M+ users in the first year. The problem wasn’t just outdated tech; it was rework, inconsistent data, and user frustration.

WatchTower: as Product Manager, I built a tool that went from zero to 1,600 daily active federal agents in 8 months, eliminated a four-year backlog, improved efficiency by 250%, and reduced errors by 90%.  It didn’t start with funding, it started with one analyst saying, “We can’t keep up.”

SENTRY: as Product Manager & Lead Architect, I built a lightweight, automated triage system in just 40 hours from concept to production-ready MVP.  It processed 5,000+ partial military trainee records, performed 1.5M+ fuzzy match comparisons, reducing a daily 4-hour manual process to under 10 minutes.

FireSpec: a mobile inspection platform for the Oklahoma State Fire Marshal’s Office.  Within months, it digitized field operations across the state of Oklahoma and revealed a 10-year inspection gap across rural schools.  I built and deployed the MVP myself, from concept to production.

The pattern was the same: no one asked for a new system, they asked for relief from chaos.

Step 2: Discover While Delivering

In 0 to 1, discovery isn’t a phase. It’s how you build.

Each release is an experiment: test, observe, adjust.

eApp: Early pilots with agency users shaped every sprint.

WatchTower: Usage analytics revealed where to focus next, real adoption replaced theoretical prioritization.

SENTRY: The logic evolved with live data; we learned from every false positive and tuned continuously.

FireSpec: Field testing with inspectors provided raw, unfiltered usability feedback that shaped each update.

Learning by shipping beats waiting for certainty.

Step 3: Lead Without Authority

0 to 1 work rarely comes with a ready-made team.  You lead by influence before you lead by title.

Across these projects, I guided engineers, analysts, policy experts, and security teams, often without formal authority.  The goal wasn’t control; it was alignment around purpose.

In federal systems, that meant earning trust across silos.  In FireSpec’s case, it meant building belief among inspectors, administrators, and the State Fire Marshal’s Office that the new system would help, not hinder.

Step 4: Prove It Works, With Data

Launch dates don’t prove success. Outcomes do.

eApp: Reduced rework by 80% and cut average form processing from a week to 30 minutes.

WatchTower: Improved agent efficiency by 250%, reduced errors by 90%, and eliminated a 4-year backlog in 8 months.

SENTRY: Reduced triage time from 4 hours to under 10 minutes while completing 1.5M fuzzy match comparisons.

FireSpec: Digitized inspections statewide, uncovering a decade of missed reportsthat improved safety oversight for rural schools.

Data converts belief into credibility.

Step 5: Your Judgment Is the Product

The constant across every 0 to 1 product isn’t code or process, it’s judgment.

Every major decision came down to informed bets with incomplete data:

• Which problem to solve first

• When to automate vs. assist

• How much friction users could handle during change

Those choices became the product.  Everything else just made them visible.

Final Thought

Taking a product from 0 to 1 isn’t about ideas, it’s about conviction, clarity, and relentless iteration.

If scaling is about process, creation is about courage:  The courage to act before consensus, to build before approval, and to lead before there’s a roadmap.

That’s the kind of product work that changes systems, and sometimes, entire organizations.

#ProductManagement #Leadership #Innovation #GovTech #DigitalTransformation #SaaS #PublicSector #DataDriven #ProductStrategy

Previous
Previous

Why I Built a Prop Computer from a 1983 Movie (And What It Taught Me About Enterprise Thinking)

Next
Next

From Chaos to Clarity:  Building a Name-Matching System That Processes 1.5 Million Records in 10 Minutes