Contract
Website Services Framework — Lot 5 Web Development
Project evidence involving Drupal, WordPress. First observed 4 Sept 2026; the response opens on find-tender.service.gov.uk.
- Budget
- £157,500 excluding VAT
- Work format
- Project
- Role family
- Software specialist
- Seniority
- Level not stated
- Observed
- 4 Sept 202612 days old
- Response destination
- find-tender.service.gov.uk
What this signal says
Leadiy recorded “Website Services Framework — Lot 5 Web Development” as a project 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
For comparison across sources, Leadiy maps the visible stack to Drupal, WordPress. Source marketplaces often mix frameworks, platforms, infrastructure and delivery language in one line, so a literal string would fragment the market view. The controlled catalog keeps stable concepts together while retaining the original stack as a concise fact below. Detection is multi-label: several technologies may be valid at once, and a stack combination is admitted only when its required components appear. Buyers and suppliers should still use the source page to confirm versions, depth and mandatory versus optional skills.
Commercial format
Leadiy reads the buying motion as Project. 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 “2026-06-10 to 2028-06-09; optional extension to 2029-02-04.” Work-location context is recorded as “Public procurement; framework already awarded to named suppliers.”
Reading the budget
The financial signal is “£157,500 excluding VAT,” exactly at the level available in the normalized record. No midpoint is invented and no missing value is estimated. This restraint is important when similar technology work can be sold as fixed delivery, hourly capacity, a retainer or employment. The number is useful for triage only after its unit and scope are understood. The application destination should be used to verify what the amount includes, whether it is negotiable, and whether platform or payment conditions change the supplier’s effective return.
Demand context from Hiring Pulse
In the current 30-day Hiring Pulse, Drupal appears in 115 of 1254 observed opportunities (9.2%). Counts are multi-label, so one opportunity may contribute to several technology buckets. The comparison is dated through 2026-09-17 and describes Leadiy’s observed sample, not the whole software market. It helps answer whether this record sits beside other visible signals, but it does not prove future demand, market share or buyer intent. The individual page and the aggregate Pulse use the same public-safe vacancy and project scope, while direct leads and personal data remain excluded from both.
Observation and publication timing
The first-observed timestamp is 4 Sept 2026, 15:34 UTC, which makes this record 12 days old when this page is rendered. Public release waited 24.17 hours, selected deterministically between 24 and 48 hours from the record identifier. That rule survives process restarts and does not drift with each request. It also separates two clocks that are easy to confuse: the source may have published earlier, whereas Leadiy records when its own system first saw the opportunity. Paid access is to the earlier matched feed, not to a claim about the source’s original posting time.
What looks similar
To build a useful neighbourhood around this record, Leadiy compares normalized technology IDs and favours the strongest overlap among pages that have already cleared the public delay. The current result is: "Contract Website Developer (Drupal or WordPress)", "Drupal Contractor (Remote | U.S.-Based | Contract)", "Website design, implementation, maintenance and hosting framework — Drupal lot" This method makes relationships inspectable and avoids copying descriptive text from the source. Similarity means shared technical vocabulary, nothing more. It does not assert shared ownership, equal scope, equivalent seniority or an identical application process, and it can evolve as later records become publicly eligible.
Where the response goes
Applying means leaving Leadiy for find-tender.service.gov.uk, identified here as Find a Tender / Sell2Wales. The link is the normalized direct source URL stored with the opportunity. No public form on Leadiy submits an application, and no contact detail is exposed as a shortcut. The destination can impose login, marketplace credits, identity checks, location limits or other terms that are outside this catalog. Verify the hostname and the current post before sharing information. If the source has closed or changed the opportunity, its live state is authoritative.
Public evidence versus earlier access
Leadiy sells timing, not a different truth: the same opportunities, one day earlier. Subscribers receive the fresh matched feed and private workflow before a record crosses its public time fence. The later page remains complete enough to stand alone, with provenance, classification, budget reading, aggregate context and related records. Subscription is not preferential treatment from the buyer, and it cannot guarantee availability or success. It is earlier awareness plus an operational workspace; the public catalog is the delayed evidence layer.
The same opportunities, one day earlier.
See the $39 / 30-day plan →Your response leaves Leadiy.
The button opens find-tender.service.gov.uk. That third-party page controls login, eligibility, proposal fields, privacy and the current status of the opportunity.