Jobs · Bid manager at an SME supplier

Bid-ready pack: from 'we are bidding' to the frame the team writes into

We have decided to bid on this tender. What do we write, what do we ask, and what could sink us?

The run

One real run of this job against Victano’s live service. The steps are the playbooks it chains; open one to see each tool call, its arguments and what came back.

1. Signed in and read the account

   1 tool call, 1 s

   Tools used

   Victanoreturned authenticated, via, data_as_of, sources_livewhoami0.0 s

   Call 1: whoami with

   {}

   {"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": …

2. Read the specification and find what would sink us

   4 tool calls, 5 s

   Tools used

   Victanoplaybook readget_workflow0.1 s

   Call 2: get_workflow with

   {"id": "deep-read"}

   {"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": "suppl …

   Victanoreturned opportunity_id, opportunity, data_as_of, sources_liveget_opportunity0.3 s

   Call 3: get_opportunity with

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

   {"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 universite …

   Victanoreturned opportunity_id, from_page, pages_returned, total_pagesread_document0.2 s

   Call 4: read_document with

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

   {"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 e …

   Victanoreturned opportunity_id, from_page, pages_returned, total_pagesread_document0.3 s

   Call 5: read_document with

   {"id": "cvp:9724122"}

   {"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":  …

3. Draft clarification questions before the deadline

   1 tool call, 0 s

   Tools used

   Victanoplaybook readget_workflow0.1 s

   Call 6: get_workflow with

   {"id": "clarification-questions"}

   {"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": …

4. You confirm

   Send the clarification questions to the buyer.

   Recorded: Checkpoint: I'm assuming the user will send the questions in section 2 through the CVP IS messaging route, and only after checking that the tender pack doesn't already answer them. The rows in section 3 will change once those answers come in.

5. Build the compliance matrix and response plan

   1 tool call, 0 s

   Tools used

   Victanoplaybook readget_workflow0.1 s

   Call 7: get_workflow with

   {"id": "response-plan"}

   {"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" …

6. You confirm

   Accept the compliance matrix.

   Recorded: Checkpoint: I'm assuming the user accepts the matrix in section 3 as a starting point that only covers the notice. It will be rebuilt once someone reads the pack on the portal.

7. Draft the proposal skeleton from the award criteria

   1 tool call, 0 s

   Tools used

   Victanoplaybook readget_workflow0.1 s

   Call 8: get_workflow with

   {"id": "proposal-skeleton"}

   {"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",  …

8. Work out where you need a partner

   1 tool call, 0 s

   Tools used

   Victanoplaybook readget_workflow0.1 s

   Call 9: get_workflow with

   {"id": "consortium-fit"}

   {"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", …

9. Wrote the document from the results

   63 s, no tool calls

The bid-ready pack it handed back

Start it yourself

Connect Victano to Claude, ChatGPT or Cursor (how), then paste this line followed by your own facts.

Where you decide

• Send the clarification questions to the buyer.
• Accept the compliance matrix.

What it will not do

• Write the proposal answers
• Send anything to the buyer
• Invent references, CVs, figures or certificates

The scenario

The company in this run is illustrative and invented. This is exactly what the assistant was asked, including the job instructions it was given (the job ships to every client as the prompt job-bid-ready-pack):

Use Victano to run the bid-ready pack job (job-bid-ready-pack) on the tender below: risks, clarification questions, compliance matrix, proposal skeleton and partner gaps.

The situation (illustrative):
Baltijos IT Paslaugos UAB is an invented company used for this demonstration: a 40-person software company in Vilnius that maintains and develops public-sector information systems, ISO 27001 certified, turnover about EUR 3 million. We have decided to bid on Vilnius University's tender for the maintenance and development of its medical residents administration information system, TED notice ted:650568-2026. Build the bid-ready pack. You do not need to wait for me at the checkpoints.

This session is already signed in to Victano with a test account; start with whoami.

Work it as the job "Bid-ready pack: from 'we are bidding' to the frame the team writes into". Read each playbook with get_workflow and follow it, in this order: deep-read, clarification-questions, response-plan, proposal-skeleton, consortium-fit. The job's own instructions follow.

# Bid-ready pack: from "we are bidding" to the frame the team writes into

Sources, not advice: the pack quotes the tender and marks every place where the company must supply its own evidence.

## When

The team has decided to bid on one tender. You are running a whole job: it ends with the pack the team starts writing from. Each stage hands the next its input and delivers something on its own if the conversation is cut short.

## Run

1. **Read it all.** Read `get_workflow('deep-read')`. `get_opportunity` for the record and the document inventory, then `read_document` page by page until `more` is false, noting the page for every finding. Sort the risks into Fatal, Priceable and Clarifiable. If the corpus holds only the notice summary, say so first and carry on with what it holds. A Fatal risk stops the job: say the bid decision no longer holds.
2. **Clarification questions.** Read `get_workflow('clarification-questions')`. From the Clarifiable bucket only; each question quotes its clause; the message states the route and the clarification deadline.
3. **Compliance matrix.** Read `get_workflow('response-plan')`. One row per stated requirement, quoted, with where it appears. Take the award criteria and weights from `qualification.award_criteria.scored_on` on the first page of `read_document` when the buyer published them there, and say whether they are percentages or points.
4. **Proposal skeleton.** Read `get_workflow('proposal-skeleton')`. One section per award criterion, sized by its weight, with the claim each section makes and an evidence slot for each claim.
5. **Partner gaps.** Read `get_workflow('consortium-fit')`. From the requirements the company cannot meet alone: the gap, the structure that fits, what the partner must bring, whether the deadline leaves time.

## Checkpoints

- After the clarification questions: the user sends them. Hand them over ready to paste and carry on; answers change rows, not structure.
- After the compliance matrix: the user accepts it. Show it, then continue unless told otherwise.

## Deliverable

```
Bid-ready pack: <tender title> (<id>), <buyer>
Closes <date> (<working days> working days from <today>). Clarifications close <date>.
Read: <pages read> of <pages held>. Not held here: <documents on the buyer's portal>.

1. What could sink it: Fatal, Priceable (with the cost), Clarifiable, each with where.
2. Questions for the buyer, ready to send, with the route and the deadline.
3. Compliance matrix: # | requirement (quoted) | where | mandatory or scored | weight | where we answer it | owner | evidence needed | status
4. Proposal skeleton: sections in award-criteria order, weight, word budget, the claim, the evidence slot.
5. Partner gaps: gap, structure, what the partner brings, whether time allows it.
6. Could not verify.
```

## Quality

- Requirements are quoted, never paraphrased; every requirement, weight, date and quotation comes from a tool result in this conversation.
- A weight the buyer did not publish reads "not published in the notice"; an inferred weight is labelled inferred.
- Working days, counted from a stated date; the pack says how many pages it read.

## Will not

- Write the proposal answers. It builds the frame a person writes into.
- Send anything to the buyer. The questions are drafts for the user to send.
- Invent evidence: references, CVs, figures and certificates come from the company.

This run is recorded without a person present. At each checkpoint, write one line that starts with "Checkpoint:" stating what you are assuming, then continue. End with the finished work product.

Recorded 23 September 2026. Every tool call, notice, date, count and quotation on this page is what Victano’s live service returned in that run; nothing was edited except by trimming long tool results. Source file: content/jobs/bid-ready-pack.run.json.