From brief to launch review, day by day.

Engagement

Thirteen milestones inside a Site engagement. What happens on each day, what you do, what the studio does, and a few real-shape deliverable previews along the way.

Days below are the plan, not the contract. Research turns up something worth chasing, a review lands late, a copy pass needs a second round: real projects hit real turbulence. When a date slips, you hear about it in the same reply that flags it. Every effort goes into staying on the calendar.

Site01 / 13

Day 0Intake

Brief arrives.

The brief lands in the studio inbox with what you need, when you need it by, and the shape of the business it is for. Two paragraphs is enough. From here the studio has one working day to respond.

Two-paragraph brief. Business, buyer, what you have now, what you want to launch. Sent to alfonso@barreiro.com or through the contact form.

You

Send two paragraphs about the business, the buyer, and the launch target.
Pick a package (Site or Site+) or say you are not sure and want a recommendation.

Studio

Confirm receipt within a few hours.
Read the brief, check calendar for the next open slot.

Day 1 · MonIntake

Scoping response, contract, deposit.

You get a written scope back within one working day. It names the package that fits, the timeline, deliverables, and any research questions before we kick off. Contract and deposit invoice ride along; work starts the following Monday.

Scoping response

Ready to countersign

Package: Site — $3,000, 2 weeks, 2 revisions
Kickoff: Monday, week of Sep 22
Ship target: Friday, Oct 3
Research questions: 3 · attached separately
Deliverables: Home + services + contact + launch review

You

Review the scoping doc, ask for changes if needed.
Sign the contract, pay the deposit (50% up front).

Studio

Send the written scope + contract + invoice.
Reserve the two-week window on the calendar.

Day 5 · FriIntake

Countersigned, deposit cleared.

Contract countersigned end of week. Deposit clears over the weekend. Studio prepares the research doc and Figma workspace for Monday's kickoff.

You

Return the countersigned contract.
Answer the three research questions in plain text or a shared doc.

Studio

Set up the Figma workspace.
Draft the research doc: product, buyer, competitors, search-intent.

Day 8 · MonDesign

Kickoff. Research review, together.

Thirty-minute call to walk through the research doc and lock the design brief. Design system starts that afternoon. From here forward the work happens async in Figma unless something needs a call.

You

Kickoff call (30 min).
Confirm the design brief and any final questions.

Studio

Walk through the research doc.
Start the design system: type scale, palette, spacing tokens.

Day 9 · TueDesign

Design system + moodboard.

By end of day two the type scale, palette, and moodboard are in Figma. This is the foundation every page in the build gets composed against. Comments happen in Figma, not on a call.

Design system · Figma

Ink

#0F172A

Surface

#F5F7FA

Accent

#48ADCF

Line

#E2E8F0

Display · Fraunces SemiBold56 / 44 / 32

Body · Plus Jakarta Sans17 / 15 / 13

Mono · JetBrains Mono13

You

Open the Figma link.
React with comments on the palette and type scale.

Studio

Ship type scale + color palette + spacing tokens in Figma.
Post a moodboard of three references from adjacent brands.

Day 10 · WedDesign

First page designs land in Figma.

The home page comes first, then services, then contact. All three shipped to Figma end of day. Async comments open through Thursday. Design system feeds every page so revisions cascade cleanly.

figma.com / files / abd-yourbusiness-v1.fig

page

Home

page

Services

page

Contact

system

Type + color

You

Walk through the three pages in Figma.
Leave comments on anything that doesn't argue what the brief said.

Studio

Ship home, services, contact pages in Figma.
Note the design decisions per page in the Figma sidebar.

Day 11 · ThuDesign

Round 1 revisions.

Client comments come in async through Wednesday night. Studio addresses every comment by end of Thursday. Anything that changes the brief itself gets flagged as scope and discussed on a call if needed.

You

Finalize all round-1 comments in Figma by end of day.

Studio

Address every comment; reply-in-thread on each one so nothing gets lost.
Ship revised Figma frames.

Day 12 · FriBuild

Design lock. Next.js build starts.

Design frozen end of week one. Next.js project scaffolded, design system tokens ported to Tailwind, layout skeleton built. No more Figma changes without a scope conversation.

You

Approve the locked design (async in Figma or a short call, your choice).
Start pulling final copy and image assets for Monday.

Studio

Scaffold Next.js project on Vercel.
Port design tokens to Tailwind.
Build the layout skeleton and reusable components.

Day 15 · MonBuild

Content integration.

Home, services, contact all get their real copy and images. Formspree wired for the contact form. Structured data, sitemap, robots.txt shipped alongside. The site starts to look like the site.

You

Send remaining copy and images by end of day.
Confirm form recipient email address.

Studio

Plug in copy and imagery.
Wire Formspree, JSON-LD, sitemap, robots.txt.
Ship first preview URL on Vercel.

Day 16 · TueBuild

QA: accessibility, performance, responsive.

axe DevTools pass on every page. Lighthouse pass at 90+ across the board. Mobile / tablet / desktop layouts checked at real breakpoints. Any surface that fails gets fixed before final review.

You

Open the preview URL, click around on your phone and laptop.
Flag anything that looks wrong at any breakpoint.

Studio

Run axe DevTools + manual keyboard walkthrough.
Fix any Lighthouse regressions.
Verify every layout at 375, 768, 1440.

Day 17 · WedBuild

Final client review.

You get the live preview URL and one working day to walk through it. Comments come in async. Any final polish happens Thursday. This is the last chance for changes before deploy.

You

Walk through the preview end to end.
Send any final polish notes.

Studio

Address final polish notes.
Prepare the production deploy.

Day 19 · FriBuild

Deploy. Repo and Vercel transfer.

Production deploy in the morning. Repo transfers from studio's GitHub to yours. Vercel project transfers from studio's account to yours. By end of day you own everything and the studio has no admin credentials.

vercel deploy — yourbusiness.com

deploying…

You

Accept the GitHub repo transfer.
Accept the Vercel project transfer.

Studio

Push to production.
Transfer the repo + Vercel project.
Send the launch email with all logins and links.

Day 49 · +30Review

Launch review lands.

Thirty days after launch the studio runs the four-tier review on the site as it actually is (not as it was at ship). Twelve to fifteen findings for Site, twenty to twenty-five for Site+, ranked by severity, paired with effort estimates. Delivered as a PDF you can act on without another call.

Launch review · sample PDF

Sample launch review

Strategic3 findings
UX4 findings
Visual4 findings
Technical4 findings

Read the sample →

You

Read the PDF at your pace.
Pick the two or three findings you want to act on first.

Studio

Run Strategic, UX, Visual, Technical passes on the shipped site.
Write the review PDF with severity + effort per finding.
Send the PDF, offer to answer questions async.

Prefer a system view?See the engagement as a map →

Ready to start?

Send the two-paragraph brief. Response within one working day, scoping doc back the same week.

See the packages Start a project →