Syntax Space Studio

Studio

How we work


Six stages, each with an artefact the partner can hold. Onboarding the next partner touches content and data, never code.1

  1. Lead

    Every engagement starts as a lead in the studio's backoffice, with its research and its design directions kept beside it.1

  2. Proposal

    A priced document, prepared for one partner and served behind an access code. Every claim in it traces to a source, and the sources are listed inside the document.13

  3. Three directions

    Three working sites, not three pictures, so the choice is made on real pages at real density. Where a partner's own data does not exist yet, sample content stands in — and says so on the page, so that real and sample are never mistaken for each other.23

  4. Gated review

    The directions are reviewed on a gated host, with one reviewer code per partner and a separate one for the priced proposal, so the wider team can review the designs without seeing the price. The partner picks one and the decision goes on the record.2

  5. Build

    The winning direction's repository becomes the partner's site. Nothing is load-bearing on JavaScript, nothing loads from a third party, and every figure on a page is read from a dated source file rather than typed in.34

  6. Portal

    The partner's own door: proposals, invoices and the engagement's record, behind their own sign-in, which they keep.1

What we do not do

The same rules apply to this site. It is the first thing we built under them for ourselves.

Sources

  1. Syntax Space Studio — backoffice/PLAN.md §1 (the backoffice plan of record, internal). Accessed September 2026.
  2. Syntax Space Studio — docs/architecture — the mocks-portal record, the first instance of the per-partner gated review (internal). Accessed September 2026.
  3. Syntax Space Studio — CLAUDE.md (the studio’s working rules, internal). Accessed September 2026.
  4. Syntax Space Studio — docs/architecture/interface-doctrine.md (internal). Accessed September 2026.
  5. Syntax Space Studio — docs/architecture/www-public-site-plan.md (this site’s plan of record, internal). Accessed September 2026.