What Happens in the First Week After You Hire Us (Step by Step, No Jargon)

If you've been burned before, "we'll get started" sounds like nothing. So we treat week one as proof of process — not just proof of design talent.

This is the same onboarding flow we use for rescue handoffs, new builds, and MVP rebuilds. Details shift by project size; the rhythm doesn't.

Before day one: what we need from you

You won't get a homework dump. We ask for four things:

1. One sentence goal — "More booking calls from Google" beats "modern website"
2. Access you already have — domain registrar, old site login, brand files, copy docs
3. One decision-maker — feedback from six people slows everything; one voice plus optional reviewers
4. Examples you like (optional) — screenshots of sites whose vibe matches yours, not copy-paste targets

If you're coming from a failed project, send whatever you have — even a broken link. We've started audits from less.

First doubt we hear: "What if I don't have perfect content ready?"

Answer: placeholders are fine. Silence isn't. We'll use structured drafts until your final copy is ready.

Day one: kickoff and alignment

60–90 minute call (or async if time zones fight us). Plain-language agenda:

• What success looks like in 30 / 60 / 90 days
• Who your customer is and what they should do on the site
• Pages and features in scope — and explicitly out of scope
• Timeline with named milestones (not "soon")
• How you'll pay — milestone-based, tied to deliverables

You leave with:

• A written scope summary (email or shared doc)
• A communication channel — WhatsApp, Slack, or email, your preference
• Named contacts on both sides

No code yet. On purpose. Misaligned projects move fast in the wrong direction.

Days two–three: structure and access

This is the unglamorous work clients only appreciate later:

• Domain, hosting, repo, or CMS set up in your accounts
• Project board with tasks you can actually read
• Sitemap / user flow — boxes and arrows, not Figma polish
• Technical check if we're rescuing: what's salvageable, what's theater

If we're rebuilding after no-code or a cheap gig, day two often includes a rescue audit — what's broken, what data exports cleanly, what must be recreated.

You see:

• Access confirmations (you hold the keys)
• A milestone calendar for the next 2–4 weeks
• First draft of page structure — even rough wireframes

Days four–five: first visible progress

Now design or build starts — depends on project type:

• Marketing site — homepage direction or style tile (fonts, colors, hero layout)
• Web app / MVP — core user path scaffolded (login → main action → confirmation)
• Rescue — critical bug fixes or staging environment so you can see movement

We share a staging link when possible. You comment in plain English: "button feels hidden," "this copy is wrong," "too corporate." You don't need to say "reduce padding 16px."

Internal rule: something tangible by day five unless blocked by missing access — and we say that out loud immediately, not on day twelve.

End of week one: what you should have in hand

Checklist we hold ourselves to:

• Written scope and milestone plan
• You own domain / hosting / repo access
• Communication rhythm agreed (e.g., async update every 48 hours)
• Visible progress link or design direction
• List of what we need from you next — specific, short, dated
• No surprise invoices or "that wasn't included"

If any box is unchecked, that's on us to fix in week two — not on you to chase.

What we deliberately don't do (and why)

• Vanish for two weeks to "focus" — silence reads as scam after a bad hire
• Build the whole thing before showing you — misalignment gets expensive
• Lock you out of accounts — if you can't leave, we failed
• Drown you in technical terms — you shouldn't need a glossary to approve work

Strategy isn't overhead. For non-technical owners, visibility is the product as much as the website.

Your role as a non-technical owner

You're not supposed to become a developer. Your jobs:

• Decide — priorities, tradeoffs, approvals within 24–48 hours when possible
• Clarify — answer "who is this for?" better than we can guess
• Introduce risk early — legal requirements, launch dates, partner integrations

Best clients say: "I don't know how, but I know what outcome I need." That's enough.

How updates work — no chasing required

Default rhythm:

• Async updates every 1–2 business days — short, bullet format
• Weekly sync optional — 15–30 minutes unless you want more
• Blockers flagged same day — missing logo, delayed copy, access not granted

You should never wonder "is anything happening?" If you do, tell us — that breaks the process and we fix it.

---

Hiring help should feel like relief, not a second job. Week one is designed to prove we're organized, you stay in control, and the project moves in English — not engineering slang.

If that's the bar you're holding every agency to, good. It's the bar we hold ourselves to as well.