Home / Subcontracting
SubcontractingA defined interface package inside your project.
We build GIS maps, live status views and operator workflows over a team's existing data and APIs. Bring us in for one bounded module or named senior front-end capacity in your repository.
The case studies describe the interfaces we delivered; the platforms, data and outcomes belong to the wider project teams.
Facts for a first review
- Named lead
- Nick Beuca · front-end architecture, maps and live-data interfaces
- Working model
- Our contribution is scoped inside the prime's project, agreed before work starts
- Code
- Delivered inside the prime's repository, with access rules agreed with the consortium
- Relevant work
- Operator-facing interfaces described in the SWARCO and SOTERIA case studies
Choose a boundary your team can buy and review.
One GIS or live-data module
We agree one operator task, the map/status/detail screens, supplied feed or API, review environment and acceptance checks. We implement and hand over that module in your repository.
Best when the data owner and integration point are known. Feed creation, analytics models and 24/7 operations need separate owners.
Scope a module ↗Named front-end capacity
A senior Angular/GIS engineer joins a defined backlog under your product lead, with agreed days, access and review cadence. This fits a prime that already owns the architecture and needs delivery capacity.
We confirm availability and the technical boundary before making a bid commitment.
Discuss capacity ↗A user-facing layer worth reviewing
GIS and operator interfaces
Angular, OpenLayers or Leaflet front-ends for cadastral, road-safety and live-data workloads, with keyboard access and contrast checked from the start.
Live-data workflows
Interfaces fed by WebSocket and streaming sources, with the states around live data — pauses, backlogs and recovery — designed rather than improvised.
Accessibility and documentation
WCAG 2.1 AA as a baseline, code-level issue lists after testing, and a handover that documents feed assumptions and known limits.
All three are delivered inside the prime's project, using the prime's repositories and access rules. We do not take ownership of the platform's data or operations.
What a subcontracting agreement looks like
Scoping
We write the user-facing boundary together with the consortium: which screens are in scope, which data sources are used, and what is explicitly out of scope.
Delivery
We work in the prime's repository under their access rules, with reviews held with their team and our lead named in all decisions.
Evidence
The delivered interfaces are published with the case studies, and the technical evidence is described there in detail. Client references are shared only where disclosure is permitted.
For a bid, we agree our role and procurement route early. The lead organisation checks the applicable call and contract rules.
Points a consortium can verify
- A named individual leads the front-end, and clients speak directly with him.
- Relevant interface work is described in the SOTERIA and SWARCO case studies.
- Deep specialism in live GIS and C-ITS data; the same lead designed the interfaces in both projects.
- Accessibility is tested as part of delivery, not added afterwards.
The case studies name our part in those projects. The platforms, data, and outcomes belong to the wider project teams.
What we do not claim
- We do not own your data, your backend or your 24/7 operations.
- We do not claim a security certification or a completed accessibility audit for your project.
- We deliver the user-facing layer; feeds, models and operations stay with the prime.
If a bid needs more than the front-end, we work as one member of the delivery team, always with our part explicitly scoped.
Bring the task, not a full specification.
Tell us who uses the interface, what they need to decide, which feed or API exists, who owns it, the proposed contract route and the decision date. A public tender or project link is enough to start. We can arrange an NDA before seeing non-public material.