Guide
AI software from a description: how to describe it so it works
Software for a company can now be built from a description in plain words. AI writes the code and you tell it what the program has to do. How well it turns out depends mostly on the description, so this guide shows how to write a good one, with an example you can start from.
What "software from a description" means
You skip the specification for a developer and the months of waiting. You explain the work in ordinary words, the way you would to a new colleague on their first day, and AI turns that into a working application with screens, data tables, sign-in for your colleagues and reports. You look at what it built and, if something is off, you correct it in words again. The approach itself is covered on the Vibe coding page.
Start from the work, not from the screens
The mistake we see most often is a description that opens with "I want a button here and a table there". AI will build them, but it won't know what they are for. Start instead from what happens in your company today: who does what, with which data, and where the time goes. The screens then follow from the way you work.
- Who will use the software: the owner, sales, the warehouse, the accountant.
- What comes in, such as an order by phone, a supplier invoice or an enquiry from the website form.
- What has to happen next, for instance a stock check, an approval or an email going out.
- What goes out at the end, whether that is a quote, a monthly report, a reminder or a document for the customer.
Example: describing an order system
A good first description can look like this. It is short, yet it answers the four questions above and says 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." From those few lines you get customers, items, orders, roles, a notification and a report, and there isn't a single technical term in the text.
What to put in the description
You don't have to think of everything up front, because the software can be extended as you go. Still, saying the following things at the start saves you most of the corrections later.
- The words your company uses ("request", "site", "repair"), so the software shows them to colleagues the same way.
- Who sees what, and who can change what.
- The rules you know by heart, such as "above this amount the manager approves" or "no address, no order".
- Where your data lives now: an Excel sheet, an old program, a folder of documents.
- When someone needs an email, on which event, and who that person is.
- Which reports you look at every week or every month.
- What you do NOT want, for example a field nobody fills in or a step that only slows people down.
Common mistakes in a description
AI does exactly what you described. A vague description gives you vague software, which is why the mistakes below are the expensive ones.
- Everything at once. A whole ERP system in one sentence. It works far better to get one job running properly and then move to the next.
- No roles. "Everyone sees everything" is rarely true, and it is harder to fix later.
- No examples. Everybody means something different by "a sales report", so say which columns you want to see.
- Technical words for no reason. You don't need to pick a database. Just say what has to be kept.
- Describing the current spreadsheet instead of the work. The software will copy the spreadsheet's flaws along with it.
What happens after the first version
The first version is rarely the final one, and that is fine. You open it, try it with real data and say what you want changed: "add a phone field", "email me as well", "hide prices from the driver". A change is simply the next message in the conversation, with no new order and no new deadline, and each change is saved as a version you can return to. Once the software does what you need, you invite your colleagues. Each of them signs in with their own role, and any action with consequences is recorded in the audit log.
- Your Excel sheet is imported as it is, so nobody has to retype it.
- The software has its own address with a certificate, and we take care of hosting and updates (more under Hosting).
- The data stays in the European Union and is not used to train AI models, as explained under Data security.
- The source code belongs to you, and one button pushes it to your own GitHub repository.
A description to the platform or code from a chat: the difference
You can also give your description to a chat assistant, and it will hand you code. The difference shows up afterwards, because the server, the address, the database, sign-in with roles, backups and maintenance are then all yours to sort out. With us the description turns straight into working software your colleagues can sign in to. There is a fuller comparison in the article Can ChatGPT build software for your company?
Examples of software built from a description
Each of these has its own page explaining what it does and when it is worth it. You don't choose a template. You describe your own work, and the page is just a place to start. The full list is on the Solutions page.
- Stock management software and stock and sales.
- Order management and invoicing software.
- CRM and customers and quotes.
- Appointments and help desk.
- ERP for a company that has outgrown its spreadsheets.
If you would rather not write the description yourself
Some companies would rather talk the work through with a person. In that case someone from our team runs the project with you: they listen, write the description, go through the first version with you and finish the job. Have a look at Services and Custom software, or ask for a written 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, and we look after launching and maintaining it.
In what language do I write the description?
In Romanian, the way you speak at work. Names, documents and addresses keep their diacritics.
How long should the description be?
Something the length of the example above is enough to start. Length matters less than covering the four questions (who uses it, what comes in, what happens, what goes out). The rest gets added after the first version.
What if the software does not come out the way I want?
Tell us what to change and it gets changed, with every step kept as a version you can go back to. Opening an account is free and you don't enter any card details, so you can try it before paying anything.
Can I bring in the data I already have?
Yes. An Excel sheet is imported as it is, without tidying it up first.
Describe your first program
Your account is free and there are no card details to enter. Write the description in your own words and see what comes out before you pay anything.