Digital products & platforms
From a business need to a product people can use. For companies that need a first useful version of a new product, or have a website or platform that nobody wants to touch any more.
The first conversation is free: 30 minutes online, no preparation and no commitment.
Who this is for
Companies with a product idea
You have a business goal and an initial vision, but no team to turn it into a first version. You need someone to help choose what really has to be in version one, and then build it.
Organisations with a website nobody wants to touch
The site was built years ago, the agency has changed, the plugins are out of date and every content change needs a developer. Marketing avoids it, and customers see it every day.
Companies with many brands and sites
A handful or dozens of sites, each built differently, published differently, with different consent and analytics. You need a shared foundation on which a new brand can launch in days, not months.
What we usually find
The same patterns come up in most projects we take over or start:
- A feature list for the first version that would be enough for three versions.
- A CMS site with a dozen plugins, half of which are no longer updated.
- Publishing content that needs a developer, so the content is out of date.
- Cookie consent and analytics implemented differently on every site, with nobody who understands all of it.
- No acceptance criteria, so “done” means something different to each side of the contract.
- Nobody has decided who publishes content, grants access and handles updates after launch.
Most of these are resolved by one well-run scoping stage. The last two are also a regulatory question, which is part of our digital compliance work.
What we work on
Discovery & design
We clarify the problem, map key journeys and build wireframes or prototypes. The aim is to check the important assumptions before committing to implementation. Interfaces are designed for usability and accessibility, see UX/UI & design.
Websites & applications
Responsive websites, web applications and CMS-based experiences. Content structure, accessibility, performance and search visibility are part of the work from the beginning.
APIs & shared platforms
Integrations, administration tools and foundations for multiple websites or services. We define data ownership, access rules and responsibilities between systems. The platform runs on an environment your team can maintain, see cloud & infrastructure.
What we have done before
The founders’ experience from projects delivered before the company was set up, directly and in cooperation with agencies, for startups, agencies and large organisations. More under achievements.
- Many brands, one platform: the sites of many brands built and maintained on a shared foundation, across several markets at once.
- Static publishing instead of always-on servers: faster sites, lower costs and a smaller attack surface.
- More than 120 analytics properties and tag containers in one consistent layout for whole portfolios of sites, with consent managed from one pattern.
- Permissions for the client, agencies and media houses in one system, granted and reviewed in one place.
- More than 6 years without a security incident on the sites we ran.
Example: a new brand in days, not months
A typical starting point and what we built from it. The client’s name, figures and configuration details are something we discuss in a meeting.
Before
Every new brand site was a separate project: choosing an agency, a new template, new consent and analytics configuration, new access. Launch took months, and the result looked and worked differently every time.
After
A shared platform: one CMS pattern, components and templates, static publishing, consent and analytics deployed from one configuration. A new site became a decision about content and brand, not about technology.
Result
Dozens of sites maintained by a team of a few people. A change to consent, tags or a component made once for the whole portfolio. One access model for the client, agencies and partners.
Three steps, each one you can stop after
Free consultation
30 minutes online. You tell us who the product is for, what it should do and what already exists. We tell you where we would start and whether a new product, a rebuild or tidying the current one makes more sense. No preparation, no commitment.
Workshop and first-release plan
Fixed scope and a fixed price agreed before we start. Users, their key tasks, a prioritised scope for the first version, wireframes of the most important journeys and an implementation estimate. We review the result with your team.
Implementation
Built in stages: working versions to look at, content prepared in parallel, testing, launch and handover. Each stage has acceptance criteria and a price agreed before it starts. After every stage you decide whether we continue.
What the workshop covers
- Users and their tasks: who uses the product, why, and what they must be able to do in the first version.
- A prioritised first-version scope: what goes in now, what later, what not at all and why.
- Wireframes or a prototype of the key journeys, ready to test with real users.
- An operating model after launch: who publishes content, grants access and handles updates.
- An implementation estimate in stages and a proposed sequence, with acceptance criteria for each stage.
This is what a fragment of a first-release plan looks like. The figures are illustrative, the layout is real:
| Feature | For whom | When | Acceptance criterion |
|---|---|---|---|
| Service catalogue with search | Customer | Version 1 | Every service found in 3 clicks or one query |
| Enquiry form with attachment | Customer | Version 1 | The enquiry reaches the CRM with all fields in under a minute |
| Content editing without a developer | Marketing | Version 1 | An editor publishes a new page alone in 15 minutes |
| Customer account and enquiry history | Customer | Version 2 | Deferred: needed only once orders repeat |
| Accounting system integration | Finance | Not now | No volume data; decide after 3 months of operation |
The workshop also works as a basis for a quote from another supplier: the scope, wireframes and acceptance criteria stay with the company whoever builds.
What stays on your side
We work in your accounts, on your domains and in your repository. The product, the content and the access belong to the company, not to the contractor.
- Source code, configuration and documentation in your repository, with setup instructions.
- Content published by your team without a developer, with a written editorial process.
- Consent, analytics and tags in one documented layout, ready to show an auditor.
- Knowledge transfer to your team, as workshops where useful, or an agreed monthly scope of development and maintenance.
A product also needs an operating model
We plan who publishes content, manages access and handles updates. WordPress, a static website or a custom application can each be the right choice. We choose around the product and the team, including its ability to maintain the result. Repeatable editorial steps such as publishing, checks and notifications become automations, and when no ready-made tool exists, we build it as custom R&D.
FAQ
How long does the first version take?
It depends on the scope we agree in the workshop. The aim of the workshop is a version small enough to launch in weeks, not months, and complete enough that someone actually uses it.
We already have a website. Rebuild or new?
That is the first question at the consultation. Often it is enough to tidy content publishing, consent and hosting on the current site. We build a new one when the current one blocks your goals, not just when it annoys you.
Do you design the look as well?
Yes. Wireframes, prototypes and the interface are part of the work, with an emphasis on usability and accessibility. If you have your own design team or brand system, we work within it.
What about our current agency?
We can work alongside the existing team or take over a clearly defined part. The split of responsibilities is written down before we start.
How do you charge?
First consultation: free, 30 minutes online. Workshop: fixed price. Implementation: stages with acceptance criteria and a price agreed for each stage. Development and maintenance: a monthly scope agreed after handover.
Who owns the code and the content?
You do. The code goes to your repository, the content and accounts belong to the company, and the transfer of rights is written into the contract. How we handle data from the contact form is described in the privacy policy.
Let’s define the first useful release
Tell us who the product is for, what it should do and what already exists. We will propose a time.
The first conversation is free: 30 minutes online, no preparation and no commitment.