JavaScripting VS TenderRadar.co.uk

TenderRadar.co.uk's answer:

UK organisations that sell to the public sector and do not have a bid team sitting on a licence for an enterprise procurement platform. In practice that means SMEs, universities and colleges, consultancies, training providers and charities.

Typical users are business development managers, bid writers and owner-managers: people for whom checking four portals every morning is a job that gets skipped in a busy week.

Larger organisations run a separate radar per department, so estates, research and professional services each see their own pipeline rather than everyone's. Agencies and consultancies run several client accounts from one login.

TenderRadar.co.uk's answer:

Every match carries the reason it was shown. Most alert services hand you a list and leave you to work out why each thing is on it; Tender Radar puts the reasoning beside each notice, so you can disagree with it and tune the profile.

It also works backwards from award data, not just forwards from new notices. Because contract end dates are published, it knows which 31,000 UK contracts end in the next 18 months, who holds each one and which buyer let it. That is the window in which an incumbent can be displaced, and it opens months before any notice appears.

And the underlying data is free to browse. Buyer, supplier, CPV and framework pages, including which suppliers sit on which framework agreements, are open without an account.

TenderRadar.co.uk's answer:

Price and honesty about what is in the box. One plan at £30 a month covers every feature, with unlimited recipients and no per-seat charge. Comparable products start at £99 to £199 a month, and the enterprise platforms run into five figures a year.

There are no feature tiers, so the renewal radar, the framework data and the intelligence pages are not upsells. There is no sales call before you can see whether it works: 30 days free, no card.

Every published figure has a method page showing how it was counted, and the raw data can be downloaded. If a number here is wrong, you can prove it, which is not true of most of this market.

TenderRadar.co.uk's answer:

UK public procurement is published but not surfaced. Notices are split across four national portals, each with its own thresholds, search behaviour and quirks, and none of them will tell you which of this morning's notices matter to you, which contracts are about to come round again, or who holds the work now.

Organisations deal with that in one of two ways. Either somebody is given the job of checking portals every morning, which is expensive and gets skipped, or nobody checks and the first you hear of a contract is when the deadline has passed.

Tender Radar was built to do the checking, and then to answer the question the portals cannot: what is coming up. That second part came from watching suppliers lose work they never knew was in play, because the incumbent had been talking to the buyer for months before anything was published.

TenderRadar.co.uk's answer:

Next.js, React and TypeScript for the web application, with Tailwind CSS. Python for the data pipeline that reads the procurement portals each weekday. SQLite for the contract and award database. Claude (Anthropic) for scoring notices against a customer profile and writing the reason for each match. Stripe for billing, Resend for email delivery. Hosted on DigitalOcean.

TenderRadar.co.uk's answer:

• UK universities and their commercial subsidiaries
• Specialist training and CPD providers
• Consultancies bidding into central and local government
• Facilities and parking services suppliers