How does custom software development work?
4 min readUpdated
To the first version in use: simple tools 4 to 8 weeks, business applications 3 to 6 months, complex platforms more than 6 months. You see progress in working software every week or two.
You don’t need to understand code to follow the project. Knowing how your business works is enough; below is what happens at each step and what we need from you along the way.
What happens in the first conversation?
We don’t talk about technology. We ask how you work today, where the time goes, and which part of the business lives in one colleague’s head. Then we ask what happens when that head goes on vacation. The answer tends to be the most useful thing we hear all meeting.
The aim is to understand the problem before anyone picks a solution. Quite often the job turns out simpler than it looked at the start. If you’d like to prepare, a page describing the problem helps: How should you describe what you need?
The first conversation is free.
What do you get before the build starts?
A description of the system in plain language: what we’ll build, why, and how you’ll use it. With it comes a free estimate of the cost and of the time to the first version in use. You read it, comment on it and confirm it before anyone writes a line of code. What moves the price is in How much does custom software cost?
Where it helps, we also show you a sketch of the screens or a simple prototype before any programming. A sketch is quick to change. The same change after a month of programming can take days. So this is the moment to say “that’s not how we do it here.”
How do you follow progress during the build?
We build in short rounds of a week or two. At the end of each round you get a new version to try, with whatever was added since the last one. Feedback arrives early, while a change is still cheap, rather than three months in. A developer who goes quiet for three months is rarely just being modest.
Before the system goes into use, you try it on a test version with real data and an ordinary day’s work. Anything that doesn’t behave as you expected gets fixed then, before your staff or clients run into it.
How long does it take to the first version in use?
Roughly, by type of system:
- Simple tools (records, schedules, internal dashboards): 4 to 8 weeks.
- Business applications (orders, clients and tasks, with several roles and reports): 3 to 6 months.
- Complex platforms (many users, integrations and rules, or one system serving several companies): more than 6 months.
Within a range, the date moves most with connections to systems you already use, old data to bring across, and how much the first version has to cover. If you have a deadline that won’t move, tell us in the first conversation and we’ll plan the first version around it.
The system runs on your own server or on a private server in the EU that we set up and maintain for you. Your data stays yours.
What happens after the first version?
The first version in use is rarely the last. After a month of real work you usually know what’s missing, and the business keeps changing. So do the regulations, and security updates turn up whether anyone ordered them or not.
That’s why maintenance is agreed together with the build. It covers security updates, upgrades and changes when the way you work changes, and it is charged separately from the build. If you need support at night and on weekends, on-call cover and an SLA are agreed and priced separately too.
If you’d like to know what this would look like for your business, get in touch.
Frequently asked questions
Most of it at the start: the first conversation and reading the description of the system. During the build, it is enough to try each new version every week or two and tell us what’s off. It helps if one person on your side makes the decisions.
Tell us straight away. Short rounds exist so a change is caught while it is still cheap. If it changes the scope, we tell you how it affects the date and the cost before we start on it.
Yes, and it is often the better start. The first version covers the work that gets stuck most, and the rest is built once that version is in use.
Where to next
Roughly: simple tools €5,000 to €10,000, business applications €10,000 to €25,000, complex platforms from €25,000. We charge no VAT. You get a figure for your system in a free estimate after the first conversation.
Describe the problem, not the solution: what gets stuck today, who will use the system, what you use now and how you’ll know the project worked. Add a budget and a timeline. One page is enough; no specification needed.
Work that repeats and follows clear rules: invoices, bookings, reports, customer notifications and stock. Start with whichever one costs you the most.
Tell us where it gets stuck.
Instead of spreadsheets and separate tools, one system shaped around the way your business works, with the server and network beneath it. You can keep the spreadsheets if you insist.
In your own words
Short or detailed, whichever is easier. We read all of it.
The first conversation is free, and we reply within one business day.
Or write to info@techcraft.hr, WhatsApp or Telegram.
From the list
Mark what you recognize in a list of fifteen problems, and the first conversation starts from there.
Nothing is required, this list included. You send the inquiry on the next page.
Finish the inquiry