Lintejas Engine

All articles

Lintejas · 18 November 2026 · 3 min read

How We Build Software with AI and Still Check Everything

AI can write code fast. Speed without checking ships mistakes. The nine steps Lintejas follows before any change reaches a customer.

AI can now write working software in minutes. That is true, and it is also where many projects go wrong. Code that appears quickly looks finished long before it is.

At Lintejas, most of our building is done with AI agents. Our customers are small business owners who record their sales on our apps and factories that keep safety records on them. They cannot afford our mistakes. So the speed goes into the building, and the time we save goes into checking.

Here is the path every change follows.

1. The need is written in plain words

Before any code, the request is stated the way a customer would say it. "Owners cannot see why a booking was refused." If the need cannot be said plainly, it is not ready to be built.

2. Open choices are decided by a person

Prices, wording that customers will read, anything to do with payments: these are decided by the founder, not by an AI.

3. Visual work starts as a mock-up

For anything a customer will see, a picture comes first, at phone, tablet and desktop sizes. It is cheaper to change a picture than a product.

4. Work happens on its own branch

Nothing is edited on the live product. Each change is built separately so it can be reviewed, or thrown away, without touching what customers use.

5. Automated tests run

Tests check the behaviour, and they check the screens at eight sizes from a small phone to a wide desktop, in English and Tagalog. A change is not called done until they pass.

6. A person reviews it

The change is presented with what was tested and, just as important, what was not. The founder reads it and decides.

7. Release is deliberate

Only an approved change is published. There is no automatic path from an AI's output to a customer's phone.

8. The live version is confirmed

After release we check that the new version is really the one being served. "It should be live" is not the same as "it is live".

9. Mistakes become rules

When something goes wrong, the lesson is written down as one line and added to the project's rules, so the same mistake is not made twice.

Three rules that never bend

  • Honest words. No income promises, no invented reviews, no false urgency, in the products or the marketing.
  • Customer data stays private. Secrets and personal details are never written into code or logs.
  • Nothing unseen goes live. If it was not checked, we say so, and it waits.

Why this matters to you

If you are choosing software for your business, or hiring someone who builds with AI, ask them two questions: "How do you check what the AI wrote?" and "Who approves it before it goes live?"

A clear answer to both is worth more than any feature list.

What would you want checked first in an app you rely on every day?

Building something? Talk to us.

Custom software, automation and AI tools, built with the checks described here.

Get in touch

Next: Six Small-Business Tasks Worth Automating First