Plan first, then build
Concept & Planning
From the problem to a viable concept, before the first line of code.
A well-thought-out concept saves expensive detours during implementation. We define scope, workflows, data and interface, so it is clear from the start what gets built and why.
In the end you hold a written concept, wireframes or a clickable prototype, the data model with all interfaces and a binding fixed-price quote.
Strategy settles the whether, concept the how
In strategy & consulting we clarify whether a project is worth it and what should be built. The concept phase starts right there and plans how the solution looks in detail.
That covers the requirements, the workflows, the data, the interfaces to your systems and the interface. Everything is written down and made visible before development starts.
Mistakes in the concept are cheap, mistakes in finished code are expensive. An hour of thinking often saves days of rework.
Request a projectWhat the software must do
Sharpen requirements
An idea becomes a clear list of what the software must do, and just as important: what it does not need to do. That keeps the scope tangible and the budget predictable.
The result is a written concept that captures scope, workflows and requirements. A shared foundation both sides can rely on.
First clarify whether and what
On site and online
Understand the workflows
Good software is not made at the desk alone. In an on-site workshop I look at how your business really works and talk to the people who will use the tool later.
For everything else, online meetings are often enough. That keeps the effort small for you, and we still move quickly.
How I work
See it before it is built
Wireframes & prototype
With wireframes or a clickable prototype you see early how the software will feel: which screens exist, which steps are needed and where each piece of information sits.
In feedback rounds we refine the draft until it fits. Changes here cost a few strokes, later in code considerably more.
View delivered projects
The foundation
Data model & interfaces
Which data exists, how does it connect and where does it come from? The data model is thought through cleanly instead of patched later.
Likewise we define which systems get connected, such as inventory, shop or existing databases, and how data flows between them.
More on my technologies
Clarity on cost
Binding fixed-price quote
Based on the concept you get a binding fixed-price quote for the build. Not a rough estimate, but a price based on a well-thought-out plan.
Larger projects I split into deliverable stages, so you have something usable early and the risk stays small.
More on the build
How your concept comes together
-
First conversation
We talk about your project and clarify which scope makes sense for the concept phase.
-
Workshop
On site or online we capture workflows, data and requirements, directly with the people who work with them.
-
Draft
I create the concept, wireframes and data model and define which interfaces are needed.
-
Feedback rounds
We go through the draft together and refine it until it fits.
-
Concept & quote
You get the finished concept and a binding fixed-price quote for the build.
What does a concept cost?
The concept phase is a standalone service and is paid separately. The price depends on the scope of your project, so there is no flat rate. After the first conversation you know what to expect.
You then get the build as a binding fixed-price quote, based on a plan that was thoroughly thought through beforehand.
Request a project
Tell me what is not working for you.
Describe in a few sentences what it is about and what is missing today. The more concrete, the more useful the answer. First response usually the same day.