Emploi Retraite's job platform for people over 50, built by Provis from scratch.
Candidate and employer accounts, paid access to CVs and a guided CV builder, built in French and English. Live today, and run by Emploi Retraite's own team.
- Two-sided job platform
The live platform, checked 9 Oct 2026. The look is Emploi Retraite's own brand; Provis built the platform.
Client: Emploi RetraiteJob platform for people 50+, Quebec, CanadaOne platform for both sides of the hire.
- From scratch
- for both sides
- Candidate and employer accounts, the CV builder, job posting, alerts, plans and an admin side for the team.
- Private until paid
- role and plan rules
- Who sees what is set by the platform, not left to each user.
- Guided CV
- one question at a time
- It starts with the sectors a candidate wants to work in.
At a glance
- Problem
Small businesses needing experienced people for short contracts, and people over 50 who wanted to keep working, needed a simple place to meet.
- Solution
Candidates build a CV once and get job alerts; employers post an offer, pick a plan and receive CVs.
- Where it stands
Live on emploiretraite.ca and run by Emploi Retraite, with new offers posted in October 2026.
- Client
- Emploi Retraite (emploiretraite.ca)
- Industry
- HR tech: a job platform for people 50+ and retirees
- Market
- Canada (Quebec)
- Platform
- Web platform for candidates and employers
- Services
- SaaS development, payment integration, CRM integration, automation
- Built with
- Laravel, PHP, Stripe, HubSpot, Zapier
- Design
- Look: Emploi Retraite's own. Flows and logic: Provis
- Engagement
- Completed and handed over
Two groups who needed each other, and no simple way to meet.
Emploi Retraite saw both sides. Small businesses in Quebec needed experienced people to cover a contract or a leave of three, six or twelve months, without the time to recruit and train someone new. Many people over 50 wanted to keep working, but mainstream job sites were not built for them, and many had not needed a CV in years. Emploi Retraite wanted one simple platform for both, and Provis built it.
How a job reaches a candidate
- Employeropens an account and posts an offer
- Plan and paymentthe employer picks a plan and pays by card through Stripe; until then, no CVs
- Alert filterfinds candidates whose profile and preferences match
- Job alertby email and in the candidate's account
- One-click applywith the CV already on the platform
- Employer on a planreceives the CVs, with contact details
Green steps run on the platform Provis built. Step 2 runs through Stripe, which Provis connected; HubSpot and Zapier are connected for the team's own tools.
Posting jobs is the easy part. Earning both sides' trust is the work.
-
Job sites built for someone else
Long forms are a poor fit for people who have not needed a CV in years.
What Provis builtA guided CV builderCandidates answer one question at a time, with a progress bar, starting with the sectors they want to work in; Emploi Retraite's site puts it at about five minutes. After that, they apply to any offer in one click with the same CV.
-
Candidate details only for serious employers
Emploi Retraite wanted a candidate's details to reach serious employers only, not anyone who posted a job.
What Provis builtPrivate by defaultA candidate's CV, surname, last employer and contact details reach only employers on a paid plan. Without a plan, an employer sees no CVs and no contact details.
Role-based access: who sees what Who Sees The candidate Their own CV, the offers sent to them and what they applied to An employer without a plan No CVs and no contact details An employer on a paid plan The CVs of candidates who apply to its offers, with surname, last employer and contact details The same pattern fits any product where different users should see different data.
-
Employers who wanted candidates, not admin
A small business wants the right CVs in front of it, not another system to learn.
What Provis builtJob alerts and Stripe plansEach offer is emailed to the candidates whose preferences match, so employers do not have to go looking. They post the offer, choose a plan and pay by card, and the CVs come to them.
What Provis built, in order.
- BuildAccounts, the CV builder, posting and search, in French and English
- ConnectStripe, email alerts, HubSpot and Zapier
- Hand overThe platform and its documentation, to Emploi Retraite's team
-
Build: accounts, the CV builder, posting and search, in French and English.
-
Connect: Stripe, email alerts, HubSpot and Zapier.
-
If this were your first version: ship the core loop first (an employer posts and pays, a candidate applies, the employer receives the CV), then add what each side asks for next.
-
Where Provis's part ends: the job offers, plan pricing, site content and its translations, and customer service have been Emploi Retraite's since handover.
Hand over:
Provis built the platform they run on.
The platform and its documentation went to Emploi Retraite's team, who run it themselves.
The agreed scope was delivered.
Emploi Retraite runs the platform itself.
How Provis builds web platformsWhat each side sees.
The screens are in French, with translated captions. Select one to enlarge it.
- Candidate: the guided CV builder, step one.
- Progress bar across the steps
- One question per step, starting with sectors
- What finishing unlocks: job alerts
- Each sector a picture tile with a tick box
Employer: posting an offer, step one: region, city, sector, title and the role.
Candidate: job offers with filters and a job-alert button.
See it live:emploiretraite.ca (opens in a new tab)
After the project
Handed over, as agreed.
The agreed scope was delivered, and Emploi Retraite runs the platform itself.
- Code repository in Emploi Retraite's name
- Hosting and domain in Emploi Retraite's name
- Documentation handed over
If Emploi Retraite brings Provis back, the work starts from that documentation and its own repository.
How every Provis project runs
- One project leadyour single point of contact
- A written weekly update and a demoof what was built that week
- A staging link and your repoyou see the work as it is built; the code goes straight into your repo
- QA before launchour QA team tests every feature
- Yours from day onecode repo, cloud account and domain in your company's name; our team joins as collaborators, and you can remove access at any time
- Our team works in India, on ISTCalls and demos are booked in your working hours, and messages are answered within one working day.A 9 am call in New York is 6:30 pm in India (7:30 pm in winter); 9 am in London is 1:30 pm (2:30 pm in winter). India is 1.5 hours ahead of Dubai and 4.5 behind Sydney (5.5 during Sydney's summer, October to April).
Emploi Retraite chose to run it itself. Others keep Provis on.
- On a platform you already run: the pieces built here (role rules, paid plans, a guided form) added in modules, behind staging and QA, without a rebuild.
- On a platform like this one: new plan tiers, changes to alerts and regular upgrades.
Each change goes through the same staging link, QA and weekly demo as a build, and the code stays in your repo.
Building a platform, portal or store where different users see different things?
Tell us who your users are, what each needs to do, and what each side pays for. We reply within one working day, and come back within two working days with an approach, a rough timeline and a rough cost range. No charge, no commitment.
- A SaaS product: user roles and paid tiers that unlock features, added as modules to the product you already run.
- A new platform or marketplace: two kinds of accounts, with payments that open access to the other side.
- An online store or B2B portal: trade accounts and members-only prices on the same role-and-plan rules, and a product quiz that asks one question at a time, like the CV builder.
WhatsApp usSend us a message
indicates a required field