Before You Subscribe to a Custom Website or App: Scope, Support and Your Way Out

A monthly quote for a custom website or app can cover both building it and keeping it running. Before you sign, separate those two jobs. Ask what you can accept at launch, what the provider handles each month, and what you could take with you if you left. You can then compare offers that would actually do the same work.

What should you be able to accept at launch?

Write down the work people need to finish. For a website that brings in enquiries, follow one enquiry from the form to the colleague who handles it. Check that someone on your team can change a service page and find out if the form stops working. For a membership app, ask to see a member pay, get access and cancel, and a staff member resolve a failed payment. Those jobs may need different accounts and integrations, even if both proposals say “custom development”.

Agree who supplies content and data, which integrations are included, and who handles deployment. Decide what counts as acceptance, who approves it, and what happens if your team is late with an input. Ask exactly when billing starts: signing, a milestone or launch can mean different things. Record the agreed trigger and what you can check at that point.

What does the monthly payment keep running?

Ask the provider to name the work included after launch. Who hosts it, applies updates, watches for failures and checks that a backup can be restored? Find out who answers when a form fails or members cannot sign in, how the issue reaches someone who can fix it, and what response you can expect under the agreement. Our guide to what happens when a custom app breaks explains why responsibility depends on how it is operated.

Use real changes to draw the line. Updating service hours, redesigning the enquiry flow and adding a new payment provider are different jobs. Ask which are included, which need an estimate, and who approves the extra work. List other subscriptions and licences the site or app needs, who pays for them and what happens if one changes or ends.

UK government purchasing guidance treats continuing supplier management as part of the purchasing decision. The useful idea here is to agree how the service will be run before you commit to it.

How do you compare the cost of two offers?

Use the same launch scope and support needs for each proposal. Add the setup fee, recurring charges over the minimum commitment, and any required third-party costs you can identify. Write likely extras separately, with their assumptions, so you can see what would change the comparison. Use the same period if you compare a subscription with a separate build and care agreement. Include work your own team would have to do under each option.

Check how the agreement renews, when notice must be given, and what charges or obligations continue after notice. A provider taking care of more of the work can be worth paying for. The question is whether that work is useful to you and whether you are comfortable with the cost and the responsibilities you keep.

What could you take with you if you cancel?

Ask for a written answer for each thing the business depends on: the domain, content and data, admin accounts, and any app-store or payment-provider accounts. Note who controls each one now and whether another operator could get the access they need. Check the licence separately: what may you continue to use or modify, which components would be handed over, and which licences or services would need replacing?

A download of your content or member records may be useful in a move. To keep running the same site or app, someone may also need deployable software, instructions, access and replacement services. Our guide to moving an existing website without rebuilding explains how those pieces affect portability. If the agreement offers a data export, try one export with representative records before depending on it.

Ask the provider to walk through a departure at the end of the term. When does hosting stop? How long can you retrieve records? What help is available, at what cost, and who takes over if the usual contact is unavailable? UK government guidance on cloud lock-in describes the trade-off between useful provider services and the effort of leaving. For your site or app, the test is whether the benefits are worth the specific dependencies and exit costs you have identified.

Write down what you are agreeing to

Keep a short record beside each quote. Include the launch deliverables and how you will accept them, the ongoing work and when extra charges apply, the full commitment and renewal terms, and who controls each account or can take over at the end. Ask the provider to fill in unclear answers before you sign. If one proposal still cannot show who will restore the site or what happens when you cancel, you have found a gap worth resolving before comparing prices.

Discuss a Timeless website or app

We build custom websites and apps through Timeless with ongoing care under a monthly model. Bring the work you need at launch, the care you want afterwards and any handover requirements. We can discuss the scope and terms that would apply to your project.

Questions about website and app subscriptions