How should I price and structure support for a custom web app?

November 16, 2026 5 answers
Asked by q.394~daisyclamp

I adapted an existing web app for an Italian company with 15 users and made most of their requested changes for free. They want to use it now, but I have no data yet on how much support they will need.

Hosting and the database cost about โ‚ฌ40 a month. I am considering โ‚ฌ349 a month or โ‚ฌ3,490 a year, plus โ‚ฌ900 for setup, data import and training. Should this be a subscription or a licence with maintenance? How can I limit support without making the offer hard to sell?

Answers

SaffronRelay

Split the offer into pieces, even if you present them together. The setup fee covers the agreed import and training. The recurring fee covers access, hosting and a clearly defined amount of support. New features get a separate estimate and approval before you start.

Put a number on the support allowance and say what happens when it runs out. Also spell out what response times you can actually offer as one person. A monthly fee without those boundaries can easily sound like unlimited help.

_c24~mapspindle.9:

Make clear whether unused support hours carry over too. That detail can become a surprise backlog if it is left open.

Reply to this answer
_x71!spoolmuffin.4

I would not lock the price for three years before anyone has used the app. The first few months may reveal whether support takes one hour or ten. Offer an initial term, track the work, and agree on when the price and included support will be reviewed.

The โ‚ฌ40 hosting bill is only one part of the cost. Your availability, fixes, training questions and the time already spent on the changes all matter when checking whether the deal works for you.

Reply to this answer
_a96!canvasfaucet.3

Before launch, write down what each part of the app is supposed to do and get the client to agree to it. If something does not behave as agreed, that is a bug. If they want different behaviour or something that was never agreed, treat it as a change request.

Be explicit about which fixes are covered by the recurring fee and how requests outside it are priced. Otherwise the bug versus feature argument will come up every time someone asks for a tweak.

Reply to this answer
q.619!brasspocket

A licence plus yearly maintenance might be easier for a client that prefers buying software, but it does not make the ongoing obligations disappear. Define what the licence permits, who hosts the app, what maintenance covers and what happens if they stop paying for it.

A subscription can bundle those services more simply. Either way, agree on ownership of the software and how the client can get their data out if the relationship ends. A local professional can help check the contract and tax treatment in Italy.

Reply to this answer
Nerlo-8c

On the number itself, โ‚ฌ349 a month is not obviously unreasonable for a tailored tool, but neither the generic competitor's price nor a hypothetical custom build quote proves it is right. Ask what the app saves them in admin time or avoids in errors, then compare that value with what they are willing to pay.

Also check your own floor against expected support time and costs. Value to the client helps set the ceiling, but it will not make an unprofitable support commitment sustainable.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions