Guides to read before commissioning software

Practical texts for anyone considering custom software who wants to arrive at the first conversation with a clear head.

  1. 01Verifactu: what it requires from your invoicing software, and from whenIf your company invoices in Spain with software built for it, the regulation on invoicing systems applies to you too. Here is what it asks for, what is worth reviewing and how we approach the work, without promising what only the tax authority can say.
  2. 02When to move from spreadsheets to custom software (and when not to)A spreadsheet is an excellent tool until the day it is not. This guide helps you recognise that day with concrete signs, without assuming the answer is always a new program.
  3. 03How to prepare a custom software project: what to have ready before you startHalf of a good project is decided before a single line of code is written. This is what to gather before the first conversation with us or with any other supplier.
  4. 04Custom software: the pros and cons, without the sales pitchPeople who sell custom software tend to mention only the upside. Here are the downsides too, because they are real, and what can be done to make them weigh less. If it does not pay off for you after reading this, better to know now.
  5. 05Verifactu for companies invoicing in Spain from their own softwareMany subsidiaries and foreign companies issue their Spanish invoices from their group’s system or from their own platform. If that system falls under Verifactu, it has to be adapted, and the decision is often made far from Spain. This guide explains what changes in that particular case.
  6. 06How much custom software costs: what it depends on and market rangesIt is the first question in almost every conversation, and the honest answer is “it depends”. Here we explain what it depends on, how it is usually contracted and which ranges are common in the Spanish market, so you arrive at the first meeting with a reasonable idea.
  7. 07Custom software or an off-the-shelf ERP? Criteria for choosing wellIt is one of the first questions any company faces when it wants to put its management in order. The honest answer is that an ERP is often the right choice, and that custom software makes sense for one specific part of the business, not all of it.
  8. 08Custom or no-code: what each is for and when to switchNo-code tools let you build an application without programming, and for many cases they are the best choice. This guide explains where they shine, where they start to cost you and how to move to custom software without losing what you have built.
  9. 09Spreadsheet or database: what changes when your data moves into tablesA spreadsheet and a database both keep information in rows and columns, which is why they look alike. They are not. This guide explains the difference with a real-world example of a sheet broken down into tables.
  10. 10How long custom software takes to build and what it depends onThere is no figure that fits every project, and be wary of anyone who gives you one before seeing your case. What can be explained is the phases the work divides into and what makes each one take more or less time.
  11. 11What to ask for in a custom software development contractA good contract goes unnoticed while everything goes well and saves the day when something goes wrong. This list gathers the points worth having in writing. It is not legal advice: the final wording should be reviewed by your lawyer.
  12. 12How to choose a custom software provider: questions and warning signsAlmost every provider gives a good presentation. The difference shows in the answers to a few concrete questions, and in what happens when you ask them to show you something that works.
  13. 13How to migrate data from Excel or Access to a new systemOld data is almost never as clean as it looks. A good migration is rehearsed, counted and validated before the switch-over day, not after it.
  14. 14What an MVP is and when a small business should build oneMVP stands for minimum viable product. For a small business commissioning an internal system, the useful definition is simpler: the first phase that someone on your team genuinely uses, with real data, from day one.
  15. 15How not to depend on a single person or a single providerThe macro only one employee understands and the provider who holds every password are the same risk wearing different clothes: the day they are gone, your company cannot touch something it relies on.
  16. 16GDPR checklist for an internal application: what to review before go-liveAn internal application that stores data about customers, employees or suppliers processes personal data. This list helps you not to forget anything while designing it; it is no substitute for the view of your data protection officer or adviser.

ServicesSectorsIntegrationsProcessesGlossarySee all projects

Tell us the problem

A person on the team reads it and replies with a proposed next step.

Tell us your problem