LabLocum is the project where restraint matters most. The obvious version would be a marketplace that promises speed. The better version starts with visibility, compliance boundaries, and stakeholder research.
Where it is now
LabLocum is at concept and validation stage, with a public holding page, pilot-interest flow, privacy notice, risk audit, professional evidence profile template, pilot brief, and internal control pack. The production site is intentionally careful about what it does not claim.
Pilot-interest submissions are limited, stored privately, and protected with AES-256-GCM support. The public copy avoids agency replacement, instant booking, payroll, worker ranking, guaranteed compliance, NHS approval, and procurement-bypass language.
The barriers
The barrier is not just product-market fit. It is sector trust. Healthcare staffing touches governance, procurement, data protection, quality systems, local approval routes, and professional judgement. Building too aggressively would be a product error as much as a compliance risk.
There is also an explicit external dependency around healthcare sector re-entry. That means the project has to be prepared without pretending it is operational before the boundary is resolved.
How I did it
I built the validation layer first. Instead of collecting sensitive documents or launching accounts, the site gathers broad stakeholder interest, explains the pilot boundary, and publishes useful artefacts such as the Laboratory Staffing Risk Audit.
This is regulated-sector thinking applied to startup work: define the risk, document the boundary, gather evidence, and only then increase operational scope.