GALLAXI.

[PROCESS] — HOW I WORK

Plan the work, work the plan.

Every engagement runs through the same four stages. The names are unsurprising — the rigour is in what each one delivers, when, and how it’s signed off. No surprises at handoff, no scope creep at week 8, no “we’ll figure it out”.

  1. 01

    Discover.

    1 — 2 weeks

    Frame the problem before drawing it.

    Every project starts with a 1-page brief that answers four questions: what problem we're solving, who it's for, what success looks like in six months, and what we can afford NOT to do. Signed by both sides before design starts.

    [deliverables]

    • Strategy brief (1 page)
    • Stakeholder interviews (3 — 8)
    • Constraints map
    • Success metrics agreed in writing
  2. 02

    Design.

    2 — 5 weeks

    Smallest possible system that solves it.

    Wireframes and visual systems built around one rule: the next 10 deliverables must be able to lean on these decisions without breaking. Iteration in Figma, weekly reviews with the client, no surprises at handoff.

    [deliverables]

    • Wireframes (low-fi → hi-fi)
    • Design system in Figma
    • Typography + colour tokens
    • Component library with states
    • Reviewed against accessibility (AA min.)
  3. 03

    Build.

    2 — 6 weeks

    Production code or production handoff — same care.

    If I'm building (Astro, WordPress, Webflow), the code is mine and the deployment is mine. If a dev team is building, my Figma includes redlines, motion specs, and a Loom walkthrough so they can ship without guessing.

    [deliverables]

    • Production code (Astro / WordPress / Webflow)
    • Or: dev-ready Figma with redlines + motion specs
    • SEO baseline (sitemap, structured data, meta)
    • Lighthouse audit before launch
  4. 04

    Ship.

    1 — 2 days

    Deploy, hand over, and stick around.

    Live deploy with a 14-day no-questions post-launch window for small fixes. Final files in your drive with a walkthrough video. Closing invoice the same day. Retainer optional, not pushed.

    [deliverables]

    • Live deployment
    • 14-day post-launch fix window
    • Final files + walkthrough video
    • Closing invoice + retainer option

[PRINCIPLES] — HOW I THINK

Four rules
I don't break.

RIGOUR

Every decision is documented and re-checkable. No "trust me" moments. If I can't explain the why, the why probably isn't there yet.

RESTRAINT

The smallest system that solves the problem beats the most thorough one. Optionality is a tax — paid by whoever maintains the work later.

CONTINUITY

Same person from kickoff through deploy. No junior handoff, no agency project manager between us. Slower, but the work compounds.

HONESTY

If a project isn't a fit, I tell you on the first call and recommend someone else. If a scope is wrong mid-project, we re-cut it together. No padded hours, no quiet drift.

[06] — GET IN TOUCH

New projects.
Open inquiries.

Send a message →

Response within 24 hours · Available across the EU · EN · HR · DE