Website Werkzaak Rivierenland — open-source CMS successor to Drupal — software opportunity

What this signal says

Leadiy recorded “Website Werkzaak Rivierenland — open-source CMS successor to Drupal” as a rfp / procurement signal, not as a copied job-board article. The public page keeps only the facts needed to understand the commercial request: the role or outcome, normalized technologies, engagement format, stated budget, observation time and the exact destination for a response. Contact names, email addresses, outreach drafts, private notes and the imported source row stay outside this page. The useful question is therefore narrow: what kind of software demand is visible here, and what should a supplier verify before deciding to respond?

How the technology was normalized

The controlled technology reading for this record is Drupal. That label is derived from explicit terms in the role, primary technology and stack fields; it is not inferred from the buyer’s identity or from private contact context. Normalization folds common spelling and naming variants into one catalog so this page can be compared with other records. A combination tag appears only when every required part of that combination is detected. The result is a search aid, not a guarantee that every named tool is equally central to the delivery scope.

Commercial format

Leadiy reads the buying motion as RFP / procurement. This matters because the response shape for a deliverable, contractor seat, formal proposal and employment application is not interchangeable. The category is a classifier output rather than a legal characterization, and the original post wins if its terms change. The available duration wording is “Contract 2027-01-01 to 2030-12-31, plus three optional one-year extensions through 2033.” Work-location context is recorded as “Open EU procedure; participation is not reserved and the contract is GPA-covered. Delivery place is the Netherlands; Ukraine-based prime-bidder and consortium e.”

Reading the budget

The source did not provide a budget for this opportunity. “Budget not provided by source” describes that missing commercial field; it does not mean the opportunity page is unpublished or unavailable. Leadiy does not estimate a range from similar records because fixed projects, hourly work, contracts and salaries are not safely interchangeable. Confirm compensation, currency, rate unit, scope and payment terms at the response destination before deciding whether to proceed.

Demand context from Hiring Pulse

In the current 30-day Hiring Pulse, Drupal appears in 119 of 1216 observed opportunities (9.8%). Counts are multi-label, so one opportunity may contribute to several technology buckets. This aggregate context is intentionally bounded. The denominator is the current observed sample, technology counting overlaps, and small buckets may be suppressed. A single listing cannot establish a trend, and a technology’s share in Leadiy’s feed is not market share. The useful comparison is operational: it shows whether the normalized topic recurs among recently observed opportunities and gives the individual signal a dated reference point. Direct leads, contact data, raw source rows and private qualification notes do not enter that public calculation.

Observation and publication timing

Timing here is explicit: observed by Leadiy on 21 Sept 2026, 02:31 UTC, 7 days old at the current request, then admitted to the public catalog after 42.97 hours. The system never recomputes a shorter delay because a page is requested frequently. This is an evidence timestamp, not a promise that the source remains open, and not a reconstruction of when the buyer first posted. Visitors who need the freshest matched records use the authenticated product; the public page is intentionally the later, indexable edition.

What looks similar

Similarity is based on shared normalized technology tags and then recency, not on company identity or copied source prose. "Update design Drupal", "100% Remote — Drupal Developer (W2 ONLY)", "Senior Drupal Developer" These neighbours are useful for comparing delivery shape, budget visibility and technology overlap. They are not duplicates and they do not imply that the same buyer, scope or qualification rules apply. When no suitable public neighbour exists, the page says so instead of padding the section with unrelated links. New public records can change this comparison set after their own delay and quality checks pass.

Where the response goes

This page’s action route is explicit: it opens TED / TenderNed / Cobrief on ted.europa.eu. Leadiy provides context and provenance, not an application proxy. A click can therefore lead to a third-party login or proposal workflow governed by that service’s own privacy, eligibility and payment rules. The public catalog never replaces those instructions and never publishes a hidden email address as an alternate route. Review the destination hostname, confirm that the opportunity is still active, and respond only through a path you trust.

Public evidence versus earlier access

The commercial distinction is one sentence: the same opportunities, one day earlier. The paid workspace is for acting on newly matched signals with private workflow tools; this public edition is for later discovery, citation and market context. Paying does not improve the source’s terms or guarantee a response. It changes when the Leadiy record becomes available and adds the operating context needed to triage it. That boundary keeps the open catalog genuinely useful while preserving a simple reason to subscribe without hiding where the original response must be submitted.

Website Werkzaak Rivierenland — open-source CMS successor to Drupal

Drupal Developer / Senior Functional Analyst

Drupal Developer