06 / Tender alerts

SmartQS Tender Alerts

Public tenders matched to a contractor's CIDB grading and regions, emailed twice a week, with the compulsory briefings they can still attend at the top.

Year
2026
Status
In build.
The SmartQS tenders list: briefings ahead, each card with the compulsory briefing date, venue and grading.

The problem, stated properly

Miss a compulsory site briefing and your bid is thrown out, however good your price is. The briefing is usually set about eleven days after the advert goes up, so by the time a tender surfaces in a weekly roundup, the meeting has often already happened. Contractors solve this by checking portals daily. Most don't have the time.

A contractor tells us three things once: class of works, grading, regions. Twice a week they get only the tenders that match and are still open, ordered so the ones they can still act on come first.

The rule that shaped it

The SMS is not a shorter report. It is the one fact that expires.

The email is the report. The SMS leads with the briefings still ahead, names the first one in full, and links to the rest. The composer trims to two GSM-7 segments and strips anything outside that alphabet, because one en dash turns the whole message into UCS-2 and halves what fits.

The SmartQS email report.
The email. Briefings ahead, new since last time, closing within seven days. Never an empty email.
The alert profile: class of works, grading, regions.
The profile: three things, told once.
The tenders list on a phone.
On a phone, where a contractor on site actually reads it.

What it is built from

  • Python + FastAPI
  • Postgres
  • React + Vite
  • eTenders OCDS ingest three times a day
  • Claude Haiku for classification, cached forever
  • Resend and Twilio

Known limits

Stated plainly, because a client should know what they have.

  • The first live SMS to a South African number depends on a registered sender.
  • Site scrapers beyond eTenders are phase two.

Need something like this to run on?

A thirty-minute call, then a written scope within five business days. No obligation either way.

Start a project
Call
30 minutes
Scope
5 business days
Build
Weeks, in the open