Tidemere Residences
One private application for the family and the people who run their homes. Built to the shape of your operation, not a template. Hosted on your own instance. Speaking to no one but you.
Three questions, answered straight
Who is in the house. What is happening today. What needs doing. What the family said and who has it in hand. What is broken and where it stands. Who sleeps where. What the house has written down, and who has signed it. One place, kept by the house.
Every household runs on six things: today, the inbox, the calendar, the people it serves, the people who work in it, and the schedule. Tidemere makes those six real and keeps them in one place. Around them it adds the rooms your house needs, and nothing else.
The director runs it from a desk. Staff use it on their own phones as an installed web app, nothing from an app store. The family opens it when they want to see their house. Each person sees exactly their share. It runs on an instance that is yours alone.
It is built around the estate director. It fits a director who runs the whole operation herself, and it fits a family office with a VP, department heads and a security team, because it is shaped to the operation rather than the other way around.
A Tuesday, in a two-house operation
An operation drawn from a real brief: an estate director, a housekeeper at each house, the grounds by a vendor, two principals who work in technology. Sample names. Real screens.
Both houses at once: who is on shift, what the family said overnight, three open matters on the maintenance desk, one in hand, a vendor on Friday. Miami is already three hours into its morning.
Her shift, her four tasks from the morning build, the opening checklist with the two lines she has already ticked, and the one policy she signed last week. Nothing of the other house. Nothing of the family's calendar.
The checklist asked for a photo. It was taken inside the app and lives on the record, never on a personal phone. The guest house was aired for the weekend after next.
Sent from the family's own door. It lands on the director's desk as a ticket with a trail, priority high, and the principal can see it is in hand without asking twice.
The director puts them on the Stay, gives the Quists the guest suite, and the board says one head still has no bed. The rooming list goes to the principal to agree. Housekeeping's list for that Friday will say "prepare the guest suite" by itself.
Hourly staff are notified only on shift, by that property's own clock. Off the clock, everything waits in the Inbox. The one exception is an emergency notice, which reaches everyone.
What the director sees
These are product screens set in type, not illustrations. Every line on them is live in the working model, and every one carries who did it and when.
The shape of it
The whole day at a glance for the seat that opens it. The director's is both houses. A housekeeper's is her own shift.
One person, one thing. Messages travel the chain of command so an ask lands on the right desk and nowhere else.
The family's calendar, and the house's. What the family keeps private reads as a plain label to everyone running the day.
The people the house serves: family, friends who visit, the guests of a Stay. Preferences, dietary notes, sizes, history.
The people who work in it, and the vendors who come. Seats, devices, departments, who may see what.
Shifts, time off, availability. Hourly staff are reached on shift only, by the property's own clock.
Modules, switched on in conversation
Dark means on for a two-house operation of this shape. The rest wait quietly until the house needs them, and switch on without a rebuild.
Nothing out of a box
Tidemere is one application made of rooms, and the rooms are shaped to the operation that lives in them. The same software runs a three-person house and a thirty-person estate because neither is a preset. This is what that means in practice.
Every building, room, space and service area goes into the Property Register, exactly as your team calls it. After that, nobody types a room name again. The maintenance desk, the room board, the checklists and the calendar all pick from the same list.
Three boxes or thirty. A department with no head rolls its desk up to the director on its own. When the hire lands, the desk moves to them, and nothing else changes.
Who sees whom. Which phone is a company device. Who approves spending, time off, a new phone. What the family keeps private. Each is a setting the house holds, not a request we file.
An operations manual and training booklets for staff, heads, leadership and the family, written for the house that receives them, every button named as it appears. Updated in the same build as the software, never after.
A one-page worksheet on the shape of the operation, with stand-in names. We build your house on it. You walk through it as yourself, on your own phone, before anyone signs anything.
Where we hold the line
Each household runs on its own instance with its own database. No path exists between one house and another.
No analytics, no trackers, no advertising, no scripts from anyone else. Even the typefaces are served from your instance.
Support access exists only when your administrator grants it, for a set number of hours, written into your audit record. Withdraw it any time.
Every camera in the app is the app's own. A photo for a ticket or a checklist goes to the record and never to a camera roll.
Hourly staff are reached on shift, at that property, by its own clock. The one exception is an emergency notice.
Presence comes from the season and the calendar; on-shift status from the published schedule. Never from following a phone.
Not now, and not as a future line of business. The records exist to run the house, for no other purpose.
Deliberately. The house must be able to read its own record, audit it, and hand it to the next director. The keys are the house's, and that is the point.
The questions advisors ask
These are the answers we give in the room. Nothing here describes a plan; each line is built and written into the manuals a house receives. The full page is at tidemere.com/security.
Before any demo
A one-page worksheet on the shape of your operation, with stand-in names. We build your house on it, and you walk through it as yourself, on your own phone. Every answer you want in writing goes in writing. The founder ran houses before he wrote software for them; ask him anything your advisors would.
No pricing grid, no plan with checkboxes. Configured in conversation, to the scale of the house.