An on-site developer who works inside your team

Your IT team has two or three people, and there is more work than they can handle. A new client portal, an integration with your bookkeeper's software, an old system that must be replaced before the vendor ends support. The job opening has been online for four months and few people have applied. Meanwhile the schedule slips and the list of open work grows.

When an on-site developer is the best answer

Not every shortage of hands is solved by outsourcing a project. Sometimes the work is so tied to what your own people do that it only moves when someone sits next to them. Same morning stand-up, same repository, same coffee. Then an on-site developer makes more sense than a project we build at our office in The Hague and hand over at the end.

We see three situations most often. A peak: a migration or launch that needs more capacity than you have for three months. A gap: someone leaves or falls ill, and the opening does not fill. And a knowledge gap: your team could learn a new technology alone, but faster with someone who has done it before. In all three cases, you should not wait half a year for the right hire.

How the assignment works

It starts with a free intake. We want to know what work is waiting, which language and environment you build in, and who assigns the tasks. Then we propose one person. You meet them before anything is signed, because a résumé says little about whether someone fits your team. You decide the schedule, from one day a week to full time, at your office or partly remote.

The first two weeks are a trial. If it does not click, it stops with no discussion and no notice period. If it does, we agree on a period with a clear end date. Every week you get a short report: what was done, what is left, and where we are running into trouble. It is not a three-page timesheet. It is half a page you read in two minutes.

One contract, a team behind the developer

A freelancer works alone. If they get stuck on a strange error message or an old database, the problem becomes yours. Our on-site developer has colleagues who can take a look. A question about an integration, a security issue, or a piece of infrastructure nobody on your side knows is discussed inside Optimi. You do not pay extra hours for it or bring in a second party.

You have one contract with Optimi and one point of contact. If the developer is out for a week, we arrange a replacement or catch up on the work. If it turns out your team needs new knowledge more than extra hands, we say so. A day of AI training and workshops at your site is then often cheaper than a developer who stays for months.

Knowledge stays with you

The biggest risk of hiring outside help is that the knowledge leaves with the person. That is why our developer works in your repository, following your rules for code and documentation. They do not work in a separate environment that must be moved later. You own everything that is built, from day one.

The last two weeks of an assignment focus on handover. What was built, why it was built that way, and where the sharp edges are. This goes into a document your team can still read a year from now. If you then want someone to take your colleagues' questions without pulling your developers away, our service desk and help desk is the logical next step. But the aim of the assignment is that you no longer need us for the work we came to do.