Systems and websites that take work off your team.

You write a few sentences about what you need. Then a call about the process, an estimate for the scope, delivery and support after launch. I run projects end-to-end, with no handoffs between departments.

There is no off-the-shelf price list, because an estimate depends on scope. I price what gets written down: we agree what needs to be built, I split it into stages and put a number on each one. Either a fixed price for a defined scope, or a day rate for longer engagements. The first call and the price range are free and carry no obligation, and nothing gets built before you have both.

The price follows the scope, the deadline and how much risk I take on. The smallest engagements I accept from new clients are a few days of work. Small changes to systems I already maintain go through the maintenance agreement. The price covers deployment to the server and handing over the accounts; what stays outside it is what you buy directly in your own name: hosting, the domain and paid integrations.

I give you a timeline together with the scope, after the call, because it depends not only on what has to be built but also on how quickly content and decisions arrive from your side.

I work in stages, so you see a working piece before the whole thing is finished, and every stage has its own date. If something slips, you hear about it in the week I see it, not at the end.

I start a new project once the previous one is live, so we agree the start date on the first call.

Yes. A contract with the scope, the dates and the rules for changes written down, so both sides know what is included and what happens when a new idea shows up mid-project. I will sign an NDA before the first detailed conversation if you need one.

Most of the systems I build run inside companies and are covered by confidentiality, so I cannot show them publicly.

On a call I walk through them without names: what the problem was, what got built and what changed in the way the team works. Publicly I can show this site and my own tools on GitHub.

I'm a developer, not a designer. On simpler projects I use my own tried-and-tested layout, like the one on this site. When the look matters a lot, I bring in a designer I work with, or work from a design you supply. I bring this up on the first call, so there are no surprises.

It's up to you. You can take over everything, because the project, its data and documentation are on your own accounts. You can leave maintenance to me: monitoring, backups, updates and fixes at an agreed level. Or you can hand it to someone else.

Yes, that is a common scenario. I run PHP and Laravel upgrades on live systems, from older, unsupported versions to current ones, with no downtime. I start with a review of the code and infrastructure so I can tell you straight what can be saved and what has to be rewritten.

Code and data created specifically for your project are transferred to you in the contract, together with the access and documentation you need to maintain and extend it. The open-source libraries the project uses stay on their own licenses. That is standard and does not limit what you can do with the code.

If the website uses my custom CMS, you get a perpetual license to use it on your site, with the right to adapt it for your own needs, without depending on me.

The code, the data and the documentation are yours: you get them on request at any time, and the server, the domain and the service accounts are in your name, so nothing is locked away with me. The repository can sit on my account or on your company’s, whichever you prefer. I write documentation so another Laravel developer can take the project over without talking to me: how to run it, how the integrations work and why the bigger decisions were made.

On longer engagements we agree upfront who picks the work up if I am unavailable.