AICLOUD.BG

Working with leading AI partners.

Claude Gemini OpenAI AWS Vertex AI Databricks DeepSeek Cerebras Qwen Stability AI

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 tell it what the program has to do. How good the result is depends mostly on the description, so this guide shows how to write one and gives you an example you can use as a starting point.

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 explain it to a new colleague on their first day, and AI turns that explanation into a working application with screens, data tables, sign-in for your colleagues and reports. You judge it by how it works (you never have to read the code), and when something is off you say so in new words. There is more on the approach itself on the Vibe coding page.

Start from the work, not from the screens

Descriptions most often start with "I want a button here and a table there". AI will build them, but it will have no idea why they are there. Start instead from what happens in your company today: who does what, which data they work with, and where time gets lost. Once the work is clear, the screens follow from it.

  • Who will use the software: the owner, sales, the warehouse, the accountant.
  • What comes in, for example an order by phone, a supplier invoice or an enquiry from the website.
  • What has to happen next: a stock check, an approval, an email to someone.
  • What goes out at the end (a quote, a monthly report, a reminder or a document for the customer).

Example: describing an order system

This is what a good first description can look like. It is not long, but 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 this description you get customers, items, orders, roles, a notification and a report, and there is not a single technical word in it.

What to put in the description

You do not have to think of everything at once, because the software can be extended later. If you mention the following at the start, though, you will save yourself the most corrections.

  • The names you use for things ("request", "site", "repair"), so your colleagues see them that way too.
  • Who sees what, and who can change what.
  • The rules you know by heart today: "above this amount the manager approves", "no address, no order".
  • Where your current data comes from: an Excel sheet, an old program or a folder of documents.
  • When somebody should get 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, such as a field nobody fills in or a step that only slows things down.

Common mistakes in a description

AI does exactly what you described. When the description is vague the software comes out vague as well, so the mistakes below are the most expensive ones.

  • Everything at once. A whole ERP system in one sentence. It is better to get one job working first and move on to the next one after that.
  • 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. Say what has to be kept.
  • Describing the current spreadsheet instead of the work. The software then copies the spreadsheet’s flaws as well.

What happens after the first version

The first version is rarely the last, and that is normal. 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 and no new deadline, and every change is kept as a version you can go back to. When the software does the job, you invite your colleagues. They sign in with their own roles, and every action with consequences is recorded in an audit log.

  • Your Excel sheet is imported as it is, so nobody has to retype it.
  • The software runs at its own address with a certificate, and we take care of hosting and updates (see Hosting).
  • The data is stored in the European Union and is never used to train AI models. Details are in Data security.
  • The code is yours and you can export it at any time.

A description to AI or code from a chat: the difference

You can give a description to a chat assistant too, and it will give you code back. The difference shows up afterwards, because the server, the address, the database, sign-in with roles, backups and maintenance are all left to you. Here the description leads straight to working software your colleagues sign in to. There is a detailed 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 makes sense. You do not pick a template. You describe your own work, and the page gives you somewhere to start. There are more examples on the Solutions page.

If you would rather not write the description yourself

Some companies prefer to explain their work to 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 then finish it. See Services, Custom software or ask for a quote. What it all costs is listed under Pricing.

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; launching and maintaining it is our job.

In what language do I write the description?

In Bulgarian or English, the way you speak at work. Names, documents and addresses can stay in Cyrillic.

How long should the description be?

Something the length of the example above is enough to start with. Answering the four questions (who, what comes in, what happens, what goes out) matters more than length. 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, 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

Creating an account costs nothing and you do not need a card. Write the description in your own words and see what comes out before you have paid anything.