Custom or off-the-shelf software for an accounting firm in Ecuador: how to decide

This is one of the questions we get most often from Ecuador: an accounting firm grows, the operation becomes heavy, and the question appears of whether to keep buying licences or commission a system of its own. The honest answer is that it depends, and there is a fairly identifiable point where the balance tips.

The right question is not which one is better

Off-the-shelf software and custom development do not compete for the same thing. Off-the-shelf solves the standard, regulated problem, which in Ecuador means issuing valid receipts to the Servicio de Rentas Internas. Custom development solves a firm's particular problem: how it organises its client base, how it splits work across its team, and how it tracks the deadlines of dozens of clients at once.

A firm with modest volume and processes similar to any other firm gains nothing from building software. One managing a hundred and fifty clients under its own rules, currently held together by parallel spreadsheets, does.

What each option solves well

When to stay with off-the-shelf

• The firm handles a client base the current team controls without parallel spreadsheets.
• Processes are standard and there are no in-house rules the product cannot cover.
• There is no budget or appetite for a project spanning several months.
• The main value sought is SRI compliance, not operational differentiation.

When custom development is justified

• The firm manages many clients and needs isolated data, team and permissions for each one.
• There are high-volume repetitive tasks, such as uploading dozens of invoices per client every month.
• Real traceability is needed: who touched what, when, and for which client.
• The firm wants to offer its clients their own branded access as part of the service.
• Per-user or per-client licence costs are already comparable to building.

The cost almost nobody calculates

When a firm compares prices, it usually compares the licence against the development budget. The third number is missing, and it is the largest one: the team hours spent moving information between systems. Export from one side, arrange it in a spreadsheet, load it into the other, check that nothing is missing. That cost never appears on an invoice, but it is paid every month and grows with each new client.

The useful comparison is not licence against development. It is licence plus manual work, against development plus maintenance.

What we learned building a platform for an accounting firm

We built a multi-client platform for an accounting firm operating in Ecuador against SRI obligations. These were the decisions with the most impact, and they work as a checklist even if another team builds the system:

• Client isolation from day one: each client with separate data, team and permissions, not a filter over a shared table.
• Bulk receipt upload: processing dozens of invoices in minutes is what frees the most hours in practice.
• Resource-level permissions rather than generic roles, because administrator and user is rarely enough in a firm.
• A full change history per task and per invoice, which is what lets you answer when a client asks what happened.
• Passwordless access with one-time codes, to cut the support load that credential management creates.

The full case study is published on our site, with the regulatory context and the technical decisions.

Five questions to decide

1. How many hours per month does the team spend moving data between systems or spreadsheets?
2. How much does that number grow if the firm adds another thirty clients?
3. Is there an in-house process that is part of the firm's value and that no product covers?
4. What is being paid today in per-user or per-client licences, projected over three years?
5. Does the firm have someone to maintain the system once built, in-house or outsourced?

If the answers to the first two are large numbers and the third is yes, the custom software conversation is worth having. If not, off-the-shelf remains the right call.