Account-based services
Offer a tool to identified users or clients, with their own data and features.
APPS/004Digital products
From an idea
to a service people use.
We develop applications for your own digital service: a customer tool, a work platform or a subscription service. We define a useful first version and how to keep it running.
A specific need.
A product with direction.
The first version does not need every imaginable feature. It needs to solve a recognisable problem and let its intended users put it to work.
Shared workspaces
Support a process that several people need to carry out or track in one place.
New service models
Assess which part of your knowledge or operations could become a digital tool.
Develop an early version further
Expand a product from observed use and measured needs.
From a proposition
to a first experience.
We agree on who the product is for, which problem it solves and what is needed to operate it after launch. The first version is designed around that purpose.
Starting point
- Idea
- Users
- How it will be used
Digital productOutcome
- Experience
- Functions
- First version
A tool of your own.
A specific delivery.
These are the elements we define in the proposal. The final scope depends on your starting point and business priorities.
/001Product definition
We define the audience, problem, proposition and essential features needed to begin.
/002Experience design
We prepare the screens and user journeys needed to test the service.
/003Development by scope
We build the first version’s features and the agreed integrations.
/004Preparation for use
We define access, publication, initial testing and the tasks needed to operate the product.
/005Handover and continuity
We hand over the access, documentation and guidance covered by the agreed scope. Follow-up or maintenance is defined separately if commissioned.
From the idea
to its first real use.
(4)Define who it is for
We agree the problem it solves, who will use it and what they need to be able to do.
Scope the first version
We prioritise the main journey and identify features that can wait for another phase.
Design and develop
We build the agreed screens, accounts and features, testing throughout delivery.
Prepare operations
We review launch, support and recurring costs before opening the service and considering its next improvements.
Designed for your team.
Sustainable for your business.
Agreed scope
A custom application needs priorities and limits. We document features, user journeys and acceptance criteria before development.
Data and access
We define the profiles, actions and information each person needs, along with the planned backups, recovery and access management.
Operation and ongoing development
We define where the application runs, its recurring costs and who maintains it. Later versions are prioritised according to actual use.
Before we start.
(5)Can we start with a small version?
Yes. We choose a useful journey that can be maintained with the available resources. Later features are assessed against actual use and project needs.
Does this include recurring payments or subscriptions?
These can be included if the product needs them. The provider, payment states, cancellations and service terms must be defined before integration.
Does everything have to be defined from the beginning?
We need a clear goal and scope for the first version. Further features can be prioritised after testing; changes are assessed before they are added.
Can we connect the tools we already use?
We review the integration interfaces, permissions and terms. If a connection is not feasible, we explain alternatives and their limitations before committing to development.
What happens after delivery?
We agree on hosting, support, maintenance and documentation. The proposal distinguishes operation of the delivered version from extensions and recurring services.
Engineering × Design.
For the next step.