YourVisionOurTechnology

Service · Decide before you build.

Creative & productconsulting

Short, focused engagements that turn a vague idea into a scoped plan — or stop a build that should not happen.

The problem

Building before the problem and audience are clear, which turns into expensive rework and a product nobody asked for.

Who it’s for

Founders and teams facing a large build decision who want an independent read before committing budget.

Overview

We run this as a fixed, short engagement with a written deliverable. The output is a plan you could hand to any competent team — not a pitch to hire us.

The work covers the problem, the users, the competitive landscape, the technical options and the honest cost and risk of each. Where the answer is 'do not build this yet', we say it plainly.

Design-thinking workshops are run with your actual team, because the people who will operate the product usually know where it breaks.

Creative & product consulting

Decide before you build.

What’s included

01

Problem definition

The job to be done, the users, and what success would look like in numbers.

02

Discovery workshops

Structured sessions with your team to surface constraints early.

03

Competitive review

What already exists and where a real gap sits — if one does.

04

Technical options

Two or three routes with cost, timeline and risk stated honestly.

05

Prototype or wireframes

Enough fidelity to test the idea with users before committing to a build.

06

Written recommendation

A scoped plan any competent team could execute, owned by you.

How the work runs

  1. 01

    Frame

    The decision to be made and what evidence would settle it.

  2. 02

    Workshop

    Sessions with the people who will operate the product.

  3. 03

    Research

    Users, competitors and technical constraints.

  4. 04

    Prototype

    The riskiest assumption tested cheaply.

  5. 05

    Options

    Routes costed, with trade-offs made explicit.

  6. 06

    Recommend

    A written plan, including the option not to build.

Tools we use

Design-thinking workshopsUser interviewsFigma prototypingTechnical spikesCost & risk modellingRoadmap definition

What you get

Deliverable
Written plan
Engagement
Fixed & short
Portable
Any team can execute
Includes
'Do not build'

Where it applies

Pre-build validation

Test the idea before committing a development budget.

Rescue a stalled project

An independent read on why it stalled and what to do next.

Build vs buy

An honest comparison against off-the-shelf options.

Roadmap definition

Turn a long wishlist into a sequenced, costed plan.

Frequently asked questions

Do we have to hire you to build it afterwards?
No. The deliverable is written so any competent team can execute it. A number of clients take the plan elsewhere and that is a fine outcome.
How long does it take?
Most engagements run two to four weeks depending on how much user research is needed.
What do we actually receive?
A written recommendation with the problem definition, user research, costed technical options and a sequenced roadmap — plus any prototypes produced.
Will you tell us not to build?
If the evidence says so, yes. That answer is usually the most valuable one we can give.

Got a project in mind? Let's make it a reality together

Looking to make your mark? We'll help you turn your project into a success story.