Building your own tool can look like the quick route, but what weighs on you afterwards is maintaining it: someone has to fix it, adapt it when your process or the regulations change, and keep the knowledge when the team changes. So the question that decides isn't "can we build it?" but "who will maintain it two years from now?". As a general rule, buy when the problem is common and another company takes care of keeping its rules up to date, and build when the process sets you apart and you have someone to maintain it.
Compare both options against the same requirements
Buying and building can only be compared if you ask the same of both. Request or estimate each cost item separately, even if some come to zero, for the same scope and the same period:
- Setup: configuration and rollout if you buy; design and build if you build.
- Licences, subscriptions or infrastructure, and how they change as users and usage grow.
- Integrations with the rest of your tools.
- Adapting to changes in regulations and in your process.
- Support and incident handling.
- Team training.
- Exit: exporting your data and moving to another tool or another team.
And the same conditions for both: an owner inside your company, exportable data in a format you can use, documentation, testing before every significant change and an exit plan. For a bought tool, check the current plans and renewal terms. For a built one, make sure the code, the accounts and the documentation are in your company's name.
When building makes sense
Building makes sense when these three conditions are true at the same time:
- The process sets you apart. It's part of how you win clients or deliver your service, and bending it to fit a tool would cost you that edge.
- The tools on offer force workarounds on you. Parallel spreadsheets, steps copied by hand or fields used for something other than what they say, and those workarounds cause errors or delays you can point to.
- Someone will maintain it. A named person or team, in-house or external, with time set aside to fix, adapt and document.
If the third one fails, it's worth waiting or looking for a middle option, even if the first two hold.
When buying is the better call
- The problem is common. CRM, invoicing, payroll and accounting solve needs that many companies share, and vendors tend to spread the cost of maintaining them across their customers. For CRM, a tool like Attio can be configured around your process without building from scratch.
- The rules change and someone has to keep up. Invoicing is a good example. In many countries, invoicing software has to meet tax rules that change over time. In Spain, for instance, the invoicing systems regulation (Royal Decree 1007/2023) requires the producer of the software to certify, through a statement of compliance, that it meets the requirements. According to the Spanish Tax Agency, if a company builds its own invoicing software, the company itself has to certify it. And the deadlines have moved: Royal Decree-law 15/2025 pushed them to 1 January 2027 for companies that pay corporate income tax and to 1 July 2027 for everyone else. Whoever builds their own invoicing takes on keeping up with those changes, in Spain or wherever they invoice.
- There's no capacity to maintain it. If nobody will have time to maintain it, a bought tool with support is usually the more prudent option, even if it doesn't fit perfectly.
An example: in-house quotes, bought invoicing
Picture a services company that quotes every project with an inherited spreadsheet. The sheet combines rates, margins and timelines in a way the team sees as part of its edge. Only one person knows how to change it, and when a quote is accepted, someone copies the amounts by hand into the invoicing software.
This is how it looks once you separate what you build from what you buy:
- Data that comes in: a client asks for a quote for a project.
- Owner: the head of operations, who owns the quoting tool and the rate table.
- What gets built: an internal quoting tool with a single table of rates and margins, documented and in the company's name. It's the part that sets the company apart.
- What gets bought: the invoicing software stays an off-the-shelf product, and its vendor takes care of adapting it to the regulations.
- Rule: when a quote is accepted, its lines move to the invoicing software through an integration. Nobody copies amounts by hand.
- Exception: a discount outside the rate table needs sign-off from management before the quote goes out, and who approved it is recorded.
Observable result: rates live in one place, the accepted quote and the invoice match line by line, and certifying the invoicing software stays with its vendor. What was built is small, which is why it can be maintained.
The middle option: build on top
Between buying a closed product and developing from scratch there are middle options. You can configure a base tool such as Notion or Airtable in depth, build an internal app on top of it with Softr, or connect the tools you already have with automations in Make or n8n. The same requirements apply to them as to everything else: an owner, documentation, testing and an exit plan.
Six questions before you decide
Ask them the same way for the buy option and the build option, and request or write down the answers:
- Which part of the process sets you apart and which part is the same as in any other company?
- Who will be the owner, and how much time will they have to maintain it?
- Which regulations affect this piece, and who will keep up with their changes?
- What's the total cost across the seven items for the same period?
- How would you get your data out if you changed tool or team tomorrow?
- Whose name are the accounts, the code and the documentation in?
How we work at The Optimal Flow. In all our projects, tool accounts are created in the client's name, we work with delegated-permission access to those accounts, and the documentation for what we build is handed over to the client and stays in their name.
If you want to build these pieces in-house, you can train your team with courses such as internal MVPs with Softr or vibe coding for internal apps.
Next step
If your case meets the three conditions for building but you don't have the capacity to build or maintain it in-house, see how we approach custom development and custom ERPs and systems, or book a call. Come with a clear idea of which part of the process sets you apart and who will maintain it two years from now.
Sources
- Spanish Tax Agency, FAQ on certifying invoicing software (statement of compliance) (in Spanish): certification falls to the producer and, for in-house software, to the company itself.
- Spanish Tax Agency, notice on the extended adaptation deadline (Royal Decree-law 15/2025 of 2 December; in Spanish). Deadlines may change again; check the current version, and check your own country's rules if you invoice elsewhere. Sources checked on 21 October 2026.




