Yes, and it is a step of its own in the journey. Between the moment you describe your activity and the moment the application is built, a plan screen shows you what is about to be produced: the views, the data entities, the indicators, the values of your choice lists. Everything there can be changed — added, renamed, reordered, hidden, deleted — and nothing is built until you approve it. On top of that comes a point people often discover too late elsewhere: the size of the application is DERIVED from your description, it does not come from a catalogue of features to tick. This page states exactly what can be cut, at what moment, and what that does not solve.
The real risk is not too little, it is too much
Market figures all say the same thing, and they say it on both sides of the Atlantic. In France, a large share of self-employed people abandon their management tool within the first six months. In the United States, most small businesses use less than half of their software's features, and one in three abandons it within the year. The dominant cause is neither price alone nor missing features: it is the opposite — a tool designed for a team of fifty, two hundred features of which fifteen get used, and a complexity that only shows up at the first real action.
That is a risk a generation tool can reproduce exactly, and it should be said plainly: describe your need in large-company vocabulary and you will get a large-company application. So the question “can I remove what I don't need” is not a comfort detail. It is the question that decides whether you will still be using your tool in six months.
The size of the application is derived from your description
A generated application does not come out of a catalogue: its structure is deduced from what you wrote. The number of views follows a tier read from your description — an everyday need, plainly stated, gives an application of four to six views; an intermediate need, six to eight; a rich or multi-service need, beyond that. So you are not, in the literal sense, paying for features you do not use: they are not produced.
The corollary is the one thing to keep in mind before writing: describe the trade as you live it, not as a tender would phrase it. “I'm a dog groomer, I want to track my appointments, my customers and their animals” and “multi-site management platform with compliance and flow monitoring” do not produce the same application, and the first is the one still open in six months. If the need genuinely grows, the application can grow with it — it is the reverse order that never works.
The plan can be reread — and cut — before anything is built
Once your description has been analysed, the plan screen presents the proposed structure before anything is built. Views can be added, renamed, reordered, duplicated, hidden and deleted. Data entities — your customers, your jobs, your items — can be added, edited and removed, and the plan suggests others you are free to ignore. Dashboard indicators can be added and deleted one by one. Down to the values of your choice lists, which can be adjusted: the technical identifier as well as the displayed label.
A single safeguard is in place, and it works in your favour: hiding the LAST visible view is refused, because an application with no navigable screen makes no sense. Everything else is yours to change. And approving the plan is precisely what triggers the build: until you approve, nothing is produced — you cut before, not after.
What it does not solve
Cutting in the plan is no substitute for knowing what you need, and the plan does not show finished screens: it shows a structure. What you judge there is a skeleton — which views, which data, which indicators — not a layout. A view deleted by mistake is not lost for good either: the description can be replayed and the application can be evolved afterwards, which is the subject of another question in this hub.
The most effective safeguard remains upstream, and it fits in one sentence: start small on purpose. An application of five views that gets opened every morning beats an application of twelve where only three are ever visited — which is exactly the gap the abandonment figures above measure. The plan exists to make that choice visible and reversible before it costs anything.