Skip to content

Case study · AI + SaaS Products

From requirements to a clear product strategy

The studio expected a proposal and a deck. The real question was what they were actually building, and why.

The approach
  1. 01Business requirements
  2. 02Questions, not a proposal
  3. 03A clear product strategy
Client
a digital product studio
Problem
Business requirements in hand, but no clear direction to build from.
Approach
A conversation about what was being built, turned into a product strategy.

The problem

The studio arrived with business requirements and the expectation that an agency answers them with a proposal and a deck. That is how the first conversation usually goes.

A deck speaks to how an engagement is sold, not to what should be built. Before writing one, Stallwart asked what the studio was actually building, and why.

The reality behind the problem

A deck feels like progress because it is something to hold: a tangible answer to a set of requirements. It is the wrong answer for that reason, because it speaks to how the engagement is sold, not to what the product should be, and writing one before the product is understood commits to the wrong thing early.

The requirements the studio brought described what the product had to do, but not why, or which parts mattered most. A proposal built on them would have been polished long before anyone had agreed what was actually being built.

What was assumed

We need a proposal and a deck.

What Stallwart asked

What are we actually building, and why?

The desired outcome

The goal was not a document to approve. It was a direction the studio could build from, with the reasoning behind it in hand.

  • The intent behind each requirement understood, not just the requirement as written.
  • A clear sense of what the product has to do, and why it exists.
  • The parts that matter most separated from the parts that can wait.
  • Decisions the team can act on, rather than a checklist to quote against.
  • A direction the founder can build from without coming back for more.

The system we designed

Stallwart turned the first call into a conversation rather than a pitch: no deck, no proposal, just questions about what the studio was building. Those questions turned the business requirements into a clear direction to build from, which is what the founder left with.

How it works

  1. 01

    Open with questions, not a deck

    The first call spent understanding what was being built, not presenting a proposal. The conversation is the work, not the preamble to it.

  2. 02

    Read the requirements for intent

    Business requirements taken as the start of a conversation about what the product has to do and why, rather than a checklist to quote against.

  3. 03

    Turn it into a direction

    The conversation resolved into a clear product strategy the studio can build from, so the founder left with a direction rather than a document to approve.

The approach

Requirements turned into a direction to build.

  1. 01

    Business requirements

    What the product has to do.

  2. 02

    Questions, not a proposal

    A real conversation about what was being built.

  3. 03

    A clear product strategy

    Requirements turned into a direction to build.

No deck, no proposal. A conversation about what was being built, turned into a strategy.

Architecture

What sits underneath.

The strategy organized the requirements into a direction, from the intent behind them down to the decisions that follow from it.

01

Intent

Why the product exists and what it has to do, drawn out of the requirements in the conversation rather than assumed from how they were written.

02

Priorities

Which parts matter most, separated from what can wait, so the direction is weighted rather than treating every requirement as equal.

03

Decisions

The choices that follow from the intent and the priorities, each one something the team can act on rather than a line to quote against.

04

Direction to build

The resolved strategy the studio builds from, which is what the founder left the first call holding.

The hard parts

Where the engineering judgment was.

01

A conversation, not a pitch

The first call is the most useful place to understand what is being built. Spent on a pitch, it answers how the work is sold instead.

The trade-off

No deck to hand over afterwards, which can feel like less on paper.

02

Requirements before proposal

A proposal written before the product is understood commits to the wrong thing early. The questions have to come first.

The trade-off

Slower to a signed scope, because the thinking is done before the paperwork.

03

Leave with a direction, not a document

A founder who knows what they are building and why can make decisions. A deck they did not need cannot.

The trade-off

The value shows up as clarity rather than as a deliverable to file away.

Reliability & guardrails

How it avoids the wrong call.

A direction is only worth building from if it holds up, so the questions were aimed where getting it wrong would cost the most.

Traced to intent

Each decision rests on why the product exists, not on an assumption carried in from how a requirement happened to be written.

The hard-to-reverse choices first

The decisions most expensive to undo later were the ones questioned hardest in the room, before anything committed to them.

No premature commitment

Nothing was fixed in a proposal before the product was understood, so the direction does not lock in the wrong thing early.

Honest about the unknowns

Where a requirement did not yet have a clear answer, that was named rather than papered over with a confident-sounding plan.

Productionization

What turns it from a demo into software.

What turned the conversation into a direction the studio could build from after the call, not a conversation that fades.

A direction the founder holds

The founder left knowing what to build and why, which lasts in a way a filed deck does not.

Anchored to the requirements

The strategy answers the requirements the studio brought, so it stays tied to the real work rather than floating free of it.

Clear enough to act on

The direction resolves into decisions the team can move on, which is what makes it a strategy rather than a discussion.

Open to revisiting

As the product takes shape, the direction can be questioned again the same way it was formed, so it bends rather than breaks when a requirement changes.

What changed

The studio left with a clear product strategy rather than a proposal to approve. The business requirements were turned into a direction to build from, with the reasoning behind each decision in hand rather than hidden inside a pitch.

What changed was the kind of first conversation the studio had: questions about what they were building instead of a presentation of how the work would be sold. That is what let the founder leave knowing their direction rather than holding a document to file.

  • From a proposal to a direction to build from.
  • From a pitch to a conversation.
  • From requirements as a checklist to requirements read for intent.
  • From a document to approve to clarity to act on.

In practice

Founder, a digital product studio

The founder recalled a first call with no deck and no proposal, just questions about what they were building, and described it as the first agency conversation that actually felt like a conversation.

Ownership & handover

What you receive, and keep.

The direction is the studio's, with no dependency on Stallwart to use it.

  • The product strategy and the direction it sets.
  • The reasoning behind each decision, not just the conclusion.
  • The mapping of the direction back to the business requirements.
  • The questions that produced it, to ask again as the product changes.
  • A direction the studio can build from and change without Stallwart.

What we learned

The insight that generalizes: the first call is the most valuable part of an engagement, and spending it on a pitch wastes it. Questions about what is being built, and why, turn a list of requirements into a direction a team can act on, where a proposal written before that answers how the work is sold rather than what the product should be. The thinking has to come before the paperwork.

This work connects to

  • AI + SaaS Products
  • Product strategy
  • Scoping and discovery

Frequently asked

What is digital product strategy?

It is the direction a product is built from: what it has to do and why, drawn out of the business requirements before any build begins. The strategy turns a list of requirements into decisions a team can act on.

Why start with a conversation instead of a proposal?

A proposal speaks to how an engagement is sold, not to what should be built. Questions about what is actually being built come first, because a proposal written before that commits to the wrong thing early.

Do you need full requirements before the first call?

No. Business requirements are the start of the conversation, not a prerequisite for it. The first call is where they are read for intent and turned into a direction, so bringing what you have is enough.

What did the studio leave with?

A clear product strategy rather than a deck to approve. The business requirements were turned into a direction to build from, which is what the founder took away from the first conversation.

Sitting on requirements with no clear direction?

One conversation, no deck, and you leave with a product strategy to build.

Last updated: October 10, 2026