Most messages I get start with the same sentence: “I have a project but I don’t know where to start.” This is written for the person saying it. You don’t need technical knowledge — you need the order of the decisions.
What first, how second
The usual first mistake is starting from technology: “Should it be React? Should we build an app?” The first question is different: whose work does this software make easier, and how? If you cannot say it in one sentence, the scope is not clear yet.
- Who will use it? (customers, staff, or both)
- Which task does it make easier? (booking, order tracking, reporting)
- How is that task handled today? (paper, WhatsApp, spreadsheets)
- What does success mean? (for example, fewer phone bookings)
Where the budget becomes clear
The budget becomes clear once the scope is written down. After the first call I write out the screens and the scope; the price and the timeline live inside that document. If the scope grows, we discuss the difference beforehand — no surprise invoice at the end.
Who you should work with
- Someone who asks about your business, not your technology
- Someone who puts scope and price in writing
- Someone who can show a working build every week
- Someone who does not disappear after delivery
Changes are cheap in the prototype and expensive after launch. That is why the first two weeks are the most valuable.
One paragraph is enough
You do not need technical detail when you write to me. What your business does, where it gets stuck, what you want to happen — one paragraph is enough. We work out the rest together.
Was this useful?
Rate it — you can change your vote later.
