The things people ask first.

A household operating system: it holds your family's schedule, responsibilities, meals, people and care in one place, works out what needs to happen next, and asks a specific person to take it.

About ten minutes. Connect the calendars you already use, say who's in the house, and answer a short set of questions about your normal week. After that it works from what actually happens rather than from you maintaining it.

Not yet — the beta is iPhone. Android and a browser version are both on the list and neither has a date, for the reason given on the vision page.

Nothing during the beta, with no card required. We haven't set a price for launch, and we'd rather say that than post a number we might change. Founding families keep founding pricing for good.

For the calendar, prep and meals, no — it's useful on day one for one person. For the part that actually moves work off your plate, yes: someone has to be able to receive an ask and answer it. That's the whole point, so we'd rather be plain about it than let you discover it later.

No. Imported events are read and keep their original identity. Everything you add here — who's driving, what to bring, who agreed — lives in a separate layer that belongs to LifeSyncOS. We never edit or duplicate an event in your real calendar.

Not on its own. There's no mailbox connection and no inbox scanning. You paste, forward or screenshot the thing that matters, and it shows you what it found before writing anything down.

You see the proposal before it becomes a fact, and you correct it there. AI is never what decides who's driving, who agreed, or what's finished — those come from records and from you. A wrong guess costs one tap.

A decline is kept, not erased, and it moves you straight to the next person instead of starting over. An unanswered ask stays visibly pending — it never quietly ages into looking handled.

Their yes was to specific terms. Move the pickup by 45 minutes and the old agreement becomes history rather than coverage, and they're asked again with the new details. This is the single behaviour the product is built around.

Teens can have their own sign-in with a limited view — their schedule and what they've been given. Younger children are profiles a parent manages rather than accounts.

Yes, with a scoped invitation. Someone invited for Thursday evening sees Thursday evening and the care notes for that visit — not your week, your people or your documents. The access ends when the thing it was for ends.

Yes. Coverage leans on whoever actually helps — a grandparent, a neighbour, a carpool parent — and they get invited to one specific thing rather than to your whole household.

Not today, and we'd rather say so. Two adults inside one household works now. A child living across two separate households needs its own permissions model and is a named piece of future work, not a quiet limitation.

No. There's no advertising business here and no third party buying household patterns. The people paying for LifeSyncOS are the families using it. The full detail is on the trust page.

Only with you looking at it first. It drafts the message and shows you the recipient, the channel and the exact words. Sending is always your action, never the app's.

No. It knows a pickup happens at a school at 3:15 because that's on the schedule. It does not follow anybody's phone around, and that isn't something we plan to add.

Export the whole household as one file, then delete it. Deleting removes it rather than archiving a copy for us to keep. Your connected calendars are untouched because we never wrote to them.

One family in Kansas City, using it on our own week before anyone else's. That's why it says no to so many features — each one has to survive a real Wednesday first. The longer version is here.

Because there aren't real ones yet, and inventing them would break the exact promise the rest of the site is making. When founding families have been living with it, their words go here with their names attached.