Discuss

03 / Website, web app & mobile development

Websites and apps. Built around people.

Websites, web services and mobile apps built around useful actions. From the first user journey to a working product.

  • Websites & customer portals
  • Web services
  • Mobile apps
Discuss my productExplore scenarios
The project journeyClick or turn the cube
PROJECT STAGES01 / 04
Rotate the cube.
Click the cube or an arrow.
01 / Discover

Define the users and the product’s core workflow.

  • From workflow to interface
  • Usable across screen sizes
  • Your code and access

01 / Scenarios

What will your users do?

Start with the action that gives someone a reason to open your product. Choose the closest scenario.

Website & portalInternal toolsMobile app & MVP

Illustrative workflow / 01

Discover your offer. Take the next step.

Customers need to understand your service, send a request and return for a status update or document without calling a manager.

  1. Introduce

    Structure the website, clarify the offer and prepare public service pages for search.

  2. Enable

    Design an enquiry, order or booking flow that works on a phone.

  3. Keep informed

    Show status, history and documents in a customer portal.

What changes

A clear journey from first visit to the next interaction.

How to assess value

Completed actions · form errors · mobile usability

Illustrative workflow / 02

The process has outgrown a spreadsheet.

Files are duplicated, access rules are unclear and someone always has to ask which version is current.

  1. Map

    Understand roles, daily actions, data and exceptions.

  2. Design

    Create an interface with permissions, validation and change history.

  3. Connect

    Integrate the tool with existing systems and plan data migration.

What changes

A shared workspace built around your workflow and team roles.

How to assess value

Task completion time · repeated entry · status clarity

Illustrative workflow / 03

Put the idea in users’ hands.

You need a first release to learn whether the product helps people and what should come next.

  1. Focus

    Define the audience and one complete first-release journey.

  2. Build

    Develop the interface, backend and essential integrations.

  3. Validate

    Test on devices, prepare release and make feedback easy to collect.

What changes

A product with a core workflow ready to test with real users.

How to assess value

Journey completion · user feedback · drop-off reasons

02 / The deliverables

Your product. From first screen to launch.

Bring product thinking, design and engineering into one agreed plan.

  1. First-release scope

    User journeys, priorities and acceptance criteria so you know what will launch.

  2. A considered interface

    Prototype and design covering loading, errors and mobile and desktop layouts.

  3. Working software

    Interface, backend logic, integrations and checks for core user actions.

  4. Room to develop

    Source code, access, deployment instructions and a prioritised list of improvements.

03 / An easier place to start

A big idea. A focused first release.

Define the users and their purpose. Choose one complete journey for the first release and explore it in a prototype.

Discuss my product

For our first conversation

  • Who the product is for
  • The problem it should solve
  • References or sketches, if available

What happens next

First-release scope, milestones and an estimate. Discovery or prototyping is scoped separately where needed.

Cost and timing depend on workflows, design, integrations, migration and launch requirements.

04 / Questions

Before we begin

Budget, data and the details worth discussing early.

Can we start without a specification?

Yes. Describe the problem in your own words and share what you have. We help define requirements, constraints and the first stage. Any paid discovery work is agreed in advance.

Who will own the code and access?

Source code, access and rights transfer are set out in the contract. Third-party library and service licences are accounted for separately so you understand the conditions of use.

Can you continue an existing project?

Yes. We first review the current code and requirements, then explain what can be reused, what needs fixing and how to reach launch.

Should we build a website, a web app or a mobile app?

A website works well for presenting an offer and collecting enquiries. A web app suits recurring browser-based workflows, such as a customer portal. Consider a mobile app if the core workflow depends on a camera, notifications or offline access.

What determines the cost and timeline of development?

User workflows and roles, design, integrations, data migration and launch preparation drive the estimate. For mobile apps, plan separately for store requirements and the submission review window.

What should we prepare for a first-release estimate?

Describe the users, their main task and the features the first release must include. Share any prototype or references and point out which decisions you want to carry forward.

Just need a first release? Explore MVP developmentAlready have a prototype? Explore project improvement

Good projects
start with hello.

Tell us a little about your project.
We’ll figure out the rest together.

Discuss a project
A QUICK INTRODUCTION

What would you
like to build?

Leave your contact details and tell us about your project.

Choose a service
What do you need?
Add a budget, deadline or link Optional +

Demo: nothing is sent. Please use fictional details.