Your team does the same work every week. I build AI systems that take it over.
Support email, order processing, content: I capture how your team does it, build the system, and hand it over. In production in weeks, run by your team, not me.
30 minutes. If I can't help, I'll tell you straight.
24 countries
One AI agent answers all the support email
2000+
Google Ads experts run their day on PPCOS
3M rows
Of search data, turned into category pages that rank
$10k/mo
The SaaS quote my client never had to pay
Your business runs on memory.
Every business has an Alex. The one who knows how the container prices get calculated, which customer emails need care, why the report is built the way it is. Explaining what Alex does takes half a day, and afterwards still nobody else can do it. That's not a process. That's a liability.
While Alex is around, everything works. When Alex is on holiday, sick, or gone, the work piles up or goes wrong. Hiring doesn't fix it. The new hire just learns a copy of the same problem.
And no, the answer is not replacing Alex with AI. It's taking the repeat work off Alex's plate, so they can do the work only Alex can do.
If your team can explain it, I can automate it.
That's the whole test. Sit me next to the person who does the work. If they can walk me through it, what comes in, what they check, what goes out, I can build a system that does it.
I call the process the Context Sprint. I capture the knowledge, then build the system around how your team already works. The AI models are already good. The knowledge is what's missing.
And no, not every idea survives. 85% of my own AI experiments land in the trash. That's the method. The 15% that works, works in production. You only pay for that part.
What changes.
The work stops waiting for one person.
Orders, emails, reports: handled the same way whether Alex is at their desk or on a beach in Portugal.
Hours land back on the calendar.
The system eats the repeat work, and the week suddenly has room for the work that needs a human brain.
Nobody gets replaced.
The person who explains the workflow to me is the one who ends up running the system. They lose the grind, keep the judgment calls.
You own everything.
Your accounts, your tools, your data, your docs. If I disappear tomorrow, the system keeps running.
A customer emails a trailer shop at 2 AM, in Polish. A minute later there's a correct answer waiting. That system answers support email in 24 countries, every day.
Recent work.
Real systems. Real teams. Real production work.
An AI Email Support Agent for E-Commerce
A Laravel + Filament email agent that classifies, drafts, and auto-sends customer support email. Multilingual. 13-step safety gate. Running inside a Dutch trailer-parts shop that ships to 24 EU countries.
PPCOS. An AI Operating System for Google Ads
29 Google Ads skills and a setup course that takes a marketer from never opening a terminal to running their first AI agent the same day. Live inside a 2200+ member PPC community.
What people say.
Hi, I'm Alfred.
I spent 9 years in marketing: Google Ads, content, e-commerce, SaaS. Real budgets, real mistakes. Then I taught myself to build with AI, the FAFO way.
That combination is the job. Developers can code but haven't done the work. Consultants know the work but can't build. I sit in the middle: I understand the workflow AND I build the system.
Start small. Scale what works.
Every engagement starts with a free discovery call. We find the one workflow that eats the most hours, then pick the right size for the first build.
I build everything myself. No juniors, no outsourcing. That caps it at a few builds per quarter.
Pilot Build
Fixed scope, 2-4 weeks. We pick one workflow and I build it end to end, in production. You see it running on your real work before committing to anything bigger.
If the pilot doesn't run in production, you don't pay the final invoice.
Book a free discovery callFull System Build
Custom AI systems built on your tools and your workflows. Full handover: documentation, training, your team runs it. No dependency on me.
Fixed quote after the discovery call.
Book a free discovery callTeam Training Day
One day with your team. I teach them how to build and run AI workflows themselves, on their real work, not slides.
One day with your team, fixed price.
Book a free discovery callUsing AI daily, but stuck at the chat window?
I also do 1-on-1 coaching. Same approach, scaled to one person. We build your systems together and you keep the skill.
See coachingIs this for you?
This is for you if...
- You run an agency, e-com shop, or consultancy where the team burns hours on repeat work
- You tried AI tools, but nothing stuck in production
- You want systems on your own tools and data, not another SaaS subscription
- You want your team self-sufficient, not dependent on a vendor
This is NOT for you if...
- You want a chatbot to slap on the website
- You want a one-off prompt workshop with no follow-through
- You have no repeat work to build on yet, every job is a one-off
- You want someone to run it forever for you
How this compares
Off-the-shelf AI tools
- Fit to your workflows
- Generic. You bend your workflow around the tool.
- Who runs it after
- You keep paying and wait for their roadmap.
- What you own
- Another subscription.
- Knows the work
- It knows the tool. It does not know your operation.
Hiring a dev agency
- Fit to your workflows
- They can code, but they have not done your kind of work.
- Who runs it after
- You wait on them for every change.
- What you own
- Code you may not understand.
- Knows the work
- You explain the business again and again.
Working with Alfred
- Fit to your workflows
- Built on your tools and data.
- Who runs it after
- Your team is trained and self-sufficient.
- What you own
- Everything. Docs, workflows, accounts, system.
- Knows the work
- 9 years doing the work before building the systems.
Questions you probably have.
It depends on scope. After the free discovery call, I give you a fixed quote for the work. The pilot build exists so you can start small and see the system running before a bigger commitment.
No. The person who explains the workflow to me is the one who ends up running the system. The system takes the repeat work they already hate. They keep the judgment calls, the exceptions, and the interesting part.
That is the point of building around how the team already works. Your team is involved during the build, so the system does not land like a random tool from outside. Handover and training are included.
No. Everything runs on your accounts and your tools. Documentation and training are part of the handover. I build myself out of the picture.
That's the point. If your team can explain the workflow, I can automate it. Nobody on your team needs to code to run the system. Most of my clients sell trailer parts, rent equipment, or run agencies. Not software.
That is what the pilot is for. Small fixed scope. Real production work. And if the pilot doesn't run in production, you don't pay the final invoice.
Everything runs on your accounts and your infrastructure, so your data stays where it already lives. I don't take customer data home. If your workflow touches personal data, we design around that from day one.
A few hours from the person who knows the workflow, spread over the build. If explaining it takes half a day, that half-day is the best investment you'll make: it's the knowledge your business runs on, finally written down.
Book a free discovery call.
30 minutes. You tell me where the hours go. I tell you what I'd build first and what it costs. If I can't help, I'll say so.
Book a free discovery callIf your team can explain it, I can automate it.