RFP Workflow Improvement 2026 | Company Context

Implementation status disputed — review pending (2026-09-28). The user believes this work may still be live and may not have been implemented. Earlier completion and issue-closure assertions below are historical reports, not confirmed implementation. Keep this record visible until the owner distinguishes analysis, agreed process, actual rollout, and routine adoption, and sets the next milestone/date.

This was a bounded diagnosis-and-shaping project for Datopian's RFP workflow. Daniela owned it from the business-development side. The purpose was not to redesign the full bid system, but to turn a weak and poorly tracked RFP picture into a usable diagnosis and a first practical improvement plan.

The earlier record reported this project complete; that claim is now under review. The follow-on live track is RFP Response Quality Process v0.1.

What this project was

Datopian submits a meaningful number of RFPs, but the win/loss picture was weak, outcome tracking was inconsistent, and the team did not have a confident evidence-based view of why bids were being lost.

This project existed to answer four practical questions:

where we are currently losing
which causes of loss appear repeatedly
which process gaps are creating avoidable losses or weak learning
which follow-on improvements should be opened next as separate implementation work

Key findings

Reviewed set: 30 submitted RFPs in the last 12 months
Full-set win rate: 10% (3/30)
Known-outcomes-only win rate: 17% (3/18)
Win rate is the same (~17%) whether the bid was invited or proactively sourced — the source channel is not the bottleneck
All 3 confirmed wins are hosting/support/maintenance contracts — zero wins on new-build or custom development
Main loss themes: proposals too generic on scored criteria; missed mandatory compliance requirements; pricing uncompetitive or unjustified; weak post-submission follow-up

Previously reported changes — implementation unconfirmed

Win/Loss Picture — 30 RFPs with source analysis (invited vs proactive)
Bid Gate — 3-question gate embedded in the RFP issue template in datopian/sales; covers both win bids and presence bids
Sourcing calibration loop moved to datopian/lead-gen/calibration; Meiran script runs Mon/Fri; recurring review event in Daniela and Yoana's calendars

Follow-on tracks

RFP Response Quality Process v0.1 — active, owned by Daniela
leadlinks #52 — active issue tracker

Historical milestone claims — verify before relying on them

Milestone / checkpoint	ETA	Expected outcome	Done	Completion date
Win/loss picture consolidated	2026-05-09	Usable baseline with known outcomes, unknowns, and key gaps	✅	2026-05-09
Rejected-bid feedback synthesized	2026-05-16	Clear diagnosis of the main recurring causes of loss	✅	2026-05-16
First improvement plan drafted	2026-05-20	Prioritized conclusion that proposal quality and fit/selection are the main issues	✅	2026-05-20
Follow-on tracks reset	2026-06-03	Follow-on work split into sourcing improvement and response-quality improvement	✅	2026-06-03
Source data added	2026-06-05	All 30 reviewed RFPs marked invited or proactively found	✅	2026-06-05
Metrics split by source	2026-06-05	Invited and proactively found have separate metrics; both ~17% win rate	✅	2026-06-05
Bid gate installed	2026-06-08	BID-GATE.md published; 3-question template live on RFP issues in `datopian/sales`	✅	2026-06-08
Enriched analysis closed	2026-06-08	leadlinks #22 closed with source split and follow-on priorities documented	✅	2026-06-08
Sourcing calibration loop established	2026-06-09	Calibration folder in lead-gen; script cadence confirmed; recurring review scheduled	✅	2026-06-09

Links / Evidence

#22 Enrich RFP workflow analysis — closed
#51 Improve RFP sourcing via Meiran fit reports — closed
#52 Improve RFP response quality process — active