Relationship operating system

Biweekly onsite rituals for couples who want clarity, privacy, and follow-through.

Onsite turns reflection, planning, and accountability into one deliberate flow instead of a pile of notes, calendars, and half-finished conversations.

Start onboarding locally Preview workspace

BiweeklyResponsive web firstStrong privacy defaults

Cadence14 daysThe default rhythm is a lightweight but consistent reset.

Private inputs2Each partner writes first, then chooses what to share.

Core areas4Check-ins, goals, planning, and archive shape the first release.

Landing page placeholders

Structured sections ready for final copy.

The marketing surface is intentionally scaffolded now so product positioning can evolve in parallel with implementation instead of being bolted on at the end.

Why this matters

Placeholder for the emotional problem statement

Placeholder copy

Use this block to explain why couples lose alignment when life gets busy, and why a recurring shared ritual matters.

Value add

Placeholder for the practical outcomes

Placeholder copy

Describe how the product creates better communication, clearer planning, more accountability, and less mental overhead.

Functionality

Placeholder for the feature promise

Placeholder copy

Explain the biweekly flow, private-to-shared progression, goals, planning, archive, and future financial review module.

How it works

Private first, shared second.

Core v1 flow

The UX is designed so sensitive reflection can stay private unless a partner explicitly shares it. Once both people have reflected, the product shifts into joint planning and accountability.

Each partner completes a private reflection.

Each section can stay private or be shared intentionally.

The couple completes the shared onsite together.

The finished cycle is archived as a snapshot.

Feature overview

Everything important is easy to find.

UX priority

The product IA keeps the main rhythm obvious: current onsite, goals and bank, planning, archive, then settings.

Private reflections with explicit section-by-section sharing

Joint onsite workspace with goals, planning, and event review

Manual reward and penalty bank tracking with room for later automation

Archive snapshots that preserve how each cycle actually unfolded

Security

Privacy is part of the product, not a backend footnote.

Security first

Separate accounts, explicit sharing controls, couple-scoped authorization, and minimal operator visibility are built into the product model.

Private sections remain private until the author chooses otherwise.

Iteration

Built with current libraries, not hand-rolled primitives.

Modern stack

The stack uses current Next.js, React, Prisma, Tailwind, Radix Themes, and form validation libraries so the product can move quickly without recreating basic interface patterns.

Use proven components first and reserve custom UI for the product-specific flows.

Roadmap

The model is ready for more without distorting v1.

Future-ready

Calendar sync and financial review are not in v1, but the data model and route structure leave room to add them without a redesign.