Marple is a recruitment platform for agencies and in-house teams who are tired of choosing between a database that does nothing and an enterprise suite that does everything badly.
Every piece of AI in the product suggests — a summary, a match, a draft, a next step. A person accepts, edits or rejects it. Nothing is written to your data, sent to a candidate, or moved through your pipeline without someone deciding it should be.
Candidate information is some of the most sensitive personal data an organisation handles. Our AI runs in EU regions, and personal identifiers are stripped before any model sees a profile — the AI assesses what someone can do, never who they are.
Match results cite the requirement they answer. Sourced profiles carry the page they came from. A recruiter can always ask "why is this here?" and get an answer they can check.
Shipped
Everything in this section is live and demonstrable.
Landing next
A consistent visual hierarchy across every surface, so panels, cards and form fields read the same everywhere, in both themes.
Generated interview questions and notes keep their headings, lists and emphasis — and you get heading controls in the editor to restructure them yourself.
Both ways of creating a role — writing from a brief, or pasting an existing advert — now return the same complete result, and requirements stay concrete and verifiable rather than generic. This makes every downstream ranking better at once.
Send a colleague a link to a candidate's notes or a company's activity and they land exactly there.
Every record shows who created and last changed it, automatically.
Committed, in build order
A public jobs page for your organisation, with filters candidates actually use — location, work mode, contract type. Every role gets its own shareable page you can send to a client, drop in a message, or post anywhere. Built to be found: correctly structured so Google for Jobs and the major aggregators index your roles automatically, with no extra work and no per-board fees.
Candidates apply from the public page, resume and all — and the application lands in your pipeline already structured, because the resume is read on arrival.
Connect your LinkedIn account, and publishing a role offers you a ready-drafted post to edit and share to your network. Your job feed also plugs into LinkedIn job wrapping for customers who already run LinkedIn Recruiter.
Subscribe to a role, a candidate or a company and get told when something happens on it — not only when you were the one who acted. Digested, not per-event.
Choose what you're told about, and on which channel.
Connect Microsoft 365 and Gmail with a secure one-click sign-in instead of a stored password — which also opens the door to calendar sync.
Placements get a real lifecycle — offered, declined, started, fell through, left early — with reasons. Which unlocks honest reporting on what actually works.
One click between the organisations you belong to.
Manage tenants, plans and feature availability from the product.
Rich-text notes on contacts, job posts and applications, alongside candidates and companies.
Planned, not yet scheduled
Decisions, not omissions
We think a roadmap is more useful when it says what is not coming, and why.
A model can return a confident-looking percentage about a person's future, and recruiters would reasonably read it as a measurement. It isn't one — there's no reliable data to learn from, and it's precisely the kind of automated profiling that employment law is right to be careful about. We'd rather show you what your own history actually says.
It's discrimination, plainly. When an employer says they can't consider other nationalities, what they usually mean is that they won't fund relocation — which is a property of the role's budget, and we model it as exactly that.
Your sourced pipeline is your asset, and pooling people across organisations would make us a data broker instead of a recruitment platform. Every profile you source belongs to your organisation alone.
The card where you decide whether someone is worth considering is the last place appearance belongs.
No auto-advancing, no auto-rejecting, no emails sent without someone reading them. Every suggestion has a person between it and your data.
Publishing a role offers you a drafted post to read, edit and send. A job description gets edited three times in its first hour, and none of those drafts belongs on your feed.
This roadmap describes our current intent and is not a commitment to deliver any particular feature by any particular date. Items shift as we learn what customers actually need. Anything under "Available today" is live now.
Customer requests decide build order more than anything else here. Tell us what your desk needs and we will tell you where it sits.
