SaaS product design and development

A SaaS product is more than an interface and a database. I connect user needs, business rules, commercial model and architecture to build a coherent product.

Real interface of the Peachie platform
Preview of the Peachie course editor

A prioritised product scope

Journeys designed for real use

Architecture ready to evolve

Does this sound familiar?

We start with your situation, not a checklist of services.

You have an idea, but the scope keeps growing

Separate what's essential for the first useful experience from what can wait.

Early users are hitting friction

Onboarding, journeys or features prevent the product from showing its value.

Your platform needs to grow up

Business rules, data and integrations become more complex as you grow.

What I can take care of.

Together we define a useful, realistic scope, then I work where it will make the most difference.

Product scoping & MVP

Turn a broad idea into a testable proposition with the assumptions, journeys and features needed for a useful first release.

Product experience

Onboarding, dashboards, empty states, errors and critical flows designed to reduce friction.

Business features

Roles, permissions, data, automations, editors, client spaces and integrations tailored to the product.

Monetisation & growth

Payments, subscriptions and measurement considered from the start, then iterations guided by real use.

peachiePeachie platform home page
Create a course01 Introduction 02 Your first lesson 03 Quiz & progress Content · Learners · Sales

The tools I use.

I choose tools around your project and your environment. These are part of my practice for this type of work.

FigmaJavaScriptBootstrapGSAPStripe
Peachie · real project

A living product, built and improved over time.

I'm a co-founder of Peachie, a platform to create and sell courses, manage clients and track business activity. I work across product, UX, architecture and full-stack development.

Explore Peachie
Course editor in Peachie

A clear process, from start to what's next.

You know what I'm doing, why I'm doing it and what comes next.

  1. 01

    Clarify value

    Define who the product serves, the problem it solves and what proves it is useful.

  2. 02

    Design the system

    Map journeys, data and business rules before locking in isolated screens.

  3. 03

    Deliver a strong core

    Build the priority scope end to end, ready to be tested in the real world.

  4. 04

    Learn and evolve

    Study feedback and improve the product without losing its coherence.

Questions before we begin.

Straight answers to help you decide if this service fits your project.

Can you join before we've written a specification?

Yes. That's often the best time to separate real needs from prematurely chosen solutions and define a realistic MVP.

Do you build back-office tools too?

Yes. Administration, roles, workflows and internal tools are part of the product and should fit actual operations.

Can you join an existing product?

Yes—to improve a feature, clarify architecture, refine the experience or support a new phase of growth.

Have you built a SaaS before?

Yes. My work includes Peachie, an all-in-one platform for course creators, and Boocut, a booking and management product for hair salons.

What if the next step lies elsewhere?

A project rarely stops at one discipline. Explore other ways to move yours forward.

Shall we look at your project together?

Tell me about your situation and what's holding you back. I'll reply with an initial, practical assessment.

Contact me