Services · dedicated teams
Four clauses that matter more than any CV you will be sent.
Named engineers working inside your repository, your sprint and your standards, on your priorities, for a defined period. Every supplier says that sentence, so this page is about the part nobody publishes: what the contract says when the engineer leaves, when you want to hire them, and when you want to know who owns the code.
The terms below are taken from a framework agreement and statement of work we have signed, not from a template written for a website. If your procurement team wants them, they are available — as the starting point for a contract rather than as an offer, since what any particular engagement commits to is what both sides end up signing.
Clause one
What happens when the engineer goes
The fear every buyer has and almost no supplier page addresses. People resign, fall ill and change countries; the question is not whether it happens but who carries the cost of the gap.
Clauses two, three and four
Exclusivity, hiring, and who owns the code
- The engineer is yours for the duration. The specialist named in a statement of work is engaged exclusively for you, and we undertake not to re-assign them to another customer while it runs. A shared engineer is how a day rate quietly gets cheaper and a delivery date quietly gets later.
- You may hire them. After nine months you are free to approach any specialist who worked for you — during the engagement or after it ends — with no release fee and no conversion charge. It costs us people occasionally. It costs considerably more to be the supplier whose engineers know they are unsellable.
- Exclusive rights pass to you on acceptance. Programs, databases and other works created under the statement of work become yours when the acceptance act is signed. Check this clause in every supplier's paper: "a licence to use" and "exclusive rights transferred" are different sentences, and the difference arrives three years later when you want to sell the company or change supplier.
And the modes, since it decides the invoice
Part time means more than eighty hours of a specialist's time in a month; full time means more than one hundred and sixty. At the end of the month both sides sign a certificate for the work actually done and the invoice follows that certificate rather than preceding it. Work outside normal hours is priced separately and agreed before it happens.
The question your legal team asks first
This is a contract for services, not staff leasing
In Italy, supplying workers who take their instructions from the client is somministrazione di lavoro, and only an agency entered on the Ministry's register may do it. We are not an agency. What we sign is a contract for services, and art. 29 comma 1 of D.Lgs. 276/2003 tells the two apart by what actually happens — who organises the means, who coordinates the people, who carries the business risk — rather than by what the contract is called.
In practice you set the backlog, the priorities and the acceptance criteria, and everything about engaging the person stays on our side: the contract, the fee, the equipment, the substitution. Our people are independent professionals — in Italy with their own VAT registration, abroad under their own national registration — and you never become their counterparty. The full division and the two questions worth asking any supplier are set out on the Jmix page: the statute does not change with the technology, so it is written once.
What we can actually place
Roles, with the work behind each one
Not a capability matrix. Five kinds of engineer we have put inside somebody else's team and been paid for monthly, which is a lower bar than it sounds and one most lists do not clear.
01 · DevOps and platform
CI/CD and automated test pipelines, Ansible, GitLab, Linux on Ubuntu and Debian, monitoring, certificate management — and migrating legacy applications into Kubernetes, which is the piece that is usually the reason for the engagement. A lead-level engineer, full time, inside the customer's own platform team.
02 · Java, Spring and Jmix
Internal systems with a large domain model and a real access model. Jmix engineers specifically are scarce in Italy and we say how scarce on the page that deals with them, rather than implying a bench we do not have.
03 · .NET and mobile
C# and .NET across server and device, .NET MAUI and native iOS and Android — including work on a payment application that stayed in production throughout a framework migration.
04 · Flutter and Dart
Cross-platform mobile, including inherited codebases rather than green fields — a product whose four applications share one codebase is a different kind of maintenance problem from four separate apps, and a different kind of engineer.
05 · Python, data and models
Training pipelines, evaluation harnesses, classification and detection work. Useful when you have a data team that needs hands rather than a research partner who needs a problem.
And the number, honestly
One or two engineers, exceptionally three. Beyond that it stops being augmentation and becomes a team, which needs a scope, a delivery obligation and somebody on our side accountable for it — a different contract and a different conversation.
Adjacent questions
Three cases where this is the wrong instrument
Nobody is free to direct the work
Augmentation assumes a technical lead with time to give. Without one, an engineer inside your sprint produces competent work on the wrong things, and the first person to notice is usually an auditor.
You want the outcome, not the hands
If what you actually want is a system delivered and handed over, buy that instead — the obligation should sit with us, not the hours — how a build runs, and how the stack gets chosen
You need a dozen people next month
Then you need a body shop and you should use one. We would have to subcontract people we have not worked with to fill that order, and passing through strangers is the one thing this page is arguing against.
Questions
The ones a procurement team should ask
Can we hire the engineer ourselves?
Yes, and we have signed that clause rather than argued about it. The arrangement we agree to is that you may approach any specialist who worked for you, during the engagement or after it ends, once nine months have passed. No release fee and no conversion charge. A supplier who makes its people unhireable is protecting its margin with somebody else's career, and the engineers notice before the clients do.
What happens if the engineer becomes unavailable?
You are told thirty days in advance where that is possible, and we have thirty days to put forward a replacement you accept — and we do not invoice you during that period. If no suitable replacement is found inside the window, that statement of work ends. The unbilled part is the point: a supplier that keeps charging while it solves its own staffing problem has no reason to solve it quickly.
Will the person also be working on somebody else's project?
No. The specialist named in a statement of work is engaged exclusively for you for its duration, and we undertake not to re-assign them to another customer. This is in the contract because a shared engineer is the quiet way a day rate gets cheaper and a delivery date gets later.
Who owns what the engineer writes?
You do. Exclusive rights to the programs, databases and other works created under the statement of work pass to you on signature of the acceptance act. It is worth checking this clause in any supplier's paper: "licence to use" and "exclusive rights transferred" are different sentences with very different consequences three years later.
Is this staff leasing? Our legal team will ask.
No, and the distinction is statutory rather than cosmetic. Supplying workers who take their instructions from the client is somministrazione di lavoro, which in Italy only an agency on the Ministry's register may provide; what we sign is a contract for services, and art. 29 comma 1 of D.Lgs. 276/2003 draws the line by what actually happens rather than by what the contract is called. The full explanation, including which powers stay on which side, is on the Jmix page — the law does not change with the technology.
How is the time counted and invoiced?
Two modes: part time, meaning more than eighty hours of a specialist's time in a month, and full time, meaning more than one hundred and sixty. At the end of each month both sides sign a certificate for the work done and the invoice follows it, rather than preceding it. Work outside normal hours is priced separately and agreed before it happens, not discovered on the invoice.
Next step
Tell us who the engineer would report to
Not the job description — the person on your side who will set the priorities, and the person who will still be there when the engagement ends. Those two names decide whether this works.