Should a specialist recruiter build or subscribe?

A recruiter's spend here buys finished builds, not a seat that renews every month whether or not you use it. Each lifetime slot is tied to one app, and that app arrives as a working web app rather than a prototype or a template you finish yourself. Data storage, logins and payments are part of the build.

Think about what your desk actually needs before you choose a tier. A narrow specialism usually wants one tool: a candidate shortlist you can filter by role and location, with records you maintain rather than records someone else last refreshed. That is one build, and one slot covers it.

If your search tool sits alongside a separate client tracker, or a second tool for a different specialism, each of those is its own build and its own slot. The tier you pick should match the number of separate tools you genuinely intend to use, not the number you might imagine needing one day.

Three lifetime tiers are published on softwareprogrammer.app: one app lifetime, three apps lifetime and ten apps lifetime. The difference between them is the number of apps you can have built, and nothing else in the brief suggests a variation in what each build includes. Data, logins and payments are named as part of the build.

The one app tier suits a recruiter testing the idea on a single tool. The three app tier covers a desk with two or three distinct workflows: candidate search, a client or vacancy tracker, and perhaps a second specialism. The ten app tier is for a desk or a small team that already knows it will keep producing briefs.

Because lifetime is counted in apps, the tiers do not expire and do not renew. A slot sits unused until you write a brief and have it built. That is the shape of the offer as published, and it is worth reading the tiers directly on the site before you decide which one matches your plans.

The usual worry is a database that has gone stale by the time you search it, so the question becomes whether a built app can stay current. What the brief supports is this: your app is built with its own data and logins, so the records it holds are the ones you and your team put there and keep there. That is a different arrangement from renting access to a shared pool.

A second doubt is speed. Not every brief can be handled automatically, and more involved builds go through review before they ship. A tight, specific brief for a candidate search tool with location filters is the kind of scope that keeps a build moving; a sprawling brief that tries to cover every process on your desk invites review and delay.

A third doubt is whether the money is wasted if you only ever build once. On the one app tier, you are paying for one build. If that single tool is the only one you need, the tier has done its job, and the upgrade question simply does not arise for you.

Upgrading comes down to how many separate tools you can name without inventing them. If you can point to a second workflow you would build this quarter, the three app tier starts to make sense. If the second and third builds are speculative, stay on one app and revisit the question when a real brief appears.

Another signal is team size. A single recruiter working one specialism usually has one clear tool in mind. A desk with several consultants, or one consultant covering two unrelated specialisms, tends to accumulate separate builds, and separate builds consume separate slots. Count the tools, not the people, before you move up a tier.

Whatever you choose, the store where every deal in this space is sold carries its own rules, and those rules apply to your purchase alongside the tier you select. Read them before paying, then write the brief for the first build while the detail is fresh in your mind.