← The JournalAiForm Studio / Procurement

Procurement Notes / 03 / Building AiForm Procure

The Goal Isn't More Bids. It's Better Bid Decisions.

Why finding more tenders is only useful if suppliers can decide which opportunities are actually worth pursuing

By TE Motaung · 14 September 2026 · 6 min read

A business professional walks through a minimalist architectural space toward diverging paths, representing the judgement and choices involved in deciding which procurement opportunities to pursue.

One of the easiest ways to describe a tender platform is by volume.

How many opportunities are available? How many sources are being monitored? How many new tenders were added today? To me, those numbers matter; hence, I pay attention to them while building AiForm Procure too. But I'm becoming increasingly convinced that they are not the most important measure of whether procurement technology is actually useful to a supplier. This is because a supplier doesn't need to bid on more tenders; it needs to make better decisions about which tenders deserve a bid in the first place. And those are two very different objectives.

Discovery solves only the first problem

Public procurement can be difficult to navigate because different institutions publish opportunities across different sources, at different times, and in different formats. That creates an obvious technology problem: make those opportunities easier to discover.

Aggregation helps. Search helps. Filters help. Alerts help. And matching helps. However, these things can dramatically reduce the amount of time a supplier spends looking for opportunities. There is, however, a point at which better discovery creates another problem.

You find more.

Now what?

If a business moves from seeing 20 opportunities to seeing 2,000, we haven't necessarily made procurement easier. We may simply have replaced scarcity of information with abundance of information. The next problem becomes judgement.

Relevant doesn't necessarily mean suitable

Imagine a cleaning company receives a tender match. The category is correct while the location is within its operating area. Further, the closing date gives the business enough time to respond. On the surface, that's a good match. Then the supplier opens the documents. Perhaps the contract requires experience at a scale the company cannot demonstrate. Perhaps there is a compulsory briefing it has already missed. Perhaps the required equipment would demand substantial upfront capital. Perhaps the payment structure would put too much pressure on cash flow. Or perhaps the tender requires certifications, personnel, or previous projects the supplier cannot prove.

The matching system wasn't necessarily wrong.

The opportunity is relevant.

It just isn't necessarily pursuable.

That's an important distinction.

A match should start a decision, not finish one

This is something I've been thinking about quite a lot while building AiForm Procure. Procurement technology naturally wants to become smarter. We want better recommendations, better matching, better alerts, and better supplier profiles.

Eventually, it becomes tempting for the technology to say:

“This tender is for you.”

I think we need to be careful with that since a platform can know quite a lot about a supplier, its industry, location, CSD information, B-BBEE information, where applicable, company information, verified records, and its previous areas of work. And increasingly, technology can extract and understand quite a lot about the tender too. But the final bid decision involves something much more contextual.

Can this particular business deliver this particular contract, under these particular conditions, at this particular moment?

That's not simply a matching problem, but a business decision.

Five questions before a bid

I think a useful procurement platform should increasingly help suppliers answer five questions quickly.

1. Do we qualify?

Start with the non-negotiables. Mandatory documents. Registrations. Briefings. Certifications. Grading requirements where applicable. Functionality thresholds. Whatever the tender specifies.

If there is a requirement the supplier cannot satisfy, discovering that early is valuable. There is little benefit in spending hours preparing the rest of a submission that cannot progress beyond the compliance stage.

2. Can we actually deliver?

This is different from asking whether the tender falls within your industry. A company may provide a particular service but not have the capacity for a contract of that size.

Think about people, equipment, suppliers, geography, operational capacity, working capital, and existing commitments. Winning a contract creates an obligation to perform it.

3. Can we prove it?

This is one of the subtler procurement problems.

Capability and demonstrable capability are not always the same thing.

A business may genuinely be able to perform the work. But if the tender requires three reference letters, evidence of previous projects of a certain value, particular qualifications, or specific technical documentation, the evaluation will depend on what the supplier can demonstrate. Knowing this before preparing the bid matters. A lot!

4. Do we have enough time?

This week's AiForm Procure data gave us a useful illustration. On Friday, the platform was tracking 2,085 open RFQs, of which 785 were live and accepting bids. By Monday, the total had barely changed at 2,087. But only 682 were still live and accepting bids.

The headline volume barely moved.

The opportunity window did.

Tender discovery therefore has a time dimension. A perfect opportunity discovered after a compulsory briefing—or hours before closing—isn't particularly useful.

5. Does it make business sense?

This may be the most important question of all. Procurement discussions naturally focus on winning. But winning isn't automatically good business.

Can you price the work sustainably? Can you fund delivery before payment arrives? What happens if costs increase? What resources will the contract consume? What other work might you have to turn away? What is the risk relative to the potential return?

Sometimes the commercially intelligent decision is to bid. And sometimes it is to walk away.

Passing is also a procurement decision

This is perhaps the part we don't celebrate enough. A business spends four hours assessing a tender and decides not to bid. Was that time wasted? Not necessarily.

If that assessment prevented the business from spending several days preparing a submission it was unlikely to win—or from winning a contract that would have created serious operational problems—then the assessment created value.

A good no-bid decision can be as important as a good bid decision!

That changes how I think about the role of procurement technology. Success shouldn't only be measured by how many opportunities we show you or even how many opportunities you bid on. A better question might eventually be how much unnecessary bidding did we help you avoid?

This matters particularly for smaller businesses

Large organisations can have dedicated bid teams. Someone can monitor opportunities. Someone else can interpret specifications. Finance can model the numbers. Technical staff can assess delivery requirements. Management can make the final decision.

Many SMEs don't have that structure.

The person discovering the tender may also be the person running the business, preparing quotations, managing staff, speaking to customers, and worrying about cash flow.

For that supplier, every unnecessary bid has a real cost. Not only money.

Time!

That makes precision more valuable than volume. Ten genuinely relevant opportunities may be considerably more useful than 1,000 loosely related ones. And one opportunity that the business is well positioned to pursue may be worth more than all of them.

Where I think procurement technology should go next

The first generation of procurement discovery asks:

Where are the opportunities?

The next asks:

Which opportunities are relevant to me?

I think the more interesting question now is:

Which of those opportunities am I actually positioned to pursue?

That requires several layers to begin working together. Opportunity discovery. Supplier information. Verification. Tender requirements. Matching. Timing. And ultimately, human judgement. This is also where the distinction I wrote about previously becomes important:

Supplier compliance is reusable. Tender compliance is contextual.

If a platform already knows verified information about a supplier, the supplier shouldn't have to mentally start from zero every time it opens another opportunity. The technology should help bring what is already known about the business into conversation with what this particular tender requires.

Not to manufacture certainty. Not to promise qualification. And certainly not to automatically tell the supplier to bid. But to make the decision easier to understand.

Something like:

Here's what appears to match.

Here's what requires your attention.

Here's what we don't know.

Now decide.

Better discovery should lead to better judgement

I still believe South African procurement has a discovery problem. Making public opportunities easier to find remains important. But discovery cannot be the destination. If technology simply helps suppliers find more tenders and encourages them to submit more bids, we may only be making an inefficient process happen faster.

The more interesting opportunity is to help businesses become more selective. Find the opportunity. Understand it. Assess the fit. Know when to pursue it. And know when to pass.

Because ultimately, the goal isn't more tenders. It isn't even more bids.

It's better bid decisions.

TE Motaung, Founder, AiForm Procure

Find more. Search less.

Built from this thinking

AiForm Procure

A South African procurement platform exploring how discovery, supplier verification and opportunity intelligence can support better procurement decisions.

View the AiForm Procure case study
Procurement Notes / 04

Supplier Compliance Is Reusable. Tender Compliance Is Contextual.

Procurement Notes / 05

One Search. More Sources.

View all Procurement Notes