antechway / studio
04 · ProcessBrief → live in three weeks

A short, written process.

Same calendar week, every project. One Linear board, one Slack channel, one Loom thread per review. Two scheduled calls per week, never more.

Loom > Zoom · Linear > Email
Week-by-week

Each row is a week. Each cell is a real artefact you receive, dated and named.

The timeline, in detail.

01 / 04
Week 0

Brief & fixed quote

A 30-minute call, a written scope, and a fixed-price quote inside 24 hours. No hourly rates, no surprises.

Calls1 × 30 min
Loom reviews2 × 10 min
Async messages~ 15 / week
Decisions logged∞, in Linear
Artefacts delivered
  • Written scope (PDF)
  • Fixed-price quote
  • Project timeline
  • Working agreement
02 / 04
Week 1

Design

Three directions as static frames, then one clickable prototype. You decide in Loom reviews, not in meetings.

Calls2 × 30 min
Loom reviews3 × 10 min
Async messages~ 15 / week
Decisions logged∞, in Linear
Artefacts delivered
  • 3 design directions
  • Figma prototype
  • Component library v0
  • Copy outline
03 / 04
Week 2

Build

We build on a staging URL; you see daily builds. Copy is migrated to the CMS in parallel across the two launch languages.

Calls2 × 30 min
Loom reviews2 × 10 min
Async messages~ 15 / week
Decisions logged∞, in Linear
Artefacts delivered
  • Staging URL, day one
  • Daily build digest
  • CMS with editor access
  • Performance baseline
04 / 04
Week 3

Launch & handover

Performance pass, training, DNS cutover. 30 days of post-launch support included, retainer optional.

Calls2 × 30 min
Loom reviews2 × 10 min
Async messages~ 15 / week
Decisions logged∞, in Linear
Artefacts delivered
  • Lighthouse report
  • Editor training video
  • DNS cutover plan
  • 30-day support
Visual timeline

Drawn as you would draw a minimalist timetable: lanes, ticks, no ornament.

The same three weeks, drawn.

Week 0Week 1Week 2Week 3
Discovery
Design
Copy & i18n
Build
QA & perf.
Training
Launch

The bars overlap on purpose. Design and copy do not happen in tidy sequence — they negotiate. We schedule the negotiations.

Principles

Four sentences, on the studio wall. We violate them roughly once a year.

Four principles, on paper.

  1. 01 / 04

    One number

    A written, fixed price before any work begins. The number on the proposal is the number on the invoice — for the first year and every renewal after.

  2. 02 / 04

    One language at a time

    We design and build the primary language first, then port to the second with the same care. No machine translation. Ever.

  3. 03 / 04

    One source of truth

    One CMS, one component library, one analytics tool. If a tool has to be explained twice, it leaves the project.

  4. 04 / 04

    No dark patterns

    No fake scarcity, no countdown timers, no consent dialogs designed to be clicked the wrong way. Your visitors are not the enemy.

Working agreement

A list of how we work, attached as page two of every quote. It changes about once a year.

The studio working agreement.

  • 01One Slack channel, one Linear board, one Loom thread per review
  • 02Two scheduled calls per week, never more
  • 03Asynchronous-first; everything important written down
  • 04Two senior people on every project, named on day one
  • 05Source code yours from week one, MIT-licensed where possible
  • 06Documentation as a deliverable, not an afterthought
  • 07Daily build digest by email at 18:00 CET
  • 08No surprise invoices, ever
  • 09No after-hours pings unless something is actually on fire
  • 10You own the domain, the analytics, the content
  • 11We say no to scope creep, in writing, with alternatives
  • 12A retrospective on launch day, archived for both of us
Who does what

A lightweight RACI matrix — annotated in plain words. Pinned to the inside of every proposal.

Who does what.

TaskOwnerNotes
Provide brand assetsClientStudio assist
Write copy (DE)Studio drafts, client editsEditorial
Translate to FR/ENStudio (human)Native speaker
Choose photographyClientStudio direct
Stock photo curationNever
Domain registrationStudioRenews yearly
DNS cutoverStudioClient approves
Cookie/consent bannerStudioCompliance default
Analytics setupStudioGoogle Analytics + Search Console
Access handoverStudioShared whenever you ask
Year-2 small editsStudioSubscription
Year-2 new featureStudio quotesAdd-on
Tools we run

The tools we use during the build, and what happens to your access on launch day.

Tools, in plain words.

01
Figma
Design files, prototypes, hand-off
Free reader access for client
02
Linear
Project board, issues, decisions
You get an invited seat
03
Loom
Async reviews instead of meetings
Three minutes, watched at 1.5×
04
Slack Connect
Shared channel during build
Closed on day 30
05
Notion
Docs, retros, working agreement
Exported as PDF on launch
06
GitHub
Source, CI, preview deploys
Repo transferred to your org if you want
07
Vercel
Edge runtime, previews
Owned by your account on launch
08
Google Analytics
Traffic & conversion data
Set up on every build, access on request
Next step

Two paragraphs, one written quote, twenty-four hours.

Tell us about the project in plain words. You will get a fixed-price quote — or a polite, fast no — within one working day.

Discuss your project