Launch Plus
In development$1,995paid once
For 1 site
One site, with its whole brand written down
For freelancers
One round, from invite to sign‑off
For freelance designers and developers whose client signs off. Follow one review round: you invite your client, they review and recommend, you steer, and the look they approve is recorded by its hash.
Invite
You
invitesYour client reviews the round
Your client
review_roundsComments and votes
Your client
commentsvotesA recommendation becomes a steer
You
review.steerApproval
Your client’s approver
approvals
Two sides of one round
You
What you do
- Invite your client with a single‑use token
- Publish a round
- Read the feedback and steer
Your client
What your client does
- Review what you publish
- Comment, vote and recommend changes
- Approve one look
- See the project’s activity log and download it as a spreadsheet
- See where each project stands, and what’s waiting on them
Your own session can never approve, and your client never gets a round you have not published.
1
Invite your client with a single‑use token
Step 1: invite · You
Add your client, and record their SOW signatory. Each invite is for one email, bound to your workspace and that client, and it works once. Redeeming it opens a session for that client only.
- Only the sha256 of the invite’s token is stored, never the token
- A used, expired or unknown invite gets the same refusal
- Recording the signatory creates their invite, if they are not one of this client’s users yet
Invite
single-use, one workspace, one client
- Your client’s address (illustrative)
- Client
- One client in your workspace
- Token
- Random, shown to you once
- Stored as
- sha256 of the token
- Use
- once
- Opens
- A session for this client only
2
Your client gets only the rounds you publish
Step 2: review · Your client
Publishing a round snapshots your review’s current directions: each one’s name, thesis and brand risks. A later steer or re-run never changes that snapshot.
- A round exists only once you publish it, so there is no draft to stumble on
- Another client’s round answers not found, never forbidden
- The round keeps each direction’s name, thesis and brand risks as published
Round 1
as published: name, thesis and brand risks
- demo-analogous-rotate-split-hero-14d3
- A stand-in direction built from analogous palette, rotate motion, split-hero layout, for "A home page for a design review app". Brand risks: none
- demo-high-contrast-breathe-centered-stack-9cc4
- A stand-in direction built from high-contrast palette, breathe motion, centered-stack layout, for "A home page for a design review app". Brand risks: none
- demo-pastel-drift-bento-84dd
- A stand-in direction built from pastel palette, drift motion, bento layout, for "A home page for a design review app". Brand risks: none
- another client’s round
- not found
3
They comment, vote, and recommend a change
Step 3: feedback · Your client
On each direction: a thumbs up or down, comments, and recommendations, a kind of comment you can act on. A vote can change until that direction’s look is approved; then its votes lock.
- Comments are escaped, length-limited and rate-limited
- Each person gets the tally and their own vote, never a teammate’s
- A recommendation arrives open, for you to act on
demo-high-contrast-breathe-centered-stack-9cc4
round 1 · feedback
- votes
- up 1 · down 0
- comment
- The contrast reads well on my phone.
- recommendation
- Make the headline larger. Keep the palette. (open)
4
You turn their feedback into a steer
Step 4: steer · You
A model never applies a client’s recommendation by itself. You fork the direction with their wording as the note, the fork runs as a new direction, and you publish the next round.
- A steer forks a direction, it never overwrites one
- Each earlier round keeps its snapshot as it was published
- You decide what to act on
Steer, then publish
Recommendation, round 1
- Parent
- demo-high-contrast-breathe-centered-stack-9cc4
- Child
- high-contrast-larger-headline
- Note
- Make the headline larger. Keep the palette.
- job
- queued → succeeded
- Round 2
- published
5
The approver signs off one look, and it is recorded
Step 5: approval · Your client’s approver
The approver is the person you record as the SOW signatory, or a designee set from one of your client’s accounts instead. They approve one direction of one round. The record pins the exact HTML by its sha256, and nothing can edit it afterward.
- An approval from your own session is refused
- With no approver on record, nobody can approve
- Append-only in the database itself: no update, no delete
- One approval per direction per round; a second is refused
Approval
append-only, one per direction per round
- Approved by
- Your client’s signatory (illustrative)
- Basis
- signatory
- When
- 2026-10-06 14:32 UTC
- Round
- 2
- Direction
- high-contrast-larger-headline
- sha256
- 651695435153d6ff68f2a33d44e18be5c665e4bc1cf9f57e461b2889ae44a277
- Note
- This one. Keep the type as it is.
- What it refuses
- ADMIN_MAY_NOT_APPROVEyour session can never approve
- NO_APPROVERnobody on record, nobody approves
- LOOK_APPROVEDalready approved, never edited
Plans
Where freelancers fit
Launch Plus is one client's site with its whole brand, paid once. Agency is 5 sites, under your own brand.
Agency
In development$7,495paid once
For 5 sites
Five client sites, under your own brand
Nucleus is not open yet. These are its prices.
Today a client has one approver at a time.
Questions
Straight answers
How does my client sign in?
With an invite: a single-use token issued for their email, for one client in your workspace. Nucleus shows the token to you once, and you pass it on. Redeeming it opens a session for that client only. Your client has no password to keep.
Does my client see the designs?
Yes, through a round you publish to them. The round gives them each direction’s name, thesis and brand risks, and their session can open a short-lived signed preview of a direction it lists, as that direction is now. Once you deliver a site to them, it can also open that site’s delivered design the same way, to point at a part of it, and each change made to it, before and after. When a project is complete, they can download its handoff package, which holds screenshots of the approved look and the theme built from it. Nothing else. Their approval pins that direction’s HTML as it stands when they approve.
Can I approve on my client’s behalf?
Not from your own session: an approval from it is refused. Only the approver on record can approve a look: the person you record as the SOW signatory, or a designee set from one of your client’s accounts instead.
Who chooses the designee?
It is set from one of your client’s accounts, never from your own session. Every change is recorded, and your client can read the history.
Is the approval an e‑signature?
It is an approval record: which account approved, on what basis, when, which round and direction, and the exact HTML by its sha256. We call it a sign-off.
Is my client’s feedback used for training?
No. Nothing trains on them. Comments and votes stay in your workspace. Approvals and their notes stay there too, and they tailor only that client’s own next designs.
Is it open yet?
Not yet. Join the waitlist to hear when Nucleus opens.