Transformation cases

Every one of thesearrived as somethingsmaller than it was.

A website. An identity. A process that took too long. In each case the visible request turned out to be a symptom of something wider — and fixing only the visible part would have moved the problem rather than removed it.

How each case is set out

The business situation → the system that actually changed → what became possible afterwards

Sectors

Commerce, enterprise software, fintech, mobility, technology and education

Main cases

What changed inthe business.

Each is described by the type of change and the situation that caused it. The client name comes second, because the situation is the part you may recognise.

01/04

Marketplace & operating-model change

SG Organic

The situation. A wellness retailer asked for a better e-commerce site. Positioning was unclear, mobile buying was weak, vendor and delivery work was coordinated by hand, and management had little current visibility.

What changed. The operating model behind the storefront — how the marketplace, payments, vendors and reporting fit together — rather than the storefront alone.

What it made possible. Marketplace growth, and AI-assisted workflows the team can keep extending.

Positioning

Marketplace

Operations

Brand & category change

TALK Studios

The situation. A credible idea that the market could easily read as public speaking, therapy or coaching. Trust sat with one person, which limited how far the organisation could grow.

What changed. The category was defined before anything was designed, and trust was moved from an individual to an organisation.

What it made possible. Programmes for schools and organisations, and a base for future products.

Edde

The situation. An EV delivery cycle that took seven weeks and crossed several teams and systems, losing time and context at each handover.

What changed. The operating journey was mapped end to end and redesigned, then carried into the products the teams actually use.

What it made possible. A three-week cycle — a 50% reduction — and a 40% increase in product engagement.

Workflow redesign

Enterprise product

Team leadership

Ongoing practice

Upsense Studio

The situation. Founders and growing companies who need the business problem framed before anything gets built.

What changes. Product, brand and AI-enabled platforms are shaped from the operating need, then taken through to delivery.

What it makes possible. One route from problem framing to a working system, without handing the thinking to someone else halfway.

Product

Brand

AI platforms

Earlier work

Where the operating-model view came from.

Fourteen years of working inside enterprise software, fintech and financial platforms — close enough to the workflows to see why interface problems are usually process problems.

Enterprise SaaS
Deskera

HRM, CRM, accounting and inventory workflows contributing to a 20% increase in adoption and business conversions.

Fintech
AlgoMerchant

Onboarding and information architecture contributing to 66% growth in daily logins and 55% growth in sales.

Financial platforms
DirectFN & Xinfinit

Data-intensive financial applications delivered across 10+ international markets, with responsive practices contributing to 40% mobile adoption growth.

Recognise any ofthese situations?

The approach page sets out how a business gets diagnosed, which part to change first, and how the work is sequenced so it holds.