Planning feels like spending before anything happens. In fact it is the stage where changes cost almost nothing.
A concept feels uncomfortable. You pay for something you can't use, and at the end you're holding paper instead of a working solution. The urge to skip it and get started is understandable.
The trouble is that changes get more expensive with every step. That isn't a sales argument; it's the structure of the thing.
Changing a sentence in a concept takes minutes. Changing a sketch, half an hour. Changing a screen that's been built, half a day. Changing something already in use and holding data costs the half day plus the data migration, plus retraining, plus the week where both run side by side.
The same thought, four times the price, purely because it arrived later.
A concept is therefore not primarily a document. It is the phase in which you can still change your mind painlessly. And you will change your mind — that's the normal case, not a failure.
Usually not what people expect. It's rarely the technology.
Most often it emerges mid-build that a small thing isn't small. "We'll need this for business customers too" sounds like an addition and can mean a second pricing logic, a second invoice format and different tax rates. It can be built in — but had it been known from the start, the solution would look different from one with it bolted on afterwards.
The second most common: something gets built that wasn't the actual problem. That happens when the conversation turns to the solution before the workflow. Starting with "we need an app" fixes an answer before the question is settled.
It doesn't have to be thick. Ten readable pages beat forty nobody reads. Five things matter:
The workflow today — who does what, in what order, and where it sticks. Written down literally, not idealised.
The workflow afterwards — the same description, but as it should be. The difference between the two is the actual brief.
What is out of scope. The most valuable section. Naming what stays out prevents the quiet expansion that makes most projects expensive.
Scope in stages. What comes first, what after, what possibly never. That way you can decide after stage one whether stage two still makes sense.
Effort and timeframe, honestly estimated, with a ceiling. An estimate without a ceiling isn't one.
If you read it and don't understand it, it isn't a good concept — however expert it looks. A concept you can't check is one you can't sign off.
Second warning sign: it describes only what will be built, not what changes in your working day. Then the conversation was about the solution and not about the work.
It happens, and it isn't wasted money. A concept concluding that the build doesn't add up, or that an existing off-the-shelf product will do, has saved you many times its cost.
That is a good yardstick when choosing, incidentally: anyone who never advises you against something is selling you something.
If you have an idea and no plan yet — describe it to me in two sentences. Sorting it out is something we can do together.