Set up by the people who built it

You do it, and you may not need a developer

The lightest route writes no code at all. Create a connection in the desk, point the export your current system already produces at the address it gives you, and that is the setup: it reads your own column headings, reports every rename it made, and refuses exactly what a manual import would refuse. Every run is recorded, including the ones that brought nothing, because a source that quietly stopped is the failure nobody notices.

Where you do have a developer, there is the API as well: generate a key, choose the areas it may touch, read the endpoint list. For somebody who already knows your CRM that is a day of work rather than a project. Grants are per area and per level, so the integration that pushes placements cannot read your billing ledger, and revoking a key stops it on the next request.

We do it

A fixed piece of work: we write the integration between BookKept and whatever you already run, test it against your real book, and hand it over with the keys. Your consultants keep the desk they know and never learn a second system.

This is the option that suits an agency with no developer, or with one who is already fully spent on something else. It is scoped and quoted before it starts, because a compliance system that arrives late is a compliance system that missed a statutory date.

We do the lot

The agency's public website rebuilt on the same system, on your own address, with the client portal and the worker portal already wired to the record behind it.

The point is not that you get a website. It is that there is one system under the website and the back office, so a client approving a timesheet, a worker checking their rota and a consultant raising an invoice are all reading and writing the same record. Nothing is typed twice and nothing is reconciled afterwards, because there is no second place for it to disagree with.

• Your site, designed for your agency rather than assembled from a template.
• The client portal your clients actually use: briefs, approvals, invoices, the compliance position on their own people.
• The worker portal: rota, timesheets, documents, change requests, and the paperwork the law says they get.
• Your book migrated in, either through the importer or by us, with every column rename reported rather than guessed.

Your own address

Agencies on this route get their own address, either a subdomain of ours or a domain you already own:

An approval link a client receives then arrives from an address they recognise, which matters more than it sounds: the whole chain hangs on somebody clicking a link in an email, and an unfamiliar domain is the difference between a click and a spam folder.

An address decides appearance and never permission. The hostname is written by whoever makes the request, so it selects the name and colour a page wears and nothing else. Sign-in still checks a password, a portal link still checks its own token, and an integration key still carries its own agency.

What a reseller cannot offer

• The rules are configuration, and we ship it. Right-to-work changes on 1 October 2026 and umbrella regulation lands from April 2027. Those arrive here as dated rule packs, not as a release you have to schedule. Your integration does not move.
• One party to ask. When something is wrong there is no argument about whether it is the software or the implementation, because it is the same people.
• Your data is never held hostage. An offboarding bundle hands the whole tenant back, importer-shaped, round-trip verified. That is built because it should exist, not because anybody expects to use it.

How it goes