When a Custom Module Beats a Workaround in Your Business Platform
A weekly manual workaround can cost more than a custom module. Here is a five-question test for deciding which one your business platform needs.
Some links in this post are partner or affiliate links. Unified WebTech is a DashNex Authorized Partner and may earn a commission if you sign up, at no extra cost to you. See our disclaimer.

On this page
Every Monday, someone at a small consultancy opens the booking calendar, copies each new client's details into the invoicing tool, then emails a portal login by hand. It takes about ten minutes per client. Nobody calls it a problem, because it works. It is also a workaround, and its price never appears on a statement.
This article covers when that price justifies a custom module and when it does not. We build custom DashNex modules for a living, so we have a bias. We will still tell you that building too early is as expensive as patching too long.
What a workaround really costs#
A workaround is any process built around a missing feature: a zap, a spreadsheet, a copy-paste routine, a second tool. The subscription fee is the visible part. Most of the cost sits in the glue between tools, the same pattern we found in our small business SaaS audit.
Manual minutes that add up#
Take a step that takes six minutes and runs 20 times a week. That is two hours a week, or roughly 100 hours a year, spent moving data from one box to another. These figures are an illustration, not a benchmark, so swap in your own.
Nobody logs those hours, so they never get weighed against the cost of fixing the gap. They also land on your most capable people, because those people know how the workaround works.
Errors that reach customers#
Manual steps produce mistakes. A mistyped email address means a portal invite goes nowhere. A skipped row means an invoice is never sent. Duplicate records mean a client gets two reminders, or none.
Customers do not see your internal process. They see a late invoice or a login that never arrived, and they judge you on it.
Tool sprawl around one missing feature#
The third cost is the extra tool. One missing feature leads to a connector, then a second subscription to store what the connector produces, then a third to alert you when the connector fails. Each addition is reasonable alone. Together they form a stack you maintain to cover one job.
Signs a workaround has become a liability#
A patch outlives its purpose quietly. These are the triggers we look for:
- The same manual step repeats every week. A one-off fix is fine. A weekly ritual needs a proper home.
- It breaks after vendor updates. If a changed field name or API version knocks it over, you are tied to someone else's release schedule.
- Only one person understands it. When that person is on holiday, invoices stop.
- Staff avoid it. If people skip steps or keep private spreadsheets, the process has already failed and the data is drifting.
- You check it before trusting it. If you open three tabs to confirm a booking really created an invoice, the automation is not saving the time you think it is.
One trigger is a note on your to-do list. Three means the workaround is a liability.
The five-question decision test#
Score each question from 0 to 2 and add the totals at the end. The scoring forces an honest answer on each factor instead of going with whichever option feels more urgent.
Frequency and volume#
How often does the process run?
- 0: a few times a year.
- 1: monthly, or a handful of times a week.
- 2: daily, or dozens of times a week.
Frequency is usually the strongest argument for building. A small saving repeated every day beats a large saving you collect once.
Data ownership and portability#
Where does the data live, and could you take it with you?
- 0: the data sits in one tool you control and can export easily.
- 1: it is split across two tools, with export possible but messy.
- 2: it is spread across several vendors, or trapped in a connector or an account you do not control.
Scattered customer records carry a risk beyond cost. If a vendor changes terms or you switch tools, you want the records to move with you. A module that writes into your own platform keeps that data in one place.
Cost of failure#
What happens when it breaks?
- 0: an internal inconvenience fixed the same day.
- 1: a delayed task or an apology email.
- 2: lost revenue, a missed invoice, a compliance problem, or a customer who cannot access what they paid for.
Judge the worst realistic case, not the average one. Money not collected and clients locked out score 2 every time.
Native features you have not turned on#
Does your platform already do this?
- 0: yes, or the vendor has put it on a roadmap with a date.
- 1: partly, and you are unsure about the gaps.
- 2: no, and you have checked the documentation and asked support.
A low score here argues against building, so check before you pay anyone. Some workarounds exist only because nobody read the settings page. We cover how to evaluate platform limits in questions to ask before choosing an all-in-one business platform.
Rate of change#
How often do the rules of this process change?
- 0: every few weeks, because you are still working out how it should run.
- 1: a few times a year.
- 2: rarely, because the process is settled.
Stable processes suit a module. Fast-moving ones are better left flexible, because every change to a built module costs time and money.
Reading your total#
- 0 to 4: keep the workaround. Document it and move on.
- 5 to 6: borderline. Re-check the native features answer, then try tightening the workaround before building anything.
- 7 to 10: a custom module is likely to pay for itself. Get a proper price.
Treat these bands as a guide, not a rule. A 2 on cost of failure can justify a build even when the total looks low.
Worked example: booking to invoice#
Here is a gap we see often. A client books a session. Nothing creates portal access, and nothing generates an invoice, so the owner does both by hand. Our explainer on custom DashNex modules covers bookings, portals and invoices in more detail.
The workaround version#
A booking tool takes the appointment. One connector passes the details to a spreadsheet. A second pushes a row into an invoicing app. A calendar reminder tells the owner to email portal credentials manually.
That is three tools plus a manual step for one job. When a client changes their name or email after booking, the update reaches only one of the three places. When a connector fails, the first sign is a client asking where their invoice is.
The custom module version#
A custom module watches for a confirmed booking inside the platform, creates the client's portal access, and drafts the invoice from the booked service. The booking, the portal account and the invoice share one client record. One person owns the module, and it should be re-tested against the same acceptance checks whenever the platform updates.
If you already run your business on DashNex, this is the kind of platform where such a module can sit next to your existing bookings and client records instead of in yet another tool.
The module does not remove all the work. Someone still reviews exceptions such as refunds or changed bookings. It removes the repetitive part and keeps the data in one place.
Comparing three-year cost and risk#
To compare the two options, use the method from our post on calculating the real three-year cost of a software subscription. List every cost line across 36 months for each option, including your own time.
For the workaround:
- Subscriptions for each tool in the chain, including likely renewal changes.
- Weekly manual hours multiplied by 156 weeks.
- Time spent fixing breakages and correcting errors.
- The cost of a missed or wrong invoice, estimated from your last few incidents.
For the module:
- The build quote.
- A maintenance allowance for platform changes and small adjustments.
- Time spent reviewing exceptions.
- Any subscriptions you can cancel once it is live.
Put your own figure against each line. In our experience the module wins when the process runs often and a failure costs real money. The workaround wins when volume is low or the process is still changing. Weigh the risk as heavily as the cost: a workaround spreads risk across several vendors, while a module concentrates it in one build you can test and own.
When a workaround is still the right answer#
We turn down module work when the numbers do not support it. Keep patching when:
- The process is a one-off. A single migration or a seasonal task does not need a permanent build.
- Volume is very low. If it runs five times a year, an hour of manual work each time is cheaper than any build.
- Requirements change quickly. If you are still learning how the process should work, a module locks in guesses. A spreadsheet adapts for free.
- You may replace the tool within months. Building on a tool you are about to leave wastes the investment.
Building too early is a real mistake. A module built around a half-formed process gets rebuilt, and you pay twice. Run the workaround long enough to learn what the process needs, then build once.
How to scope a module worth building this week#
A good scope costs a few hours and saves a lot of arguments later.
- Write the current process step by step. Include every manual touch, every tool opened and every exception. Watch someone do the work instead of relying on memory.
- Define inputs and outputs. What triggers the process? What should exist when it finishes: a portal account, an invoice, an email, a record update?
- Set acceptance tests. Write them as plain checks, such as "a confirmed booking creates exactly one invoice" and "a cancelled booking creates none."
- Name the owner. One person approves the scope, signs off the tests and receives support requests after launch.
- Request comparable quotes. Send each studio the same brief structure so the quotes line up. Our guide on writing a brief so agency quotes are comparable applies equally to module work.
This week's action list:
- Score your most annoying workaround on the five questions.
- Check your platform's documentation and support for a native feature.
- Write out the process steps and three or four acceptance tests.
- Pick an owner.
- Send the brief to two or three builders and ask for the same breakdown from each.
FAQ#
Can we start with a workaround and migrate later?#
Yes, and we often recommend it. Keep the data clean, use consistent client IDs, and write down the process as you go. That documentation becomes the brief for the module later. Trouble starts when the workaround scatters records across tools with no shared identifier, because the migration then needs a cleanup first.
Who maintains a custom module after launch?#
Agree this before the build starts. Often the studio that built it handles fixes and platform-update changes under a defined arrangement, while your named owner decides on and approves changes. Ask what happens if the platform changes something that breaks the module, and how quickly you would hear about it.
How do we tell whether a vendor's native feature will close the gap on its own?#
Look for a dated roadmap item, not a vague promise. Ask support directly whether the feature is planned and whether it will cover your exact case, such as a specific trigger or field. If the answer is "maybe next year," score the question as if the feature does not exist, then decide whether you can live with the workaround until it arrives.
Already on DashNex? See the how-to guides
Get new posts by email
One email when something new is published. Unsubscribe any time.


