Built for two

Planning a wedding as a couple, without one of you becoming the project manager.

The default failure mode of couple-planned weddings is quiet: one partner drifts into being the project manager, the other into being a guest with veto power, and resentment compounds on both sides. The fix is structural: split the wedding by area, keep one source of truth both of you actually look at, and log decisions so they stay decided.

Division of labor

Split by area, not by task.

Handing out individual tasks ("you call the florist Tuesday") makes one of you the dispatcher, which is exactly the project-manager trap. Divide by area instead: one of you owns food and drink end to end, the other owns music and photography. Owning an area means holding its vendors, its budget line, and its decisions, not awaiting assignments.

Split by energy, not stereotype: the partner who cares about the playlist owns the band. Areas neither of you wants (transportation exists in every wedding and sparks joy in none) get traded explicitly, like the chore it is.

One source of truth

If it lives in one partner's inbox, it isn't shared.

Most planning friction isn't disagreement; it's information asymmetry. One of you knows the caterer changed the price because the email came to your inbox; the other finds out at dinner, three weeks later, mid-budget-conversation. Nobody did anything wrong, and it still feels like being managed.

The cure is a workspace where everything lands by default: every task with a visible owner, every contract with its payment schedule, every vendor thread readable by both of you. Juno is built as exactly this: one studio for the two of you, as equal peers. There are no roles, no permissions, no admin. Both of you see everything and can edit everything.

  • Tasks carry owners and due dates, so "who has this?" is a glance, not a negotiation.
  • Vendor email forwards to the studio's own address; threads stop living in whichever inbox answered first.
  • Payments record which partner's money funded them, so settling up later is arithmetic, not archaeology.
  • Decisions are logged with who decided and why (see below).

Staying decided

Decide things once.

Couples rarely fight about a choice; they fight about re-making it. "Why did we pick this venue again?" is dangerous because nobody remembers the answer. Juno keeps a decision log: what you chose, which alternatives you weighed, and the rationale, written down at the moment of deciding, when the reasons are still sharp.

June, the AI wedding planner in the studio, quietly reinforces all of this: they read what you both share, address proposals to the studio rather than to one partner's chat, and file new information where both of you will see it. The couple stays the decision-maker; June just makes sure you're both deciding from the same facts.

One studio, two equal planners.

Open your studio, invite your partner from settings, and split the wedding like a team instead of a manager and a client.

Questions

Asked, answered.

How should couples split wedding planning?

By area, not by task: each partner owns whole domains (vendors, budget line, and decisions included), chosen by genuine interest rather than tradition. Agree on the shared anchors together (budget, guest count, venue), trade the areas nobody wants explicitly, and keep everything in one workspace so neither of you becomes the dispatcher.

What if one of us cares way more about the details?

That's normal, and it's fine, as long as it's a chosen division rather than a drift. The detail-loving partner takes the detail-heavy areas; the other holds real areas of their own and shows up reliably for shared decisions. What breaks couples isn't uneven interest, it's invisible effort: a shared workspace makes the work visible, which is most of the cure.

Do both partners get equal access in Juno?

Yes. A studio is shared by two people as equal peers. There's no owner account, no roles, no permission tiers: both of you see every task, contract, thread, and decision, and both can edit everything. That's a deliberate product decision, not a missing feature.

Keep reading