Buying Software Programmer as a specialist recruiter

Your search starts with a brief, not a database. You write down the role, the location and the specialism you place into, and a working app comes back with the data, logins and payments already wired in. That is the whole purchase: a tool shaped around the searches you actually run, held in a slot you own rather than rented by the month.

The value sits in the narrowness. A generalist job board carries everyone and sorts nobody well, so you spend the morning filtering noise. An app built to your brief can be arranged around one specialism from the start, with the fields and filters that matter to your placements, and nothing that does not.

You are not buying access to a shared pool that other recruiters also draw from. The app is yours, and the lifetime term is counted in apps rather than in months, so the clock never runs down on a tool you built for a desk you have run for years.

The tiers differ in one dimension only: how many apps you get. The smallest tier gives you a single lifetime slot, which suits a recruiter placing into one specialism with one tool to support it. The larger tiers add slots, and each slot holds one app.

Nothing is held back from the smaller tier in terms of what an app can contain. The difference is capacity, not capability. If your desk needs a candidate-facing app and a separate internal tool, that is two slots, and the single-slot tier will not stretch to cover both.

So the cheaper tier leaves out headroom rather than features. Buy it when you know your work fits inside one build. Move up when you can already name the second and third app you would commission, rather than buying extra slots on a guess about future needs.

The worry is staleness, and it is a fair one. A database that was accurate when you subscribed drifts the moment people change roles, and a recruiter searching a stale pool wastes the morning on candidates who moved on last quarter. Any tool you buy has to be refreshed by someone, and that someone is you.

The second worry is the wait. A detailed brief goes through review before work begins, so a broad recruiting tool may sit in a queue before anyone touches it. That is not a flaw in the deal, but it does mean the platform suits a planned build better than an emergency one you needed last week.

The third is scope. One lifetime slot covers one app, so a second separate tool needs its own slot, and the store where every deal is sold carries its own rules that apply alongside your tier. Read those rules before you commit, because they are not negotiable at the point of purchase.

Set the app-count tiers against what your desk actually runs. If you place into one specialism and need one tool, the single-slot tier is the honest comparison. If you maintain a candidate-facing app and an internal shortlisting tool, count two slots and compare from there, not from the smallest figure on the page.

Then compare against the alternative you already live with: a subscription database refreshed by a vendor, priced monthly, shared with every other recruiter on the same list. The trade is control against convenience. You take on the refreshing, and in return you get a tool arranged around your specialism rather than everyone's.

The deciding question is how many separate builds you can name today. Write the briefs first, count them, and buy the tier that covers that count. Anything beyond it is a guess, and a guess is a poor reason to pay for slots that may sit empty.