Packages

Three sizes, and what puts a job in one of them

A setup is measured on three things: how many working processes the workspace has to carry, how many databases those processes need, and how much of the joining-up has to be worked out rather than copied. The packages below are those three things at three settings.

There is no figure on this page and none anywhere on this site. The price, the timescale and the number of revisions included belong in a written quotation for the job in front of us: putting a figure here that had to be true of every job would mean inventing one.

Plan your Notion workspace How the work runs

One person

Single space

One working process, set up properly. Notes, tasks and projects joined to each other and one home page that answers what is in hand today.

What is in it

A structure drawn up from your own way of working, not a stock layout renamed.
Databases joined so that nothing has to be copied from one to another.
A home page that opens on what is in hand rather than on everything.
One template for whatever you start most often.
Written notes covering how to add to it without breaking the joins.

What is not

Shared editing, permissions and anything that depends on more than one person is a Team space.

Ask about Single space

A small team working on the same projects

Team space

Several processes that hand work to each other: projects and tasks, meetings that leave decisions behind them, and views that let people see each other’s work without asking.

What is in it

Everything in Single space, laid out for more than one pair of hands.
Relations that carry work across: a meeting raises tasks, a project shows them.
A board, a list and a schedule over the same records, so nobody keeps a second copy.
Templates that make the tenth project arrive set up like the first.
A short written convention for naming, filing and archiving, agreed with you.

What is not

A handbook that the whole team reads and keeps up to date is Connected operations.

Ask about Team space

A team whose workspace has become the place work actually happens

Connected operations

Several processes across a team with a knowledge base behind them, kept honest by review properties, templates and a navigation layer built for people who were not there when it was made.

What is in it

Everything in Team space, with a handbook joined to the work it governs.
Review properties, so an entry that has gone stale says so instead of being quietly wrong.
Navigation built around the questions people actually arrive with.
Archiving that keeps the workspace fast to read as it fills up.
A second look after you have used it, with the adjustments that come out of real use.

Ask about Connected operations

Side by side

What each package is measured at, side by side

Every row below is read from the packages themselves, so this table cannot fall out of step with the cards above it, and a row added to one package appears here without anybody retyping it.

What each package is measured at. The figure for any of them is quoted in writing.
Measured on	Single space	Team space	Connected operations
Processes	One	Two or three, joined	Several, across the team
Databases	A small connected set	A wider set, with relations between them	A full set, joined in both directions
Views	One way in, two ways to read it	Per person, per project and per week	Entry points by role as well as by record
Templates	One	One for each thing the team starts often	A template for every routine start
Handover	Written notes and one walkthrough	Written notes and a session with the team	Written notes, a session per role and a review afterwards

What moves a quotation

Published, because “it depends” is not an answer

These are the things that actually change what a setup costs. Knowing them means you can ask for a smaller job rather than guess at one.

How many processes

A process is one thing the workspace has to carry from start to finish. One is a Single space; several that hand work to each other is where the work goes up, because the joins have to be designed rather than listed.

How many databases, and how they join

Databases are cheap to make and expensive to join badly. The count matters less than whether a record has to be found from both ends, which is what decides how many relations and rolled-up properties there are.

How much has to be worked out

Building a structure you have already described is quick. Working out what the structure should be, from how the work moves now, takes longer, and it is the part that is easy to leave out of an estimate.

Whose workspace it is built in

Building on sample data in our own workspace and handing you a template is one job. Building inside your workspace, around records you already hold, is another, because the existing material has to be read before anything is moved.

How much migrating there is

Bringing what you already have into the new structure is quoted separately from designing it, because its size has nothing to do with the size of the structure.

Training

Each package names the handover session it carries, and that is what is included: one walkthrough with Single space, a session with the team with Team space, a session per role plus a review afterwards with Connected operations. Sessions beyond the ones the package names - a second cohort, somebody who joined later, a refresher months on - are quoted with the rest.

Two routes

Built in ours and handed over, or built in yours

Every package can take either route, and the route is settled in the brief, before the quotation, because it changes both what the job involves and what access we ever hold.

Template handover

We never touch your data

The workspace is built in ours, on sample records, and handed to you as a template you duplicate into your own account. Nothing of yours is opened, shared or moved, and no access is asked for at any point. You fill it yourself, with the written notes beside you.

Suits

Anyone whose material is confidential, and anyone who would rather not hand over access to an outside company.

Built in your workspace

Access, agreed in writing, for as long as the work takes

You invite us into a workspace you control, at the level of access we agree in writing beforehand. We build in it, alongside what is already there, and the access is handed back and removed when the work is signed off. What we were given, and when it ended, is written in the order confirmation.

Suits

Teams already working in Notion who want the new structure around records they are using now.

Paying

How money actually works here

No basket, no card field and no checkout on this website. The whole of it is written down before anything is owed.

Currency

Pounds sterling

Every quotation is in pounds sterling (GBP). The amount quoted is the whole of what is payable for the work described, including any tax due on it, and nothing is added to it afterwards.

Order

In writing, both ways

You accept the quotation in writing, and the order exists once we have confirmed it back to you in writing. Until that confirmation goes out there is no contract and nothing is owed by anybody.

Payment

By invoice, from the confirmation

An invoice follows the confirmation, with the due date on it. Pay it by bank transfer to the account named on it, or by card through a secure payment link in the same email. The link opens a payment page belonging to Stripe, our payment provider; the card is entered there, and this company never sees or stores the details. This site takes no payment at all.

Cancelling, refunds and what happens if the work is not as described are set out on the Delivery & Refunds page, and the terms the whole of it runs under are on the Terms of Service page. Anything that is not clear, ask before you accept a quotation: support@worknestle.org.