A long-term tech partner for a small product, without a retainer
Keep a small website or app healthy for years: maintenance, demos for new ideas and lower running costs, handled in writing with a fixed price per job.
Published
Many small products were built once by a freelancer or an agency, and then left alone. Two years later the owner has a working product, rising monthly bills, plugins nobody updates, and no one who remembers how it was built. Hiring a developer full time makes no sense; a monthly retainer often means paying for hours you do not use.
This is how I work with owners who want someone to stay with the product over time.
What “looking after” a small product actually includes
- Keeping it secure and running: updates, a supported PHP or runtime version, backups that are tested, certificates that renew.
- Knowing what it costs: a list of every service you pay for, what each one does, and what could be cheaper.
- Small improvements: a new form, a payment option, a faster page, an integration with a tool you started using.
- Written notes: what was changed, why, and how to undo it, so the knowledge stays with you, not in someone’s head.
Demos before big decisions
Before you pay for a large feature or a new product, a small working demo often answers the real question: will people use it, and does the idea work with your data? A demo can be a clickable page, a form that saves to a real database, or a short automation. Built on free hosting plans, it costs nothing to run while you test it, and you only invest in the full version once you know.
Lowering running costs
Running costs grow quietly. These are the usual places money leaks:
- Hosting sized for traffic you do not have. A small site rarely needs a dedicated server or a top-tier plan.
- Usage-based bills. Some platforms bill by traffic or function calls; one popular post on Indie Hackers describes a founder receiving a hosting bill of around $1,800 and moving to Cloudflare. Know which of your bills can grow without warning.
- Overlapping subscriptions: two form tools, two analytics tools, a paid plugin replaced long ago.
- Paying per seat for tools only one person uses.
Moving to cheaper infrastructure is not always worth it. Sometimes the move costs more than two years of the old bill. The point is to know the numbers and decide on purpose.
How it works with me
- No retainer. Each job has a fixed price agreed in writing before work starts.
- Everything in writing, so you have a record of every decision and can hand it to someone else at any time.
- You keep the keys: accounts, code and domains stay in your name. I get temporary access when a job needs it.
To start, describe your product: what it does, where it runs, what you pay each month and what worries you most. The first step is usually a review with a written list of risks and savings, priced up front.