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.

  • Your client gets only the rounds you publish to them
  • Only the approver on record can approve, and never from your own session
  • The approval pins the exact HTML by its sha256
Join the waitlistWalk through a round

The round, step by step

who acts, and the record behind each step

  1. InviteYouinvites
  2. Your client reviews the roundYour clientreview_rounds
  3. Comments and votesYour clientcommentsvotes
  4. A recommendation becomes a steerYoureview.steer
  5. ApprovalYour client’s approverapprovals

One review round, told step by step below.

Two sides of one round

YouWhat you do

  • Invite your client with a single‑use token
  • Publish a round
  • Read the feedback and steer

Your clientWhat your client does

  • Review what you publish
  • Comment, vote and recommend changes
  • Approve one look

Your own session can never approve, and your client never gets a round you have not published.

  1. Step 1: inviteYou

    Invite your client with a single‑use token

    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
    Next: the round

    Invite

    single-use, one workspace, one client

    sample record
    Email
    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
    The shape of an invite: what Nucleus stores, and the token it shows you once. Every value here is illustrative.
  2. Step 2: reviewYour client

    Your client gets only the rounds you publish

    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
    Next: feedback

    Round 1

    as published: name, thesis and brand risks

    sample directions
    • 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 roundnot found
    Sample directions from the offline demo runner. A round shows each direction’s name, thesis and brand risks.
  3. Step 3: feedbackYour client

    They comment, vote, and recommend a change

    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
    Next: the steer

    demo-high-contrast-breathe-centered-stack-9cc4

    round 1 · feedback

    sample record
    • votesup1down0yours:up
    • comment

      The contrast reads well on my phone.

    • recommendationopen

      Make the headline larger. Keep the palette.

    The shape of feedback as Nucleus stores it. Every value here is illustrative.
  4. Step 4: steerYou

    You turn their feedback into a steer

    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
    Next: approval

    Steer, then publish

    sample record

    Recommendation, round 1

    • recommendationopen

      “Make the headline larger. Keep the palette.”

    Steer

    Parent
    demo-high-contrast-breathe-centered-stack-9cc4
    Child
    high-contrast-larger-headline
    Note
    Make the headline larger. Keep the palette.
    • jobqueued
    • jobsucceeded

    Round 2

    published
    • demo-analogous-rotate-split-hero-14d3
    • demo-high-contrast-breathe-centered-stack-9cc4
    • demo-pastel-drift-bento-84dd
    • high-contrast-larger-headlinefork
    A steer queues a job and forks the direction. Publishing snapshots every current direction into the next round.
  5. Step 5: approvalYour client’s approver

    The approver signs off one look, and it is recorded

    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
    Join the waitlist

    Approval

    append-only, one per direction per round

    sample record
    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
    The shape of an approval as Nucleus stores it. Every value here is illustrative. The refusals are the API’s own codes.
Plans

Where freelancers fit

Free and Studio, with what each is planned to include. Prices at launch.

Free

Prices at launch
  • Upload a design you already have
  • The review flow, with one invited approver
  • A recorded sign-off
  • The gates that apply to the upload
Join the waitlist
For the freelancer with clients

Studio

Prices at launch
  • A higher allowance than Builder
  • Several brands
  • Several client approvers per project
Join the waitlist
See the plans

What each plan includes may change before launch.

Today a client has one approver at a time. Several per project is planned for Studio.

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?
Not in a round, which gives them each direction’s name, thesis and brand risks. A design’s preview is a short-lived signed link that your session can make and theirs cannot, so your client sees a design when you show it. 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. Comments, votes and approvals stay in your workspace, and nothing trains on them.
Is it open yet?
Not yet. Join the waitlist to hear when Nucleus opens.

From the first round to a sign‑off on record

Nucleus is not open yet.

Join the waitlist