What exactly do you build?+
We custom-build user-friendly operating systems, designed entirely around how your business works. Think of it as an all-in-one system that handles your entire business operation — everything in one place and automated where necessary, required and possible.
Rather than buying a generic platform and trying to configure it to fit, you get something that understands your specific rules, your exceptions, and your workflow based on what you tell me you need and want.
How is this different from off-the-shelf software?+
Off-the-shelf tools (like Noloco, Zapier, Make, Airtable or similar platforms) give you a generic template you then configure yourself. The problem is they hit a ceiling quickly when your business has complex or specific rules — and they put the burden of setup and maintenance on you.
What I build knows your business: your pricing logic, your customer workflow, your exceptions. You don't configure it. You tell me what you require and I build it.
What kinds of businesses do you work with?+
Small businesses, typically 2 to 30 staff, that have outgrown spreadsheets but aren't ready to hire a development team. The businesses that benefit most tend to have workflows that are too specific or complex for an off-the-shelf tool to handle well.
Industries I've worked in include hospitality, FMCG, retail, tech, and professional services — but the approach applies to any business with operational complexity and manual processes that should be automated.
Can you give me a real example of what you've built?+
A London art gallery was manually re-entering every sale across 3 separate systems. Each sale took 36 minutes of admin. I built them a system that saves them approximately £5,600 at their staff rate.
A London property surveying business has improved their report processing time by up to 48 hours, allowing them to take on 3–5 extra surveys per week and increasing their survey volume by a third.
How do I know if I need something like this?+
You probably have a real operational cost to address if several of these are true:
• Your team manually re-enters the same data across multiple tools
• You spend significant time each week on admin or reporting that should happen automatically
• You've tried a platform and found it couldn't handle your specific workflow
• Errors are creeping in because of manual data entry
• You couldn't double your sales volume without your back-office breaking
We're a small team. Is this overkill for us?+
The businesses that benefit most are exactly your size. Large organisations have development teams. Very small operations haven't yet built up enough volume for automation to make sense. The sweet spot is a business that's complex enough to have real operational pain, but not large enough to have the in-house resource to fix it.
If your team is regularly losing hours to manual admin, the size of the team isn't the question — the cost of that time is.
We already use [some tool]. Can't that do what we need?+
Possibly, and if it can, I'll tell you. Part of the initial conversation is understanding exactly what you need and whether an existing tool would genuinely cover it.
The cases where existing tools fall short are when your workflow has specific rules or exceptions a generic platform can't encode, when you need systems that wouldn't otherwise talk to each other to connect in a particular way, or when the time cost of configuring and maintaining a platform outweighs the benefit.
Can you work with the tools we already use?+
Yes. As long as your current tool stack allows for API integration, this is possible. If not, or the cost of integration is prohibitive, I find another automated solution for you.
I don't ask you to rip out what works. I build around it.
What does working with you actually look like?+
It starts with a discovery conversation — typically up to 60 minutes — where you explain your current processes and where the pain is. I need to understand as much as possible about your operation to determine whether I can genuinely help and what the right solution might look like.
If we proceed, I'll produce a scoped proposal outlining what we've discussed, what I'll build and what your bespoke system will do. The build happens in phases, with working versions reviewed at each stage. You see it taking shape before it's finished.
How long does a project take?+
It depends on complexity. A focused CRM with one or two modules could be working completely within four weeks. A more comprehensive system covering multiple operations might take 12 weeks, built in phases.
I'll give you a realistic timeline in the proposal, and projects are structured so each phase delivers something usable — not a big reveal at the end.
How involved do I need to be during the build?+
More at the start, less as it progresses. The most important input you give me is a clear picture of how your business actually works — the rules, the exceptions, the edge cases. That typically happens in one or two structured sessions at the beginning.
Your main involvement during the process is reviewing each phase as it's delivered and confirming it works as expected. I don't need you in the weeds.
Do you work remotely or in-person?+
Remotely. Most of what I do doesn't require physical presence, and the tools I use are designed to work across locations. If you're based in London, in-person sessions are available where useful, but not a requirement.
How much does it cost?+
It depends on what's being built. Smaller, focused systems start from a few thousand pounds. More comprehensive systems covering multiple operational areas are priced accordingly.
I price by project scope, so you know what you're getting and sign off on the cost before anything starts. The first conversation is free and there's no obligation to proceed. The ROI Calculator on this page is a useful tool to see whether what you're getting represents value for money.
How do I know if it's worth the investment?+
The simplest way: add up what the manual process actually costs. If a member of staff spends two hours a day on admin that could be automated, at your staff rate, across a full working year — that's your current cost. A system that eliminates it typically pays for itself within a year, often considerably less.
I can help you work through that calculation as part of the initial conversation. If the numbers don't stack up, I'll tell you.
Do you charge ongoing fees?+
Not as a default. What I build is owned by you once paid for in full — there's no monthly licence, no platform fee, and no dependency on a subscription.
You can choose to retain me for ongoing support, development or amendments after the initial build. That's available but optional at £50.00 per month, which means support queries are answered within 24 hours and further development is charged at a reduced rate. The running costs of the system itself (hosting, any third-party tools it connects to) are typically minimal and are yours directly.
What if the project changes in scope mid-build?+
Scope changes happen. The proposal I write is designed to be clear about what's included, which means additions are visible and can be costed separately rather than quietly inflating the original project. I generally future-proof the build so don't expect added costs when changes need to be made.
If something comes up mid-build that changes what you need, we'll agree on what it means for scope and any additional cost before any additional work starts. No surprises.
What technology do you build with?+
For most small business operations systems: Google Apps Script, Google Sheets as a structured database, and progressive web apps for mobile access. These are powerful, maintainable, and avoid expensive infrastructure.
Where needed, I integrate with external platforms via their APIs where possible and if not cost-prohibitive.
Do I need technical knowledge to use what you build?+
No. The systems I build are designed for non-technical users. Interfaces are completely user-friendly, intuitive, simple, and task-focused. Your team shouldn't need to understand what's happening in the background to use it.
Staff training is included in handover, and all documentation is in plain English — not technical jargon.
What if I want to understand how it works?+
The entire system build is fully documented. You'll receive a complete written record of how the system is built, what every part does, and how to maintain it. The documentation is written for someone who wants to understand their system, not for a developer.
If you ever need a developer to work on it in the future, they'll have everything they need to pick it up.
Can you connect my system to a specific platform?+
Most likely yes. Integrations with accounting software, payment processors, Shopify, Slack, Gmail, Google Drive, and others are generally available — sometimes at an added cost depending on the platform. If a platform has an API or data export, there's usually a way to integrate it.
The best way to check is to mention it in the initial conversation.
What happens after the system is delivered?+
You receive a fully documented, working system along with a handover session covering how to use it and how to make simple changes. The documentation is written for your team, not for a developer.
If something isn't working as expected in the period immediately after launch, I'll fix it as a priority. Beyond that, ongoing support and development is available if you want it — but the system I hand over is designed to run without me.
What if something breaks?+
A system failure means your business suffers and I don't want that. If there is a system failure I will support where necessary — it's important that you communicate exactly what has happened and what is not working. Depending on the reason for the failure, a support charge may be applicable.
Can the system grow with us as the business changes?+
Absolutely — and this is one of the advantages of bespoke over off-the-shelf. We can build the system out over a period of time, allowing you to budget accordingly.
Projects are structured with this in mind. The architecture is designed to accommodate future modules, not bolt them on awkwardly.
Do we own the system, or are we tied to you?+
You own it, completely. The code is yours, the documentation is yours, and there's no proprietary platform between you and your system. You're not dependent on me continuing to exist, continuing to offer services, or any ongoing licence.
That's a deliberate principle. You should leave a project like this with something you control — not a new dependency.