How it works.
No concept marathon, no black box, no vanishing after launch. Every project follows four clear phases, with real interim results and replies usually within one working day.
How a project runs here.
Each phase has a clear result. If a phase is not right, we do not move on to the next. It is that simple.
I listen. Before I say anything.
Before a single line of code is written, I understand your reality. Not what it says on a form, but what you actually experience: where things get stuck, who is responsible, how much time is lost to manual work?
Result of this phase“Now I know what the real problem is. And whether I am the right person for it at all.”
What I do
- Initial call, free of charge
- A brief record of your processes
- A look at your existing tools
- Finding the bottlenecks
What you contribute
- Time for a conversation
- Someone who knows the process
- A rough idea of the goal
- Honesty rather than perfection
I sketch the solution. Before it is built.
A concept does not mean 40 pages of prose nobody reads. A concept means a clear outline of what will be built, what it costs and when it will be ready. No adjustments on the invoice.
Result of this phase“You know what you are getting, what it costs and when it will be running. No flying blind.”
What I do
- Solution outline, visual and functional
- Fixed-price quote with scope
- A realistic timeline
- Risks and alternatives
What you contribute
- Approval or questions
- Access to relevant data
- Decisions on priorities
- A contact person for questions
I build in the open. Not in a black box.
At regular intervals you see real interim results, give feedback and I adjust. No “four months of silence, then a big launch”. If you want to change something, now is the time. You can see the current status, open quotes and documents at any time in the customer portal.
Result of this phase“The system is running. Clean, documented, handed over, and you know it because you watched it take shape.”
What I do
- Development in clear stages
- Regular demos
- Tests and feedback loops
- Documentation, written as we go
What you contribute
- Feedback on interim results
- Content such as texts and images
- Testers from your team
- Decisions at crossroads
I stay. Even after launch.
Launch is when everyday use begins. I remain available, maintain, extend and optimise. Ongoing support is included as an option in every quote, and you decide how close you want me to be.
Result of this phase“Your system runs and grows with you. You are not on your own.”
What I do
- Maintenance and updates
- Monitoring and backups
- Further development as needed
- Support within the agreed response time
What you contribute
- Feedback when something is not working
- Ideas for new features
- A support agreement of your choice
- Trust rather than micromanagement
FAQ.
What I get asked again and again, and what I prefer to answer openly.
What does a typical project cost?
Every project gets an individual quote. Scope, complexity and requirements decide, not a price list. After the initial call and the concept, you receive a clear fixed price, with no small print and no surcharges afterwards.
Do you offer fixed prices?
Yes, as standard. After phase 02 you receive a fixed price for the agreed scope. Changes to the scope are discussed in advance and costed separately, never quietly added on.
How are later changes billed?
Small adjustments at an agreed hourly rate, larger extensions via an additional quote. You always know in advance what something will cost.
How long does a typical project take?
That depends on the scope. I estimate the timeline realistically in the concept and say honestly when a deadline is getting tight. Half-promises help nobody.
When can we start?
The initial call usually within a few days. The project start depends on my workload; I will give you the date as soon as I confirm.
What if it is really urgent?
Sometimes it can be done faster, sometimes not. There is no express surcharge, but I will tell you openly whether your preferred date is realistic before I commit.
Who is my contact person?
Me personally, from the first conversation until after launch. No sales team, no handover to project managers. On larger projects, specialists from my network join in, but I remain your contact.
How often do we meet?
Regularly: more often during analysis and concept, then in clear stages during delivery. On site in Saxony or by video, whichever you prefer. In between by email, Slack or Signal.
What do I need to provide as a client?
Not much, but the essentials: time for feedback, content such as texts, images and logo, and access to relevant systems. And honesty: tell me if something is not right, not just at the end.
Who looks after the system after launch?
I do. Ongoing support is included as an option in every quote; we agree the scope and response time individually. If you want to take it over yourself later, the documentation is made for exactly that.
What if I want to extend it later?
I build for extension from the start. New features, languages or integrations usually work without a rebuild. I estimate the effort, you decide.
Who owns the code and data?
You do. Always and completely. The code stays with you or in your Git, the data on servers of your choice, preferably in Germany. No lock-in; you can switch at any time.
Sounds like a good framework?
Phase 01 already starts in the free initial call. No commitment, no sales pitch, just listening.