Case Study 04 · AI Product Build

From disconnected handoffs to one governed lifecycle

Federal and commercial revenue work moves through a long chain of hands: pipeline, pricing, awards, flow-downs, subcontracts, delivery, invoicing and closeout. I'm designing and building Ozbek with AI-assisted development so that entire chain lives in one platform, with governance and regulatory checks built into every step.

Ozbek overview video: one platform from opportunity to closeout

2:33

Start here · Narrated overview

Ozbek in two and a half minutes

One platform from first opportunity to final closeout: sales, bids, contracts, suppliers, delivery, billing and support, with governance and regulatory checks built into every step.

Watch the overview

Lifecycle stages

Step governed workflow

Connected platform

Markets: GovCon and commercial

The deep dives

One deal, start to finish

A three-part narrated walkthrough following a single fictional federal deal through the entire platform.

7:35

Part 1

Dashboard to award

A federal IT services opportunity moves from the pipeline through pricing, bid and approval to a signed award.

Watch Part 1

7:00

Part 2

Award to closeout

The same deal carried through subcontracting, delivery, invoicing, margin and final closeout.

Watch Part 2

8:56

Part 3

Contracts, FAR clauses and the audit file

A deep dive on automated clause checks, flow-downs, signed contract documents and an audit-ready file.

Watch Part 3

The platform

Ozbek platform graphic showing the Capture, Validate, Approve and Deliver workflow

The problem

Every handoff was a place for something to slip

Running federal subcontract portfolios, I watched the same pattern repeat. The pipeline lived in one system, pricing in spreadsheets, contracts and flow-downs in documents, and invoices and payables somewhere else. Deadlines, compliance requirements and margin all depended on people re-keying the same information and remembering what came next.

What I built

Core platform

Revenue lifecycle engine

One record that follows the work from first opportunity to final closeout.

Sales pipeline, bids and pricing
Awards and contract development with templates
Subcontract workshare with automated flow-downs
Task orders, subcontracts and certificates generated from the record
Delivery, invoicing and payables tied to the work
Margin, warranty and closeout visibility

Built-in controls

Governance layer

Checks and sign-offs designed in, not bolted on after the fact.

Capture, Validate, Approve, Deliver on every record
Approval routing before work moves forward
Signature order enforced on every contract document
Flow-down requirements carried into every subcontract
Planned for cloud and GovCloud deployment

Automated regulatory checks

Compliance runs inside the workflow, not after it

Most teams check compliance at the end, when fixing a problem is expensive. In Ozbek, the rules are part of the record, so every change is checked the moment it happens.

Clause engine. Every FAR and VAAR clause gets its own decision for the prime and for the subcontract, with the reason, version and current status.
Thresholds applied automatically. Dollar values and contract type turn the right clauses on or off without anyone looking them up.
What-if testing. Change a fact, like a subcontractor gaining access to patient health information, and the required agreements switch on instantly.
Commercial vs. non-commercial. A side-by-side view shows only the clauses that change between FAR Part 12 and Part 15.

Limitations on subcontracting. Workshare is tracked against the cap, and a subcontract that would exceed it is blocked before award. A ledger ties real payments to the cap period by period.
Pre-award checks. Eligibility and exclusion checks are dated and recorded before a subcontract is issued.
Regulatory watch. The FAR overhaul, agency deviations, removed clauses and new thresholds are tracked with sources. When a rule changes, the library updates once and every open contract is re-checked.
Audit-ready file. Awards, certificates, price analysis, the clause decision log and retention dates are indexed as the work happens, ready before anyone asks.

Ozbek is a working prototype demonstrated with fictional data. Clause status reflects research as of October 2026.

Ozbek lifecycle diagram: eleven connected stages from sales pipeline to closeout, each moving through Capture, Validate, Approve and Deliver

The expertise behind it

The software is the visible part. The operating discipline is the real work.

Ozbek is built on the same skills I bring to any organization: understanding how work actually flows, turning policy into practice, and getting people to adopt the change.

Workflow analytics

Mapping where work stalls, measuring handoffs and cycle time, and redesigning the process with Lean Six Sigma discipline before automating it.

Data-driven decisions

Turning operational data into reporting leaders act on. My reports went to executive Sales, Operations, Finance and Program leadership.

Policy and SOP crosswalks

Mapping regulations to internal policy to step-level procedures, so every requirement has an owner, a control and evidence it was met.

Implementation

Taking tools from design to daily use, including approval workflows, trackers and databases built in Oracle APEX, SharePoint and Power Automate.

Training

Building the guidance and hands-on support that make a new process stick, from frontline staff to leadership.

Change management

Leading people through new ways of working, from tiger teams to soldiers overseas, with clear expectations and steady follow-through.

What this shows

I build the systems I wish I'd had

Ozbek brings together my federal subcontracts and supplier experience, Lean Six Sigma process design, and hands-on AI product development. It is still in active development, with production mode underway across all modules, and I'm documenting the build as it grows.