The spreadsheet nobody dares to touch
Most custom software begins life as a spreadsheet. A packing shed, a renovation crew or a small clinic builds a clever workbook, and it serves them well for years. Then the person who understands it takes a holiday, the file grows slow, or two people edit it at once and a week of entries vanishes. That is usually the moment an owner starts searching for a developer.
It is a reasonable moment to think, but it is not proof that you need to build anything. A spreadsheet that has outgrown itself often needs a better ready-made tool, not a new one from scratch. The useful question is narrower: does a product already do this job well enough, and what would we give up by following its way of working?
Give the shelf a fair trial first
Off the shelf means a product that many businesses already use for accounting, scheduling, inventory or customer records. You pay a subscription or a licence, you adopt its way of working, and the vendor handles updates and security. For most tasks in most Fraser Valley businesses this is the sensible answer, and it is usually the cheapest way to learn what you truly need.
Test it properly before you decide it falls short. Run real work through it, and if you can, through a full busy season, because a trial in the quiet weeks hides the trouble that appears when the farm stand is crowded or the renovation calendar is full. Keep a running note of every workaround your staff invent.
Signs the shelf has run out
Custom software starts to make sense when the same workaround keeps coming back. Perhaps your process is the reason customers choose you, and every product you try forces you to flatten it. Perhaps staff copy details between three programs each day because none of them fit together. Or you pay for a long list of features while the one you need is missing.
Watch for the opposite trap as well. Wanting software that mirrors your current paperwork is a habit, not a business reason. Sometimes the product's way of working is better than yours, and a small change to your routine costs far less than a build.
- A rule your business follows that no product lets you set
- Staff re-typing the same details into several programs
- Customers or partners who need their own login to your data
- Per-user fees that rise with every hire or new location
- A job at the core of how you earn, not a side task
What a custom build really costs
A build has a visible price and a hidden one. The visible price covers design, programming, testing and launch. The hidden one is everything afterwards: hosting, security updates, changes when your needs shift, and a developer who still remembers how it works years from now. A ready-made product spreads those costs across thousands of customers. With custom work, they are yours alone.
Scope sets the figure, so be wary of anyone who quotes without asking questions. Our website shows time-based work at $50 to $99 per hour and projects from $1,000, and a small, clearly defined piece sits very differently from a full system. Ask for the estimate in two parts, the build and the running costs, and ask who owns the code at the end.
Buy the core, build the gap
Between buying and building sits a third option that suits many small businesses. Choose a ready-made product for the common work, then add a small custom piece for the one thing it cannot do, such as a quote calculator, a customer portal or a link between two programs. You keep the product's stability and spend only on what is truly yours.
Before you talk to a developer, check whether your product offers a published connection point, usually called an API. Without one, a custom layer can be hard to attach. Then use the questions below to compare providers. If you would like a second opinion first, the Abbotsford studio offers a free consultation by phone, video or in person.
- Who owns the code, the hosting account and the data when we finish?
- What will it cost each year to run and keep secure?
- How will you document it so another team could take over?
- Can the first version be a small piece that proves the idea?
- Who answers the phone when something breaks in the busy season?
A line that keeps moving
Ready-made products keep adding automation, connection points and built-in assistant features, and that pushes the line toward buying. Many of them also let small custom pieces sit on top, so you can add only what is missing. For a Fraser Valley business, the likely result is a blend: a product at the centre, a small custom layer where you differ, and a regular check on whether that layer is still needed.
- 01Review each custom piece once a year and retire it when a product catches up
- 02Prefer tools that publish a connection point for your data
- 03Keep the documentation current while the builder still remembers why
Questions & answers
Not always, though the total is usually higher. A product often looks cheaper in the first year. A build can win when per-user fees climb with your staff or locations, or when workarounds eat hours every week. Compare costs over several years, including upkeep, instead of the first invoice.
That depends on the agreement, so settle it in writing before work starts. Ask that you hold the finished code, the hosting account and the data, and that the developer hands over documentation. A lawyer can review the wording. Without these points, changing providers later can be slow and costly.
Yes, and it is often the safest path. Keep your data exportable, avoid storing key records only inside one product, and note each workaround. That list becomes the specification if you later decide to build, and tidy records make any move far easier.
If a product covers most of it and the rest is a habit, it is probably too small. A better test is time: when the missing piece costs your team hours each week or loses you customers, a build deserves a conversation. We are glad to look at it with you.
