Vibe coding in SMEs: which projects deserve a first trial?

Your team probably has a list of ideas for applications. The best first vibe coding project is a frequent task that you understand well and can easily verify. It should teach you something useful without immediately involving the whole business.

Find an observable difficulty

“We waste time” is too vague. “Every quotation request is missing a piece of information” gives you a starting point. For a few days, record omissions, duplicate entry and requests for clarification.

Count how often they happen over a defined period. Ask the person involved to show you their current method. You may discover that an extra field in an existing tool already solves part of the problem.

Use five simple criteria

For each idea, examine its frequency, clarity of rules, ease of verification, data sensitivity and whether someone owns the project. You could score each criterion from one to three and explain each score in a sentence.

This ranking supports a discussion; it is not a scientific formula. A frequent task whose outcome you cannot check does not become a priority simply because it gets a good average score.

Three examples to explore

An intervention preparation sheet could check that essential information is present before printing. An internal calculator could apply a known formula. A questionnaire could recommend resources using explicit answers.

These examples allow trials with fictional data. For each, define the expected output: a complete sheet, a correct calculation or an explained recommendation. The criterion should be visible when someone uses the prototype.

Reduce dependencies in the first trial

A tool that immediately needs customer accounts, payments and synchronisation with your sales software involves several workstreams. Break it down. An initial version can simply demonstrate the journey and produce a result to examine.

Write down what remains manual during the trial. For example, the salesperson copies the summary into the usual system. This makes the limits clear and avoids implying that a connection already works.

Decide before you build

Give the project a validation question: “Can someone who is new to this form prepare a complete request without calling me?” Also set a trial duration and a review point.

If nobody wants to own the project, or its rules change every week, begin by clarifying the organisation. Vibe coding helps make a method tangible. It does not replace agreement about how the work should be done.

At the end, decide whether to continue, simplify or stop. Dropping an idea after a small trial can be useful too: you will have avoided a larger development effort.

Do you have a business task to explore with AI? Discuss your needs with eloRezo.

Content and sources checked on 30 October 2026.