ANNA × LEMON JUICEA × LJ

SHARED DESK · TEST

Traffic, projects, and what happens next.

A working surface for Anna × Lemon Juice: where each thing is, whose turn it is, what happens next. Buttons work. Checkmarks are temporary. Notion keeps the record.

Updated Sept. 27 · proposals, not agreements · test dashboard, not a client portal

How a new job gets sorted.

First decide where the work naturally belongs. Then name the project type. Each route is one model worth testing, not a fixed package or an agreed role.

Who is closest to the problem?

ROUTE

One model worth testing · design week → build week

We talked this through on Sept. 25: Jay could lead a design week, Anna a build week, with both on the Monday client calls. Not agreed yet. Worth testing on a real project.

LEADShared

NEXTBefore quoting: scope, platform, fee, deliverables, one decision maker.

Whose turn is it?

Stage, whose turn, next action, and where to keep working. Color means who’s leading right now, never who owns it; the label always says it in words.

PILOT 01 · STRATEGYWITH: BOTH

Natalie / Mud Hut Pottery

Small site + photography. A lightweight non-Squarespace site is the experiment; platform still open. Natalie already uses Square in person, so a tiny Square-linked shop is worth testing.

NEXT → Jay + Anna: settle Anna’s role (strategy only, a production day, or more), fee, platform, deliverables and revision limit before quoting. Wed Sep 30 · 4:30 PM.

PILOT 02 · PROPOSEDWITH: JAY

Linda / Brooklyn Foto

Squarespace, unless Linda gives a reason not to. Proposal: a Shared Build Day where Anna builds and Jay learns alongside. Linda hasn’t approved another collaborator yet.

NEXT → Jay: finish logo/type/color and get the photography substantially ready. Then talk with Anna about introducing her and a possible Build Day.

WORTH TESTINGWITH: JAY

From a Distant Star

Jay’s greeting-card shop on Squarespace, November window. Anna suggested a focused workday with a few real sample products. Possible pay experiment, only if Anna finds it interesting.

NEXT → Jay: get a few real sample products and files ready before asking Anna for a shop workday.

LATER · IDEAWAITING

Restaurant / menu system

One-page restaurant site plus separately scoped menu design, print/digital output and possible e-paper updates. Anna flagged it as promising.

NEXT → Later: one believable demo, then decide deliverables and who handles ongoing menu updates.

Opportunity Watch is a habit, not a project: both of us noticing where the other’s expertise could improve or expand something.

Next things to do.

These checks are a prototype only. They reset when the page reloads; Notion is still the shared record.

ANNA (from Sept. 25)

JAY

BOTH (proposed)

UPDATE SHARED RECORD IN NOTION ↗

Project + editorial timing in one place.

Natalie / Mud Hut Pottery

Strategy conversation. Confirm scope and Anna's level of involvement before promising a production week.

Linda / possible Shared Build Day

After Jay’s brand layer and photo prep, and only once Linda has agreed to another collaborator.

From a Distant Star

Current launch window. Use a few real products to test commerce workflow and responsibilities.

Restaurant / menu demo

Prototype one clear offer before turning it into a repeatable service.

Jump back into the actual work.

The Desk is the glance. Notion is the working memory.

This page is intentionally lightweight. Meeting notes, project records and open questions stay in Notion, our shared working memory. It isn’t the client website, the design tool or the answer to every problem. The goal is to make the next action visible without duplicating the whole system.