Save this plugin to Following and return to review observed changes. Follow up to 10 plugins free.
Description
From the marketplace listing
Tenda helps businesses find public sector contracts to bid for, and win them. It reads tender notices from official government sources and explains each one in plain English: what the buyer wants, when bids close, which portal to bid through, the conditions you must meet and how bids are scored.
Tenda covers the UK (Find a Tender, Contracts Finder and Public Contracts Scotland), the US federal government (SAM.gov), the Government of Canada (CanadaBuys), every public buyer in Germany and France, and the rest of the European Union above the EU thresholds (TED).
Ask Tenda to:
- Find open tenders and upcoming opportunities by what is being bought, place, kind of buyer, value and closing date.
- Explain a tender: its lots, value, deadline, conditions of participation and award criteria.
- Show who won past contracts, what buyers paid and which contracts are due to be tendered again.
- Judge how well a tender fits your company, with the reasons for and against and anything that would rule you out.
- Check which registrations, certifications, insurance and policies you need before you bid.
- Brief you on a bid answer from the buyer's criteria and word limits, or check your draft the way an evaluator would.
- Watch for new tenders, and for clarifications, deadline changes and awards on the ones you follow.
Signed in to a Tenda account, your team can also save its company profile, track tenders in a shared pipeline, record bid and no-bid decisions, run a bid sprint against the deadline, set up automations such as a weekday shortlist of the best new fits, and have Tenda draft a whole bid for you to review and edit.
Searching and explaining tenders works without an account. Tenda gives guidance, not guarantees: it never promises that a bid will win, and a person should review every bid before it is submitted.
Language: English · Automatically detected from descriptions.
Skill · Oct 28, 2026 · 13:03 UTC · Compared with Oct 24, 2026 · 13:45 UTC
WHAT CHANGED
Instructions updated for write-and-check
Skill instructions — Now says: ---
name: write-and-check
description: Write a tender's bid answers with the person, answer by answer, and check each the way an evaluator would before it...
Observed in instructions or declared skills. Runtime behavior has not been tested.
---
name: write-and-check
description: Write a tender's bid answers with the person, answer by answer, and check each the way an evaluator would before it goes in.
---
# Write and check
1. Find the questions: call `add_tender_do...
After
Oct 28, 2026 · 13:03 UTC
---
name: write-and-check
description: Write a tender's bid answers with the person, answer by answer, and check each the way an evaluator would before it goes in.
---
# Write and check
1. Find the questions: call `add_tender_documents...
Skill · Oct 28, 2026 · 13:03 UTC · Compared with Oct 24, 2026 · 13:45 UTC
WHAT CHANGED
Instructions updated for weekly-scan
Skill instructions — Now says: ---
name: weekly-scan
description: Go through this week's public tenders for the person's company, pick the few worth a look, and say what changed on the...
Observed in instructions or declared skills. Runtime behavior has not been tested.
---
name: weekly-scan
description: Go through this week's public tenders for the person's company, pick the few worth a look, and say what changed on the ones they follow.
---
# Weekly scan
1. Call `get_tender_updates` for what ...
After
Oct 28, 2026 · 13:03 UTC
---
name: weekly-scan
description: Go through this week's public tenders for the person's company, pick the few worth a look, and say what changed on the ones they follow.
---
# Weekly scan
1. Call `get_tender_updates` for what changed...
Skill · Oct 28, 2026 · 13:03 UTC · Compared with Oct 24, 2026 · 13:45 UTC
WHAT CHANGED
Instructions updated for setup
Skill instructions — Now says: ---
name: setup
description: Set up Tenda once it is installed. Opens Tenda's setup in the chat, where the person names their company, picks where it works...
Observed in instructions or declared skills. Runtime behavior has not been tested.
---
name: setup
description: Set up Tenda once it is installed. Opens Tenda's setup in the chat, where the person names their company, picks where it works and what it does, and sees the open tenders that fit.
---
# Set up Tenda
...
After
Oct 28, 2026 · 13:03 UTC
---
name: setup
description: Set up Tenda once it is installed. Opens Tenda's setup in the chat, where the person names their company, picks where it works and what it does, and sees the open tenders that fit.
---
# Set up Tenda
Call `...
From the developer’s listing and package; capabilities are not independently tested. Package observed Nov 2, 2026.
Declared capabilities
Find open public tenders and upcoming opportunities
Explain a tender in plain English
Look up past contract awards and upcoming re-tenders
Declared limitations
Unrelated request
Jobs are not tenders
Portal passwords and submitting bids
Review scenarios; not an exhaustive list.
Cost & access
Tenda doesn't sell anything in ChatGPT. It never shows plans, prices, upgrades or checkout links there; Tenda's paid plans are bought on Tenda's own site.
Terms may have changed since this observation.
Starter prompt
Find open IT support tenders in the UK closing in the next month
---
name: bid-or-no-bid
description: Help the team decide whether to bid on one tender, from its fit, its conditions, the competition and the buyer's history, then record the call.
---
# Bid or no bid
1. Call `get_tender_details` for what is bought, the value, the deadline, the conditions and how bids are scored. Its competition facts say who holds the contract now, what the buyer paid before and how many bids it usually gets.
2. Call `assess_tender_fit` for the reasons for and against, and anything that rules the company out.
3. Call `check_bid_readiness` with the tender, for what the company is missing before it can bid.
4. If the buyer's documents matter, call `add_tender_documents` with `read_published` true, for the checklist of what the bid must include.
5. Put Tenda's five questions to the user in one short list, with what you found for each: fit, eligibility, capacity, competition and value. Let them answer.
6. Once the user says bid or no bid, confirm it and call `record_bid_call` with their answers and reason.
- The decision is the team's. Give your view only when asked, and say what it rests on.
- Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.
---
name: setup
description: Set up Tenda once it is installed. Opens Tenda's setup in the chat, where the person names their company, picks where it works and what it does, and sees the open tenders that fit.
---
# Set up Tenda
Call `set_up_tenda` straight away, with no arguments. It shows Tenda's setup in the chat, and the person finishes it there.
- Say one short line with it, such as "Let's set up Tenda." Don't list the steps: the setup shows them.
- If ChatGPT asks the person to sign in to Tenda first, call `set_up_tenda` again once they have.
- Once it's done, the person can open Tenda from ChatGPT's sidebar. If they ask what next, offer to show the tenders that fit best with `assess_tender_fit`.
- Never mention Tenda's plans, prices or upgrades.
---
name: weekly-scan
description: Go through this week's public tenders for the person's company, pick the few worth a look, and say what changed on the ones they follow.
---
# Weekly scan
1. Call `get_tender_updates` for what changed on the tenders the team follows: deadline changes, clarifications, cancellations and awards. Lead with anything that needs action this week.
2. Call `assess_tender_fit` with no tender to rank the open tenders that fit the saved company profile. If there's no profile, ask what the company does and where, then use `search_tenders` with `published_since` set to seven days ago.
3. For the best three, give the buyer, value, closing date, the fit score and the one reason for and against that matters most. Link each notice.
4. Offer the next step for one of them: the bid or no-bid call (the bid-or-no-bid skill), or adding it to the pipeline with `add_to_pipeline`.
5. If the person wants the best new fits every weekday without asking, offer Tenda's morning shortlist: call `add_automation` with `template` "morning_shortlist", read its rules back, and call `turn_on_automation` only once they say yes.
- If a search finds nothing, call `get_coverage` before saying a tender isn't public, and say which sources were read and when.
- Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.
---
name: write-and-check
description: Write a tender's bid answers with the person, answer by answer, and check each the way an evaluator would before it goes in.
---
# Write and check
1. Find the questions: call `add_tender_documents` with `read_published` true, or with the text the user shares. Use the scored questions, word limits and weights it returns.
2. For each question, call `draft_bid_response` with the question, its limit and the user's own evidence, then show the draft.
3. Call `review_bid_draft` on each answer the user is happy with, and fix what it marks down before moving on.
4. If the user wants Tenda to draft the whole bid instead, call `start_bid_draft` and follow what it says about confirming first. Check progress with `get_bid_draft`, which also gives the Word file when it's ready.
- Use only facts the user or their saved profile gives. Never make up case studies, numbers or accreditations.
- A person must read every answer before it's submitted. Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.
Release notes
Check the details or fit of up to 20 tenders at once. With a Tenda account, set up automations such as a weekday shortlist of the best new fits, share a tender as a link anyone can open, take a tender off the pipeline, and save the company's trading name and the classification codes it works under.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
