Custom software development: what the process looks like and ask the agency

Software development tailor-made makes sense when a ready-made solution from the market does not monitor how the company really works — when the work is reduced to Excel spreadsheets, double-entering the same data in multiple places, or manually connecting tools that are not made to work together. Before going into development, it is worth knowing what the process looks like, how long it takes and what distinguishes a serious offer from one that later outgrows the budget.

When to buy finished and when to order the production

Ready-made software (CRM, reservation system, cash register) solves 80% of needs for much less money and time. It only makes sense to order software development when that missing part — the specific process, the integration with the domestic payment system, the report that no one makes finished — really costs the firm time every day. If the problem occurs once a month, it's cheaper to pay someone for an hour of work than to order an app. The difference between a ready-made solution and a custom-made one is described in more detail in the text on custom software development.

What the production process looks like

A serious process goes in stages, not in one big leap from contract to finished product:

• A list of the actual process in the company — what is done manually today, who does it, how long it takes.
• Specification — a list of functions with priority, not the general sentence “build us a system”.
• The first working part (MVP) that solves the most painful step, not the whole process at once.
• Testing with people who will actually use the software, not just the client.
• Commissioning and repair period after the first weeks of real use.

A firm that skips the list of processes and goes straight to the specification usually ends up paying for the finishing touches because the developer guessed what the job looked like, rather than checking it out on the spot.

Who should be in the team on the client's side

Najčešća greška nije loš izbor agencije, nego to što firma prepusti cijeli projekat jednom čovjeku koji nema vremena da odgovara na pitanja developera. Softver koji se pravi po mjeri traži nekoga sa strane naručioca ko poznaje proces iznutra i ko je dostupan za kratke odgovore u toku razvoja — ne za sastanak jednom mjesečno. Kad tog čovjeka nema, developer nagađa, a nagađanje se plaća kroz dorade poslije puštanja u rad. Isto važi i za obim testiranja: ljudi koji će softver koristiti svaki dan primijete probleme koje niko drugi ne vidi, zato test faza ne smije proći samo kroz ruke naručioca ili vlasnika firme.

What to ask before signing the contract

The price of software development depends solely on the scope of work — a serious agency does not give the exact amount before the specification, but the range and explanation of what goes into which part. Before signing, it is worth asking: who owns the code when the project is completed, whether the price includes the maintenance period after commissioning, and what happens if the scope of work changes halfway through the development. The agency that avoids these issues usually charges for the changes at a higher price later. Similar logic applies to custom programming in general — the contract must clearly state who holds what after delivery.

Post-commissioning maintenance

The software used every day requires repairs and minor modifications even months after commissioning — new server versions, changes in the law or tax rates, an additional feature that proves necessary only when people start working with the tool. A company that orders development without a maintenance plan is often left with software that no one understands to fix in a year. The same principle of planning in advance applies to development of websites in Podgorica — The price without a maintenance plan is only half the story.

The development time for a smaller tool with a clear specification is usually measured in weeks, not months — the problem arises when the specification changes along the way, so each new idea is added to the already started work instead of being planned for the next phase. A firm that accepts in advance that the software will grow in stages, rather than expecting the finished product from day one, gets a more stable result and fewer surprises in the bill at the end.

If you're thinking about building software for your business, get in touch to talk about what that software should really address.