How engagements run

Predictable delivery, end to end.

No surprises in week six. Weekly demos, written updates, a milestone structure where the next step is always clear, and a partnership model that keeps working after launch.

  1. 01

    Discovery & scoping

    A short call (or a written exchange — whichever you prefer) to understand the problem in your words. You leave knowing what we'd build, why, and roughly what it costs. We leave with enough to write a real scope.

    • What you'll get from us: written scope, fixed quote, timeline, named milestones
    • What we need from you: project context, success metrics, current site / app assets
    • Typical timeframe: 2–5 business days from first message to quote
  2. 02

    Design & prototyping

    Designs go into Figma first, then a Webflow staging site so you can see the real thing on a real screen before any code is locked in. Reviews happen on Loom (async) or a short weekly call.

    • Tools: Figma, Webflow staging, Loom, Notion
    • Cadence: weekly demo, written update Friday
    • You always know what's next and what we need from you
  3. 03

    Build & milestones

    Engineering structure applied to delivery. Each milestone has a clear definition of done, a demo, and a checkpoint. Scope changes get costed before they're built — never after.

    • Milestones costed in the original quote — no hourly creep
    • QA at every milestone, not just before launch
    • Staging site live from day one — always something to show
  4. 04

    Launch

    Pre-launch checklist covers performance, accessibility, SEO, analytics, redirects and rollback plan. Launch happens during a quiet window — your team is briefed, your accounts are yours, your DNS is documented.

    • Core Web Vitals verified green on real devices
    • 301 redirects mapped from any legacy URLs
    • Analytics, Search Console and consent banner tested live
  5. 05

    Post-launch & partnership

    Launch isn't the end. Most clients move into a retained partnership — managed hosting, monthly improvement hours, priority support, and a regular cadence for shipping small improvements that compound over time.

    • Retained partnership: monthly improvement allocation + priority support
    • Ad-hoc work: faster turnaround for retained clients, fair quote for everyone else
    • Real handover always: you own the accounts, you can leave any time
Tools & communication

Async-first, with the right tools.

Most updates happen in writing — short, scannable, in one place you can find them again. Loom for visual walkthroughs (faster than a meeting, watchable in your time zone). Notion for scope, decisions and the running project log. Slack or email for day-to-day. Calls are reserved for decisions that need a real conversation.

You won't be chased to join standups. The team won't be on your calendar daily. The trade-off: a written update every Friday and a working demo every week. Most clients say it's the calmest project they've run.

Time zones

AEST base. Overlap with everyone who matters.

Home base is Australian Eastern Standard Time (UTC+10). Working hours are Monday–Friday, 8:30am–4:00pm AEST.

Overlap windows: NZ all day, Asia most of the day, UK / Europe early morning AEST (late afternoon European time), US East late evening AEST (morning ET), US West the same.

For most international clients, the async-first workflow means time zones are a logistical detail, not a blocker. Full breakdown on International clients.

Ready when you are

Start the conversation. Get a real answer.

Tell us the problem. You'll get a clear scope, realistic timeline and fixed quote inside 48 hours.