Waves Studio

Guide to decide

Custom or existing tool: how to decide

Key takeaways: An existing tool is usually the best way to start if your way of working is standard. A custom product pays off when your way of working is what sets you apart, or when the tool forces workarounds. The decision should compare total cost, not just the starting price.

Frequently asked questions

How do I know whether I need something custom yet?

If you spend hours each week moving data between tools or adapting your way of working to theirs, it is probably worth studying.

Can you keep what I already use and improve it?

Sometimes yes: we connect the tools you already use with an automation, without replacing them.

What if I get it wrong?

That is why we start with a definition and a prototype you approve before we build, and the contract includes adjustments after delivery.

When an existing tool is enough

In those cases, starting there is a good decision. You also do not have to pick one path: sometimes an existing tool for the standard parts and something custom only for what sets you apart is the best mix.

When a custom product pays off

Six criteria to compare

CriterionExisting toolCustom product
Functional fitCovers the usual; specifics are handled with workarounds or not at allDesigned around your process, within the agreed scope
Initial investmentLow or none: you subscribe and configureHigher: definition, design and development; quoted according to scope
Recurring costsMonthly fee, which usually grows with users and featuresHosting, third-party services and optional maintenance, as agreed
MaintenanceDone by the vendor, on its schedule and with its changesAgreed with you: what is fixed, what is improved and on what timeframes, in the proposal
Data exportDepends on the vendor and the planDefined at the start; data sits in accounts in your name
Technical dependenceOn the vendor and its termsOn whoever maintains it; that is why it is delivered documented and with accounts in your name

Indicative example: total cost over 2 years

This is an example with assumed figures, to show how to reason. They are not Waves prices or a market average. Assumptions: the tool charges €25 per user per month and costs €500 to set up; the custom product has an initial investment of €6,900, assumed maintenance of €79 a month and third-party services (hosting, messaging and the like) of €20 a month with 8 users and €45 a month with 25 users; all over 24 months and without discounts.

Formulas: tool = set-up + users x fee x 24. Custom = initial investment + (maintenance + third-party services) x 24.

Item (24 months)Tool, 8 usersCustom, 8 usersTool, 25 usersCustom, 25 users
Initial investment€500€6,900€500€6,900
Per-user fees8 x €25 x 24 = €4,800€025 x €25 x 24 = €15,000€0
MaintenanceIncluded in the fee€79 x 24 = €1,896Included in the fee€79 x 24 = €1,896
Third-party servicesIncluded in the fee€20 x 24 = €480Included in the fee€45 x 24 = €1,080
Total over 2 years€5,300€9,276€15,500€9,876

With 8 users the tool is cheaper. With 25, the tool total exceeds the custom product total, although the custom product also grows (in the example, through third-party services). There is no number of users that works for every case: it depends on the real fee, on what the product costs and on how much its services grow. And if the tool does not fit your process, there is a cost the table does not show: the time lost on workarounds. That is why we work it out with your real figures.

A middle path

Often the best option is a step in between: a custom dashboard, or an AI automation that links the tools you already use. If you already know you want an app, see how much a custom app costs.

Tell us about your project

Write to us at hola@wavesstudio.ai and tell us what you need. We are a digital product studio working with businesses in different industries.

← Back to the home page

Tell us about your project