Team
Who stands behind the data.
Procurement data is only as trustworthy as the people and process behind it. This page names who runs DataMesh Consulting and sets out the editorial standards we hold the tender corpus to — how it is sourced, how it is checked, and how to get something corrected.
The team
Yalçın Yörük
Founder & Principal
Builds and operates the DataMesh extraction pipeline end to end — the multi-stage ladder that pulls clean, canonical tender records from 100+ public procurement portals, the data-quality filters that keep junk out of the corpus, and the AI matching layer.
Editorial standards
- Sourcing. Every tender is extracted directly from an official government, supranational, or inter-governmental procurement portal — never republished from a third-party aggregator. The source portal and original notice URL are recorded on every record and surfaced on each tender page. See our methodology for the extraction pipeline in detail.
- Fact-checking. Records pass a deterministic data-quality gate before they are published: junk and misextracted titles are rejected, page-chrome masquerading as a description is stripped, and implausible contract values are suppressed rather than displayed. We prefer a missing field to a wrong one.
- Corrections policy. If a tender is misattributed, stale, or wrong, email yy@datameshconsulting.co.uk with the tender URL. Confirmed errors are corrected at source so the fix propagates everywhere the record appears, and the sitemap is revalidated on the next update.
- Update cadence. Monitored portals are re-checked on a schedule and changes propagate to this site within minutes of ingestion. Each tender page reflects the latest data we hold from its source.
- AI disclosure. Extraction uses deterministic rules first and an AI reasoning fallback only for ambiguous source HTML. AI is used to structure and match public data — it does not invent tender facts.
Get in touch
Editorial questions, corrections, or partnership enquiries: yy@datameshconsulting.co.uk.