Keep one record per vacancy, with every place it was advertised.
Job Posting keeps one record for each vacancy: the role, the branch, how many people you need, who approved it and every place it was advertised. Applications from your careers page land on that record and not in a personal Gmail. Fill the seat and the post closes, so an opening from March stops pulling CVs in September.
A vacancy usually starts as a sentence in a WhatsApp group. Somebody puts it on a job board, somebody pins a notice at the gate, and a cousin is asked to ask around. Replies then arrive on three phones.
One record per vacancy changes that. Role, branch, openings and pay range sit together, and each posting carries its date and its link.
What your team uses today.
The module takes over these, one at a time, so nothing has to stop while it is set up.
- A spreadsheet of open roles
- A personal email inbox for applications
- Job text copied from the last advertisement
The problems this is meant to ease.
What job posting does.
What this looks like in a working week.
Illustrative scenarios, written to show the shape of the work. They are not accounts of client systems.
The people who open this every day.
From first conversation to daily use.
Trace the current process
Describe how a vacancy starts today. We write back the approval steps and the channels you use.
Set up the careers page
You supply role templates and branch names. A careers page arrives on your own site for you to try.
Add the approval step
The owner chooses who approves openings. You get a screen where a manager raises a vacancy and approval is recorded.
Run a live opening
HR posts a real vacancy and watches applications arrive. The group leaves trained, with changes noted.
How you would know it is working.
Record where you stand before it goes live, so the change is measured against your own figures.
- Vacancies open past their expected date
- Applications by source channel
- Vacancies posted with an approval on record
- Posts still live after the seat was filled
- Applicants reaching interview, by channel
It is one part of a system, not an island.
A module earns its place by what it passes to the next one. These are the connections we set up most often.
- Your careers page
- Resume management
- Candidate tracking
- Employee database
Products that include it.
How we would put it in.
Questions owners ask about job posting.
Can it post on LinkedIn or other job boards by itself?
No. Those boards charge for posting through their own systems, and most small employers still post by hand. What you get is a record of where you posted, and applications from your careers page in one list.
Is a spreadsheet enough for four hires a year?
Probably. One person, a few vacancies and a folder of CVs will hold together fine. Three branches hiring at once changes that.
Can somebody apply from a phone?
Yes. The form works in a mobile browser, which is where most applicants are. A PDF or a photo of a CV attaches.
Will it sit with the HR system we already run?
It can. A hired candidate passes into your employee database and is not typed in again. If an HR package already holds those records, tell us which one, and we will judge whether joining the two pays off.
What affects the cost of a job posting module?
Branches, roles and approvers set the base. Careers page design, links to resume and candidate tracking, and WhatsApp alerts add work. The approval step can be dropped for a small team.
What decides how soon vacancies can be posted from it?
Your role list and approval rule. The initial cut holds the vacancy record, approval, channel log and careers page. You supply role details and branding, and the proposal names the dates.
Businesses that ask for this.
Modules that work with it.
Tell us how you handle job posting today.
A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.
What happens after you share your requirements
- A senior engineer reads your answers. Nobody phones first.
- Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
- If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
- No call is booked and nothing is paid until you have read the note. Your details stay with us.
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirements