About Tidemere

Built by the people who ran the operation.

Tidemere was not designed by a team guessing at what a household or a club might need. It was built by senior operators who had already done the job, inside one of the most complex, multi-residence households in the world.

Where it started

One household, four disciplines, one shared problem.

Before Tidemere existed, this team ran the daily operations of a single household spread across several residences: the people, the properties, the children, the kitchens, and the systems holding all of it together.

Each of them met the same problem from a different side of the house. A request that should have taken one message took five. The current version of a standard was never the version in use. A detail that mattered to a child, a guest, or a board member lived in someone's memory instead of anywhere reliable.

None of it came from a lack of skill or care. It came from running a complex operation on tools that were never built to work together. Tidemere began as the fix this team built for itself, long before it was a product.

Who built it

Four functions, one operation.

Tidemere carries a piece of each discipline that built it. The product reflects the job each function actually had to do, not a theory of what that job might look like.

Resident operations

The picture, in one place.

Years spent reassembling the full picture by hand every morning, from a dozen separate sources, shaped the unified inbox, the daily digest, and the merged calendar.

Childcare

Nothing lost at a shift change.

Caring for children across several properties, where nothing may slip between caregivers, shaped the shift handoff, the child profile, and the parent's curated digest.

Culinary

An allergy is never small.

Running a kitchen for a household where a mistake was never a small one shaped member ordering and the allergy stop built into it.

Technology

Responsible for it, not writing about it.

Being accountable for a household's systems, security, and vendor access, rather than writing about them, shaped the integration model and the security architecture.

Why a product

What worked for one household, built for more.

After years of solving these problems privately, the pattern was plain: the same gaps exist almost everywhere a household or a private club runs at this level of complexity. The tools are familiar. The way they are forced to work together is not.

Tidemere is that same fix, built carefully enough, and generally enough, for other households and clubs to use. The standard did not change. Only the number of people it serves did.

On discretion

Private, by design.

The household this team came from remains unnamed, on purpose. Discretion was the standard there, and it is the standard here.

For the same reason, this page does not yet carry names or titles. That will change in time. The care will not.

Begin

Every Tidemere relationship begins with a conversation.

Speak directly with the team about what Tidemere could look like for your club or your household.

Request a conversation