Pricing

Priced by pipeline, not headcount. Pay for the opportunities you run and the governed agent operations they consume — ours or yours, same meter. Never for who’s logged in. Bring as many humans and agents as you want.

One sign-in. A separate workspace for every client.

Each client gets its own BidAngel workspace, not a folder inside yours. Their library, past performance, documents, pursuits and audit history stay inside that client’s workspace, and nothing in the product reads across it.

Multi-client pricing is agreed per firm while this is being built. If you run bids for several clients, we’d like to build the rest with you.

How our pricing works

• Workspace fee. A predictable monthly platform fee covering source coverage, integrations, governance, and audit.
• What counts as a Pursuit. A Pursuit is counted when an opportunity is promoted past qualification into an active pursuit, whether a person or an agent promoted it. One cancelled within 48 hours, or a duplicate of one already counted, is not counted.
• What counts as an agent operation. Actions that change or create something, whether an agent or a person in the app starts them, are counted in weighted units. Most count 1. A section or answer drafted by AI from your content counts 10 (1 if no supporting content is found). Generating a compliance matrix counts 20, plus 2 for each 20 requirements. On your own AI-provider key, every action counts 1. Reading is never counted. Every operation is typed, bounded, and auditable.
• Per billing period, no rollover. Allowances are counted per subscription billing period. Unused allowance does not roll over to the next period — each period’s meter starts fresh. Overage in a period bills at the rates below.
• Usage limits. Workspace administrators can set daily and monthly agent-operation limits, in units, not dollars. Limits reset at 00:00 UTC daily or on the first day of each UTC calendar month. At the limit, new counted operations are declined; operations already in progress complete and may take usage slightly past it, and that usage is billed. Reading is unaffected, and promoting a Pursuit is never blocked.
• Usage notices. When a meter first reaches 80% and 100% of your included allowance, and each further 10%, workspace administrators get an in-app notice, and administrators and your billing contact get an email. Live usage and overage to date appear in billing settings.
• Buyer-side reads, in the same meter. Buyer-side reads are planned and not yet available. When buyer-side agents can query your published capability graph or read your submission packages, those reads will roll into your agent-operations envelope at a steep discount weight (typically 0.1–0.3× a supplier-side dispatch). Most tenants never notice; very high-traffic ones overflow the same way as any other operation. We never charge you per buyer query as a separate line. Buyer-facing credentials and the buyer-side meter rollup are planned — see the note below.
• Transparent overages. US$40 per additional Pursuit. US$25 per 1,000 additional agent-operation units, charged per unit (buyer-side reads will contribute at their discount weight). No seat audits. No surprises.
• Single sign-on on any plan. Included in Command and Sovereign. On Scout and Operate it is an add-on, priced per identity-provider connection; ask us when you need it.

• Per-seat tools charge more when your SMEs review one answer. We don’t. Bring every reviewer, every executive sign-off, every occasional contributor — no license expansion, no seat audit at renewal.
• Per-block tools sell users in groups of ten. We don’t. Add or remove humans and agents freely. The meter cares about pipeline, not who is logged in.
• Legacy procurement tools require sixty-day cancellation notice and double-digit renewal hikes. We don’t. Monthly cadence. Predictable workspace fee, transparent overages, no auto-renewal trap, no “Bloomberg-terminal” annual contract floor.
• And buyer-side queries don’t bill at full weight. Being discoverable to buyer-side agents under your credentials is structural to the platform — not a separate paywall.

Buyer-facing credentials — both manifest reads (Flow 1) and claim-graph access (Flow 2) — are not yet available. They are designed, and will be built when a buyer-side design partner commits to using them. The architecture and signing contracts are specified end-to-end, with implementation following counterparty readiness. The credential allowances in the table reflect the entitlement each tier will carry at general availability.

Interested in design-partner status? Get in touch.

What’s in each tier

Capabilities unlock as you move up. Every tier is agent-operable: an agent you connect over MCP can use every tool for the features your tier includes, narrowed only by the allowlist on its key. You pay for pursuits and agent operations, not for tool access.

Need a custom plan? Have specific compliance or deployment requirements?