Small-scope custom software projects
Custom software does not have to mean a big project. What a small scope looks like, what to cut from version one, and when a narrow project is no longer enough.
A small-scope custom software project covers one process, one set of screens, and keeps its boundaries deliberately narrow - delivered in weeks, not months. Published price ranges for business and web application development in Croatia run from around €1,000 to over €50,000, so many owners see only the top end and conclude that building is not for them. Small projects exist, and they are usually the right answer.
Why small scope wins
Standish Group’s CHAOS research has shown the same pattern for years: small projects succeed roughly 90% of the time, large ones less than 10%. The reason is not technology but scope - fewer moving parts means fewer assumptions that can turn out wrong. A short timeline also means you see the result before the business changes.
What to cut from version one
| Cut in version one | Never cut |
|---|---|
| Roles and detailed permissions | Your data and its export |
| Reports and dashboards | Backups |
| A mobile app | Login and basic security |
| ”Just in case” integrations | Change history |
Everything in the left column can arrive later, and usually arrives cheaper once you know how the system is really used.
”Small project” is not “unfinished project”
The difference is scope, not quality. A small system does one thing completely: the data is clean, the code is tested, backups exist, and someone maintains it. An unfinished system has five half-built things and nothing you can rely on. Maintenance still costs the same - budget 15-25% of the build per year.
When a narrow scope is not enough
If the process crosses several departments, if data must stay in sync with an ERP in real time, or if the software is the product you sell, a small project will not hold. That calls for an MVP in about 12 weeks, not a small internal tool.
How a small project grows into a bigger one
A good small build is a first step, not a dead end. The condition is that the data is yours and exportable, and that an interface to other systems exists. The next process then arrives as a module rather than a second application.
If you are unsure where to start, the signs spreadsheets are no longer enough and realistic delivery timelines both help.
Frequently Asked Questions
How long does a small build take? Typically a few weeks to two or three months, depending on the number of screens and integrations.
What does a small project cost? Less than people expect: small internal tools in Croatia usually start around €1,500-5,000.
Is this the same as an MVP? No. An MVP is the first version of a product still looking for a market; this is a tool for a business that already works.
Can I start with one process and add more? Yes, provided the data is yours, exportable, and reachable by other systems.
Is building worth it at such a small scope? It depends on the cost of the process, not the size of the company - custom software development for a small business has the calculation.
Related Articles
- Custom software development for a small business
- What is custom software development?
- How long does custom software development take?
Have one process that is choking you?
Describe it in a few sentences and we will tell you whether it fits into a small, deliberately narrow project.
Reach out at [email protected] or via the form on our homepage.