← Insights

What a Tender costs, and why re-runs are free for sixty days

Per package, not per seat; free re-runs through addenda and clarification rounds; the library free to maintain. Pricing shaped by how a bid actually unfolds.

2 October 2026 · Tender Answer team · 2 min read

A bid involves a bid manager, two proposal engineers, three design engineers for a day, QA for an hour and commercial at the end. Half of them touch the tool once per tender. Seat pricing would charge for people who answer one question. So Tender Answer meters tender packages.

The unit

One Tender is one package analysed end to end: register, matrix, deviation table, draft response, engineer question list and clarification questions, for a package up to 300 pages. Each additional 150 pages is 0.3; each additional lot's data sheets in a multi-lot package is 0.3. Pay as you go is USD 180; annual plans include a monthly pool and bill overage lower.

Sixty days of re-runs, free

A bid is not one event. Addenda arrive; engineers answer questions; the buyer runs a clarification round after submission. Every one of those changes the matrix. Charging per re-run would make teams hesitate to upload the addendum or forward the clarification, which is backwards. Anything on the same tender within sixty days is free.

Frameworks

A framework matrix is the baseline for years of call-offs. Call-offs within sixty days are free; after that, a call-off answered as a delta is 0.3 of a tender — because that is roughly what it is.

The library is free

Uploading and maintaining datasheets, certificates, ITPs and past responses costs nothing. A library with gaps produces a matrix full of Needs engineer, which defeats the purpose; nothing should discourage completeness.

Model tokens as a separate line

Tender packages and documentation libraries are long. Reading them is token-heavy, and the cost appears as its own meter at the provider's list price — model_access_usd — with the ledger showing tokens per tender. With your own key the meter is zero.

On the Google Cloud invoice

Annual plans bill once at purchase through Marketplace; included tenders are netted in the workspace and only overage is reported hourly as tenders. Both meters appear as separate line items on your existing Google Cloud invoice and count toward commitment. Every tender carries a request id.

Caps

Monthly tender cap and model-spend cap per workspace. At the cap, new tenders queue and the owner is told.

Related

Tender Answer is in early access.

We are onboarding a small number of design partners with real documents and real deadlines. Tell us what you work on and we will set up a workspace with your material.