Guide
AI software from a description: how to describe it so it works
These days software for your company can be built from a description written in plain words. You explain what it has to do and AI writes the code. How good the result is depends mostly on how well that description is written, and this guide shows you how to write one, with an example you can use as a starting point.
What "software from a description" means
Instead of drawing up a specification for a developer and waiting months, you describe the work in ordinary language, much as you would to someone starting at the company today. AI turns that explanation into a working application with screens, data tables, sign-in for your colleagues and reports. You judge what you see on screen without looking at the code, and you refine it with further instructions. If you want to know more about the approach, see the Vibe coding page.
Start from the work, not from the screens
We often see descriptions that open with "I want a button here and a table there". AI will put them in, but it won’t know what they are for. It works better to describe what happens in the company today: who handles each task, which data they work with and at what point time gets wasted. Once that is clear, the screens follow naturally.
- Who will use the software: the owner, sales staff, the warehouse or your gestoría.
- What comes in, for instance a phone order, a supplier invoice or an enquiry from the website.
- What has to happen to it: check stock, get approval, send an email.
- What goes out at the end, whether a quote, the monthly report, a reminder or a document for the customer.
Example: describing an order system
A good first description might look like this. 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." From that text alone you already get customers, items, orders, roles, a notification and a report, and there isn’t a single technical word in it.
What to put in the description
You don’t need to have everything worked out at the start, because the software is filled in as you go. Even so, some things save you a lot of corrections if you mention them early.
- The names you use for things ("request", "site", "repair"), so your colleagues find the same words in the software.
- Who can see each thing and who can change it.
- The rules everyone knows by heart, such as "above this amount the manager approves" or "no address, no order".
- Where your current data lives: an Excel sheet, an old program or a folder of documents.
- When someone needs to be notified, who that is and what triggers it (notifications go by email).
- The reports you check every week or every month.
- What you do NOT want, for example a field nobody fills in or a step that only slows things down.
Common mistakes in a description
AI does exactly what you described to it. A muddled description gives you muddled software, which is why these slips end up costing the most.
- Asking for everything at once. A whole ERP system in one sentence. It works far better to get one job running and then move on to the next.
- Forgetting about roles. It is hardly ever true that "everyone sees everything", and fixing it later takes more effort.
- Giving no examples. "A sales report" means something different to each person, so say which columns you want to see.
- Using technical terms for no reason. You don’t need to choose a database; just say what has to be stored.
- Describing the current spreadsheet rather than the work you do with it. The software would end up copying its flaws too.
What happens after the first version
It is normal for the first version not to be the final one. You open it, try it with real data and ask for whatever changes are needed: "add a phone field", "send me the email too", "don’t show prices to the driver". Changes are requested in the same conversation, with no new order or deadline, and each one is saved as a version you can go back to. Once the software does the job, you invite your colleagues. Each of them signs in with their own role, and actions with consequences are kept in the audit log.
- Your Excel sheet is imported just as it is, with nothing retyped by hand.
- The software runs at its own address with a certificate, and we host and update it (see Hosting).
- Your applications’ data is kept in the European Union and is never used to train AI models. We explain this in Data security.
- The code is yours and goes to your own GitHub repository with one button.
A description to AI or code from a chat: the difference
A chat assistant will also take a description, and it will give you code back. The difference lies in what comes next, because the server, the address, the database, role-based sign-in, backups and maintenance are all down to you. Here the description turns straight into working software that your colleagues can already sign in to. We compare the two in detail 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 pays off. Treat them as inspiration: you don’t choose a template, you describe your own work. There are more on the Solutions page.
- Warehouse management and stock and sales.
- Order management and invoicing.
- CRM and customers and quotes.
- Appointments and bookings 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 explain their work to a person. In that case someone from our team takes the project on with you from start to finish: they listen, write the description, go through the first version with you and finish it off. There is more on Services and Custom software, or you can 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 Spanish, the way you speak at work. Names, documents and addresses keep their accents and ñ.
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. Signing up is free and you won’t be asked for a card, 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
Opening an account costs nothing and we won’t ask for a card. Write down in your own words what you need and see the result before you spend a cent.