Custom software: how a project works and what to prepare

Updated: 02.10.2026 · ~7 min read

Most software projects that overrun their budget or deadline share the same cause: unclear requirements at the start. Code gets written fairly quickly once everyone knows what the application has to do. This guide describes what a custom software project for a company looks like, from the first conversation until after launch, and what you can prepare to make it go faster.

The stages of a project

1. The first conversation

A conversation of about 30 minutes about what hurts right now: where time is lost, which errors keep coming back, which reports are missing. By the end you should know whether the problem calls for custom software, an existing product or a combination of the two.

2. Process analysis (discovery)

The company's real workflow is mapped out: who enters the data, who approves, which documents come out at the end, which exceptions occur. The result is a list of features ordered by priority and an estimate split into stages. With it, you decide what to build now and what to leave for later.

3. The first working module

Development starts with the module that delivers the most value, usually the one where the most time is lost today. The first usable result arrives within a few weeks. Short iterations with regular demos let you correct course before mistakes become expensive.

4. Data migration

Products, customers, suppliers and opening stock are moved from spreadsheets or the old system. The migration is done as a trial run first, so you can check the figures before launch.

5. Launch and training

The team is trained on their roles and the application goes live, ideally during a quieter period for the business. The first weeks after launch bring out the small details that never came up in meetings.

6. Maintenance and further development

The application needs security updates, backups and adjustments when legislation or the company's process changes. Further modules are added on the same foundation.

What you can prepare

• real document samples: orders, invoices, delivery notes, reports, including the spreadsheets used today;
• the list of people who will use the application and what each of them does;
• the unusual cases: returns, partial orders, special prices, cancellations;
• the systems the application must talk to: e-invoicing, the accounting software, the online store, couriers;
• one person in the company who can make decisions and answer questions within the same week.

The last point matters more than it seems. A project in which every question waits two weeks for an answer takes proportionally longer.

What drives the cost

The price of a custom application cannot be set properly before the process analysis. The factors that influence it most are:

Factor	Why it matters
Number of modules	Inventory, orders, invoicing, production, reports: each has its own screens, rules and tests
Integrations	Every link to an external system (tax authority, store, couriers, banks) has its own formats and error cases
Business rules	Customer-specific prices, multi-level approvals, cost calculations: the more exceptions, the more effort
Data migration	Old data is rarely clean and has to be checked before import
Mobile or offline use	Warehouse and field applications need synchronization and extra testing

Splitting the work into stages keeps the cost under control: you pay for what you already use and decide step by step whether the next module is worth it.

Who owns the code

Computer programs are protected by copyright. Paying for development does not automatically transfer the rights to the code: in Romania, the assignment of economic rights (Law 8/1996) has to be set out in writing in the contract. Before signing, check what you receive at the end: the source code, the documentation, access to the server and the database. At CONTROL DEVELOPMENT the code belongs to you, is versioned and documented, and can be handed over to another team at any time.

Common mistakes

• asking for every feature in the first version instead of a first module used as soon as possible;
• copying today's spreadsheets exactly, workarounds included;
• no one who can decide on behalf of the company;
• leaving data migration for the last week;
• a contract that says nothing about source code and maintenance.

Examples of the applications we build are on the Custom software page, for instance ERP or warehouse management.