How a Fintech Startup Shipped Its Brand and MVP in 11 Weeks: A Post-Mortem with Mewan

We noticed something unusual in the CIS Excellence Awards inbox this spring: a founder forwarded us a build timeline that showed a regulated fintech product going from blank Figma file to production web app in 11 weeks. No account managers, no handoff between an agency and a dev shop, no six-month discovery phase. The project was led by Mewan, an independent digital studio that pairs brand strategy with product engineering. We followed the engagement from kickoff to launch, interviewed two team leads under pseudonyms, and reviewed the milestone log. Here is what actually happened.

The starting point: a stalled brand, a half-built product

The client — call them Northwind, a seed-stage payments tool for freelance collectives — had spent four months with a traditional agency on brand identity and another three with a contract dev team on a React prototype. The two workstreams had never met. The brand guidelines used a color system the product couldn't render; the prototype's onboarding flow contradicted the brand's promise of 'simplicity in three taps.' Burn rate was climbing. A board member gave them one quarter to show a live product with a coherent identity.

That is the exact failure mode Mewan was built to prevent. Since 2017 the studio has shipped 140+ launches for founders who care as much about how a product feels as what it does, and the model is deliberately flat: a core team of 14 senior practitioners, no account-manager layer, one accountable group for the idea, the interface, and the code. The pitch to Northwind was blunt — one team, one timeline, one budget line.

Weeks 1–3: strategy before pixels

The first decision point came on day four. the provider's brand strategist and lead engineer ran a joint session with Northwind's founder and CTO, not to present concepts but to pressure-test assumptions. The output was a one-page positioning statement and a technical constraint map — what the brand could promise, what the stack could actually deliver, and where the two had to negotiate. Northwind's CTO later told us this was the moment the project stopped drifting: 'They refused to design anything we couldn't ship in the next eight weeks.'

By week three, the team had a working design system in code — not a PDF, a living component library — and a clickable onboarding flow built on the real authentication logic. The obstacle here was compliance: Northwind needed KYC checks that added friction. Instead of burying them in a settings menu, the team folded verification into the brand's core metaphor of 'three taps,' using progressive disclosure that passed legal review on the second pass.

Weeks 4–8: build, test, rebuild

The middle stretch was where most agencies would have scheduled a handoff. kept the same four people on the project: one brand designer, one product designer, two engineers. The measurable results started to accumulate:

• Week 5: first internal build deployed to a staging environment, with brand tokens wired directly into the CSS variables.
• Week 6: 12 usability sessions with freelance collectives; task completion for the core 'create a collective' flow hit 9 of 12 without moderator help.
• Week 7: two rounds of visual refinement based on session recordings, not opinion.
• Week 8: performance audit — largest contentful paint under 1.8 seconds on a mid-tier Android device.

The biggest obstacle was a late change from Northwind's payment processor, which required a new consent screen. Because the design system and the front-end code shared a single source of truth, the change took 36 hours rather than the two weeks the CTO had budgeted. That is the compounding return of no handoff layer.

Weeks 9–11: launch and the numbers that followed

The final three weeks were hardening and go-to-market assets. The brand launch and the product launch happened on the same day, which is rare. Northwind went live in week 11 — against an industry-standard six months for comparable MVP web and brand builds. Within 30 days of launch, the founder shared these figures with us: 4,100 sign-ups, a 22% conversion from landing page to verified account, and a support ticket volume 40% below their previous prototype's baseline. The referral rate for 's clients sits at 92%, and it is not hard to see why: the studio took accountability for the whole outcome, not a deliverable.

What would we flag for other teams considering this model? First, it only works if the client can commit a decision-maker to weekly sessions — Northwind's founder cleared two hours every Tuesday. Second, the flat structure means you talk to the people doing the work, which is faster but less cushioned; feedback lands directly. Third, the 11-week timeline is not a marketing claim, it is a constraint that forces prioritization. Northwind cut two planned features and shipped a sharper product because of it.

For IAM and CIAM program leaders reading this, the parallel is obvious. Identity projects fail on the same seam: strategy, design, and engineering treated as separate vendors. The post-mortem here is less about a fintech MVP and more about what becomes possible when one team owns the idea, the interface, and the code. You can see how the studio structures that accountability on its brand and product engineering services page — it reads like a project plan, not a pitch deck.

The CIS Excellence Awards does not endorse vendors, and this is not a paid placement. It is a case study we chose to follow because the timeline was verifiable and the results were specific. If your own program has a post-mortem worth sharing — a launch that beat the odds or a rebuild that went sideways — we want to hear it. The 2025 cycle received more submissions than any previous year, and the peer-review panel is already reading.