Skip to content
Lisbon · New York Founded 2017

How a project moves.

A single, integrated method from the first conversation to a live product — run by the founding partners, paced to an 11-week average launch, and signed off in writing every two weeks.

Start a project Read how we work
§ The Method

Five chapters, eleven weeks, one accountable team.

Every Mewan engagement runs through the same five chapters. The deliverables and decision points are written down in advance so a founder can mentally place their own timeline inside our method — without scheduling a sales call to find out what happens next.

  1. 01

    Discovery & Frame

    Week 1

    A two-day working session with the founders and one partner from each discipline in the room. We leave with a one-page brief, a measurable definition of success, and a fixed price for the build.

    Deliverable
    Signed brief & fixed-price proposal
    Decision gate
    Approve scope, kickoff the build
  2. 02

    Brand Strategy & Identity

    Weeks 2 – 3

    Positioning, naming, voice, and visual identity. You walk away with a brand system that reads on a business card and on a billboard, not a moodboard that dies in a Notion page.

    Deliverable
    Brand book, logo suite, type & colour system
    Decision gate
    Lock the system before pixels go to engineering
  3. 03

    Product Design

    Weeks 4 – 6

    Information architecture, interaction design, and a clickable prototype tested against the brief. The handoff to engineering is a Figma file plus a written spec — not a Loom and a wish.

    Deliverable
    Prototype, design system, engineering spec
    Decision gate
    Sign the prototype before a line of code is written
  4. 04

    Engineering & Integration

    Weeks 7 – 9

    Senior front-end and back-end engineers build against the prototype in two-week sprints. Every sprint ends with a working demo on a staging URL and a written status note — never a slide deck.

    Deliverable
    Staging build, sprint demo, written status note
    Decision gate
    Approve each two-week sprint before the next begins
  5. 05

    Launch & Handover

    Weeks 10 – 11

    Performance pass, accessibility audit, analytics, a 30-minute team training session, and a written handover document your in-house team can actually read on a Sunday night.

    Deliverable
    Live product, handover doc, training recording
    Decision gate
    Sign off the launch, schedule the 30-day review
§ The Promise

Eleven weeks average live. Fourteen days to walk away.

Two questions decide whether a Series-A CMO books a studio. How long until it ships, and what happens if the first sprint misses the mark. The answer to both is written into every contract we sign.

11

Weeks from kickoff to public launch

Measured across 140+ shipped launches since 2017. Slower for platform rebuilds, faster for focused MVPs. Never the industry-standard six months.

14

Days to walk away, in writing

If the first two-week sprint does not earn your trust, you stop work and owe nothing for the sprint — no negotiation, no exit fee, no awkward email.

Fixed-price engagements. 92% of new projects come from client referrals or repeat engagements. Net Promoter Score of 78 across the last 40 client engagements.

§ What we ask of the founder

About seven hours of your time, total.

That is the honest answer to the question every CEO asks us before signing: roughly two hours in the discovery week, one hour at the end of each two-week sprint, and ninety minutes at launch. Everything else happens without you — and we send a written status note every Friday so you never have to ask what is going on.

You will never be sold a project that quietly costs you a day a week. The reason our founders refer us is that we respect their calendar as if it were our own.

§ The Rhythm

Four sprints. One working session per sprint. Zero surprises.

An 11-week build unfolds across four two-week sprints. Each sprint has a single working session with the founders, a written demo, and a written decision gate. No opaque timelines, no "we'll get back to you next week".

Sprint 01 Weeks 7 – 8

Foundation

Design tokens, component library, routing, auth, the parts of the product that are expensive to change later.

Gate · Approve foundation
Sprint 02 Weeks 9 – 10

Core flows

The two or three journeys that pay for the product, built against the locked prototype.

Gate · Approve core flows
Sprint 03 Weeks 11 – 12

Edges & integrations

Payments, analytics, third-party integrations, the empty states, the 404s, the parts nobody sketches.

Gate · Approve edge work
Sprint 04 Weeks 13 – 14

Launch & handover

Performance, accessibility, the training recording, and a written document your team can read without us in the room.

Gate · Sign off launch
Overhead view of a working session table at the Mewan studio in Lisbon, with printed wireframes and a prototype on screen.
Working session, Rua da Madalena, Lisbon. Photo: Mewan Studio.
§ Begin

If the method fits, the next step is a thirty-minute call with one of the founding partners.

No pitch deck. No junior account manager. Just a conversation about what you are building and whether our five chapters are the right shape for it.

Start a project See the work

[email protected] · +1 (212) 555-0184 · Lisbon & New York