Discovery
We map how you actually work and agree exactly what gets built. You get a fixed scope and a fixed price before anything starts.
Build
We build it ourselves, and you talk to the people doing the work. Delivered in working steps you can see and approve, not one big reveal.
Support
Hosting and support are inside the monthly number, with a guaranteed response within one working day, and your banked credit pays for improvements as your desk changes. Bug fixes are free, always. The system grows with you instead of going stale.
The model: most builds run as one monthly number. A groundwork fee to start, then a fixed monthly payment that covers the build, hosting, support and training. The price is fixed for the whole term, no annual increases, and part of every month banks as credit you can spend on future development. Want to end it early? You settle the balance on what was actually delivered, measured against the milestone schedule we agree when you sign, and the credit counts toward it. The system is yours outright once that balance is zero; until then you are licensed to use it, which is what stops either of us arguing about it later. Standalone projects (a website, an archive unlock) stay fixed price for fixed scope. For a desk of eight or ten people, the monthly lands about where ten Vincere seats land today, and under what Bullhorn charges for the same desk. The difference is the ending: their monthly buys another month of rent, ours builds toward a system you own.
Groundwork is 10% of the build scope, paid at the start. It covers discovery and the written scope you get before anything is built.
You pick the term, one, two or three years. A shorter term means a bigger monthly and a smaller total, because you are paying for fewer months of support along the way. There is no interest either way, so the only thing a longer term costs you is the extra months.
When the term ends, the monthly stops. The system is yours, in your own environment, with the handover documentation you have had since day one.
Leaving, if it comes to that. Your records sit in your own Microsoft 365, on lists your own administrator can open today. They are not in a database we keep. So there is no export request to send us, no fee for getting your data back, and no stretch of time where we are holding it while the two of us agree terms. You settle the balance described above, the code is yours, and the data never went anywhere in the first place. This matters more than it sounds: the usual reason a firm spends another year on a platform it dislikes is not loyalty, it is the migration quote and the fear of the week the system is half moved.
After that, two things you can take or leave. Care is €150 a month: hosting, security updates, backups, a guaranteed response within one working day (a reply from us with what we found and when it will be fixed), and bug fixes. Bugs stay free and unlimited, because a bug is our mistake and not your request. A development budget is another €100 a month if you want the system to keep growing, and it pays for anything new. That is the whole line: if it is broken it is ours, if it is new it comes out of your budget. Pay the support year up front and you get two months of it free.
Three project shapes, three rough ranges.
These ranges are build scope, not a bill on day one. Most firms spread it as one fixed monthly number that also covers hosting, support and training.
Pipeline, intake, dashboard, branded documents, in your own environment.
Hybrid hosting, pseudonymisation, audit chain, for healthcare, finance and regulated data.
For 100k+ records or multi-country: Swiss-hosted core, semantic search, M365 as the workflow layer.
A custom website (career site, employer pages), growth infrastructure (job feeds, funnels, SEO) and add-ons (Archive Unlock, Power BI, intake funnels) are quoted separately, scoped to what you need. Any of these work on their own or bundled into a CRM build.
What that looks like, three ways
One worked example, so the model is not just words. We have taken €24k, a round number inside the Regulated build range, because that is the shape most firms land on. The only thing that changes across these three columns is how long you choose to spread it.
The monthly stops and the system is yours. Care is optional from here, €150 a month, or €250 with a development budget.
The build costs €24k whichever column you pick. The difference between them is months of support and development budget, not interest, which is why the shorter term is also the cheaper one. On a per-seat platform there is no column like the last row: month 37 costs what month 1 did and usually more, because seat prices go up every year, and you still own nothing.
What six seats cost elsewhere, per year
Same yardstick for everyone: six recruiters, twelve months, the vendor’s own list price for the named tier, no discounts assumed on either side.
List prices from each vendor’s own public pricing page, fetched 20 August 2026, except Vincere: their page was not reachable that day, so the figure is the consistent listing across Capterra, GetApp, SoftwareAdvice and one independent review, checked 31 July 2026. Vendors change prices; the dates are the claim.
Every row above grows when you hire. The worked example above does not: the seventh recruiter costs €0, and after the term the whole table stops applying to you.
What moves your number · show the scope ladder ↓
Same model, different scope. Your discovery call decides which apply to you.
The exact number for your scope comes from discovery, not from this page. Larger or multi-country projects scoped accordingly.
Want to narrow it down yourself first? The price estimator lets you tick the desks and add-ons you actually need and see where that lands, monthly or one-time. Same model as this page, no email needed to see the number.