Dashboard
Weighted pipeline, funded backlog, capture gates and approaching awards in one view.
The pipeline‑review slideFor mid‑tier government contractors
Pipeline, funded backlog and account activity in one operating book — without buying an ERP project or asking capture to abandon Excel.
Fourteen screens shipping · walkthroughs run on a synthetic tenant
Executive Dashboard · Meridian demo tenant — synthetic data, never a customer’s book
For mid‑tier firms, roughly $25M–$500M. Not an accounting system, not a proposal tool, not a SAM.gov alert service.
[ 01 ] What it replaces
Someone prepares the pipeline review. Someone reconciles it to funded backlog. Someone builds the board slide. Someone answers the question nobody can answer from the last version of the workbook.
That cost is already in the business. It shows up as analyst time, Finance time, IT reporting work, and a CRM that may be more system than your team needs.
None of it is a software line. All of it is a cost.
[ 02 ] Proof
The pipeline file says one thing. The backlog file says another. Staffing sits in its own workbook, and the forecast becomes an argument because each file has a different answer.
“We had four systems that never agreed with each other, and the thing reconciling them was a person. Pipeline, funded backlog, and the staffing to deliver both now sit in one book — when somebody asks what a pursuit was worth back in January, there’s an answer. Mike sat with our capture team, watched how the work actually gets done, and built that. I’ve bought software from companies with a hundred people that did less.”
[ 03 ] The test
“What did we say this pursuit was worth in January?”
“Which contracts expire in the next twelve months without a replacement pursuit?”
“How much of the fiscal‑year target is funded, growth on contract, or still go‑get?”
“Which account manager has met with this customer lately?”
The point is not a prettier dashboard. It is that the answer comes from the same book each time.
Go‑get is your fiscal‑year target minus funded backlog, growth on contract and weighted pipeline, recalculated from your rows on every load. If no target is set, it says so.
2026-08-11MERIDIAN (SYNTHETIC)go_get = fy_target − (funded_backlog + growth_on_contract + SUM(program.value × program.pwin))→ recomputed on every load · 0 model calls anywhere in the figure
[ 04 ] Shipping today
Fourteen screens are reachable. These four get opened most.
Weighted pipeline, funded backlog, capture gates and approaching awards in one view.
The pipeline‑review slideTarget, funded backlog, growth on contract, weighted pipeline, and the go‑get left.
Recomputed on loadIdentified, Qualified, Teaming, Teamed, Submitted — kept separate from pWin, with Unstaged for the untriaged.
Five gates · plus outcomesFunded backlog, period of performance, and everything expiring inside twelve months.
Prime · sub · task orderCapture owners work their pursuits, leadership sees the portfolio, and a six‑sheet Excel export goes to whoever still needs a workbook. Role access is enforced on the server, not hidden in the interface.
2026-08-11BUILD · demo-pinreachable_screens = COUNT(routes) IN src/App.tsx — read from the route table, not from a deck→ 14 reachable · 0 behind a flag
[ 05 ] The boundary
No file upload. No document storage. No proposal drafts, resumes, pricing volumes or contract files. A design constraint, not a current limitation.
Business‑development metadata — agencies and end customers, NAICS, contract types, values, dates, pWin, labor categories and rates, and your users’ names and emails.
Your pipeline is the most competitive thing you own, and the firm you’re bidding against might be our next customer. So every customer gets their own provisioned database, not a row behind a tenant filter.
It does not decide bid / no‑bid. It does not forecast staffing demand. It does not scan SAM.gov. Bid gates, staffing forecast, self‑serve import and RFP intake are marked coming soon, and stay marked until you can reach them.
Not FedRAMP authorized. No SOC 2. No CMMC assessment. We will say when that changes — which is exactly why there is nowhere here to put CUI.
2026-08-11ARCHITECTUREcui_storage_paths = COUNT(upload_endpoints) + COUNT(document_tables)→ 0
[ 06 ] Getting in
You provide a pipeline export, active contracts, labor categories and rates, and someone who can spot a wrong number.
Ten business days, about three hours of your time.
Next step
Twenty‑five minutes on a synthetic tenant running the same code production does. Bring the number you can’t reconcile today.