Practice 03 · Digital Products & Platforms
Portals, platforms and dashboards built around how your team works.
This is the front end alone, running on fictional records in your browser: nothing is saved or sent. A production build connects the same screens to your data, sign-in and permissions.
One workspace, three layers: what people see, how work moves, and the records underneath.
Illustration · Sample dataWhat people see and use. Every number on it is read from the layers below.
The steps a record moves through, and the point where a person reviews.
The records themselves: 8 enquiries, 3 projects, 5 tasks, 3 people.
From customer portals to internal tools, built around the data your business already has.
Operational views on live data, and logged-in portals where customers check status and act on it.
The week's numbers live in five tools. One operational dashboard on live data replaces the Monday spreadsheet.
A logged-in portal where customers check progress and act on it, with access control and an audit trail from the start.
Two-sided platforms that match a request with the right supply.
Supply and demand, requests and proposals. Dreilokale matches event organisers with venues from a single request.
A request short enough to finish, with the matching and the follow-up handled behind it.
The screens a team opens first thing: CRM, CMS, queues and review lists, built for speed of use.
The screens the team opens every morning, rebuilt for speed of use rather than for a demo.
The data model carries the most risk, so it is often the first thing we test, sometimes in a Discovery Sprint.
The code, the data and the infrastructure accounts are in your name. Architecture decisions are written down, so the next team starts from a record, not from reverse engineering.
The screens your team uses, with a component library aligned with your design system.
A database schema with migrations and rollback paths, and a typed API to the tools you already run.
Authentication and role-based access, with an audit trail where the work needs one.
Architecture decisions written down, a deployment runbook, and monitoring your next team can read.
Event-location matching platform
One organiser request, a venue matching engine, and the CRM, CMS and email automation behind it. Built end to end and live.
It depends on the scope. We work in phases, put something usable in front of you early, and agree the timeline for each phase in writing before it starts. When the data model or an integration is uncertain, a two-week Discovery Sprint comes first.
Usually Next.js with React, TypeScript in strict mode and Postgres. We choose per project and write the decision down, so the stack is a documented choice your next team can follow.
Platforms, internal tools and dashboards typically cost CHF 15,000 to 25,000, with a ceiling of CHF 45,000 when the scope grows. The total is fixed in the proposal and paid in milestones. A Discovery Sprint has a fixed price of CHF 3,500.
No. Morvion Workspace is a demo on fictional enquiries and projects. It shows the kind of interface we build; a production version adds sign-in, your data and your integrations.
Or the five tools it is spread across. We will ask how the work runs today and what a clear view would change.
Discuss your productExplore the Checkout Lab