Guide
AI software from a description: how to describe it so it works
Today software for your company can be built from a description in plain words: AI writes the code and you only say what it has to do. The result depends mostly on how well that description is written, so this guide shows how to write a good one, with an example you can start from.
What "software from a description" means
Instead of writing a specification for a developer and waiting months, you explain the work in ordinary words, the way you would to a colleague on their first day. AI turns that explanation into a working application with screens, data tables, sign-in for your colleagues and reports. You never need to read the code: you look at what you get and, if something is off, explain it again. More on the approach itself on the Vibe coding page.
Start from the work, not from the screens
The most frequent slip is opening with "I want a button here and a table there". AI will add them, without knowing what they are for. It works better to start from what happens in your company today: who does what, with which data, and where time gets lost. Once the work is described well, the screens follow on their own.
- Who will use the software: the owner, sales, the warehouse, the office.
- What comes in: an order by phone, a supplier invoice, an enquiry from the website.
- What has to happen, for example checking stock, getting an approval or sending an email.
- What goes out at the end: a quote, a monthly report, a reminder or a document for the customer.
Example: describing an order system
Here is an example of a good first description. It is short, yet it answers the four questions above and makes clear what matters: "An office-supplies delivery company, five people. Orders come in by phone and by email, and today we type them into a spreadsheet. I want software where a salesperson enters an order: customer, items, quantities, address and delivery date. If an item is out of stock, that should show straight away. The driver sees only their own deliveries for the day and marks them delivered from the phone. The customer gets an email when the order goes out. At the end of the month I want a report by customer and by item. Salespeople must not see the reports." These few lines give you customers, items, orders, roles, a notification and a report, and there is not a single technical word in them.
What to put in the description
You do not have to foresee everything at once, because the software grows as you go. A few things, though, save you a lot of corrections if you mention them at the start.
- The names you use for things ("job", "site", "call-out"), so your colleagues find them the same way.
- Who sees what, and who can change what.
- The rules you know by heart today: "above this amount the owner approves", "no address, no order".
- Where your current data comes from: a spreadsheet, an old program or a folder of documents.
- When somebody needs to be told, who that is and after which event (notices go out by email).
- Which reports you look at every week or every month.
- What you do NOT want: a field nobody fills in, a step that only slows things down.
Common mistakes in a description
AI does exactly what you described, so a vague description produces equally vague software. These are the mistakes that cost the most corrections later.
- Everything at once. A whole ERP system asked for in one sentence. It works better to get one job running and then move on to the next.
- No roles. "Everyone sees everything" is rarely true, and it is harder to fix later.
- No examples. "A sales report" means something different to everyone. Say which columns you want to see.
- Technical words for no reason. You do not need to name a database; just say what has to be kept.
- Describing the current spreadsheet instead of the work, which means the software copies its flaws as well.
What happens after the first version
The first version is hardly ever the last, and that is fine. You open it, try it with real data and say what to change: "add a phone field", "email me as well", "hide prices from the driver". To change something you simply carry on the conversation, with no new order or deadline, and every change becomes a version you can roll back to. When the software does the job, you invite your colleagues. They sign in with their own roles, and every action with consequences stays in an audit log.
- Your spreadsheet is imported as it is, with its own columns, so nothing is retyped by hand.
- The software runs at its own address, with a certificate, and we host and update it (see Hosting).
- The data is stored in the European Union and is not used to train AI models. The details are in Data security.
- The code is yours: you push it to your own GitHub repository with one button, and the data comes out as a table whenever you want.
A description to AI or code from a chat: the difference
You can give the same description to a chat assistant, and it will hand you code back. The trouble is what comes after, because the server, address, database, sign-in with roles, backups and maintenance are all left to you. Here the description takes you straight to working software your colleagues can already sign in to. A detailed comparison is in the article Can ChatGPT build software for your company?
Examples of software built from a description
Each of these has a page explaining what it does and when it is worth it. Treat them as ideas to start from: in the end you describe your own work, with no template to choose. More on the Solutions page.
- An inventory system and a stock and sales system.
- Order management and invoicing.
- A CRM and a register of customers and quotes.
- Appointment booking and enquiry handling.
- An ERP system for a company that has outgrown its spreadsheets.
If you would rather not write the description yourself
Some people would rather talk their work through with a person. In that case a single person from our team runs the project with you. They learn the process and write the description, then go through the first version with you on your real data and see it through to the end. See Services, Custom software or ask for a quote. Prices are on the Pricing page.
Frequently asked questions
Do I need to know programming to get software from a description?
No. You need to be able to explain what comes in, what has to happen and what goes out. AI writes the code; running and maintaining it is our job.
In what language do I write the description?
In Italian or English, the way you speak at work. Names, documents and addresses keep their accents.
How long should the description be?
About as long as the example above is enough to start. It matters more that it answers the four questions (who, what comes in, what happens, what goes out) than that it is long. The rest is added after the first version.
What if the software does not come out the way I want?
You say what to change and it changes. Every change is a version that can be rolled back. You can sign up for free without a card and try it before paying for anything.
Can I bring in the data I already have?
Yes. A spreadsheet is imported as it is, without tidying it up first.
Describe your first program
Create a free account, no card required. Write your description in your own words and look at the result before you spend a cent.