The short answer

Code is one-time revenue. Deployment, maintenance, training, customisation and response are recurring cash flow.

Code is one-time revenue. Deployment, maintenance, training, customisation and response are recurring cash flow.

Start with the formula: Indie income = project + maintenance × time + custom work × scope + training/deployment

This article turns the issue into four execution steps and six checks that teams can apply directly to their product, website or advertising dashboard.

The real scenario: the problem is a chain

After source-code handoff, the customer immediately faces domains, certificates, payment callbacks, notifications, backups, access control and upgrades. If all of this is treated as a favour, support becomes unbounded and the customer still lacks a reliable response path.

A low one-time quote is easy to sell because long-term responsibility is hidden inside free support. A sustainable model separates deployment, maintenance, training, hosting and customisation into explicit services.

Decision rule

Split delivery into launch, stable operation and continuous improvement. Define scope, response time, included hours, extra fees and exit terms for each stage.

Four dimensions to inspect first

DimensionWhat to inspect
Deploymentlaunch/migrate
Maintenancemonitor/fix
Traininghandoff
Customnew scope

Do any of these situations match your team?

Solo developer handling build, launch and support

Free Q&A starts immediately after delivery and fragments the week without a price

List deployment, maintenance and response time separately on the next project

Three-to-five-person studio with many clients

Ad-hoc requests interrupt delivery and every client feels urgent

Control scope with service packages and ticket boundaries

Custom-software team serving enterprises

The contract covers development only, leaving long-term maintenance unpaid

Turn stable operation and upgrades into renewable services

Real team scenarios and first actions
Different teams need different answers. Identify the scenario before deciding how much to invest.
The hidden revenue independent developers<em>often ignore: delivery and support</em>
Break the issue into actions, metrics and evidence before investing.

1. Four execution steps

StepAction
Define handoffCode, accounts, docs and environment
Productise supportResponse time, limits and channel
Monthly/quarterly plansMaintenance and upgrades
Track changesScope, hours, acceptance and payment
How to frame the economics
Clarify the action, cost and result before debating tools. The framework is for building your own baseline, not a revenue promise.

2. Six execution checks

01 Delivery list

Does the client know what is included?

02 Account ownership

Domains, stores, servers and third parties

03 Maintenance scope

Fixes, updates and content changes

04 Response SLA

Hours, channel and escalation

05 Custom pricing

Is scope change repriced?

06 Exit plan

Migration and knowledge handoff

Six conditions to verify before execution
No checklist is all-or-nothing, but a missing condition can invalidate the rest of the investment.

3. Four common mistakes

01

Looking at one aggregate metric

02

Treating one case as a benchmark

03

Changing several variables at once

04

Never validating the real user path

Recommended path from assessment to execution
Produce evidence first, then expand. The wrong sequence makes more tools create more confusion.

4. Quick motion overview

Growth series motion overview
Series video/GIF overview. The full video is available on the website.

Series overview

A short visual overview of the nine scheduled growth and product articles. The article below contains the full analysis.

5. Frequently asked questions

What is the core test?

Indie income = project + maintenance × time + custom work × scope + training/deployment

What should we check first?

Does the client know what is included?

What is most often missed?

Hours, channel and escalation

Which teams are most likely to face this?

Solo developer handling build, launch and support, Three-to-five-person studio with many clients, Custom-software team serving enterprises

What should a small budget validate first?

Choose one team scenario and one observable result. Spend a week establishing a baseline instead of changing product, acquisition, payments and content at the same time.

When should the team pause?

Pause when no one owns the outcome, reporting definitions cannot be aligned, or repeated tests show no change in core user behaviour.

What counts as a valid result?

A valid result is not a temporary dashboard spike. It is a repeatable change in the key action, cost and retention that the same evidence can explain.

When do we need specialist help?

When the issue spans systems, payments, privacy, permissions or multiple platforms and internal data cannot isolate the cause.

Official references

Follow HiSpark for practical growth analysis

If you are building an app, website or software product, send your product type, target market, current stage and main problem. We will identify the bottleneck before recommending development, acquisition or monetisation changes.