Matt Murphy

For founders and domain experts

A clickable prototype of your product idea

User flows, then a clickable prototype you can put in front of five real people before you pay for a build.

Discovery to prototype Four to six weeks

Not sure where to start? Product discovery

Book a 20-minute callWhere we start

A clickable prototype: the screens for one job, linked in order, with real words on every button.

What you get

  • User flows for the core job
  • A clickable prototype with real words
  • A test script for five conversations
  • Notes on what people did and said
  • A scoped plan for the first version

Best fit: web tools and focused products. Not a fit: safety-critical, medical or payments infrastructure.

How it works

  1. Discovery

    Who it’s for, and the one job it does first.

  2. Flows

    The screens and decisions, drawn.

  3. Prototype

    Clickable, with real words.

  4. Test

    Five people try it; you watch.

Proof

  • Live product

    Pathway Builder

    Software I built so community-college teams can map programs, courses and competencies into routes they can see, from short-term training to a degree. Right now I’m adding a place to weigh new program ideas with evidence.

    Read the story

  • In development

    Encore

    I’m building one system for community-college continuing-education teams: catalog, registration and payment, class operations, attendance, completion and certificates.

    Read the story

Where we start

Discovery to prototype

Timeline Four to six weeks

Included

  • Discovery sessions and a one-page product brief
  • User flows for the core job
  • A clickable prototype with real copy
  • A test script and notes from five user conversations
  • A scoped quote for the first version

Not included

  • Safety-critical, medical or payments infrastructure
  • Native apps for both platforms at once
  • Ongoing product management

The first version is quoted from the prototype.

Not sure where to start? Product discovery

Book a 20-minute callOr send a note and I’ll reply with a time.

Where

Anywhere, remotely; in person around Iowa City and Cedar Rapids when it helps.

Questions people ask

Who owns what we build?

You do. The prototype, the code and the design files are yours. I keep the right to reuse general components that carry nothing of your product.

What stack do you build in?

Next.js, TypeScript and Postgres, hosted on Vercel, with AI where it earns its place. I’ll say so when a no-code tool would do the job for less.

Can you improve a product I already have?

Yes. That starts with a usability review: where people get stuck, in priority order, then the fixes.

How involved do I need to be?

Two to three hours a week during discovery and prototype, mostly answering questions and watching users try it. Less once the build starts.

What is not a fit?

Anything safety-critical, medical or payments infrastructure, and products whose first version needs a large team. I will say so in the first call.

Other ways to work together