Built for the pursuit teams
who actually read the FAR.
Government procurement is the largest distribution channel in the United States, and most contractors pursue it with a spreadsheet, a few SAM.gov tabs, and a half-broken CRM workflow. Meridian was built to do the boring work between those tools — without asking you to migrate off any of them.
Why we built this
The work of pursuing federal, state, and local contracts is mostly attention management. There are thousands of solicitations published every day; the ones that actually fit your shop are a tiny fraction; the response windows are short; and the difference between winning and missing is often whether you saw the post in time.
Tools exist for parts of this — bid boards, CRMs, sequence senders — but the work between them is still human. Someone is still copying solicitation numbers into spreadsheets. Someone is still pasting contracting officer emails into Mailchimp. Someone is still scoring opportunities in their head and forgetting which ones they decided to pursue.
Meridian closes the loop between the source, the score, and the outreach — and does it without asking you to abandon the tools you already pay for.
How we built it
Meridian is multi-tenant by design. Every tenant brings their own ingestion sources, their own email sending domain, and their own CRM. There is no "Meridian email" sitting between you and the contracting officer; there is no anchor customer whose configuration is hard-coded in our defaults.
Scoring is deterministic. No LLM in the path between an opportunity and its score. We do this because BD teams need to defend the score — to the principal who hired them, to the proposal team they're assigning, to the board that wants to see win rates. A score that comes out of a black box can't be defended; one with eight visible dimensions can.
We use a small modern stack — ASP.NET Core 10 with EF Core and PostgreSQL — and we run it on hardware we own. No serverless cold starts, no opaque vendor lock-in. Tenant data is logically isolated through row-level filters, and DataProtection-managed secrets sit on a shared keyring between the Portal and the background Worker.
Who we work with
Small-to-mid government contractors pursuing federal, state, and local awards. BD-leads and proposal managers who already know the FAR and just need their attention to scale. Primes whose pursuit pipeline is too wide for spreadsheets but who don't need the five-figure-per-seat enterprise platforms.
What's next
More state portals. Tone-adapted outreach via pgvector RAG. A capability-statement generator that pulls from your historical wins. SSO for the primes who need it (already shipping; OIDC schemes are per-tenant). And a public API for the teams who want to wire Meridian into their existing capture management workflows.