Help for owners
I do not need a project, I need a developer I can call whenever something comes up
Short answer
If your app or site needs small changes, fixes and updates all year, a monthly arrangement suits better than a series of projects. It has a written scope, a way to send requests, and a known person who already understands your system. Start by listing what you ask for most often.
Does this sound like your situation?
- I keep needing small changes and a new quote each time slows me down.
- Something breaks every few weeks and I have to search for someone.
- The developer who built it is gone and nobody knows how it works.
- I do not need a full-time employee, but I need someone I can rely on.
- I am worried about updates, security and expiring certificates that nobody is watching.
Why does this happen?
Software needs looking after after launch
Phones, servers, libraries and store rules keep changing. An app that was working when delivered needs updates to stay working.
Project work starts from nothing each time
With one-off projects each new developer must learn your system again. A known person who already understands it works faster on small tasks.
Small tasks do not suit a big engagement
A small text change or a fix does not justify a full project process. Without an ongoing arrangement, such tasks wait or get dropped.
Nobody is watching for slow problems
Expiring certificates, full disks, old versions and unused accounts do not announce themselves. Someone has to look.
What can I do about it today?
- Write down what you have asked for in the last few monthsFixes, changes, questions, urgent calls. The list shows what kind of support you really need.
- Mark what was urgentNote which items could not wait. That shows whether you need fast replies or only a regular slot.
- Decide who sends requestsOne or two people on your side, sending in writing, so tasks do not get lost.
- List your accounts and systemsHosting, domain, app stores, code repository and third-party services, and who holds each login.
- Ask for a written scope before agreeingIt should say what is included, how requests are sent, how fast I reply and what is billed separately.
When should I bring someone in?
- A past developer left and nobody understands the system.
- You have had two or three emergencies and each time started from zero.
- Your app or site earns money and downtime has a cost.
How do I handle it?
- Start with a short reviewI look at the app, server and accounts, and write down what is there, what is at risk and what needs attention first.
- Agree a written scopeWhat is covered, how requests arrive, and what falls outside it. I reply to requests within 24 hours.
- Keep the system watchedI check the slow-moving things such as updates, certificates, backups and store requirements.
- Back up before production changesEvery change to the live system has a backup first and a tested way back.
- Report in plain wordsA short note of what I did, what I found and what I suggest next, so you can follow without technical knowledge.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is this the same as hiring someone full time?
No. It is a smaller commitment for a system that needs regular attention but not a full-time person.
Can I stop whenever I want?
The terms are agreed in writing at the start. I keep the documents up to date so you can move on without losing access.
What if I have a big new feature?
A larger piece of work is scoped separately, in writing, before it starts.
How do I send requests?
By email or a shared message channel, one request per message, so each is tracked.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.