Intelligent systems. Bold results.

If any of these describe you, we should talk:

• You don't have enough data to make informed decisions about marketing, hiring or process optimisation.
• You run a small or mid-size company.
• You want to develop an app or a system for other clients or for your own users. I was part of the team that built texttoquant.com, which ships as a hosted MCP server.
• You have processes that are costly in time or money.
• You want to optimise the workflows of your team or your own work, so you can get more done in less time and spend more time with your family and friends.
• You have an idea for an app or a software project you want to launch, but no idea where to start. If I like the project, and I can see real value in what you bring to it beyond the loose idea, I could come on as technical cofounder.

It depends entirely on what we're building. If it's an AI agent for a specific niche problem, the timeline follows the complexity of the task — I won't spend more time than the job needs. That could be one or two days, or one or two months. If you want an actual assessment, call me or write with your specifics. We don't do corporate bull-shit, so I try to be as transparent as possible.

That's fine — depending on the project, we don't need upfront payment at all. If I'm building software for the company, expect to pay a deposit and then a payment against each agreed milestone. That's very normal. What I also offer is a performance-based option: taking a percentage of the company's income over a defined period, instead of a fixed fee. This is easy to arrange, and it's what I usually do for projects where I can help you get significantly more out of the process — rather than delivering the product and then leaving.

Absolutely — if you have the need for it. My goal is always to hand the work over in a way that fits you, so you're not dependent on me. That said, there's usually a period of one to three months, depending on the project, where I help out with further iterations, new features, or maintaining the project until you've found someone else to take it on. Most of the systems I build maintain themselves with very little input, so it shouldn't be a problem at all. If you want a "tech person on speed dial", that won't be free forever — but I'm glad to help smaller businesses with tasks that aren't too time-consuming.

You tell me some of the frustrations you're running into. I ask questions to understand your processes and your business. Then I give you clear, actionable advice and solutions — free, and they don't necessarily involve my services. You'd be surprised how far you can get with free tools, without paying a third party to come into your business and make changes or additions. No sales pitch, and absolutely no commitment.

That's kind of the whole point. I wouldn't want to fix what isn't broken — we can always just optimise what you're already doing. If I do see that a process you're using is unnecessarily expensive or time-consuming, I'll tell you what I'd recommend changing.

That's a case-by-case question, and there isn't a single honest number for it. The return is usually fairly linear. I've freed up engineers who were doing repetitive simulation work by giving them a specialised agent trained to do exactly that, so the engineer could spend their time on work that matters more. I've also built plenty of agent workflows that simply save two to four hours of administrative or documentation work. So it depends on the project, and on the time and capital cost of the task being automated. And I'm not out to replace human workers. I know most company owners don't want to fire their people — they want them doing more meaningful and important work.

Not at all. It would be a complete failure on my part to leave you with a system you don't know how to operate. I always focus on making the tool genuinely easy to use for the client. If it can't be easy, I'll make sure there's proper documentation and procedures, and I'll take the time to train you personally. I've never had anyone have an issue with this. I design systems that make sense to real humans, not just other developers.

I treat your data like it's my own, because a data breach would ruin my reputation overnight. Data security and privacy isn't actually that hard. Most problems come from human error and from keeping data in places that can be compromised — I don't do that. I follow the straightforward GDPR rules and best practices, in line with the European Data Protection Board's guidance for small businesses. The core of it: the right technical and organisational measures for the risk, protecting the confidentiality, integrity and availability of your data, with regular reviews and documented procedures. I'm also not some faceless corporation that can blame the issue on a random intern or hire. In most cases I try to get the data and the finished system hosted and stored by you — I help you do it, but that means you're responsible for following best practices. Rotating your passwords. Not giving access to devices with fingerprints or keys to important systems. Basic stuff.

Reference: European Data Protection Board — Secure personal data (guidance for small businesses).

Definitely. I can either work alongside your team or handle everything independently, whichever makes more sense for your situation. I've done both, and I'm pretty good at not stepping on anyone's toes. Personally, I've only worked with mid-size teams of five to eight people, on development projects or when training a team to use specialised software. If you have something else in mind, I'm sure I'm up for it — I'd just want the details cleared first.

I cover bug fixes and small tweaks for a reasonable period. That's just good business. For bigger changes or new features, we can work out a fair rate. If you've been a client of mine, I always want to make sure you're taken care of.

Of course not. I won't disclose anything you tell me, or put in writing, that you don't want shared. If it's a system I personally thought up, drafted, tested and built for your company, I will use it as a starting point if another client later needs something similar. But I will strip out anything that could point to your company having that solution. The reason I don't disclose which clients I work with, or which solutions I've built, is this: if any of my systems were compromised, or a library or tool I'm building with, knowing my clients would become an attack vector. That's why I take this kind of privacy very seriously. Call me paranoid — fair.

Yes, and it is a normal part of the work. I host it on infrastructure I maintain, keep it patched and backed up, and put it on your invoice as a clearly stated line at a fair fixed price. You are never paying a hidden margin inside the build price, and you can move the system to your own server at any point without losing anything.