← Back to services

From idea to delivery

Prototypes and product development

Build the first thing that helps you decide what comes next.

Plan my project

The right starting point

Do you need to demonstrate it or run it?

01

Clickable prototype

For presenting an idea and testing its user journey.

  • One main journey, around 5–8 screens
  • Screen design and clickable connections
  • Sample data, without a working backend
02

Working first release

For real users and real data.

  • Own backend and database
  • Web, mobile or both
  • Agreed features, testing and launch

In a prototype, sign-in, payments and data handling are simulated. In a working release they are implemented. Mobile and combined versions have different entry prices, shown in the planner.

In practice

An idea in testable steps

  1. 01

    Goal and main user journey

  2. 02

    Clickable demonstration

  3. 03

    Gather feedback

  4. 04

    Define the next version

Concrete deliverables

What do you receive at handover?

The proposal defines the deliverables and acceptance criteria, so both sides share a clear definition of done.

  • 01Screens and journeys within the agreed scope
  • 02For prototypes: a clickable demonstration
  • 03For products: agreed features and backend
  • 04Open questions identified for the next step

How we work together

01

Discover

Goals, users, existing materials and technical context.

02

Agree

Scope, deliverables, fee and feasible schedule.

03

Deliver

Agreed steps, demonstrations and feedback.

04

Hand over and follow up

Verification, access and ongoing support arrangements.

Before we start

Is a prototype a working application?

No. It demonstrates screens and journeys using sample data. It does not store real customer data, process payments or contain a working business backend.

Do I need a specification?

No. We clarify the goal, user and main journey together. Larger or uncertain ideas also need a defined planning scope.

Can we build on the prototype later?

The journeys and feedback inform development. A working application is a separate phase; a prototype does not automatically provide production code.

What changes the price?

Prototype pricing depends on journeys, screens, roles and views. Working products also depend on platforms, business rules, integrations and data handling.

Can we skip the prototype?

Yes. If the goal and scope are clear, select a working first release in the planner.

Let’s work out what you need.

The planner opens the relevant questions and gives you a project brief and estimated budget.

Plan my project