Can managers see each other’s teams?

Only if you say so. Access is role and record level: a team lead sees their own reports, HR sees everyone, and salary is a separate permission from the rest of the record. Nothing is visible by default.

What about contractors and part-time staff?

Both are first-class rows. Contractors carry a rate rather than a salary and flow into Books as a cost; part-time capacity is expressed in hours, so the delivery plan cannot quietly assume five days.

Treepie Nest · HR & employee management

One person, one row, from offer to alumni.

The time and money consequences of employing people flow into delivery and finance instead of into a spreadsheet somebody maintains on a Friday afternoon.

Book a demo What is inside Nest

6 daysto first payroll run

1 rowoffer to alumni

−7 dayson month-end close

People — August34 employees

PersonStateEffect

A. WhitlockLeave approved−3 days

R. OseiOnboarding, day 460% capacity

M. FarahShift swappedSat → Tue

J. PetrieExpenses filed£412

K. DunnNotice servedends 12 Sep

every row on the left changes a number somewhere on the right

The problem

The people cost is already in your delivery numbers. It is just not visible.

Leave, capacity and payroll usually live three systems away from the work they pay for. Nest keeps one row per person and lets delivery and finance read the consequences rather than re-enter them.

BeforeWith Nest

A leave requesta form, a rota edit, a note to payrollone approval, three systems already know

Capacitya guess made on a Mondaywho is actually free, from the same calendar

Payrollapproved hours retyped into a portala run assembled from what was approved

Inside Nest · 6 features

6 features, and what each one is joined to.

All features →

Feature 01 of 06 · joins platformEmployee recordsOne row per person: contract, role, cost, documents and history, readable by whoever is allowed to see it and nobody else.

Read the feature page →

Who opens it

4 people, one row, 4 different mornings.

HR leadOne row per person, and the audit trail behind every change to it.

Line managerTheir own team: leave, capacity and who is still onboarding.

PayrollA run assembled from approvals rather than from three exports.

Delivery leadWho is genuinely available next month, not who theoretically is.

One record

Where Nest meets the rest of the company.

Nothing here is an integration. Each line is two products reading the same row from different sides.

See all seven →

Nest + LoopCapacity, leave and notice periods meet the delivery plan before anybody promises a date.

Nest + BooksApproved time and expenses reach the payroll run without a second entry anywhere.

Bexley Group · 112 staff · professional services

“Three people asked who had changed the holiday policy. The answer was in the audit trail, which had never once happened before.”

Tom Ackroyd, Head of People

112people, one row each

6 daysto first payroll

−7 dayson month end

0rota spreadsheets

In practice

What actually changes, and when.

Week oneWeek one is data entry nobody enjoys: contracts, start dates and holiday balances. It is the only genuinely tedious part, and it is finished once.

Month twoThe first month people notice is the one where a leave request is declined for a reason everybody can see — the delivery calendar, rather than a manager’s memory.

The quarterBy the second payroll run finance is reviewing a number instead of assembling one. That is usually where the time actually comes back.

Getting in

The first payroll run is six days away.

Migration guides →

Day 101 / 04Contracts and balancesThe tedious part, done once: start dates, entitlement and the balances people already carry with them.

Day 202 / 04Approval chainsWho approves what, and what happens when they are away. This is where most rollouts quietly fail.

Day 303 / 04Parallel payrollRun the month in both systems and compare. Nobody should trust a first run that was not checked.

Day 604 / 04Open it to staffPeople see their own record first. Managers get their team the week after that.

Under every product

The boring parts, done once.

Permissions, audit, API and backups belong to the record, not to Nest — so they are the same in every product you add.

Security & trust →

Record-level permissionsRoles, teams and field rules. Salary is a separate permission from the rest of the record.

Audit trailWho changed what, when, and what it was before. Retained for the life of the account.

API & webhooksDocumented REST, a token per integration, and webhooks that fire on the same events the interface does.

Imports & bulk editCSV in, CSV out, and a bulk editor that shows you the diff before it commits anything.

Uptime & backups99.9% target, a published status page, and point-in-time restore for the last 30 days.

Data residencyUK and EU regions. Your data stays in the one you pick, backups included.

Honest limits

What Nest does not do.

Payroll filing is UK and IrelandEverywhere else Books exports a run for your bureau. We would rather say it than imply global coverage.

No applicant trackingNest starts at the offer. Recruitment pipelines belong in a tool built for recruiters.

No benefits marketplaceIt records what you offer and what people chose. It does not sell you insurance.

Pricing

Nest is £9 a seat. Every product you add costs less.

The record underneath is free. Switch on a second product and the whole bundle steps down — up to 40% with all seven.

Nest pricing →Build a bundle

1list

2−10%

3−18%

4−25%

5−30%

6−35%

7−40%

Questions

Nest, answered.

Anything else — ask a person.

In the UK and Ireland yes, including RTI submissions. Everywhere else Books exports a run your bureau can take, which most companies find is the boring, working answer. We would rather say that than imply the coverage is global.

The other 6.

Compare all →

FlowSales & customer management LoopProject & work management DeskCustomer support & ticketing BooksFinance & accounting GrowthSEO & website growth intelligence PulseAI customer & employee assistant