Why we present it here
OpenPro is our own product. We designed it, built it and we run it: it is the most direct proof of what we can build, from the interface to the infrastructure.
It is also where we test our methods before offering them to our customers: an AI assistant connected to real data, tools exposed over MCP, and a human who keeps the decision.
One account, two roles
OpenPro brings candidates and recruiters together on one platform. A person can switch roles within the same account: look for a position, then publish a job offer.
The website is translated into 60 languages. The iOS and Android apps follow the same journeys: profile, job offers, applications, messaging.
Mia, the assistant at the heart of the product
Mia is OpenPro’s AI assistant. It searches job offers, helps write a job post and supports conversations, using the platform’s data.
The same tools are exposed by an MCP server: job search, applications, recruitment pipeline, messaging. An external assistant such as Claude or Cursor can therefore act in OpenPro, without the business logic being duplicated.
The whole ecosystem, not only the app
- A single API: profiles, job offers and applications, messaging, billing, AI assistants and administration.
- A back office for the team: tracking of activity, accounts and content.
- A job-offer reader that collects public postings, converts them to a common format and adds them to the platform.
- An infrastructure monitoring application, on the technical team’s computers.
- Infrastructure described as code, with a development environment separate from production.
What this brings to our customers
When we build an agent or a RAG for a company, we apply what we run ourselves: a clean API, access rights that are respected, tools exposed in a controlled way and a back office to manage it all.