The craft, written by
people who practised it.

The situation

The tender pack arrives with a two-hundred-row Excel grid due in a fortnight. Half the questions were already answered last year, in another bid, but nobody knows which one. Technical experts get pulled in for information they have already written down.

What the tool does

The grid is ingested as it stands, row by row. Questions already covered by your knowledge base come back with the named source extract they came from. Anything without a match stays empty and visible: that, and only that, is where an expert's judgement is required.

Your experts open a file where their work is limited to what has never been written.

The situation

The technical proposal is built on a Word template signed off by the communications team: styles, footers, diagrams, tables. Every trip through a generation tool sends it back reformatted, and someone spends a day putting the brand back together. The diagrams do not always survive at all.

What the tool does

Sections you have not edited come back as your document's original bytes, meaning a byte-for-byte XML clone, images and tables included. The brand is therefore not re-rendered and then repaired. It survives because those parts of the file are never opened.

The document that comes out is the one your communications team signed off.

The situation

Three tender packs land in the same week. The committee keeps one. The criteria exist, but they live in two people's heads and in a spreadsheet everyone fills in differently. The decision gets made, but it cannot be shown, and six months later nobody knows why that particular bid was the one.

What the tool does

Requirements are broken down the moment the pack lands. Your own qualification criteria are carried into a scored grid, with a technical Fit Score kept separate. The output is not a verdict: it is the score broken out criterion by criterion, with what it rests on.

The decision stays yours, and you can explain it to the committee, or to yourself six months later.

The situation

The bid circulates as email attachments. The version that ships is not always the one legal reviewed. Chasing happens by email, tracking lives in a side spreadsheet, and the day before submission nobody knows for certain what has been approved, or by whom.

What the tool does

One version, inside the platform. Contributions and approvals happen where the content lives, with history attached to each section. Tasks go out to contributors from the bid itself, without routing through an inbox.

The day before submission, you read the state of the bid instead of reconstructing it.

The situation

The result comes in. It gets ten minutes in a team meeting, someone promises a debrief, and the next bid starts up. A year later the same weakness shows up in the same section, and nobody connects the two because nothing was written anywhere that gets read again.

What the tool does

The bid is scored across eight dimensions once the decision is in, won or lost. What worked against a given competitor stays available for the next bid, attached to the relevant sections rather than to a write-up nobody reopens.

The debrief becomes an input to the next bid, instead of an intention.