nomoretools™

Practice / Tenders

Tenders

Answering a tender costs days. Most of that is not thinking. It is searching: the same certificates, the same references, the same sentences, this time in a different form.

← All workflowsGo to the interactive example ↓

The starting point

The work
in between.

  1. Tenders arrive through portals, by email and through a word from someone. A shared inbox is only automatic where an approved access or a dependable interface exists.
  2. Whether taking part is worth it is a gut call. The sums get done once two days are already in it.
  3. The certificates asked for sit in different places: some in a folder, some with the tax adviser, some already expired. Access, confidentiality and validity differ by source.
  4. The written answers are copied from the last tender. What stays in by accident is noticed only by whoever reads it.
  5. The deadline is absolute. A minute late is the same as not submitting.

A suitable design

What needs to
work together.

These components describe one possible individual scope. Scope and rules are agreed with your business.

01

One shared way in

Portals are connected through available, approved interfaces or exports, emails through the mailbox meant for them, and a word from someone is recorded deliberately. Imports that fail or are not possible stay visible instead of faking completeness.

02

The certificate cabinet

Every certificate with its expiry date. What runs out says so before it is needed, not in the moment it is missing.

03

Blocks of text with their provenance

Answers that have already been written and checked, with the case they came from beside them. They are carried over deliberately, not by accident.

04

The deadline counted backwards

From the submission date: what has to be ready when, and who supplies it. Not one date but a chain with lead time.

An example decision card

A tender fits your profile

Submission in 16 days. Of eleven certificates required, eight are on file and valid.

Two expire before the submission date and one is missing entirely. Nothing has been added.

What is being measured as a fit?
  • the work required matches four of your recent jobs
  • turnover threshold met
  • lot size within your usual range
  • → it fits formally. Whether it pays is your call.
Fictional starting point. You can interact with the following example.

07 · To watch

Eleven certificates. Two minutes instead of two days.

What happens here is not magic. It is a filing system that knows how long something is valid. Start the run and look at the last three lines.

nomoretools™ Submission in 16 days
11 certificates required
  1. Company register extract
  2. Trade licence
  3. Confirmation of no tax arrears
  4. Public liability insurance
  5. Balance sheet figures, last 3 years
  6. List of comparable references
  7. Self-declaration of reliability
  8. Quality management certificate
  9. Evidence of qualified staff
  10. Bank reference
  11. Declaration on the bidding consortium

An illustration. Which certificates are required is set out in the tender itself; the figures and deadlines here are invented.


The difference is the last three lines

Gathering eight certificates saves time. Knowing two weeks in advance that two expire and one is missing decides whether you can submit at all. One is convenience, the other is the job.

The missing one stays missing

It would be easy to produce something plausible for the last line. In a tender an invented declaration is not an inaccuracy but a ground for exclusion, and in the worst case more than that. What is not there stays visibly empty.

The countercheck

Where things
can go wrong.

The temptation is to have the written answers drafted for you. A text that reads well and describes the work wrongly costs more in a tender than not taking part, and in the worst case it binds you. So the agent only assembles what you have already written and checked, and marks every passage it wrote itself.

A useful first trial includes this failure case explicitly. Fast processing alone is not success if checking and correction create more work.

Your first stage

Start where
the work improves.

For Tenders, we choose a bounded first outcome with your team. Existing specialist systems can stay where they fulfil necessary requirements. We compare time relief, payments that can end and the cost of the new way of working.

The workshop gives you priorities and a roadmap. You can continue internally or with support from Markus Kirchmair. The choice of model and agent follows the task, with data and rules retained outside an individual chat.

Explore the workshop →

Ready for the next change

Keep the work simple.

The first view should show the next relevant decision. Reasoning and sources remain accessible. We leave out unnecessary features and make actual progress visible.

When a rule changes, agents can help investigate the impact, prepare the adjustment and update tests and documentation. A qualified person assesses the result and its adoption.

Try a change →

Your first step

Say yes
to less.

Less unnecessary software. More room for your work. Let’s find the useful first step.