I'm Anto Andrijanic. I build the systems recruitment and staffing companies actually run on, and I've been on both sides of them. Before I wrote a line of code for an agency, I worked inside them: I've watched recruiters lose strong candidates in spreadsheets, retype the same data five times, and chase work a system should have surfaced.
So when I build, it isn't generic software. It's the way your team already works, made fast, and owned by you. Selected work: rebuilt a failing Norwegian staffing company's server and consolidated ~25,000 scattered candidate records into one custom system; co-built Vorentis, a technical-recruitment agency, with a premium site and a custom CRM from scratch; and I build and maintain the web and systems for a Swiss client today.
You explain the problem to the same person who solves it, from first call to handover: no account managers, no juniors, no empty promises. Just systems that help your agency place more and waste less.
For healthcare and care staffing builds I bring in a domain advisor: Antonel, fifteen years inside Swiss healthcare, including hiring for a care home, working in German and Italian. I stay the one builder; he keeps me honest about how care staffing actually works.
Anto
Built for one kind of company: firms that place people.
This is for you if…
- You run a recruitment or staffing firm
- Your team fights spreadsheets, email and a tool that doesn't fit
- Microsoft 365 is already in your budget, and barely used
- You want a system shaped to you, and to own it
Probably not if…
- You want cheap off-the-shelf SaaS and will bend to it
- You need it "yesterday" with no scoping
- You're not the person who can say yes
The point isn't software. It's the outcome: recruiters place more and type less, and you're live in weeks, not months. The system should pay for itself. That's the only reason to build it.
Your data, not rented. Everything runs in your Microsoft 365 tenant, so the candidate database belongs to you: exportable any day, no per-seat licence, no ransom to leave. Under the new EU Data Act, that portability is your right, not a favour.
If a system won't make you money or save it, I don't build it. Pretty software that doesn't move numbers wastes everyone's time. Every project starts with the one number it has to move.