Loopio writes the response. It does not tell you whether to start.

What is the difference?

Qualification is the call: bid, no-bid, or review, before a word is written. Response is the artefact you lodge if the call was bid. Discovery is whether the pack reached you at all. Buying one to do another is how a content library becomes the firm’s only process.

Do you need Loopio, or a go/no-go tool?

If the last year contains a pursuit you wish you had declined in week one, you need a go/no-go tool first. That can be software that reads the pack, or a twenty-minute slot with twelve questions and an owner. Loopio will not produce that call. It will make the regretted draft easier to finish.

If the last year contains yeses that were slow because the library was a shared drive and nobody could find last time’s insurance certificate, Loopio or Responsive has a job. That job starts after the gate. Small professional-services firms, partner-led, under 50 people, almost always have the first pain and buy for the second. The invoice looks like progress. The pipeline does not.

You can own both. Many larger teams do. The order matters. Install the gate. Run the last five tenders through it. Then decide whether writing the remaining yeses is still the bottleneck. Stacking a library on an optional gate is how the gate becomes optional.

Can Loopio or Responsive do qualification?

They can host a form. Some implementations have a stage called qualify. Watch when it is filled. If it is filled after the project is created in the tool, it is a cover sheet. Qualification happens before anyone writes, with mandatories, liability, roster, and posture on the table, and with a person who is not the writer able to say no.

A checkbox named go/no-go inside a response workflow will be ticked go. The incentives point that way. The owner of the call cannot be the person measured on submissions. Software that lives in the writing environment will not change that, however many fields you add.

Where does discovery fit?

TenderSearch and the public portals answer whether you see the ATM. That is useful when you do not. It is not a substitute for a gate, and it is a poor companion to no gate at all. A better feed without a no-bid habit is a busier bid team, not a more disciplined one.

Free first: AusTender, the state portals, the panels you already sit on. Pay for discovery when the filters save hours you can name. Do not pay for it because a competitor’s BD person has a login.

What should a firm under 50 do this quarter?

Name the failing layer. Empty inbox: discovery, starting free. Full inbox of regretted work: qualification, starting with the scorecard if you will actually use it, or with software that reads the pack if you will not. Slow yeses on work that already fits: then Loopio, Responsive, or a drafting model.

Do not buy all three. A small bid team that spends the quarter implementing software is not making calls. The call is the product. Everything else is furniture.