Hiring that
stays in
Switzerland
& the EU.
Helvio reads every CV, ranks your shortlist with the reasons written out, and drafts the interview. Candidate records stay in Zürich, the AI runs in the EU, never the US, and a person always makes the final call.
helvio.ch · resident in ZürichFour jobs, off your plate.
It reads and ranks every CV
Drop in a stack of applications. Helvio parses each one and scores it against the role across skills, experience, languages and work eligibility, then hands you a ranked list with a short reason for every placement.
It drafts the interview
For any candidate, it writes questions tied to their CV and the role, with notes on what a strong answer sounds like. Pick the language, edit anything, send it to the panel.
It keeps the data home
Candidate records and CVs are stored encrypted in Switzerland; the AI runs in an EU region covered by the Swiss adequacy decision, never the US. Application logs and backups stay in the same CH/EU region. revFADP, GDPR and the EU AI Act shaped the build from day one.
It fits the tools you run
Two-way sync keeps roles and candidates aligned with Personio and your CRM, so there's no second source of truth and no migration to schedule.
The app — right here on the page.
This is the real, working prototype, not a video. Sign in, rank a shortlist, reject with a reason, draft an interview, ask Mira, watch the decision log fill. Everything reacts.
Interactive prototype with mocked data. No live backend, AI, authentication or third-party integrations are wired up yet.
From a pile of CVs to a booked interview.
Connect or upload
Sync roles and applicants from Personio, forward an email, or drop in PDFs.
Mira parses and ranks
Every CV becomes a structured profile and is scored against the role, overnight if you want it ready by morning.
You review the reasons
Open a candidate, see the match broken down, and decide. Nothing is rejected without a human looking at it.
Generate the interview
Turn the shortlist into tailored questions in one tap. Every step is logged for the record.
A lean first build that proves value, then scale.
The big AI recruiting suites cost five figures a year, run on US servers and are built for 1,000-person companies. The local Swiss tools keep data home but barely do AI. Helvio is the third option, priced for a Swiss SME. Here's the plan and the numbers.
Discovery & architecture
- Workshops, success metrics, a frozen signed scope
- The residency decision: EU-region inference (Switzerland is on the EU adequacy list) vs strictly on Swiss soil
- Data model + a revFADP / GDPR impact-assessment outline
The AI core, on Android
- Android app: roles, candidates, ranked shortlist with reasons, parsed CV, interview kit, Mira chat
- Parse · match · interview-questions in DE/FR/IT/EN
- Google Identity sign-in (multi-tenant, SSO, MFA)
- Personio + one CRM, Swiss hosting, audit log, human-in-the-loop
Integrations & reach
- iOS from the same codebase (Compose Multiplatform)
- Salesforce + Dynamics connectors
- LinkedIn, the compliant way (see below)
- Workday / Abacus umantis as per-customer setups
All-in for the full requested scope (Phase 0 + 1 + 2): roughly $63.7k–89.7k. Workday and Abacus umantis are quoted on top, as per-customer setups. These are budgetary figures for this conversation. A companion statement of work (assumptions & exclusions, acceptance criteria, payment schedule, IP / source-code ownership, warranty & support, VAT and validity) is issued before signature.
Three honest ways to do it — and the legal fine print.
The brief asks to import LinkedIn profiles and articles. The honest truth: there is no clean, official way to bulk-import arbitrary profiles, and the provider everyone relied on (Proxycurl) was sued by LinkedIn and shut down in 2025. So we never hard-wire one vendor. We build behind an "enrichment provider" interface and pick the path that fits your compliance posture.
Consent-based
Two consent-based flavours. "Sign in with LinkedIn" (OAuth/OIDC) returns identity only (name, email, photo), not the full profile or articles. For a richer profile, a connected-account service like Unipile drives the person's own session; capable, but it leans on LinkedIn's terms, so treat it as ToS-sensitive and get sign-off first. Either way data is scoped to the authenticated person or the recruiter's own session, so the product inherits their lawful position.
Data providers
People Data Labs, Coresignal or Bright Data enrich a candidate from a LinkedIn URL out of their aggregated databases: profiles, and in some cases posts. Powerful, but the compliance weight is yours to carry (see fine print). We wire it behind the abstraction so a vendor can be swapped overnight.
Official partner
LinkedIn Talent Solutions: Recruiter System Connect, Apply Connect, One-Click Export. The proper enterprise route, fully sanctioned. Requires partner approval, certification and signed agreements. A multi-month track, not a switch you flip during an MVP.
The legal fine print your DPO will ask about
- Lawful basis (GDPR Art. 6 / revFADP). "We scraped a profile" is not a basis. Enrichment relies on legitimate interest plus a balancing test you must be able to produce. revFADP (in force Sept 2023) is GDPR-aligned, so the same logic applies in Switzerland.
- Notification (Art. 14). If data is collected from a third party, you must tell the candidate within a month: what you hold, where it came from, how to be deleted. A scraped candidate base without this is the pattern regulators fine.
- The "articles" trap. Other people's posts/articles are only available via Path B, so "import articles" mechanically pushes you into the heavier scenario. Articles are out of MVP scope by default. Worth deciding whether it's a real need.
- A safer corridor. When a candidate uploaded a CV or set "open to recruiters", legitimate interest is materially stronger: they signalled they expect recruiting use.
- Data residency. Enrichment providers process in the EU, not Switzerland. Records and AI stay in Zürich/EU, but data touching a provider transits their infra, to be agreed with you in writing: a DPA, a deletion process and a no-training clause.
- No credentials on our server. We never store LinkedIn passwords on the app backend; connection tokens are encrypted and deleted the moment the integration is disconnected.
Where the brief meets reality.
We'd rather you hear this from us now than from a lawyer later.
Parsing · matching · interview questions · Swiss hosting
Solved territory. LLM-first parsing and scoring is multilingual and cheap; Swiss-resident hosting has several real options (Exoscale, Infomaniak).
Google Identity & AI-inference residency
Google's sign-in processes a little identity data in the US, flagged for legal and swappable to an EU IdP if needed. AI inference runs via an EU region (Bedrock/Vertex EU) or a Swiss-hosted model if on-soil is mandatory. The Phase-0 decision.
Salesforce / Dynamics
Both doable; Salesforce needs an event-stream subscriber rather than a simple webhook. Built behind a connector core so each CRM is an adapter, not a rewrite.
Bulk LinkedIn import · Workday
No sanctioned way to pull arbitrary LinkedIn profiles (see the section above for the compliant paths). Workday is a per-customer, partner-gated enterprise setup, quoted separately as professional services.
What it's built on.
The part your DPO will ask about.
Filtering and ranking candidates counts as "high-risk" under the EU AI Act, and revFADP puts the responsibility on a named person. We treated that as the specification. Mira ranks and explains; a person you name signs off, and the trail is there if anyone asks.
Want to see it on your own roles?
Tap through the prototype above, then a fixed-scope pilot puts Helvio on Android in a few weeks, hosted in Switzerland, with Personio and one CRM connected.