ServicesWhat I do, and who for.
Whether you have no technical team at all or already have one, the approach is the same: a written scope before we start, and nothing you cannot take over afterwards.
Build or rebuild your website
You have no technical team, and you want it to work without having to understand how.
A website, built to measure
- The situation
- You have no website, or the one you have no longer looks like you and brings you nobody.
- What I deliver
- A site built for what you actually do: quick to load, readable on a phone, and yours to grow. Brochure site, bookings, catalogue, or a craft to put on show. The hosting and the domain name are in your name, and you keep the keys.
- Not a fit if
- You want a simple blog you will update yourself every week: an off-the-shelf tool, set up properly, will cost you less. I will tell you so.
In practice Built from scratch, no bought theme and no page builder. Astro, Nuxt or Laravel, whichever fits.
A business application or internal tool
- The situation
- The things you do by hand, in spreadsheets or over email, that eat time and earn nothing.
- What I deliver
- A customer area, a back office, an internal tool that replaces three spreadsheets. Delivered in stages, so you can correct course along the way rather than at the end.
- Not a fit if
- An off-the-shelf product already covers the need: a subscription will cost less than custom work.
In practice Node.js, TypeScript, Vue or Nuxt. User accounts, permissions, online payments where the need is real.
Taking over an existing site
- The situation
- A site or an application ageing badly, a supplier gone, and nobody left who can say what is inside it.
- What I deliver
- I read the code, the data and the servers, then tell you what to keep, what to rebuild, and in what order. Before proposing a full rebuild, I always check whether a repair will do.
- Not a fit if
- You have neither the access nor the source code, and the previous supplier cannot be reached.
In practice Whatever stack is already in place. Hosting, backups and documentation put back in order.
Strengthen your technical team
You already have one. It needs an extra pair of hands, an outside opinion, or someone to get production back under control.
Architecture review
- The situation
- The product runs, but nobody knows exactly how any more. A big decision is coming: rebuild it, move hosts, take more traffic. And nobody wants to make it blind.
- What I deliver
- A read of the code, the data and the servers, then a document saying what holds, what does not, what standing still costs, and in what order to act.
- Not a fit if
- What you need is a list of tickets worked through.
In practice A read of the repository, the data model and the infrastructure. Written findings, then a meeting to go through them with your team.
05Fixed price or time and materials
Product development
- The situation
- Something to deliver end to end: a significant feature, a rebuild, or a whole product.
- What I deliver
- The code, the tests, the release and the documentation that goes with it. Delivered in visible stages, not all at once at the end.
- Not a fit if
- The specification is not open to discussion.
In practice Node.js, TypeScript, NestJS, Vue, Nuxt, Laravel. MongoDB or MySQL, depending on what is already there.
Getting production under control
- The situation
- The service goes down without warning, nobody knows why, the backups have never been tested, and the hosting bill climbs without anyone knowing what it pays for.
- What I deliver
- Monitoring that warns you before your customers do, releases you can repeat, backups that have actually been restored, and a view of the costs with what can come down.
- Not a fit if
- The infrastructure is entirely managed by a third party and cannot be touched.
In practice Linux, Nginx, systemd, Prometheus, Alertmanager. Automated deployments and a restore tested for real.
Embedded senior developer
- The situation
- A small technical team that needs someone experienced over the long run, able to take a piece of work and carry it to the end on their own.
- What I deliver
- Regular hours, a presence in your tools, and work I own on my own all the way to release.
- Not a fit if
- The role is full time and on site.
In practice Back end first, interface when it is needed. Code review, architecture documentation, handover to your team.
Always included, whatever the format.
Three things depend on neither the format nor the duration: what is written before we start, what is documented along the way, and what you are left with at the end.
- 01
A written scope
What is covered, what is not, and how we decide when something comes up.
- 02
The documentation
What was done, and above all why. The decisions as much as the code.
- 03
The handover
Your team, or whoever comes next, can pick it up without calling me.
Not sure which format fits?
Describe the context in a few lines. That is exactly what the first conversation is for, and it comes with no commitment.
Get in touch