The operating stack for political ops
Quartermint runs treasury, compliance, and scheduling operations for the people who run campaigns, PACs, and the vendors who serve principals. Each tile is a working demo on real-shape (anonymized) data — click any of them.
No login. Read-only. Click anything.
Independent expenditure committee treasury. Reference customer pattern: a Maryland PAC with bank scrape integration, FEC + MD-CRIS filing line drafts, donor dedup, runway projection, vendor ledger, audit log.
Campaign cash command center. CA gubernatorial candidate, 18 days to primary. The narrative: $821K left, $43K/day burn, zero-cash three weeks before election day. The dashboard you check before signing media buys.
Multi-entity rollup for a consultant running a national C4 + federal PAC + three state PACs across one Abundance Network-shaped program. Same platform as the PAC tile, fund switcher across five legal vehicles, cross-entity ledger and audit.
Vendor ops surface — peer to treasury. For schedulers and advance pros who serve multiple principals. Forward parses every invitation email into a Decision Card; principals decide in their inbox in 8 seconds. Auto-generates the briefing book on accept.
Treasury
PAC, Candidate, and Compliance are three views of the same treasury substrate — same shared auth, same RLS, same event graph. Different reporting schemas because committees, candidates, and multi-entity rollups have different filing burdens.
Operations
Forward is the vendor-side peer surface — same monorepo, same tenant model. Treasury answers "how much cash"; Forward answers "what's the principal doing tomorrow morning".
Vendors first
Quartermint sells to the consultants, treasurers, and schedulers who run political programs across many principals — not to principals one at a time. Buyers run multiple committees and multiple candidates in the same week.