Three examples, on purpose at different stages. One we’re about to test, one we could choose to do, one we’re just curious about.
TESTINGPilot 01 — Small Site + Photography
A real client, a small site, new photography. The client relationship sits with Lemon Juice. You’d be part of the conversation, and paid for your part.
What it tests
- Shared client intake
- Two research lenses on one client
- Strategy, together
- Whether a custom/static site is the right fit
- Photography
- The client owning and keeping their site
- How the work and the money split between us
ANNA
- Shared client conversation
- Search / SEO
- Visitor journey
- Content and site thinking
- Squarespace / technical perspective where useful
JAY
- Design research
- Creative direction
- Photography
- Design
- Custom/static build
- Deployment
- Limited shop integration, as scoped
- Technology
- Custom/static site · portable site ZIP · Netlify. PROPOSED FOR CLIENT REVIEW. The client hasn’t decided.
- Anna compensation
- Already discussed. Confirm scope and rate Friday.
Kept anonymous here. A pilot, not a pricing precedent.
OPENPossible Pilot 02 — From a Distant Star
My greeting card project, planned for November 2026. It lives on Squarespace, and it’s staying there.
I lead the concept, the artwork, the creative direction, the visual system, and the overall site. The part I need help with is the shop. I haven’t built the commerce side of a Squarespace site before, and I’d rather do it properly with someone who has.
This isn’t a someday idea anymore. It’s real, it’s coming up, and I want to figure out Friday whether there’s a useful part of it for you to take on.
Where you might fit
- Shop setup
- Product setup
- Search / SEO
- Visitor journey
- Squarespace technical implementation
- Squarespace tools + integrations, where useful
The shop, not the whole business around it.
For Friday
Is this a project you’d want to take on with me? If so, which part would you want to own, what would you need from me, and how would you normally scope and price it?
Compensation: Open. Let’s start from how you’d normally price it.
Possible Pilot 02 in the working room ↗ (opens in new tab)
RESEARCH QUESTIONExperiment 03 — One Source, Several Surfaces
Restaurant menu + e-paper publishing
The idea from my email. It’s the most experimental of the three, and not an offer.
A restaurant changes the same things over and over: menu items, prices, specials, what’s sold out, hours, events. Right now that often means changing them in several places, one at a time.
The question: could there be one simple place to keep that information, and could it produce the different things the restaurant actually needs?
ONE SOURCE OF INFORMATION
↓
Website · Phone / QR · Print · E-paper display · Specials + announcements
None of these are connected today. Part of the experiment is finding out which connections would actually help, and which would just be one more thing to maintain.
It’s your question, really: how does this business actually run, and what would make it easier? Just pointed at one small, recurring headache. It’s also a way to find out whether there’s more between us than you doing Squarespace and me doing design.
For Friday
Where have you seen clients keeping the same information in several places? Would a small structured layer actually make their lives easier, or just give them another thing to update?