Custom software cost in Lithuania, 2026: our published prices

Custom software in Lithuania in 2026 costs from €1,200 for a written technical review to €25,000 and more for replacing an old business system. At AFKzona Group a production product build starts at €12,000, an AI agent at €6,000 and an integration at €3,500, each with a written scope and a fixed price agreed before work begins.

Few Lithuanian companies publish prices for system development. Web agencies publish website prices, but a booking system, a back office or an AI agent is usually "price on request". This article puts our numbers on the table, explains what moves a project above the starting price, and shows how to compare a fixed quote with an hourly one.

What does AFKzona Group charge in 2026?

Our starting prices range from €1,200 for the technical part of a tender response to €25,000 for a legacy rebuild, with product builds from €12,000. They are starting prices, not averages: your fixed quote follows a free 30-minute call or, for larger work, a one-week scoping sprint.

An evaluation set is a list of real inputs with the answers you expect, used to prove an AI agent does its job before you accept it. A legacy rebuild is the replacement of an old system that the business still depends on, carried out while that system keeps running.

What drives the cost of custom software?

The price of custom software is set mainly by how many kinds of users it serves, how many other systems it talks to, how much existing data has to move, whether it issues money or legal documents, and how long it must run without attention. The number of screens matters much less than most buyers expect.

The drivers we price, in the order they move the total:

1. User roles. A public site plus one admin role is one system. Add counter staff, managers, contractors and customers with their own logins, and every rule has to be written, enforced and tested once per role.
2. Integrations. Each external system (payments, accounting, a CRM, a government registry) adds its own failure modes: timeouts, duplicate messages, changed formats. Each one needs retries and a log.
3. Data migration. Moving years of records from spreadsheets or an old database is often the riskiest part of a project. It needs mapping, cleaning and a rehearsal before the real move.
4. Money and legal documents. Invoices, deposits and credit notes have to be numbered without gaps, never edited after issue and reconciled against what was actually paid. In our rental system those rules are enforced by the database itself.
5. Reliability requirements. Backups, rollback, monitoring and tests against a real database cost more to set up than a demo, and far less than an outage.
6. Languages and compliance. Lithuanian and English versions, accessibility, GDPR records, and since 2 August 2026 the EU AI Act's disclosure duties for chatbots.

What does not drive the price much is the visual design of individual pages. The expensive part of most business software is the part nobody sees.

Fixed scope or hourly: which is cheaper?

A fixed price is cheaper for the buyer when the work can be written down, because the supplier carries the estimation risk and you know the total before you commit. Hourly billing is fairer when the scope genuinely changes every week, but the total is unknown and the risk of overrun sits with you.

A fixed-scope contract is an agreement where the deliverables, the price and the date are written down before work starts, and changes go through a written change note. Time and materials is billing by the hour or day for whatever work is done.

For comparison, published Lithuanian market rates are hourly. Lemon.io lists senior Lithuanian freelance developers (5–8 years' experience) at $30–38 per hour. On Clutch, Lithuanian development agencies list hourly bands of $25–49 and $50–99. Both were fetched in September 2026. These rates are not directly comparable with a fixed price, because the number of hours is the unknown.

Our view: business systems can be scoped in writing, and a buyer should ask why a supplier won't. For a changing backlog inside your own team, the embedded senior engineer covers it.

What is included in a fixed price?

A fixed price at AFKzona Group covers everything in the written scope: architecture, the build, a senior engineer's review of every change, tests against a real database, deployment with backups and rollback, documentation and handover of the repository and every access. You own the code from the first commit.

In practice the scope document lists:

• Deliverables: the screens, roles, integrations and reports, named one by one.
• Acceptance: how you check each one works. For AI agents, that is the evaluation set.
• Scope boundaries: where the project ends, stated plainly, so the price holds to handover.
• Running costs: hosting and third-party services such as payment fees or AI model usage, paid directly to their providers.
• Payment milestones: 30% to start, 40% at the first working deployment and 30% at handover. Audits and RFP responses are paid on delivery.

Small changes during a project are absorbed. Bigger ones get a written change note with the price and date impact, and nothing is billed that you did not approve.

When is a scoping sprint worth €2,000?

A scoping sprint is worth paying for when the project is large, the requirements live in several people's heads, or there is an old system whose data and rules nobody has written down. In one week it produces a written scope, a data model and a fixed price, and its €2,000 fee is credited to the build.

If you decide not to build with us, you keep the scope document. It is written to be usable by any competent supplier, which also makes it a fair basis for comparing quotes. For public-sector buyers, the same document is a sound starting point for the technical specification of a tender.

How to compare software quotes

Compare quotes on what is written, not on the headline number. A lower figure that excludes data migration, testing or handover of the code is not cheaper. Ask each supplier for the same four things, and put the answers side by side.

1. A named list of deliverables and exclusions. If exclusions are missing, assume they will reappear as extras.
2. Who owns the code and the accounts, in the contract, from the first commit.
3. How the work is tested and reviewed before it reaches production.
4. What happens when scope changes: a written change process with prices, or open hours.

If you want a second opinion on a quote you already have, a code review or a technical due diligence review of the proposed architecture costs a fraction of the build.

Get a fixed price for your project

The full price list, with the scoping sprint and payment terms, is on our pricing page. The services themselves are described on the services page, and the kinds of systems we build are listed under capabilities. To get a scope outline and a price range for your own project, book a free 30-minute call. You leave the call with both, whether you hire us or not.