Bid-ready pack

Signed in and read the account 1 call · 1 s

1. whoamisigned in0 s

   Arguments

   {}

   Answer

   {
    "authenticated": true,
    "via": "key",
    "data_as_of": "2026-09-23T04:20:37+00:00",
    "sources_live": [
     "ted",
     "cvp",
     "ft",
     "lv",
     "ee",
     "pl",
     "fr",
     "de",
     "… 10 more"
    ],
    "sources_late": [],
    "data_delay": {
     "hours": 24,
     "note": "Your tier excludes anything published in the last 24 hours, so every count here is of the delayed corpus. A recently added source loses a far larger share of its rows to this than a long-running one, and can look thinner than it is."
    },
    "email": "jobs-victano@example.test",
    "tier": "free",
    "persona": "supplier",
    "quota_remaining": {
     "doc_pages_per_day": "unlimited",
     "list_updates_per_day": "unlimited",
     "match_profile_per_week": "unlimited",
     "profiles_max": {
      "limit": 1,
      "renews": "never — this is a cap, not a rate",
      "used": 1,
      "remaining": 0
     },
     "search_per_day": "unlimited",
     "founding_beta": "Rate limits are l
   … (trimmed here; 1,387 characters in all)

Read the specification and find what would sink us 4 calls · 5 s

1. get_workflowplaybook read0.1 s

   Arguments

   {
    "id": "deep-read"
   }

   Answer

   {
    "id": "deep-read",
    "playbook": "# Read the specification and find what would sink us\n\nThis is the workflow that earns the subscription. A human reads sixty pages in two\nhours and skims the middle. You do not have to skim.\n\n## Before you start: how much of this notice can be read here\n\n`get_opportunity` and the first page of `read_document` tell you whether the corpus\nholds the specification or only the notice summary. On some national feeds (measured:\n**0% of open Spanish rows carry selection criteria inside the notice**) the buyer\nkeeps requirements on their portal and Victano holds the summary page only.\n\nWhen …",
    "personalisation": {
     "working_language": "en",
     "persona": "supplier",
     "memory_state": "on",
     "may_learn": [
      "result_style",
      "explain_scores"
     ],
     "known": {},
     "note": "Nothing learned for this workflow yet. If the user states a lasting prefer
   … (trimmed here; 1,277 characters in all)

2. get_opportunitynotice read0.3 s

   Arguments

   {
    "id": "ted:650568-2026"
   }

   Answer

   {
    "opportunity_id": "ted:650568-2026",
    "opportunity": {
     "id": "ted:650568-2026",
     "source": "ted",
     "source_id": "650568-2026",
     "type": "tender",
     "title": "Lithuania – Software maintenance and repair services – Vilniaus universiteto Gydytojų rezidentų administravimo informacinės sistemos priežiūros ir vystymo paslaugos, Nr. 6827/2026",
     "summary": "Vilniaus universiteto Gydytojų rezidentų administravimo informacinės sistemos priežiūros ir vystymo paslaugos.",
     "body_text": "Lithuania – Software maintenance and repair services – Vilniaus universiteto Gydytojų rezidentų administravimo informacinės sistemos priežiūros ir vystymo paslaugos, Nr. 6827/2026 Vilniaus universitetas (PV) Vilniaus universiteto Gydytojų rezidentų administravimo informacinės sistemos priežiūros ir vystymo paslaugos.",
     "buyer_name": "Vilniaus universitetas (PV)",
     "buyer_country": "LTU",
     "countries": 
   … (trimmed here; 5,079 characters in all)

3. read_documentnotice document read0.2 s

   Arguments

   {
    "id": "ted:650568-2026"
   }

   Answer

   {
    "opportunity_id": "ted:650568-2026",
    "from_page": 1,
    "pages_returned": 1,
    "total_pages": 1,
    "text": "Lithuania – Software maintenance and repair services – Vilniaus universiteto Gydytojų rezidentų administravimo informacinės sistemos priežiūros ir vystymo paslaugos, Nr. 6827/2026 Vilniaus universitetas (PV) Vilniaus universiteto Gydytojų rezidentų administravimo informacinės sistemos priežiūros ir vystymo paslaugos.",
    "more": false,
    "source_url": "https://ted.europa.eu/en/notice/-/detail/650568-2026",
    "data_as_of": "2026-09-23T04:20:37+00:00",
    "sources_live": [
     "ted",
     "cvp",
     "ft",
     "lv",
     "ee",
     "pl",
     "fr",
     "de",
     "… 10 more"
    ],
    "sources_late": [],
    "data_delay": {
     "hours": 24,
     "note": "Your tier excludes anything published in the last 24 hours, so every count here is of the delayed corpus. A recently added source loses a far larger share of its rows to thi
   … (trimmed here; 3,226 characters in all)

4. read_documentnotice document read0.3 s

   Arguments

   {
    "id": "cvp:9724122"
   }

   Answer

   {
    "opportunity_id": "cvp:9724122",
    "from_page": 1,
    "pages_returned": 1,
    "total_pages": 1,
    "text": "Vilniaus universiteto Gydytojų rezidentų administravimo informacinės sistemos priežiūros ir vystymo paslaugos, Nr. 6827/2026 Vilniaus universitetas (PV) Atviras konkursas cpv primary: 72267000. cpv division: 72. cpv label: Programinės įrangos priežiūros ir tvarkymo paslaugos. object type: Paslaugos SPK kategorija. procedure kind: Atviras konkursas. contract type: Pirkimo sutartis. eu funded: Ne. duration: 36 months. threshold: Virš. award criterion: Kaina/Sąnaudos. object description: Vilniaus universiteto Gydytojų rezidentų administravimo informacinės sistemos priežiūros ir vystymo …",
    "more": false,
    "source_url": "https://viesiejipirkimai.lt/epps/cft/prepareViewCfTWS.do?resourceId=9724122",
    "data_as_of": "2026-09-23T04:20:37+00:00",
    "sources_live": [
     "ted",
     "cvp",
     "ft",
     "
   … (trimmed here; 2,027 characters in all)

Draft clarification questions before the deadline 1 call · 0 s

1. get_workflowplaybook read0.1 s

   Arguments

   {
    "id": "clarification-questions"
   }

   Answer

   {
    "id": "clarification-questions",
    "playbook": "# Draft clarification questions before the deadline\n\nClarification questions are the one lever a bidder has to change the shape of a tender\nafter it is published, and they are free. Most small suppliers never ask any, usually\nbecause they assume asking signals weakness. It does not. It signals that someone read\nthe documents.\n\nThe window closes well before the submission deadline, often a week or more before.\nCheck that date first and say it out loud, because missing it means bidding on your\nown guess. On search cards, `get_opportunity` and `read_document`, read\n`clarification_time_left` when …",
    "personalisation": {
     "working_language": "en",
     "persona": "supplier",
     "memory_state": "on",
     "may_learn": [
      "result_style"
     ],
     "known": {},
     "note": "Nothing learned for this workflow yet. If the user states a lasting pre
   … (trimmed here; 1,264 characters in all)

Build the compliance matrix and response plan 1 call · 0 s

1. get_workflowplaybook read0.1 s

   Arguments

   {
    "id": "response-plan"
   }

   Answer

   {
    "id": "response-plan",
    "playbook": "# Build the compliance matrix and response plan\n\nThe compliance matrix is the difference between a bid that scores and one that gets\nmarked down for omissions nobody intended. Every requirement in the documents becomes\na row, and every row gets an owner and a place in the response.\n\n## Build the matrix\n\nRead the specification, the selection questionnaire and the scoring guidance together.\nFor every requirement, mandatory or scored, create a row:\n\n| # | Requirement (quoted) | Source doc, section, page | Mandatory or scored | Weight | Where we answer it | Owner | Evidence needed | Status …",
    "personalisation": {
     "working_language": "en",
     "persona": "supplier",
     "memory_state": "on",
     "may_learn": [
      "result_style"
     ],
     "known": {},
     "note": "Nothing learned for this workflow yet. If the user states a lasting preference, offer t
   … (trimmed here; 1,248 characters in all)

Draft the proposal skeleton from the award criteria 1 call · 0 s

1. get_workflowplaybook read0.1 s

   Arguments

   {
    "id": "proposal-skeleton"
   }

   Answer

   {
    "id": "proposal-skeleton",
    "playbook": "# Draft the proposal skeleton from the award criteria\n\nThe structure of a winning bid is not a matter of taste. It follows the evaluator's\nscoring sheet, because the evaluator reads with that sheet beside them and marks in\nthe order it is written.\n\n## Read the award criteria first\n\n**Ask this corpus for them first.** Where the buyer published the criteria and their\nweights, `read_document` returns `qualification.award_criteria.scored_on` on page 1: the\nbuyer's own wording for each criterion, paired with its number. Beside it,\n`weights_expressed_as` says whether those numbers are percentages …",
    "personalisation": {
     "working_language": "en",
     "persona": "supplier",
     "memory_state": "on",
     "may_learn": [
      "result_style"
     ],
     "known": {},
     "note": "Nothing learned for this workflow yet. If the user states a lasting preference
   … (trimmed here; 1,257 characters in all)

Work out where you need a partner 1 call · 0 s

1. get_workflowplaybook read0.1 s

   Arguments

   {
    "id": "consortium-fit"
   }

   Answer

   {
    "id": "consortium-fit",
    "playbook": "# Work out where you need a partner\n\nSmall suppliers reject good opportunities because of one missing thing: turnover,\na certification, capacity, a country, a reference. EU procurement explicitly allows\ngroups of economic operators to bid jointly, and allows bidders to rely on the\ncapacities of other entities. Most small suppliers do not know this, or do not know\nhow to use it.\n\n## Before you start: what eligibility-screen gave you\n\nThis workflow usually starts from the `eligibility-screen` workflow's output. That\nworkflow produces one of two things:\n\n- **A verdict table** with HAVE / CAN GET …",
    "personalisation": {
     "working_language": "en",
     "persona": "supplier",
     "memory_state": "on",
     "may_learn": [],
     "known": {},
     "note": "Nothing learned for this workflow yet. If the user states a lasting preference, offer to remember 
   … (trimmed here; 941 characters in all)

Wrote the document from the results 63 s, no tool calls