Portfolio, Ventures & What I Build
Product/systems design that turns AI tech into business results
Contact Us
Contact form or information will go here.
Project Detail
Praedico
Summary
Tracking completed lab tests from invoice readiness to payment reconciliation.
Lab billing workflows can become difficult to trust when completed tests, site invoices, master invoices, and payment status live in disconnected views.
I designed Praedico as a financial operations workflow that connected test completion, invoice creation, site aggregation, master invoicing, and payment tracking.
The Problem
Lab billing needed a clearer operating model.
Praedico supported a financial workflow tied to completed lab tests. The challenge was not only showing totals, but helping users understand where each test or invoice sat in the billing lifecycle.
A completed test could be ready for invoicing, grouped into a site invoice, rolled into a master invoice, or marked as paid. Without a clear structure, teams could lose track of what was billable, pending, invoiced, or already reconciled.
The interface needed to reduce ambiguity across multiple financial states. Users needed confidence that completed work had been captured, grouped correctly, invoiced at the right level, and tracked through payment.
Solution
Structuring billing as a staged workflow.
I organized the product around the natural financial lifecycle: identify completed tests, prepare invoices, group them by site, aggregate them into master invoices, and track payment.
The Overview screen gave users a high-level financial snapshot. It separated ready-to-invoice work, site invoices, and master invoices into distinct summary cards, then supported those totals with trend charts and status breakdowns.
The Ready to be Invoiced screen focused on the first operational step. Users could inspect completed tests, review totals, compare categories over time, and select records for invoice generation.
The completed-tests table made the underlying records visible. Each row preserved the test-level evidence behind the invoice workflow: account, specimen date, received date, status, test type, and unit cost.
%%FIGURE2%%%%FIGURE3%%
The Site Invoices section created the middle layer of the workflow. It helped users understand how individual billable records became site-level invoices, with summary totals, covered sites, and selected invoice states.
The invoice table gave users a direct operational list of invoice IDs, generated dates, sites, billing periods, amounts, and available actions. This was important because finance users need both dashboards and reliable record-level views.
Master invoices represented the aggregation layer. The interface showed total master invoices, total amount, paid, invoiced, and pending counts, then paired those figures with a monthly trend and a master invoice table.
Filters supported the workflow across views. Users could narrow financial records by date range, site, and test type without breaking the mental model of the billing lifecycle.
Outcome
More confidence across the billing lifecycle.
Praedico gave finance and operations users a clearer way to track lab test billing from completed work to payment. Instead of treating invoices as isolated records, the product represented the entire financial lifecycle.
The result was a more legible workflow for reviewing billable tests, creating site invoices, managing master invoices, and confirming payment.
Practical improvements included:
- Clearer separation between ready, invoiced, master, and paid states.
- Better visibility into completed tests and unit-cost evidence.
- Easier tracking of site-level invoice records.
- Stronger understanding of master invoice status.
- Faster filtering by date, site, and test type.
This project reinforced an important enterprise design lesson: financial workflows need more than totals. They need traceability from source record to final payment.
