In many SMBs, the real information system isn’t the ERP. It’s a shared spreadsheet, three email inboxes and the memory of one or two key people. As long as the business keeps running, nobody touches it. When the company grows—or a key person goes on holiday—the hidden cost of this workaround suddenly becomes obvious. The question is no longer whether you need a tool, but which one, and at what cost.
For example, an office manager exports hours from the scheduling software, copies them into a spreadsheet, cross-checks them against job sheets received by email, then re-enters everything into the invoicing system. Three hours every week, with the risk of a missing line or a transposed figure each time. Nobody decided to work this way. It simply became “how things are done”.
This situation is common in SMBs and mid-sized companies that have grown faster than their tools. Each application works well enough on its own. Things break down in between: exports, copy-and-paste, intermediate files and manual checks. That is exactly where custom software—or a well-designed connector—can make a difference.
The challenge is knowing when the investment is justified, what actually needs to be built and how to avoid turning the project itself into a problem. That’s what this article explores, and how we support SMB and mid-sized company leaders at Etixio.
What are the signs your tools can no longer keep up?
The first sign is rekeying. When the same information is entered two or three times in different tools, you pay for the same work repeatedly and create more opportunities for errors. The second is fragmentation: data scattered across spreadsheets, emails and applications, so you have to ask a particular person for a figure or a customer’s history. The third is inaccessible information: your teams know it exists, but take too long to reconstruct it—and sometimes make decisions without it.
The fourth sign is subtler: a tool that no longer keeps up. It might be business software chosen ten years ago, an application built by a provider that has disappeared, or an ERP so heavily customized that nobody dares to change it. The company starts working around its own tools with extra files, and technical debt accumulates without appearing on a dashboard.
The cost of a poor-fit tool never appears on an invoice. You see it in wasted hours, corrected errors and decisions made without the full picture.
Then there are the IT projects themselves. Many business leaders have experienced a project whose scope drifted, whose budget doubled and whose operating costs were unknown until go-live. That leaves a mark and goes a long way towards explaining the perfectly legitimate caution many SMBs feel about custom development.
Off-the-shelf or custom software: how do you decide?
Let’s be clear: custom software isn’t always the right answer. If an off-the-shelf product meets your needs with reasonable configuration, it will be quicker to deploy, share product improvements across many customers and often cost less. We explored this in our comparison of Odoo and custom development: the right decision depends on the process, not a technology preference.
Custom development becomes relevant in three situations. First, when a standard product would require costly workarounds: your way of working is a competitive advantage, and reshaping it to fit a package would mean giving that advantage up. Second, when several tools need to be connected and the value lies in information flowing between them. Third, when you need to offer a service to customers or partners that no standard product provides.
There is also a frequently overlooked middle ground: keep your existing software and build only what’s missing—a connector, a portal or a dashboard. This is often the most cost-effective option, and it’s the one we consider first.
For business leaders
Before comparing solutions, estimate what the problem costs today: weekly hours spent rekeying information, errors to fix and customer response times. Even a rough figure will be your best way to assess a proposal.
What do SMBs and mid-sized companies actually build?
“Custom software” covers many different projects, most of which are not major transformation programmes. The most common is a business application for managing cases, requests, schedules or production in a way that reflects how your teams actually work. It replaces a collection of spreadsheets with one tool that includes permissions, history and validation rules.
Next come connectors between ERP, CRM, accounting and online tools. They are invisible to users, which is exactly the point: information flows automatically at the right time, without exports or rekeying. Customer and partner portals are another category. They let users check an order, submit a document or track a case without an email or phone call, reducing support demands and improving the customer experience. Our work for Gorilla eSIM included creating a B2B channel and follows this approach.
Dashboards are a fourth category, provided they rely on trustworthy reference data. An indicator calculated from conflicting files only automates confusion, which is why the data structuring in our BI & Data service matters. Finally, companies increasingly ask us to take over, stabilize and modernize an existing tool rather than rebuild everything. Our scoping and modernization work compares targeted improvements, gradual migration and a rebuild.
Where does AI fit in?
AI now comes up in almost every initial conversation. Our answer is deliberately nuanced: it can be useful for an SMB, but for specific tasks, and it should be assessed using real examples rather than a demo. Finding information across hundreds of documents, asking questions of business data in natural language, or extracting fields from an invoice or purchase order can deliver tangible value.
We have seen this firsthand with Bobby, our AI assistant connected to our ERP, which lets our teams retrieve information by simply asking a question. But an assistant like this is only valuable when it rests on solid software: clean data, respected access permissions and reliable integrations. AI doesn’t replace the foundations; it makes them more useful. Leaders looking for a starting point can explore our AI assessment and our article on integrating AI into an SMB.
Adding AI to disorganized data means producing wrong answers faster.
How much does custom software cost for an SMB?
It’s the first question, and it deserves an honest answer: it depends on the scope, the number of integrations and the number of users. A connector between two tools and a business application used by three departments do not belong in the same budget category. Any provider quoting a fixed price before understanding your process is taking a risk—and you will usually end up paying for it.
What you can ask for is a complete view of costs from the scoping stage. We separate three items: development, go-live (data migration, training and user support) and operations, including hosting, any licences, maintenance and enhancements. The last item is most often overlooked, even though it determines the project’s return over several years.
The delivery model follows from the project. A short, clearly defined scope may suit a fixed-price project, with a known budget and deliverables. A long-running project or one that will evolve continuously may be better served by a dedicated team or a time-and-materials engagement, which offer more flexibility. In every case, any change to the budget or schedule should be discussed before the work changes—not discovered afterwards.
Do you need a CTO or technical skills in-house?
No, and it’s a concern we often hear from SMB leaders. Your role in a software project isn’t a technical one: it’s to bring business knowledge and make decisions about priorities. What matters most to your teams? Which business rule applies in a particular case? What trade-off are you prepared to make to meet a deadline? Nobody can answer those questions for you.
The technical work—analysis, architecture, development, testing and production deployment—is the provider’s responsibility. A named point of contact leads the work, delivered by French-speaking engineers in Madagascar and Mauritius and supported by technical leads. For companies that already have an IT department, collaboration takes a different form, closer to an architecture and integration partnership, as described on our page for CIOs and CTOs.
For CTOs
If you already lead an in-house team, ask the provider how they will fit into your practices: code repository, reviews, environments, conventions and documentation. An external partner should strengthen your organization, not create a technical island alongside it.
How does a custom software project unfold, step by step?
Our method has four stages, each with deliverables you approve before moving on. The goal is simple: you should never discover a scope or budget gap at handover.
Start with a real operation
We don’t begin with a feature list. We start with an actual operation: entering an order, processing a request or preparing a report. We follow it from beginning to end with the people who do the work to understand where time is lost and errors arise. This is often when we discover that the real problem isn’t where anyone expected.
Define the scope and budget
We turn those findings into a clear scope, success criteria and a budget that separates development, go-live and operations. We compare the options—including those that require no development—and recommend the one offering the best balance of value and risk.
Deliver in stages
Development progresses in short iterations, with regular demonstrations based on real cases. Your teams see the tool take shape, respond early and make adjustments while they still cost less. It’s the best antidote to the project black box that has caused so many IT projects to fail.
Go live and keep improving
Go-live includes data migration, user support and close follow-up during the first few weeks. Maintenance and enhancements follow at the pace of your needs, within a framework agreed together.
What are the four conditions for a successful project?
Successful projects almost always share the same characteristics. First, they have success criteria defined in advance: time saved, processing time, error rate or user satisfaction. Without them, it’s impossible to know whether the project achieved its goal, and the discussion ends up relying on conflicting impressions.
They also have an available business lead. Custom software is built with the people who will use it; if the business lead has no time to validate decisions, the project is bound to costly rework. The operating cost must be known before go-live, too, to avoid unpleasant surprises once the tool becomes essential. Finally, there must be a viable exit: the code, documentation and access credentials belong to you and can be handed over to your team or another provider. You should depend on a vendor by choice, never by constraint.
A good provider is also one you could leave without difficulty.
Your business deserves tools that fit today—not yesterday
SMBs and mid-sized companies readily invest in machinery, premises and sales teams. They are often more hesitant to invest in the tools that organize day-to-day work, because their value is less visible and bad experiences leave a mark. Yet every hour of rekeying saved, every piece of information found in seconds and every error avoided adds up week after week, far beyond the project’s cost.
The real question isn’t whether your business can afford custom software. It’s how much longer it can afford to run on spreadsheets, copy-and-paste and the memory of a few indispensable people.
Let’s discuss the operation that takes up most of your time: in 30 minutes, we’ll review your situation and send you a written summary with an initial estimate, with no commitment and no technical jargon.
→ Book a 30-minute conversation with our CTO
→ Discover how we support SMB and mid-sized company leaders
Custom software for SMBs: frequently asked questions
Is custom software right for an SMB?
Yes, when off-the-shelf tools would require costly workarounds, several applications need to be connected, or you need to offer a service to customers or partners. In other cases, a well-configured standard product may be enough.
How much does custom software cost for an SMB?
The cost depends on scope, the number of integrations and the number of users. Scoping should distinguish development, go-live and ongoing operations so you understand the full cost before committing.
Do we need technical skills in-house?
No. The company brings its business knowledge and makes decisions about priorities. The provider handles technical analysis, development, testing and production deployment, with a named point of contact.
Should we replace an existing tool or improve it?
It depends on the tool’s condition and how well it meets the need. Scoping compares targeted improvements, gradual migration and a full rebuild, taking cost, risk and business continuity into account.
Is AI useful for an SMB?
It can help with specific tasks, such as finding information in documents, querying data in natural language or extracting fields automatically. These uses should be assessed against real examples.
How long does a custom software project take?
It depends on the scope and required integrations. An incremental approach can put a useful first version into service, then expand it.
What happens after go-live?
Maintenance and enhancements continue within an agreed framework. The code, documentation and access credentials belong to you and can be handed over to your team or another provider.


