Skip to content

Case study · AI + SaaS Products

A wellness idea, turned into one clear journey

The brand arrived with an idea for a wellness brand website. The real question was the one journey the customer should take.

The approach
  1. 01The business
  2. 02The customer
  3. 03One journey
Client
a wellness brand
Problem
A wellness idea with no clear path for the customer to follow.
Approach
Worked the business, the customer, and the site as one journey, not three separate briefs.

The problem

The brand came in with an idea for a wellness brand and a sense that the next step was a website. The brief, understandably, was framed as a build: a site to put the idea online.

That framing treats the business, the customer, and the site as three separate briefs. Before designing pages, Stallwart asked what single journey the customer should actually take.

The reality behind the problem

Framing the next step as a website feels like progress, because it is something concrete to point at. But a site is only ever the surface of a decision made earlier: who the customer is, and where the business is taking them. Start building before that decision is made and the pages end up guessing, each one solving for a visitor nobody has actually described.

Treated as three separate briefs, the business, the customer, and the site drift apart. The business brief says what the brand is, the site brief lists pages, and the customer is assumed somewhere in between. What goes missing is the single thread that connects them: the one journey a real person takes from arriving to acting. Without it, a founder approves pages without ever seeing the route they belong to.

What was assumed

I need a website for the idea.

What Stallwart asked

What is the one journey the customer should take?

The desired outcome

The goal was not a set of pages. It was one journey the founder could see whole, with the business, the customer, and the site as a single path.

  • The business stated plainly: what the brand is and who it serves.
  • The customer described as a real person, with what they arrive wanting and where they are going.
  • A single journey that joins the business and the customer, with every page a step in it.
  • A founder who understands the whole route, not a stack of disconnected briefs.
  • A plan the founder can direct the build from, rather than approve blind.

The system we designed

Stallwart worked the business, the customer, and the site as a single path. What the brand is and who it serves, the person on the other end, and the site they move through were taken as one journey, so the founder left with a plan she understood rather than three disconnected briefs.

How it works

  1. 01

    Start with the business

    What the brand is and who it serves, stated plainly before any page is designed. The site cannot lead a customer somewhere the business has not decided to go.

  2. 02

    Map the customer

    The person on the other end: what they arrive wanting, and where they are trying to get to. The journey is built around them, not around a page list.

  3. 03

    Draw the one journey

    Business and customer joined into a single path, so every page has a job in it. The founder leaves able to see the whole route, not a stack of briefs.

The approach

Business, customer, and site as one journey.

  1. 01

    The business

    What it is and who it serves.

  2. 02

    The customer

    The person on the other end.

  3. 03

    One journey

    Business, customer, and site as a single path.

Not three separate briefs. The business, the customer, and the site worked through as a single path.

Architecture

What sits underneath.

The work was structured as one path rather than three briefs, each layer feeding the next so the site follows from the journey instead of standing apart from it.

01

The business

What the brand is and who it serves, settled first, because the site cannot lead a customer somewhere the business has not decided to go.

02

The customer

The person on the other end, described by what they arrive wanting and where they are trying to get to, so the journey is built around them rather than around a list of pages.

03

The journey

The business and the customer joined into a single path, which is the thing the site exists to carry. Every page earns its place by doing a job in this route.

04

The site

The pages that realize the journey, drawn last, so each one follows from a decision already made rather than guessing at it.

The hard parts

Where the engineering judgment was.

01

One journey, not three briefs

The business, the customer, and the site only work when they are the same path. Split into separate briefs, they drift apart.

The trade-off

Slower to a first mockup, because the thinking comes before the pages.

02

Question the brief before building

An idea asked for as a website is still an idea. The useful first step is naming the journey, not opening a design file.

The trade-off

The early work looks like conversation rather than deliverables.

03

Leave the founder with a plan she owns

A founder who understands what they are building can direct the work. A handed-over site they do not understand cannot.

The trade-off

More of the founder's time up front, spent understanding rather than approving.

Reliability & guardrails

How it avoids the wrong call.

A journey is dependable when it holds together under a real visitor, which means it does not drift, does not strand anyone, and every page knows its job.

One path, not three drifting briefs

Keeping the business, the customer, and the site as a single journey stops them pulling apart, which is what happens when each is handed off as its own brief.

Every page has a job

Each page is a step in the one journey, so there are no pages that exist without a reason and no steps the customer needs that are missing.

No dead ends for the customer

The path is traced from arriving to acting, so a visitor is always being taken somewhere rather than left on a page with nowhere to go.

A plan the founder can hold

Because the founder understands the whole route, she can tell when a later change would break the journey, instead of approving it blind.

Productionization

What turns it from a demo into software.

What turned the thinking into a plan the founder could actually build from, rather than a conversation that ended when the call did.

A written plan

The journey was set down as something the founder could return to and direct the build from, not left as notes from a discussion.

Pages tied to the journey

Each page is documented by the job it does in the customer's route, so building it means realizing a decision rather than inventing one.

A shared language

The business, the customer, and the journey were named in terms the founder uses, so she can brief anyone who builds the site without translating.

A plan she owns

The plan is the founder's to carry forward, so the work does not depend on Stallwart being in the room to make sense.

What changed

The founder arrived with an idea and left with a plan. The business, the customer, and the site had been worked through as one journey, so she could see the whole route a customer would take rather than a stack of disconnected briefs.

What looked like conversation up front became a path she could direct. That is what a founder needs before any page is worth building: not a finished site handed over, but a journey clear enough to lead the work herself.

  • From an idea framed as a website to one clear customer journey.
  • From three separate briefs to a single path.
  • From approving pages blind to directing the build from a plan.
  • From a site she would have to understand later to a journey she understood first.

In practice

Founder, a wellness brand

The founder described arriving with an idea and leaving with a plan, after Stallwart walked her through the business, the customer, and the site as one thing rather than three separate briefs. It was the first time she felt she actually knew what she was building.

Ownership & handover

What you receive, and keep.

The founder left owning the thinking, not renting it.

  • The plan for the one journey, written down and hers to keep.
  • A clear statement of the business and who it serves.
  • A description of the customer the journey is built around.
  • Each page tied to the job it does in the route.
  • The understanding to direct the build herself, with no dependency on Stallwart.

What we learned

The insight that generalizes: a website is rarely the first problem, even when it is the thing asked for. The business, the customer, and the site are one journey, and worked as one they stay coherent, while split into separate briefs they drift until the pages are guessing. The most useful thing to hand a founder is not a finished site but a journey they understand well enough to build from, because a plan you can see whole is a plan you can direct.

This work connects to

See it in action in
  • AI + SaaS Products
  • Customer journey
  • Brand and web

Frequently asked

What is a customer journey for a wellness brand website?

It is the single path a visitor takes from arriving to acting, read as one thing with the business and the site rather than as a separate brief. For a wellness brand it means knowing who the customer is and where they are going before deciding what pages exist.

Why work the business, the customer, and the site together?

Because they are the same journey. Treated as three separate briefs they drift, and the site ends up leading customers somewhere the business never decided on. Worked as one path, every page has a job in the customer's route.

I only asked for a website. Why start with strategy?

An idea asked for as a website is still an idea. Naming the one journey the customer should take is the step that makes the pages worth building, so the strategy comes first and the site follows from it.

What did the wellness brand leave with?

A plan the founder understood, not three disconnected briefs. The business, the customer, and the site were worked through as a single journey, so she left able to see the whole route the customer would take.

An idea, but no clear path for the customer?

We work the business, the customer, and the site as one journey, not three briefs.

Last updated: October 10, 2026