Move when the same data lives in several places, customers keep asking where things are, and people spend hours chasing paperwork. Try a better spreadsheet or an off-the-shelf tool first. Choose custom software only when your process is unusual or the software is part of how you win.
Seven signs you have outgrown the spreadsheet
- The same details are typed into more than one place.
- Nobody is sure which version of the file is the real one.
- Customers email or call to ask where their order or booking is.
- Approvals and paperwork are chased by hand, and things slip.
- Invoices go out late because someone has to piece the data together.
- Only one person really understands how the sheet works.
- You have started to plan your work around the limits of the tool.
Your options, honestly
- A better spreadsheet: shared, validated, with clear ownership. Cheapest and fastest, and often enough for one team with one process.
- Off-the-shelf software: proven and quick to start, with monthly fees that grow with users. Right when your process is close to what the product expects.
- No-code tools: quick to assemble and flexible, but they can become fragile and hard to hand over as the process grows.
- Custom software: built around your process, owned by you, with no per-user fees. Right when your process is unusual, when you are stitching several tools together, or when what your customers see is part of how you win.
How to decide
- Could a better spreadsheet fix the problem? If yes, try that first.
- Does an off-the-shelf product cover most of what you do without bending your process? As a rule of thumb, if it covers around four fifths of it, buy it.
- Is the missing part something your customers see, or something that gives you an edge? If yes, that leans toward custom.
- Will the process stay stable for at least a year? If it changes every month, fix the process before you build software around it.
What to prepare before you talk to a builder
- Who uses the process today, and who else should: customers, staff, finance, partners.
- The steps from first contact to payment, in order.
- The documents and data involved, with one real example of each.
- The tools it must connect to, such as accounting or email.
- What done looks like, in one or two sentences.
What a good first version looks like
A working system with real screens in the first week, a demo every week after that, and real data before launch. For a booking or portal system, a first version in six to eight weeks is realistic. Ours was delivered about eight weeks after the order.
What it costs
It depends mostly on how many kinds of users there are, how many tools the system connects to, and how many rules it has to enforce. Our own booking platform, with a customer portal, a back office and five user roles, was around €10,000. Our pricing guide shows what to expect for different kinds of projects.
Red flags in a proposal
- Hourly billing with no cap and no fixed scope.
- No working demo until the end.
- You do not own the code or the accounts.
- No plan for moving your existing data.
- A price that arrives before anyone has asked how your process works.
Questions people ask
How long does a custom booking system take?
A first working version usually takes six to eight weeks, depending on scope. You should see real screens every week.
Will I own the software?
You should. Ask for the code and the hosting accounts to be in your control from the start, and avoid arrangements with a license fee to the builder.
Can it connect to our accounting or email?
Usually yes. Integrations are one of the main things that move the price, so list them before you ask for a quote.
What if our process changes after launch?
That is normal. A system built in weekly steps is easier to change, and a care plan or a follow-up project covers changes after launch.