AI-CLOUD.RO

We work with leading AI partners.

ClaudeGeminiOpenAIAWSVertex AIDatabricksDeepSeekCerebrasQwenStability AI

Guide

Can ChatGPT build software for your company?

In short, yes, and it is only fair to say so plainly. A chat assistant writes code that works, and for a formula or a small script that is often all you need. A program your company uses every day needs more than code, though. Below you will find what you get out of the conversation, what is still missing afterwards and how long the road to working software really is.

The short answer: yes, but code is not yet a program

Ask ChatGPT to “build me a stock management program” and you will get code, usually well written and explained step by step. Some versions can even run a small piece of it on the spot and show you the result, so far so good. The gap shows up the next morning, when three colleagues want to open the same program on different computers and expect yesterday’s data to be there. What you take away from a chat is code and explanations. Business software is a system that runs at an address, keeps its data, knows who each user is and changes when the work changes. Somebody has to do everything in between, and the real question is who that will be.

  • Hosting: where the program runs and who keeps it on.
  • Data: the database, where it physically sits, and backups.
  • Users: accounts, roles and a trail of who changed what.
  • Maintenance: next month’s change and what breaks on an update.
  • Security: passwords, keys and the data you paste into a conversation.

What a chat assistant does well

In fairness, for plenty of small tasks an AI chat is exactly the right tool and you need nothing more. It explains things you don’t follow and drafts a first version, and it will answer questions at any time of day or night. When the job ends with a piece of text, a table or a script you run once, the conversation can see it through to the end.

  • An Excel formula or macro that saves you an hour of copying.
  • A small script that renames files or merges two spreadsheets.
  • The structure of a table: which columns a customer or stock list needs.
  • A first specification: what the program must do, which screens, who sees what.
  • Explaining an error message or a piece of code someone else wrote.
  • Texts: customer emails, product descriptions, an internal policy.

Hosting: where the program runs

Code from a conversation doesn’t run anywhere until someone puts it on a server. For that you pick a hosting provider, open an account, upload the code and start it. After that the program needs an address your colleagues can remember, which means a domain, plus a certificate so the connection is encrypted over HTTPS and the browser shows no warnings. Nobody thinks on day one about who will notice that the program stopped overnight, or who restarts it before the first person gets to the office. Company software has to keep running while the person who set it up is on holiday.

Data: where it lives and who keeps it

Without a database, a program forgets everything each time it restarts. So on top of the server you need a database, which someone creates, connects to the program and looks after so that yesterday’s data is still there tomorrow. Then your accountant or a larger customer will ask where the data physically sits, in an EU country or somewhere else, and who can get at it. Most people only think about backups after losing something for the first time, and that is when they learn that having backups isn’t enough, you also have to be able to restore from them. There is also the first day, when years of company records already sit in Excel and have to be imported without anyone typing them in again.

Users, roles and the audit log

Once the program has more than one user, a few needs appear that the first version of the code won’t cover on its own. Each person needs their own login and password instead of a shared one on a sticky note by the screen. Nor should everyone see everything, since sales staff have no business in payroll and the warehouse has no reason to delete customers. When a quantity or a price has changed, you have to be able to find out who changed it and when. Otherwise every gap at stocktake turns into an argument that never ends.

  • Password login, password reset and closing the account of someone who leaves.
  • Roles that decide who can view the data, who can edit it and who approves.
  • An audit log listing every change together with who made it and when.

Maintenance: next month’s change

Company software never stays the way it was first built. Next month you will want a new field, a report for the accountant or a discount rule for a big customer. Going the chat route, that means finding the current code, pasting it back into the conversation and explaining once again how the system is put together, since a new conversation has no way of knowing your program. Then you copy the changed pieces back and hope nothing else broke. After every change someone has to put the new version on the server. The code also relies on libraries that receive updates, and after one of them something that worked yesterday may refuse to start today. There has to be someone who notices and fixes it.

Security on the do-it-yourself route

The list below isn’t about any particular vendor. These are the usual risks when a program is put live by someone who doesn’t do that for a living. Nobody sees them on day one, so they are easy to leave for later.

  • User passwords stored in plain text in the database instead of an irreversible hash.
  • Access keys and passwords written straight into the code, then copied into conversations, emails or a public repository.
  • Real customer data pasted into a conversation as an example, with nobody remembering where it went.
  • A server left without updates for months, because nobody owns that job.
  • An admin page left open, with no password, at an address anyone can find.

The realistic road, step by step

Here is the usual road from conversation to program with no shortcuts, so you can see how long it is. Each step can be learned. What matters is whether anyone in the company has the time to do it, and then to do it again for every change. In a small firm that person tends to be the owner, a colleague who is “good with computers” or a younger relative, all of whom already have a day job.

  • Describe the program in the conversation and get the code.
  • Copy the code into files and install the tools it runs with.
  • Choose a hosting provider, create the account and upload the program.
  • Create the database and connect it to the program.
  • Buy or connect a domain and set up the certificate for HTTPS.
  • Start the program, read the errors, paste them back into the conversation and fix things until it works.
  • Add accounts, roles and backups, which the first version did not have.
  • Next month: the same road for every change.

What our platform adds

With us you start just as you would in a chat, by describing the program you need in English or Romanian. What you get at the end, though, is the application already running at its own address, with no code left for you to install. First comes a description of what the system must do, then how it will be built, and only after that the code, and you approve each step. The steps listed above, from the server to the backups, are no longer your job.

  • Hosting from day one, with the address, certificate and updates taken care of for you (more on Hosting).
  • A database and file storage included in the project, with backups and rollback to an earlier point.
  • The infrastructure sits in the Frankfurt region of Germany, inside the European Union; details are on Data security.
  • Colleagues sign in with their own accounts and roles, and every action with consequences stays in the audit log.
  • Your current Excel table is imported as it is, and the data comes back out as a table at any time.
  • The source code is yours: from the studio you push it with one button to your own GitHub repository.
  • For a change you open a new conversation in the same project, which already knows its own system, so there is no code to shuttle back and forth.
  • Your own domain, with a certificate, if you want the program at the company’s address.

When ChatGPT alone is enough, and when it is not

Plenty of needs don’t call for a platform at all. If the first few lines below describe you, stick with the chat and spend nothing extra. If the later ones do, you have already moved from “code” to “program”, even if you don’t call it that yet.

  • The chat is enough: you need a formula, a one-off script, some text or an idea for how to lay out a table.
  • The chat is enough: a tool only you use, on your own computer.
  • The chat is enough: you already have a developer who hosts and maintains the code.
  • Not enough: several people use the program, each on their own computer.
  • Not enough: the data belongs to customers, and someone may ask you where it is.
  • Not enough: you need to know who changed a figure and when.
  • Not enough: the program changes often and nobody in the company wants to be “the server person”.

Programs companies describe

Most companies start from a system they have so far kept in spreadsheets or notebooks. Each page below shows what a program like that does. They are examples to start from, not customer stories. There is no template to choose either; you simply describe your own work. How to do that, with an example, is in the guide AI software from a description.

What it costs and how to start

A chat assistant usually comes with a subscription, and the hosting, the database and the hours of whoever sets it all up are paid for separately. We have no subscription. You pay with prepaid credits for what you use, with nothing charged per user, and every live project carries a daily hosting fee. A paused project costs nothing. Opening an account is free and you won’t be asked for card details, so you can describe the program and look at the result before paying anything. Packs and prices are listed on Pricing. If you would rather not go it alone, we can build it with you (see Services), and if you want everything in black and white, ask for a written quote with scope, timeline and price.

Frequently asked questions

Can I build a stock management program with ChatGPT?

You can get the code from it, and for a tool that only you use that may well be enough. Once several colleagues work in the program, you also need hosting, a database, accounts with roles and a person to look after it. On the platform all of that comes with the application.

Is AI-CLOUD Romania ChatGPT?

No. AI-CLOUD Romania is a separate platform, run by 3D Code EOOD, and has no connection with OpenAI. We use leading language models from several makers, all of them reached through the platform and paid for from credits.

Do I need to know programming?

No. It is enough to be able to explain what information goes in, what should happen to it and what comes out at the end. The AI writes the code, and we take care of running and maintaining it. There is more on Vibe coding.

I already have code from a conversation. Can I use it?

You can start from what you have, since the description and the ideas in it help with the first task. A project that is already finished can also be hosted with us on the same terms (see Hosting).

What happens to the data in our current Excel?

The spreadsheet is imported in the shape it is in, and you keep the file. The steps are in the guide How to stop using Excel for stock.

How do I make a change once the program is running?

Open a new conversation in the same project and describe what you want changed. You don’t paste code or upload anything to a server, and you don’t wait for a new order to be signed off either.

Who owns the program if I decide to leave?

It belongs to you. You push the source code to your own GitHub repository, and you can export the data as a table whenever you like. If the credits run out, the project simply pauses and nothing is lost.

Describe the program, not just its code

The account costs nothing and you don’t need a card to open it. Write down what the program has to do, in English or Romanian, and try the running application before you pay anything.