Integrations · None required

Come as you are.

You don't need Notion, Google Workspace, or an IT department to run Tidemere. It carries its own database, calendar, tasks, and documents, scaled to where you are and where you're going. A single home and a small club are not smaller versions of the product. They are the product.

The binder Sticky notes A spreadsheet Text threads Your day, in order Tasks, calendar, records, documents The binder Sticky notes A spreadsheet Text threads Your day, in order Tasks, calendar, records, documents
The starting point

Most operations live in a binder.

A single residence with a housekeeper and a gardener. A swim and tennis club with two hundred families and one manager who does everything. The operation is real, and it runs, in a binder, on a whiteboard, across text threads, and in somebody's very good memory.

That is not a problem to apologize for. It is the normal starting point, and it is exactly what Tidemere was built to receive. You do not need to organize anything before you arrive, and you do not need to adopt a system like Notion first. Bring it as it is.

Setup

We take the load. You get it back in order.

Structuring your operation is part of setup, done with you, in conversation, over the same one to two weeks any Tidemere configuration takes.

1

Hand it over, in whatever shape it's in

The binder, the whiteboard, the spreadsheets, the printed schedules, the notes app. Photos of pages count. We have seen every format an operation can live in.

2

We structure it

Rosters, recurring task lists with their days of the week, calendars, standards, documents, allergies and preferences, all sorted into the shape the day actually runs in. We ask questions where the binder is quiet.

3

It comes back as a working operation

Lists staged each morning and pushed to staff phones. A calendar everyone reads the same way. One current version of every standard. The same engine the largest households run, sized to yours.

Native Tidemere

Everything the big systems do, without the big systems.

The records

Members or family, staff, vendors, preferences, allergies. Structured records that live in Tidemere itself, with no database subscription behind them.

The tasks

Recurring lists staged each morning, assigned in one motion, checked off on phones. Unfinished work is done or carried, never dropped.

The calendar

Born native: create, move, and cancel with every change logged. If you ever adopt Google or Microsoft, linking is one dropdown, later.

The documents

Standards and procedures with one current version, surfaced to the right role at the right moment. The binder, finally retired with honor.

No lock-in

Yours to take anywhere. Always.

Holding your operation's information is a responsibility, and the test of whether we deserve it is how easily you can leave. Everything Tidemere holds for you exports on request, cleanly structured, at any time, for any reason.

And if your operation grows into Notion, Google Workspace, or Microsoft 365 one day, Tidemere pushes your organized records into them through the same doors it uses to read from them, walked in the other direction. Native Tidemere is how a small operation gets ready for those tools, and the reason it may never need them.

What we need from you

Whatever you have, in any shape it is in An hour with whoever knows how things actually run Nothing else. No admin console, no IT department, no accounts to create first

Already have some systems and not others? Every combination is normal. Tidemere connects to what you have and carries what you don't.

Next step

Bring the binder.

A conversation starts with how your operation runs today, in whatever shape that takes, and what it should feel like when the day runs itself.