Services

Called Offerings until 18 September 2026. Anyone reading older release notes will see the old word.

The Services screen is a table: each service's price, how many tasks come with it, how many customers have bought it, and its margin. Clicking a service opens its own page, laid out like a project: its tasks in the order every sale gets them, with an add row on top. Changes save as they are made. The name, price and colour are behind the Details button.

A service is a thing you sell, defined once and reused: a name, a short code, a type such as retainer or fixed price, and an amount or a rate. Putting one on a project creates the contract for it, so the terms come from the service rather than being retyped each time.

A service can carry a list of tasks. When it is put on a project, those tasks are created there in order and pinned to the contract they were sold under. That is how you make every client who buys the same thing start from the same set of tasks, which is what people usually mean when they ask for project templates.

A step can repeat, and that is most of what a service is for. A monthly report is not one task; it is a task every month for as long as the retainer runs. A step set to repeat makes an ordinary recurring task — there is one recurrence system in the product and this is it.

Two kinds, and the difference matters. Repeats after it is done waits for somebody to finish the last one, which is right for a follow-up. Repeats on a schedule produces the next one when its date arrives whether or not the last was finished, which is right for an obligation: February's report is owed because it is February. Each sale gets its own chain, so one client finishing their report decides nothing about another's.

The same choice is on any task, under Recurrence. A fixed schedule used to wait to be ticked off, which meant a task nobody finished stalled its series in silence; it now advances on the calendar, and a series that fired late does not drag the rest of the year along with it.

Adding a task to everyone who already has a service. Add a task to customers on the Services screen takes one piece of work to every customer on any number of services — one task each, against their own contract. It can appear now or in so many days. Ticking also keep it on the service is the difference between a one-off sweep and a change to what is sold: with it, the same thing is added to those services' lists, so customers bought in from then on get it too.

Each task has two dates: when to start work and when it is due. On the service's page, tasks are added with a row like a project's add-task row, and its When button sets both dates as a number of days before or after one date: the sale, the contract's start date, its end date, or its event date. A wedding photographer's questionnaire can be due six weeks before the wedding, and a yearly contract's renewal call a month before its end. The start work date becomes the owner's next work date on the task. Clicking a task opens it like any task, with the title, the description, and under that the dates, whether it repeats, and whether it stays off the list until its start work date, so a year of work is not in the list on the day of the sale.

The dates can be changed before the sale is saved. Ticking Create the tasks on a new contract lists every task with its start work and due dates, worked out from the contract's dates. Any date or title can be changed and any task left out, and changing the contract's dates updates the list without undoing what was changed by hand. A contract has an optional Event on date for the day the work is for. A task counted from a date the contract does not have yet says so, and has no date until one is given.

A task can count from a date set on the service. Counted from a date in the When button shows a date picker, for work owed on the calendar rather than around the sale: quarterly taxes due on the 15th are one task on 15 January that repeats on a schedule every 3 months. A sale starts such a task at the next date still to come, so a client signed in May gets July's, not a January already gone. A task on a set date that does not repeat keeps its date even after it passes, and the review at the sale shows it.

Repeats is in the When button as well as the task. The event and end dates are set on each sale, on the sale form, and the When button says so when one of them is chosen.

Moving one year's date for every client. Opening a task on a service lists the clients who already have it, grouped by the day it is due, and any of those days can be moved for all of them at once, for the year taxes fall on the 18th instead of the 15th. Start work dates move by the same number of days. A repeating task remembers the date it was planned for and counts the next one from that, so moving one year moves only that year, whether it is moved here or on the task itself. Setting a task's repeat again starts counting from its due date at that moment.

A service's task repeats the same ways any task can. The When button has the task's own Recurrence control: after completion, every so often, the first of the month, a day of the month, a day of the week, or so many days before the month ends. A step that repeats on a day of the month or week with no due date of its own is first due on the next such day after the sale.

A service's task can be a task type. Its window picks an existing type, or Make this a new task type creates one named after the task, for admins. The picker shows even before the company has any types.

Each copy keeps its start work date. A repeating task remembers how many days before its due date work starts, from the service or from the task's own start work date when its repeat was set. Every new copy gets a start work date that many days before its own due date, never earlier than today.

A repeat stops with its contract. A repeating task sold under a contract makes no new copy after the contract's end date, or once the contract is no longer active. With no end date it repeats until the contract is stopped. The next copy stays on the same contract as the last.

A waiting step is a promise carrying its own copy of what to make, so editing the recipe afterwards never rewrites it — the same rule as work already created. A contract that stops before a step's day comes never gets it.

On the contracts screen, a contract with work still to come shows a clock and a count. Opening it lists each waiting step and the day it lands, soonest first. Any of them can be changed for that client alone — a different title, a different day, a different due date — or called off entirely. The service is untouched either way: this is one client's copy of a promise, not the recipe everybody else gets. Work already created is unaffected, and a step whose day has already come is an ordinary task and is edited there. A contract that has stopped still lists what was promised, and says plainly that none of it will arrive.

If somebody says they cannot find where to add tasks to a service, they are probably looking for something called templates. They click the service on the Services screen.