Tendorer — Tender Intelligence & Bid Management
Turns government tender chasing into a scored, auditable pipeline where every number can be defended.
A tender intelligence workspace that takes a government tender from discovery to post-award review: every opportunity is scored against your own capability profile, and every score shows the components, weights and reasons behind it.

- Industry
- Infrastructure / Public Procurement
- Role
- Architect & Full-Stack Engineer
- Type
- SaaS Platform
- Year
- 2026
01
Overview
Tendorer is a bid management workspace for organizations that compete for government tenders. It carries an opportunity through the full cycle — discover, understand, evaluate, decide, prepare, track, learn — instead of leaving it scattered across spreadsheets and mailboxes.
The defining constraint is explainability. Every score, recommendation and warning the system produces is shown next to the components and weights that produced it, and any assessment can be overridden by a person with a recorded reason. A match score of 97 is never a black box: the eligibility clauses it cleared, the ones it failed and the capability gaps behind them are all visible on the same screen.
Tender documents are parsed by a pluggable extraction provider — an offline heuristic parser by default, with an optional LLM adapter — so the platform runs with no external AI dependency and gains accuracy when one is configured.
02
Business challenge
Organizations bidding on government tenders track opportunities in spreadsheets and mailboxes. Eligibility is re-checked by hand for every tender, the reasoning behind a go/no-go decision lives in someone's head, and there is no record afterwards of why a bid was pursued or dropped.
03
Solution
A single workspace that ingests tenders, scores each one against a stored capability profile, and exposes the full reasoning behind every number — then carries the chosen opportunities through bid preparation, approval and submission with an audit trail.
What it does
04
Product screenshots
Screens from the application itself. Select any image to view it full size.
05
Architecture
How it fits together
- 01NestJS 11 REST API over Prisma 6 and MariaDB 11.8, documented with Swagger
- 02React 19 + Vite 6 SPA using TanStack Query for server state and Recharts for analytics
- 03JWT access tokens plus rotating refresh tokens in httpOnly cookies, argon2 password hashing
- 04Role-based permissions covering tenders, bids, finance, review and read-only access
- 05Pluggable document-extraction provider — offline heuristic parser by default, LLM adapter optional
- 06Scoring engine that persists the component breakdown alongside every computed score
06
Engineering challenges
- Challenge
- A recommendation nobody can interrogate does not get trusted — bid teams will not act on a number they cannot defend to a director.
- How it was solved
- Made explainability part of the data model rather than a UI afterthought: every score persists its components, weights and reasons, so the interface renders the argument alongside the number and a person can override it with a recorded justification.
- Challenge
- Document extraction quality varies wildly, and binding the product to one AI vendor would make it unusable in air-gapped procurement environments.
- How it was solved
- Defined extraction as a provider interface with an offline heuristic parser as the default implementation, so the platform is fully functional with no external dependency and improves when an LLM adapter is configured.
07
Technology stack
- Frontend
- React 19Vite 6TypeScriptTanStack QueryTailwind CSS 4
- Backend
- NestJS 11Prisma 6
- Also used
- MariaDBRechartsSwagger
08
Business impact
- 20 seeded
- Scored Tenders
- Explainable
- Scoring
- 6 permission sets
- Roles
Tender evaluation moved from ad-hoc spreadsheet review to a scored, auditable pipeline. The seeded demo carries 20 tenders scored end to end across two organizations, with eligibility gaps, risk scores and closing deadlines surfaced on a single dashboard.
09
Project status
What I took from it
- When a system produces judgements about money, the reasoning is the feature — persist it with the result rather than recomputing or narrating it later.
- Treating an AI capability as a swappable provider keeps the product deployable in environments where no external model is permitted.
Next step
Need a similar solution for your business?
Tell me what you are trying to build or fix. I will come back with how I would approach it, what it realistically takes and where the risks are.


