Automation for small businesses

The work that comes back every week now runs without you.

You have already automated things yourself, and most of it works. As long as you sit next to it and help along. I build your processes so they keep running while you are away for two weeks.

Free intro call →How I work
✓ One contact✓ If it does not run, I rebuild it✓ GDPR-compliant, EU-hosted
26
days my own shop took no order above 99 €
1,100€
in revenue that one stray number cost
0
alerts. Every status stayed green the whole time

That was my own shop, in July 2026. The uncomfortable question is how long it would go unnoticed in yours.

How I prevent it now →
Why you are here

It runs. As long as you are there.

You already automate things, you build yourself prompts and skills, and plenty of it works. Just only while you are sitting next to it, nudging. The moment you step away, it stops.

01

Three automations started. Two of them only run if you step in halfway through.

02

The prompt that genuinely works lives in your head and in a chat log.

03

Onboarding someone takes longer than doing it yourself. So you do it yourself.

You are not short of ideas or tools. You are short of the layer underneath.

Jurek Krosta
On site in Berlin or remote
Why I build this way

It took me 26 days to notice.

I'm Jurek. In July I touched a shipping rule in my own store and typed a 99 into a field that should have stayed empty. Above 99.01 € no customer was shown a shipping option at all. Ordering was simply impossible.

I found out 26 days later. No error, no red field, and when I asked the API it cheerfully confirmed the setting I wanted to see. It reported what was configured, not what the customer got. Thirteen carts worth 1,914 € were left sitting there. Since then every process I build gets a watcher that checks the result rather than the setting. That is what people actually pay me for: not for something to be built, but for someone to notice when it stops.

Book a call →Jurek Krosta
One example

This is what one looks like.

An order sets it off. A tightly instructed AI agent pulls the facts from your database, updates three systems, and asks in Slack before anything reaches the customer. Built in an afternoon, running on its own ever since.

System promptDatabaseAn ordercomes inAI agentdecides nothing on its ownShopupdatedBudgetadjustedNotecreatedSSlack asksfor sign-offYou approve

The process does not end when something is sent, it ends with you. Anything that reaches a customer passes a human first. That is the difference between automation and losing control.

How I build this →
Proof, not promises

Projects that run.

No invented quotes. Real businesses, real operations, real results, check them yourself.

Intro call

Let's talk about one process for 25 minutes.

Free, no strings, by video or in person in Berlin. You get an honest assessment at the end, including if that assessment is that you do not need anyone for this.

01You describe one task that costs you time every week
02We work out whether it is worth automating and roughly what it costs
03You get a recommendation, even when it argues against a project

My commitment: if a handed-over process does not run the way we described it beforehand, I rebuild it until it does. No new invoice, and no argument about whose fault it was.

Pick a slot.

Choose a time that suits you. The few questions in the form are there so I arrive prepared.

Clicking loads the Cal.com calendar, which sends data to Cal.com. Nothing is loaded before you click. Privacy