Services
The six things I build.
AI Agents & Automation
Stop paying people to move data between tools.
I build agents that read your emails, update your records, chase your invoices and hand off to a human only when it matters. You describe the process you're tired of doing. I automate it.
Typical build: 1–2 weeks.
- How it runs
- We map the process you want gone, step by step. I build it, run it beside your current way of working for a week, then switch it over.
- What you supply
- Access to the tools it needs to touch: your inbox, your CRM, your spreadsheet and one person who knows how the process actually runs.
- What you get
- The running agent, a record of everything it did and a written runbook for when you want to change it.
Chatbots & Assistants Trained on Your Own Data
Your customers get answers at 2am. Your team stops answering the same question.
Upload your documents, policies, product catalogue or support history. I build an assistant that answers from your content, with sources, so nobody has to guess whether it made something up. EU-hosted and GDPR-ready if you're in Europe.
Typical build: 1–3 weeks.
- How it runs
- You send me your content. I build the assistant, you test it on real questions and I tune it until the answers hold up.
- What you supply
- The documents it should answer from, and twenty real questions your customers actually ask.
- What you get
- The assistant, embedded where your customers already are, answering with links to its sources. EU hosting if you need it.
Mobile Apps (iOS + Android)
One codebase. Both app stores. Live in weeks, not quarters.
I've shipped my own apps to the App Store, so I handle the parts most developers hand back to you: store listings, screenshots, subscriptions, review submissions and the rejections nobody warns you about.
Typical build: 2–4 weeks for a first version.
- How it runs
- Two weeks of design you sign off on, then build, with a working build on your phone every Friday. I handle submission and the review process.
- What you supply
- Your Apple and Google developer accounts, your brand assets and feedback on each Friday build.
- What you get
- The app live in both stores, the source code, the store listings and screenshots and 30 days of support.
Web Apps & Dashboards
The tool your business actually needs, instead of eleven spreadsheets.
Internal tools, customer portals, admin dashboards, booking systems. Fast, secure and simple enough that your team uses it without training.
Typical build: 2–4 weeks.
- How it runs
- We agree the screens first. I build them one at a time, so you are using it before it is finished rather than after.
- What you supply
- A sample of your real data, and the names of the people who will use it every day.
- What you get
- The deployed app, the source code, accounts set up for your team and a walkthrough call.
AI Features for a Product You Already Have
You don't need a new app. You need one smart feature in the one you've got.
Search that understands questions. Recommendations that fit the user. Summaries, classification, document reading. I add it to your existing product without rebuilding it.
Typical build: 1–2 weeks.
- How it runs
- I read your codebase first and tell you what is realistic. Then I build the feature behind a switch, so you can turn it off.
- What you supply
- Access to the repository and somewhere safe to test it.
- What you get
- The feature merged, tested and documented, with the running cost per user written down before you launch it.
Rescue for AI-Generated Code
Your prototype worked until it didn't.
You built something with an AI tool, it got you 80% there and now it breaks in ways nobody can explain. I take it apart, fix what's broken and turn it into something you can actually launch and maintain.
Typical engagement: 1–2 weeks.
- How it runs
- I spend the first two days reading it, then send you an honest report: what is fixable, what should be rewritten and what each would cost.
- What you supply
- The repository, and access to wherever it is currently running.
- What you get
- A working build, the breaking bugs fixed and a written list of what I would do next in priority order.
Questions
How much does a project cost?
It depends on the work. Projects start at $500, and go up from there depending on the scope and effort involved. After our call you get one fixed price in writing.
How long does it take?
One to four weeks, depending on what it is. Automations and AI features take one to two weeks. A chatbot takes one to three. A first version of a mobile app or web app takes two to four. You get a date in writing before anything starts, and a working demo every Friday until it ships.
Do I own the code?
Yes, completely. On launch you get the repository, the accounts, the documentation and a handover call. Nothing is hosted on my accounts or tied to my licences. If you want to move to another developer six months later, you can, and nothing breaks.
What if I don't know exactly what I want?
That is normal, and it is what the first call is for. You describe the problem: the thing that is slow, manual or costing you money. I turn it into a written scope with options and prices. If I think the idea needs changing, I will say so before you spend anything.
How do time zones work if we're not in the same country?
I work flexible hours and can overlap with whatever time zone you're in. You get me on calls, not a night-shift proxy. Paying me is easy from anywhere: bank transfer including ACH to my USD account, Payoneer or Wise, and I can usually work with whatever suits you. You get a proper invoice.
What happens after launch?
You get 30 days of support included. I fix anything that breaks, answer questions from your team and help you act on the first round of real user feedback. After that it's entirely optional: you can leave it running, hand it to your own team or keep me on as a maintenance option that covers bug fixes, small changes and priority response if something breaks. We can discuss any contract.
Can you work with the team I already have?
Yes. I have worked alongside in-house developers, designers and agencies. I use your repository, your tools and your process, and I write things down so nobody has to decode my work later. If your team is non-technical, I handle the technical side and translate.
What if I'm not happy with the result?
You see working software every Friday, so problems surface in week one rather than week four. If something is not right, I fix it, and that is part of the fixed price. If we get two weeks in and it clearly is not working, we stop and you pay only for what has been delivered.
Let's find out if this is worth building.
Fifteen minutes, free, no pitch. If it’s not a fit, I’ll tell you and point you somewhere better.
Book a free call