Home / Delivery
For bid and programme leadsA named software partner for your product or team.
TARG.DIGITAL is led by Nick Beuca. We can take a defined dashboard, interface or integration module inside your product, or contribute specialist capacity to a larger programme. The scope, access and handover are agreed before work starts.
Facts for a first review
- Company
- TARG.DIGITAL SRL · EU · VAT RO46817003
- Named lead
- Nick Beuca · product design, front-end architecture and software integration
- Working model
- Defined module or agreed days inside your team; availability confirmed in the proposal
- Code
- Committed in your repository; ownership follows the agreed contract and payment terms
Client interfaces and an internal system
The client case studies describe our front-end contribution and show the screens. Our internal acquisition case shows CRM and AI-tool integration. Client references, contract details and outcomes are shared only where disclosure is permitted.
SWARCO operator interface
Angular, OpenLayers and live C-ITS message views with map, detail and monitoring workflows.
Read the case study → Road safetySOTERIA Madrid prototype
UX and Angular/Leaflet views for investigating accidents, exposure and near-miss indicators.
Read the case study → Internal buildAcquisition signal system
Public signals, CRM decisions and MCP access. This is our own system, not a client result.
Read the case study →How a UK engagement actually runs
We are an EU-based studio working with UK consultancies, operators and public bodies. Nothing about that is unusual in practice, so here is the practical detail a procurement or bid lead needs.
Commercials
Quoted and invoiced in GBP, fixed for the agreed scope. Registered in the EU: TARG.DIGITAL SRL, VAT RO46817003, Reg. J40/17951/2022. UK VAT-registered clients apply the reverse charge; no UK establishment is required to contract with us.
Working hours and response
09:00–17:00 UK time, with a same-working-day reply to anything that arrives before 15:00. Delivery is inside your repository and your ticket flow, not a handover at the end.
Data and contracts
We work on your infrastructure or on data you are licensed to share. A data-processing agreement compatible with UK GDPR is provided on request, along with confidentiality terms and named-supplier details for framework bids.
Questions we settle together
Who uses it, and for what?
We write down the operator task, relevant states and acceptance criteria with your product or domain lead.
Which system owns the data?
We identify the API or feed owner, test data, event definitions, access rules and what belongs to the existing platform.
How does it ship?
We agree repository access, review process, deployment environment, documentation and handover responsibilities.
What a module handover should contain
- Working code and build instructions in the agreed repository
- Tests and review against written acceptance criteria
- Keyboard, screen-reader and contrast checks against the applicable accessibility target
- A handover of the UI, feed assumptions, known limits and maintenance points
The exact test evidence and support period are set in the scope. The published map-module and live-dashboard examples include 30 days of fixes.
Handle non-public work deliberately
We can sign an NDA before reviewing non-public data. During scoping, a redacted schema or public sample is enough. Project access, credential handling and offboarding should follow your security process and be documented before access is granted.
We do not claim a security certification or a completed accessibility audit for every project. If a bid needs specific evidence, ask for it and we will distinguish what exists from what must be produced for that contract.
Have a front-end work package in a bid?
Send the operator task, expected integration and deadline. We can return a one-page boundary and the questions that determine scope.