Recruitment Solutions — Direct Employers and Agencies in The Bottom, BonaireNetherlands
How Expertini ATS handles Recruitment Solutions — Direct Employers and Agencies for employers hiring in The Bottom. View without a localization
Recruitment Solutions — Direct Employers and Agencies
The same platform serves two genuinely different workflows — this page explains how.
Expertini ATS supports two distinct recruitment models on one platform: direct in-house hiring, and agency recruitment on behalf of multiple clients — with Client CRM as the specific layer that makes the second model work without needing a separate product.
On this page
01Direct employer hiring
Post under your own organisation's name, run the full pipeline, and use Candidate CRM to build a reusable talent pool for future roles — the straightforward case most ATS platforms are built for.
02Agency recruitment
Create client records with their own commission terms, link jobs to a specific client (confidentially if needed), and use the Client Review Portal to share candidates directly with that client — replacing emailed PDFs with a live, tokenized link that needs no client login.
03Reporting for both models
Direct employers get Time-to-Hire Intelligence with month-over-month trend and category benchmarks. Agencies additionally get client-specific reports showing submissions, timeline, and an estimated market-rate savings figure to share with the client.
04A day in each workflow, concretely
The in-house recruiter's loop: open the pipeline, triage new applicants by CMS score, move the plausible ones to screening, schedule interviews, and check the funnel report to see where candidates are stalling. Their talent pool compounds — every applicant, hired or not, remains searchable in Candidate CRM for the next similar role. The agency recruiter's loop adds a client dimension to each of those steps: the job is linked to a client record (possibly confidentially), promising candidates get explicitly shared to that client's Review Portal, the client leaves feedback or requests an interview through the portal without needing a login, and commission tracking updates from the role's salary and that client's terms automatically. Neither workflow is a stripped-down version of the other — they're the same pipeline with the agency layer switched on or off.
05Hybrid teams and switching models
Plenty of real teams don't fit cleanly into one model — an agency that also hires for its own back office, or an in-house team that occasionally takes on recruiting for a sister company. Because Client CRM is a layer over the same pipeline rather than a separate product, the same account handles both: jobs linked to a client get the agency treatment (portal, commission, confidentiality), jobs without a client link behave as plain direct hiring. Nothing needs migrating when your model shifts — which is worth weighing against single-model ATS products, where outgrowing the product's assumption means an export-and-reimport project. The full comparison of what each model gets is on the team-size page.
Platform architecture & operations
A1How this is architected in the platform
Recruitment Solutions — Direct Employers and Agencies is not a bundle of point products — it is a slice through one platform. The platform is deliberately server-rendered: every view is prepared by the application server and shipped as complete HTML, with no client-side framework, no third-party CDN scripts, and no build pipeline between the data and the page. What renders is what the server computed — the property that makes the interface auditable.
All persistence runs on a single search-native document store; every query carries the organisation's identifier as a mandatory filter at the lowest query layer. Tenant isolation is therefore structural — a property of how every request is composed — rather than a policy that relies on application code remembering to check.
Every capability referenced on this page resolves to a registered tool or connector: the tools directory and the integrations catalogue are renderings of the same registries the application enforces at runtime, so what this page describes and what the product gates can never drift apart.
A2Operational and audit posture
Screening is deterministic and published — the same inputs produce the same outputs, hard requirements block rather than average away, and the methodology is public on the research page. Actions that touch external systems are explicit and journalled per event; usage reporting aggregates the same journals the actions write, not a parallel telemetry system.
Anything that leaves the request path — notification fan-out, webhook delivery, activity journalling, mail — runs in fire-and-forget background threads. A slow external endpoint can never make the interface hang, and a failed side effect is logged rather than silently retried into inconsistency.
Everything written is yours to take: CSV exports and the Data Export app cover the same stores the product itself reads. The exit is as open as the entrance — by design, not concession.
Frequently asked questions
We're an in-house team — do we pay for agency features we won't use?⌄
Can one account run both direct hiring and client work simultaneously?⌄
What does the client actually see in the Review Portal?⌄
At a glance
- One platform, two workflows: direct employer and agency
- Client CRM adds commission tracking and confidential postings for agencies
- Client Review Portal replaces emailed candidate PDFs
- Time-to-Hire Intelligence available to every plan
- Client-linked and unlinked jobs coexist in one account
- No migration when your recruitment model changes
See recruitment solutions — direct employers and agencies on your own hiring.
Bring a real job description to a 30-minute demo — free trial included.
Book a demo