Service
For publishers, associations and niche board operators who want to run a job board as a revenue line, with posting packages, a sector taxonomy and application routing designed for their market rather than a generic listings script.
The problem
Where it usually starts
A trade publication has carried recruitment advertising for years, first in print and then as a page of links on its website.
Where it gets harder
Candidates fare no better.
Scope of the service
A custom job board build normally covers the whole posting-to-expiry cycle. Employer accounts carry posting packages bought through the order layer: single listings, bundles, or a subscription with a monthly allowance, with a featured upgrade as a priced option. Job listings use structured fields chosen for the sector, such as location, contract type, salary band as the employer enters it, specialism and seniority, with an expiry date that archives the listing and reminds the employer to renew. Candidate accounts hold a profile and CV upload, saved searches and job alerts delivered by email at a chosen frequency. Applications are either collected on the board and routed to the employer with status tracking, or redirected to the employer's own site with the click recorded, per listing. Feed intake accepts vacancies from employers' systems or aggregators on a schedule, mapping their fields to your taxonomy and expiring what disappears from the feed. Employer branding pages collect an employer's live roles with its own description and media. Application statistics per job and per employer feed both the employer dashboard and your sales conversations.
During discovery we map how recruitment advertising is sold today: who the account manager is, how packages are priced, what the renewal conversation looks like, which employers would use a feed, and what taxonomy candidates in your sector search by. Each of those becomes a named stage in the scope document.
A professional association wants a members-only board where only member firms may post, listings are categorised by the association's practice areas, student members receive a weekly digest of graduate roles, and the membership database decides who can post at member rates. The membership link and the two-tier pricing make this a custom build, and the scope document says so plainly.
Deliverables
Process
Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.
Access to the current listings page, accounts package and email platform; a list of active employers and the packages you sell.
Discovery with the advertising manager and the editor; packages, taxonomy, application routing and feed sources are written into the scope document.
Search, job page, employer dashboard and alert email designed for candidates on a phone and employers at a desk.
Built in layers: taxonomy and listings, then employer packages and orders, then candidate accounts and alerts, then feeds and statistics.
Your team and two friendly employers post, feature and expire real roles for a fortnight and tell us where the flow does not fit.
Changes from the review are made and re-checked against the scope document.
Listings migrated, redirects tested, payment callbacks and alert sends verified against accounts you control, launch checklist signed off.
Employers post through the new board; hosting and maintenance continue under their own agreement if taken.
Integrations
Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.
How we would approach it
The situation
A professional association wants to replace a page of emailed vacancies with a board where only member firms may post, listings are categorised by the association's own practice areas, and student members receive a weekly digest of graduate roles.
Why it is a custom build
The custom route is needed because of the membership check and the segment-based digest, which go beyond the single public employer tier the package assumes.
The scope we would propose
Pricing
Every proposal is priced on scope. These are the factors that move it most for this kind of build.
FAQ
If public employer accounts, a configurable taxonomy, standard packages and on-board or redirected applications cover your market, the job board package is the right fit and we quote for that. Membership-gated posting, unusual pricing tiers or feeds from several systems with different field maps point to the custom route.
Yes, where the employer or aggregator can provide a feed in a documented format. Each feed is mapped to your taxonomy during planning, runs on a schedule, and expires listings that disappear from the source. The scope document names each feed and its field map.
No. Each listing can collect applications on the board and route them to the employer with tracking, or send candidates to the employer's own careers page with the click recorded. Many boards use both depending on the employer.
Yes. Live listings, employer accounts and candidate registrations are migrated, and every old job URL is mapped to its new address so search visibility and existing links are kept.
You do. The source code, listings, employer and candidate data are handed over at delivery. Hosting and maintenance are optional and agreed separately.
Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.