AI-CLOUD.GR

We work with leading AI providers.

ClaudeGeminiOpenAIAWSVertex AIDatabricksDeepSeekCerebrasQwenStability AI

Guide

AI software from a description: how to describe it so it works

Software for your company can now be built from a description in plain words. You say what it has to do and AI writes the code. How good the result is comes down mostly to the description, so this guide shows how to write one, with an example you can use as a starting point.

What "software from a description" means

You write no specification for a developer and wait no months. 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 into an application with screens, data tables, sign-in for your colleagues and reports. You check whether the result does what you need and ask for corrections in words wherever it does not. More on the approach itself on the Vibe coding page.

Start from the work, not from the screens

The most common mistake is a description that starts with "I want a button here and a table there". AI will build them, but it will not know why. Start from what happens in your company today: who does what, with which data, and where time gets lost. Once the work is described, the right 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, such as a stock check, an approval or an email going out.
  • 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." Out of this description come customers, items, orders, roles, a notification and a report, and it took not a single technical word.

What to put in the description

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

  • The names you use for things, such as "request", "site" or "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 must be notified, who that is, and whether it goes 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. A vague description gives you vague software, and that is why the mistakes below cost more than the rest.

  • Everything at once. A whole ERP system in one sentence. Better one job that works, then 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. Say what has to be kept.
  • Describing the current spreadsheet instead of the work. The software will then copy its 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". For each change you simply carry on the conversation, with no new order and no new deadline. Every change is kept as a version, so you can go back whenever you like. Once the software does its job, you invite your colleagues. Each signs in with their own role, and whatever changes is written to an audit log.

  • Your Excel sheet goes into the software as it is, and nobody has to retype anything by hand.
  • The software runs at its own address with a certificate, and we handle hosting and updates (see Hosting).
  • The data stays in data centres in the Frankfurt region, inside the EU. More under Data security.
  • The code is yours and can be exported 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 hard part comes 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. A detailed comparison is in the guide Can ChatGPT build software for your company?

Examples of software built from a description

Each of these has its own page saying what it does and when it makes sense. They are not templates to choose from. You describe your own work, and the page simply gives you somewhere to start. More on the Solutions page.

If you would rather not write the description yourself

Some companies prefer to tell their work to a person. In that case someone from our team takes on the project with you. They listen, write the description themselves, go through the first version with you and carry it to the end. See Services, Custom software or ask for a quote. For costs, open Pricing.

Frequently asked questions

Do I need to know programming to get software from a description?

No. It is enough to know your own work and be able to explain it to someone else. AI takes care of the code, and we make sure the software keeps running and is maintained.

In what language do I write the description?

In Greek, using the words you use at work. Names, documents and addresses are written in Greek characters and stay that way.

How long should the description be?

To begin with, something the size of the example above is enough. Length matters less than whether it answers the four questions: who works with it, what comes in, what happens and what goes out. 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 kept as a version, so you can go back whenever you need to. Because the account opens at no charge and without a card, you try it first and pay only if it suits you.

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

Open a free account and write in your own words what the software should do. You will see the first version before you spend a cent.