Built properly.
Then looked after.
Neo Innovations is an independent software practice. Custom web applications, rescue work on projects that have stalled, and ongoing care for the systems a business actually runs on.
Most technology problems in a small business are not really technology problems. They are the absence of someone who owns the outcome.
That is the job. One senior person, accountable from the first line of code to the late evening when something breaks — instead of four suppliers pointing at each other.
01 Build
Software built to outlast the enthusiasm that started it.
Web applications for businesses whose work does not fit an off-the-shelf tool. Built on mainstream foundations — Next.js, Django, PostgreSQL — so any competent developer can pick them up after me. Nothing exotic, nothing locked to a single vendor, nothing you cannot walk away with.
-
Progressive web apps
Installable on any phone, tablet or desktop without going near an app store, and tolerant of a bad connection in the middle of a working day.
-
Real multi-user systems
Roles and permissions, approval workflows where junior staff enter and senior staff verify, and an audit trail that shows who changed what.
-
Wired into what you already use
Bookings, payments, stock and messaging connected to the gateways and tools already in the business, rather than replacing all of them at once.
-
Escape from legacy software
Moving off single-PC desktop programs that no longer have a future, carrying the historic records across intact rather than starting from an empty database.
02 Rescue
When the last developer stopped replying.
A stalled project is rarely beyond saving. Usually it needs an honest audit, a security pass and a clean handover of the keys. I take over systems other people built: read the code, find what is genuinely wrong, say plainly what it will take, and then get it stable.
-
An audit you can act on
A written read of the system: what is sound, what is at risk, what it costs to fix, and what can safely be left alone. Often the finding is that a rewrite is not needed.
-
Security hardening
Debug mode left on in production, an exposed admin, insecure cookies, missing headers, end-of-life dependencies. The unglamorous pass that everything else sits on.
-
Getting the keys back
Access handover run as a checklist — servers, code repository, database and backups, DNS, email, payment gateway — so nothing is quietly still in someone else's name.
-
Onto hosting you control
Migration to infrastructure with real shell access, a staging environment separate from live, and offsite backups that have been restored at least once to prove they work.
-
Visible progress
A numbered defect register and test rounds after every release, so you can see what was fixed and what is still open instead of taking it on trust.
03 Look after
The in-house IT department you do not have to hire.
A fixed monthly arrangement covering the whole technology side of a small business: the website, email, hosting, online stores, and the everyday questions nobody else can answer. One point of contact, on a predictable fee, with no employment overhead behind it.
-
Keeping it running
Uptime monitoring with alerts, offsite backups, security patches and dependency updates, and a fix when something breaks rather than a ticket number.
-
Email that arrives
Google Workspace accounts, aliases and storage — and the deliverability work behind them: SPF, DKIM and DMARC set up properly so your mail stops landing in spam.
-
Hosting and domains
Servers, DNS, certificates, staging environments and migrations. Held in your accounts, documented, so the setup is understandable by someone other than me.
-
Everyday tech support
The go-to for the online side of the business: logins and accounts, marketplace stores and listings, business messaging tools, and advice when you are not sure how to handle something.
-
A written update, monthly
What was done, what is queued, and where a request sits when several land at once. Short, in plain English, and sent whether or not you chase for it.
What that is made of.
Build
- Next.js and React
- TypeScript
- Django and Python
- PostgreSQL
- Supabase
- Progressive web apps
- REST APIs and webhooks
Run
- Linux servers, root access
- nginx and systemd
- Vercel and Cloudflare
- Staging environments
- Automated offsite backups
- Uptime monitoring
- Hosting migrations
Secure
- Security audits
- Dependency hardening
- Role-based permissions
- Audit trails
- Rate limiting and abuse control
- Access and key handover
- Backup restore testing
Support
- Google Workspace
- Email deliverability
- DNS and domains
- Payment gateways
- Marketplace stores
- Staff training
- Documentation and handover
How I work.
-
You own everything.
Every account stays in your name — servers, domains, repositories, data. I hold access, not ownership. If we part ways, nothing has to be prised back.
-
Nothing starts without a scope.
Anything beyond the agreed work is quoted and approved before it begins, not explained after it is done. If a request is going to run long, you hear that first.
-
Third-party costs pass through at cost.
Hosting, licences, gateways and services are billed at what they actually cost, with no markup, and the receipts are there if you want them.
-
Month to month.
No long lock-in on ongoing work. If it stops being worth what it costs you, say so and we stop.
-
Remote, and honest about it.
The work happens on your systems online. If something needs a person physically in the building, I will say so rather than pretend otherwise, and help you brief whoever goes.
-
Told straight.
If an idea is premature, risky, or cheaper solved another way, you will hear that — including when it means less work for me.
Tell me what is not working.
A short description of the situation is enough to begin. If it is a rescue, send whatever access or documentation you still have and I will come back with an honest read on it.