The division of responsibility
You direct the work. We carry the employer.
This is the distinction that matters, and it is written into the agreement rather than left to custom. Each engineer's role, seniority, allocation and start date are confirmed in writing by both sides before they begin.
You direct their day-to-day tasks and priorities exactly as you would an employee. We remain responsible for their remuneration, taxes and social contributions, for their availability, for reporting their hours, and for replacing them within a reasonable period in case of prolonged absence or on your reasonable written request.
- Named individuals agreed in writing before they start
- Your sprint, your backlog, your tooling, your definition of done
- Our payroll, taxes and social contributions, with no employment relationship on your side
- Monthly timesheets and a written report against the agreed allocation
- Replacement within a reasonable period, on your reasonable written request
- Non-solicitation running both ways for twelve months after the engagement
- Confidentiality surviving five years, and indefinitely for trade secrets
- Sixty days' notice to end an allocation for convenience, either side
Roles available
Who you can allocate.
Seniority and rate are fixed per role in the statement of work and held for the initial contract term. Team composition is proposed by us and agreed with you.
| Role | Typical responsibilities | Common allocation |
|---|---|---|
| Senior software engineer | Architecture, backend and frontend development, technical direction, mentoring | Full time |
| Software engineer | Backend and frontend development against an agreed design | Full time |
| QA engineer | Test strategy, automation, release verification | Full or part time |
| DevOps engineer | Infrastructure, CI/CD, deployment, observability, cost | Full or part time |
| Security engineer | Security monitoring, detection engineering, incident response | Part time or retainer |
| Project manager | Planning, coordination and reporting across the engagement | Part time |
| Market / business analyst | Market research, analysis and management reporting | Part time or project |
| AI compliance consultant | EU AI Act, agentic AI governance, data protection | Part time or project |
Why this shape works
Three problems it removes.
The hiring cycle
A European engineering hire often takes three to six months. An allocation starts on an agreed date, and if the fit is wrong you can request a replacement.
The entity problem
No local company, payroll registration or employment exposure in another jurisdiction. One EU supplier, one invoice in euro, one governing law.
The capacity cliff
Allocations scale up and down against a monthly notice period, so a delivery peak does not become a permanent cost base you have to unwind later.
Getting started
From first call to first commit.
Requirement
Roles, seniority, stack, time-zone overlap and the shape of the work. We tell you honestly what we can staff and what we cannot.
Profiles
Named candidates with real profiles. You interview them exactly as you would a direct hire, and you decline the ones you decline.
Confirmation
Role, seniority, allocation and start date confirmed in writing by both sides in a statement of work under the framework agreement.
Onboarding
Access under named credentials, your security and operational policies applied, and a first delivery target inside the first two weeks.
Steady state
Your priorities, your ceremonies, monthly timesheets and reporting from us. Scale the allocation up or down as the roadmap moves.
Need engineers this quarter?
Tell us the roles, stack and timing. We will confirm what we can staff and by when.