From business problem to working product.

We build apps, websites and online stores for startups and growing businesses, from the first idea to a product that works.

Move your mouse. The product is alive.

Work we are proud to show

Real products, live today. Open one to read the case.

See all 8 projects, across commerce, education, food and fintech

Which of these sounds like you?

Pick the sentence closest to your situation. The product changes to match.

MVP development and technical strategy.

  1. Clarify the problem
  2. Scope and roadmap
  3. Architecture
  4. First release
  5. Iterate
Everything this covers

We start with the problem. Technology comes second.

See how we think

Two small tools, to show how we think before we talk. They move the product, so you can watch the idea work.

Follow an order through a system

Illustrative, not a real WAFU product. Watch the product light up as the order moves.

  1. Customer app
  2. Gatekeeper (API)
  3. Orders
  4. Waiting line (queue)
  5. Payments
  6. Stock
  7. Messages

Press the button to send an order through seven parts of a typical online system.

Sketch your first version

A starting sketch to bring to a conversation. It is not a quote or a plan.

What are you building?
What does it need?

Interface

Storefront · Checkout

Services

Sign-in and accounts

Data and hosting

Catalog · Orders · Hosting and monitoring

Start from this sketchIt fills in the project field of the contact form. You can change it there.

How a project moves

  1. Discover the business problem

    We start with what the business needs to change, who will use the product, and what a good result looks like.

  2. Define scope and risks

    Scope, constraints and technical risks are written down before build work begins.

  3. Design the experience and architecture

    User journeys, interface and system design are worked out together, so engineering and design do not drift apart.

  4. Build in reviewable increments

    Working software is delivered in stages you can review, so direction can change while change is still cheap.

  5. Test and prepare for launch

    Testing, store preparation and release support, so launch is a planned step and not a scramble.

  6. Support, learn and improve

    After release we look at how the product is actually used and improve it from there.

Tell us what you want to build.

A short description of the problem is enough to start the conversation.