Blog How to choose
Off-the-shelf or bespoke software? The answer is almost always both
The decision is not off-the-shelf versus bespoke: it is which part of your work is the same as everybody else's — and not worth paying for twice — and which part is genuinely yours. The first you buy ready-made; the second gets built on top.
The two costs nobody puts in the spreadsheet
The comparison is usually drawn between the subscription for the off-the-shelf product and the quote for bespoke development, and on those terms off-the-shelf always wins. But neither of those figures is the real cost.
The cost of off-the-shelf that does not fit is not paid on the invoice: it is paid in the parallel spreadsheet somebody maintains for what the tool will not do, in the data typed twice, in the report assembled by hand every month, and in the people who quietly stop using the tool because it costs them more work than it saves. It is paid in instalments, invisible in the accounts, and it is expensive.
The cost of fully bespoke is not the quote either: it is what it costs to keep alive. Bespoke software does not receive the features other customers asked for, does not update itself when a rule changes, and depends on the firm that wrote it still existing and still employing the person who wrote it. Three years in, plenty end up frozen: they work, but nobody dares touch them.
Which part of your work is actually yours
The exercise that saves the most money takes an hour and a sheet of paper: separate what you do the same as any other firm in your sector from what you do in a way that sets you apart.
The proportion is almost always the same. Adding a person, tracking their holiday, recording working time, booking hours to a project, issuing an invoice or filing a CV are done more or less identically everywhere. What is genuinely yours is usually far smaller than it feels: one particular way of pricing, an approval flow inherited from a large client, a report in the exact format a regulator demands, an integration with the sector-specific program you have been running for fifteen years.
Paying for bespoke work on the first is throwing money away. Giving up the second because “the tool does not do that” is worse: it means changing how you work to suit a piece of software, which is exactly backwards.
The third way: standard base, your own layer
What works is buying the 90% that is the same for everybody and building the 10% that is yours on top. It sounds obvious and is rarely possible, because it depends on one condition you cannot see in a demo: that whoever sells the product is whoever writes the code.
With a large vendor on the other side of the world and an implementation partner in between, “your bit” gets solved with a connector, a custom field or an external workaround that has to be redone at every upgrade. With a team that owns the code, it gets solved inside the product and maintained with it.
- Ask who writes the code. If the answer is “the vendor” and you are talking to an implementer, your bit is going to live outside the product.
- Ask what happens at the next upgrade. What is built for you has to keep receiving the product's improvements. If the answer is “we freeze your version”, that is not bespoke: it is a dead end with a date on it.
- Ask about leaving before you arrive. Full export as CSV and an API over the same entities you see on screen, including the part built for you. If the data only comes out “on request”, you already know what leaving costs.
- Ask for the order in writing. First check whether it is a setting, then whether it would help other customers, and only then quote. Anybody who quotes the first thing you ask for is not looking at your problem.
Configuring is not developing, and it pays to know where the line is
A lot of what gets requested as “bespoke development” is really configuration, and that is good news: it is free and it is there the same afternoon. The line is usually here.
Configuration: what you call things, the states and types in your catalogues, calendars and working agreements, who approves what, what each role can see, the reports you build by picking columns and filters, and which blocks of the platform you have switched on.
Development: a screen that does not exist, a calculation using a formula only you use, a document in a format imposed from outside, an integration with another program, or an automation that chains several things in a way that is not the usual one.
The useful question in a demo is not “can it do X?” — the answer is always yes — but “is X configuration or development, and how soon do I have it?”.
How to contract the bespoke part without surprises
Three things in writing before anybody writes a line of code, and they apply to a two-day job as much as to a two-month one:
- What it does, on one page. Not a forty-page document: one page both sides read and understand the same way. If it does not fit on a page, it is not clear yet.
- A fixed price and a date. And what happens if it runs long. An hourly estimate with no ceiling is an estimate that always doubles.
- Who maintains it afterwards, and at what cost. It is the question almost nobody asks and the one that decides whether you can still use it in three years.
And one honest warning
“Almost anything” is not “anything”. Some requests should not be accepted, and a supplier who says yes to all of them is a supplier who will disappoint you: whatever breaks the data model, whatever forces the same information to be kept in two places, or whatever only makes sense because an internal process is badly set up and what is needed is to fix the process rather than program it.
The conversation worth having with whoever will build it is that one: not whether it can be done, but whether it is worth doing. And only somebody who knows the product from the inside can have it.
Frequently asked questions
Is bespoke software more expensive than off-the-shelf?
The development is; the total cost over three years often is not, and it depends entirely on how much extra work the ill-fitting off-the-shelf product makes you do. What almost always comes out cheaper than either pure option is a standard base with your own layer on top: you pay ready-made for what is the same for everybody and build only what sets you apart.
How do I know whether what I need is configuration or development?
By asking in the demo, in those words. Configuration is what you can change yourself from inside the application — names, catalogues, calendars, permissions, reports, which modules you have. Development is anything that requires writing code. A good share of what gets asked for as development turns out to be configuration.
Does what they build for me get updated with the product?
It should, and it is the question to ask before signing. If the bespoke part lives inside the same product, it keeps receiving the improvements and the fixes. If it lives in a frozen copy with your name on it, in two years you will be choosing between upgrading and keeping your part.
What if the firm that built it disappears?
That is why full export is tested before you start, not on the day you need it. If you can take all your data out as CSV and through an API whenever you want, the risk is bearable; if you cannot, the risk is the whole business.
How long does a small bespoke job take?
If it really is small — a report, a field, a simple screen — days rather than months, provided whoever builds it knows the product from the inside. What stretches timescales is almost never writing the code: it is agreeing what had to be built.
All of this is built into Fichaloto. See how it works.
Keep reading
How to choose
Twelve questions worth asking before you sign
None of these twelve questions is technical. Every one of them is answered in a sentence, and you can ask for the answers in writing before signing anything.
Compliance
A clocking record that cannot be quietly rewritten
Most time-tracking tools store hours in a table anyone with database access can edit. That is fine until the day somebody asks you to prove a number.
Capacity
Planned, clocked, charged: three numbers that should match and usually do not
Most companies can tell you what they planned and what they invoiced. Very few can tell you, for a given week, whether those two things are related.