Tenda

View saved version →

---
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.

View saved version →

---
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.

View saved version →

---
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.

View saved version →

---
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.