What custom software costs in Moldova and Romania in 2026

Software companies do not publish prices, and the reason is honest: the same sentence in a brief can mean three weeks or three months. That does not make ranges useless. It makes them a starting point you can plan around.

Below are our own 2026 ranges, taken from delivered work, for companies with 10–200 employees. We are based in Chișinău and our rates reflect that — the clients they are quoted to are in several countries.

The ranges, by project type

• A single automation — invoicing, one report, one sync between two systems: 4,000–12,000 EUR, 2–4 weeks.
• ERP to online store integration, two-way, with stock and statuses: 12,000–30,000 EUR, 4–8 weeks.
• Company website, custom build, technical SEO, CMS: 6,000–20,000 EUR, 4–8 weeks.
• Online store, B2B or B2C, integrated with your ERP: 25,000–70,000 EUR, 3–5 months.
• Mobile app, one codebase for both platforms: 18,000–80,000 EUR, 2–6 months.
• Internal platform — several roles, back office, three or more integrations: 60,000 EUR and up, delivered in stages.

Two notes on reading these. First, the low end assumes your data is in reasonable shape and one person on your side can make decisions. Second, projects that sit between two rows cost the higher one.

What pushes the number up

The systems you already run. A documented API is a week. An ERP with no API, where we read a database or parse exported files, is three to five weeks and a maintenance agreement. This single factor moves estimates more than anything else.

Data that needs cleaning first. If the same client exists three times under three names, that has to be fixed before automation, or the automation faithfully multiplies the mess. Budget for it as its own phase.

The number of people who must approve. A project with one decision-maker moves at one speed. A project where every screen needs three departments to agree moves at another. This is not a technical cost, but it is real and it shows up in the timeline.

Exceptions. “It always works like this, except when…” — every one of those clauses is scope. Five per cent of orders being atypical can be a third of the build.

Fixed price, time and materials, or capped

Fixed price works when the scope is genuinely closed: a website, a defined integration, a single automation with known rules. You get budget certainty. You pay a risk premium — typically 15–25% — and changing scope means a change order.

Time and materials works when the scope will be discovered as you go, which is most platform work. You pay for what you use. It requires trust and visible progress, which is why we deliver in two-week increments you can stop after.

Capped time and materials is the middle we use most: billed by actual work, with a ceiling we cannot exceed without your written agreement. You get the flexibility of one and the sleep of the other.

Whatever the model, the payment schedule should follow delivery, not the calendar. If the schedule pays out on dates rather than on working software, the incentive is wrong.

How to read an estimate

A usable estimate names four things. If any is missing, ask before comparing prices:

1. Assumptions
   • Which systems, which API versions, whose design, whose content.
2. Exclusions
   • What is explicitly not in the number. This is the most informative section and the one most often absent.
3. Phases
   • What lands first, and what you can cancel after.
4. After launch
   • What maintenance costs per year, and what is covered.

Budget 15–20% of the build cost per year for maintenance on anything with a mobile app or a third-party integration in it. Platforms change under you whether or not the project is finished.

Two signals worth acting on

A firm price on the first call is a bad sign. Nobody can price an integration before seeing the API documentation. A number given that fast is either padded heavily or will arrive as change orders later.

An estimate with no exclusions is not an estimate. It means nobody has thought about where the edges are, and you will find them together, at your expense.

What to bring to the first conversation

You will get a far more accurate range if you arrive with: which systems are involved and whether they have APIs, roughly how many records and transactions per month, who decides on your side, and what the deadline is driven by. Fifteen minutes of preparation moves an estimate from a guess to a range you can plan against.

We reply within 24 business hours with concrete questions and a first estimate. No mandatory call.