Platform & web development

Digital platforms are not born on a drawing board. I accompany them from strategy to technical implementation and shape how the people involved work together along the way. Each stage is usable on its own.

A platform is not a product. It is a place where several parties do something with each other. Anyone who builds one decides less about technology than about rules: who may take part, who gets what out of it, and what happens when somebody ignores them. The technology comes afterwards, and it is the easier half.

The work therefore runs in three stages, and each stands on its own. You can stop after the strategy and still have something to show for it.

Platform strategy

A platform strategy mobilises an ecosystem so that it takes part in creating value. To do so it combines several elements: narrative, technologies, rules, channels, contexts, services, protocols and more. I help you identify these elements, make them visible and bring them together into a strategy.

The questions involved are uncomfortable, and they come early. Which problem does the platform solve, and for whom, in a way that brings that person back? What makes the other side start at all while nobody is there yet? And what would be the reason to leave again?

The result is a picture of the ecosystem: its actors, the paths between them and the points where something is created. It is not a business plan and not a market analysis, but the ground on which you could write both.

Platform design

Platform design works out the processes and determines which actors are to take part. Incentives, the benefit for every side and the interplay of those involved count here as much as the technical translation of the platform concept.

This is where the strategy becomes something you can draw: who puts something in, who takes something out, where moderation happens, where a rule decides and where a person does. This includes the unpleasant part: what happens to contributions nobody wants, and who is responsible for that.

Incentives are the core. A platform where one side works and the other harvests lasts exactly as long as the first side has no alternative.

Implementation

Now the concept becomes software. That involves conception, development and process design. I build with proven open-source parts rather than dependencies that turn expensive later, and I build so that somebody else can develop the software further in five years.

It is built in stages that are usable one by one. The first version may be a list two departments maintain together, the second the same list with an interface. That is slower than one grand launch, but it has an advantage that outweighs this: after every stage you see whether the assumption from the strategy holds, and you can change course while that is still cheap.

Process design covers what happens around the software. Who maintains the content, who answers enquiries, who decides on an exception? A platform without those answers runs technically and stands still anyway.

Scope

I take on strategy, design and implementation together, so nothing is lost between the stages. When a project grows beyond one person, I bring someone in. Responsibility for the result stays with me.

Operations are not included. I hand over a platform that you or your hosting provider keep running, and I do not provide on-call cover. Nor do I do the marketing a platform needs so that the first side turns up at all. And if the strategy shows that there is no second side, I say so instead of building a platform for nobody to stand on.

What you get

  • From one source

    Strategy, design and build, with nothing lost in handovers between providers.

  • Open standards

    Proven open source components instead of dependencies that get expensive later.

  • Built to maintain

    An architecture someone else can still develop further in five years.

  • Usable in stages

    Every stage stands on its own, no all-or-nothing at the end of the project.

Process

  1. 1

    Strategy

    Clarify the ecosystem, the actors and the value proposition.

  2. 2

    Design

    Shape processes, incentives and how the people involved work together.

  3. 3

    Concept

    Translate the platform concept into a technical design.

  4. 4

    Build

    Development, process design, going live.

Cost

Billed by person-day, as a senior consultant. I will tell you the day rate in our first conversation, together with an estimate of how many days your project needs. Both binding, before you decide.

Where the scope can be drawn clearly, I also offer a fixed price. I will tell you which of the two comes out cheaper.

Related services

First the prototype, then the platform

While requirements are still moving, a prototype is the cheaper route to clarity, and it arrives in days, not months.

To prototyping →

Let us talk about your platform.

Let us talk about your project.

Call +49 228 629 380 60 I can be reached on working days. If I cannot pick up, I will call you back. Book appointment Take a free slot in the calendar A short conversation clears up a lot.