Skip to content

Automation Library

Automations I run for you, hosted in the EU.

For a shop, salon, agency or service firm: ready-made n8n workflows, tested before they touch your business and run on my own instance in Germany. You get the outcome. You never open the editor.

Speed-to-lead: what happens to a lead, in eight stepsBuilt.
  1. 1A lead arrives from a form or a webhook
  2. 2Spam checksRules
  3. 3Duplicate check over 30 daysRules
  4. 4Safety check on the message
  5. 5VIES and homepage lookups that never block
  6. 6Qualification against your criteriaRules and AI
  7. 7Auto-reply with your booking linkRules and AI
  8. 8Saved, a hot lead alerts sales, two chasersPerson

How the managed model works

These hold in every package.

  • I run it

    You get outcomes, and I run the workflows on my own instance in Germany, hosted at Hetzner. Email goes out through Resend, which processes it in the United States and keeps account data and email logs there, and WhatsApp goes through your own WhatsApp Business account. Telegram carries alerts and approval notices only, never personal data of your customers or leads.

  • AI on Mistral's EU endpoint

    AI steps run on Mistral's EU endpoint, which uses data centres in the EU and EFTA.

  • Demo mode first, then your approval

    In demo mode a workflow only sends to the addresses you list. Once live, anything sent on your behalf can wait for your approval: Telegram tells you a draft is waiting, and you read and approve it on my server.

  • AI-written text is labelled

    A reply sent automatically says so, and a sentence drafted by AI is labelled as such: in the footer in speed-to-lead, as the first line in the order-status replies. We settle the wording and where it sits with you before go-live.

  • I watch it

    I watch the workflows for failures and am alerted when one breaks. No fix time is promised.

  • You can leave

    You can leave with your data, as an export and a runbook for each workflow. I then delete it from my automation server, and my encrypted backups are overwritten as the backup cycle runs.

Packages

Each card says what the package does, what you provide and what it leaves out.

Built

Speed-to-lead

Leads from your website go cold while your team is busy.

Estate agency networks and B2B service firms that win work from a web form.

  1. A form or a website webhook sends the lead in. A spam and duplicate check runs first.
  2. A safety check reads the message before anything acts on it.
  3. Optional: the company VAT number is checked in VIES and its website is summarised.
  4. AI scores the lead against your criteria: budget, location and timeline.
  5. The lead gets a reply with your booking link. The target is under a minute.
  6. The lead is saved to your CRM or sheet. A hot lead alerts your sales person in Telegram with a reference number and score, never the lead's details; the details reach you by email.
  7. Follow-ups go out at 24 h and 72 h. They stop when the lead books or replies.
  8. A weekly funnel report closes the loop.
You provide
  • Your scoring criteria
  • Your reply templates
  • Your booking link
  • Access to your CRM or sheet
You get
  • A first reply to each lead that passes the checks. The target is under a minute.
  • A Telegram alert to your sales person for each hot lead, without lead details.
  • Your response time, measured before and after.
  • A weekly funnel report.
Limits
  • Replies are templates plus at most one personalised sentence, and that sentence is checked before sending.
  • WhatsApp is not in this version.
  • Replies are in English and Polish. Scoring keywords are mostly English.
Built

Post-purchase desk

"Where is my order?" emails and withdrawal requests fill your support inbox.

Online shops with about 1,500 or more orders a month on Shopify, WooCommerce or a custom platform.

Directive (EU) 2023/2673 added art. 11a to Directive 2011/83/EU: a trader who concludes distance contracts with consumers through an online interface must offer a withdrawal function. Member states apply the implementing rules from 19 June 2026 (Malta: regulation 13A, L.N. 145 of 2026); other states may still be transposing it.

  • Withdrawal function: built
  • Order-status answers: built

The withdrawal function

  1. Your team adds a "Withdraw from contract here" link to your site, pointing to the form.
  2. The customer fills in a two-step form.
  3. An automatic acknowledgement goes to the customer with the content of the statement and the date and time.
  4. Reminders follow the refund deadline.
  5. A refund is made only after you approve it.

Order-status answers

  1. A customer asks where an order is.
  2. The status is read from your shop and carrier data, and the answer goes only to the email address that placed the order.
  3. Any other question goes to a person as a draft.
You provide
  • Access to your shop and carrier data
  • Your withdrawal and refund wording, for your lawyer to approve
  • A person who approves refunds
You get
  • A withdrawal function with the form and the acknowledgement; your team adds the link.
  • Refunds that wait for your approval.
  • Order-status answers from your own shop and carrier data.
Limits
  • A person always handles anything that is not an order-status question.
Built

Confirm-or-release reminders

No-shows leave empty slots in the diary.

Multi-chair salons.

  1. A booking comes in.
  2. A reminder goes out 48 h before, with Confirm, Reschedule and Cancel.
  3. A second reminder goes out 24 h before, with the same three choices.
  4. With no answer 6 h before the slot, reception gets a call list. When a customer cancels, reception gets a waitlist suggestion for the freed slot.
  5. Reception marks a no-show in one tap.
  6. Each month you get a no-show report against your own baseline.
You provide
  • Access to your booking system
  • Your customers' WhatsApp opt-ins
  • Someone at reception for the call list
You get
  • Reminders the customer can answer in one tap.
  • A call list for slots nobody confirmed, and a waitlist suggestion for slots a customer cancelled.
  • A monthly no-show report against your own baseline.
Limits
  • WhatsApp needs the customer's opt-in and costs per message.
  • I measure your baseline for four weeks first.
  • I do not promise a percentage.

The rest of the portfolio

More workflows from the library. They have no package page yet, so ask about them on the call.

  • Morning owner briefing

    The state of the business in one message each morning.

    Built

  • Client document chaser

    Chases clients for the documents you are waiting on.

    Built

  • VAT-checked invoicing

    Invoices that check the customer's VAT number first, created in Xero and sent to no national e-invoicing system (KSeF).

    Built

  • Multilingual listing builder

    Listings written in several languages from one source.

    Built

  • Storefront check

    Regular checks that your online storefront works.

    Built

  • Rebook and win-back

    Brings customers back to book again.

    Built

  • Message receptionist

    Answers booking messages when reception is busy.

    Built

  • Review engine

    Asks customers for a review after a visit.

    Built

  • Short-let guest journey

    Guides guests of a short-let from booking to checkout.

    Built

  • Affiliate link health monitor

    Watches your affiliate links and flags the broken ones.

    Built

  • Partner programme desk

    Handles questions and sign-ups for your partner programme.

    Built

How I test

Every workflow goes through these steps before it reaches your business.

  1. Every workflow is built against fictitious test data.
  2. Each one gets a test table: the happy path, edge cases, prompt-injection attempts, a dependency failure and a privacy case.
  3. An automated review pass, not a person, then tries to break it, and I read every failing case before a client goes live.
  4. Last, it runs on a sandbox, with the email, Telegram and AI calls replaced by fixed results until a live test is run.

A statement on this page without a rank mark is asserted: I say so, and nothing on the page checks it.

Pricing

Scoped to you.

Setup
A fixed setup fee for each package.
Monthly
A fixed monthly fee for each package.
Quote
You get it in writing after the call.
At cost
WhatsApp messages, SMS and paid data APIs are passed through at cost.
AI usage
Included, under a fair-use limit that your quote states.
Currency
EUR, excluding VAT.
VAT
Reverse charge for EU businesses outside Malta whose VAT number validates in VIES. Malta VAT otherwise.
Invoiced by
Michal Jatczak, sole trader registered in Malta.
Service level
No SLA and no on-call duty. Dates are set in the written quote.

Book a 30-minute call

Questions

Who can see our data?

I can, because I run the workflows. They run on my own instance in Germany, hosted at Hetzner, and a workflow only handles the data its job needs. AI steps send the text they work on to Mistral's EU endpoint; Mistral may keep it for a limited period to monitor abuse, under its own terms. Email goes out through Resend, which processes it in the United States and keeps account data and email logs there, and WhatsApp messages go through your own WhatsApp Business account; both sit outside my instance. Telegram carries alerts and approval notices only, never personal data of your customers or leads. The Subprocessor Register lists my providers, and Telegram, which is not one of my sub-processors. Your WhatsApp Business account and the other accounts a package uses stay your providers, under your agreements with them.

Where does the AI run?

On Mistral's EU endpoint, which uses data centres in the EU and EFTA. The workflow engine itself sits on my instance in Germany.

What if the AI gets it wrong?

Replies are templates plus at most one personalised sentence, and that sentence is checked before it is sent. Anything sent on your behalf can wait for your approval, which you give on my server once Telegram tells you a draft is waiting. A workflow starts in demo mode and only sends to addresses you list. Before it goes live, every workflow is tested with prompt-injection attempts and failure cases. Anything outside its job reaches a person as a draft reply.

Do you need access to our shop or mailbox?

Only to what a package reads or writes. Speed-to-lead needs your CRM or sheet. The order-status part of the post-purchase desk reads your shop and carrier data. I confirm the exact list on the call.

Can we leave, and what happens to our data?

Yes. Within 14 days after the package ends you get your data as an export, consent records included, together with a runbook for each workflow, so someone else can run it. I delete your data from my automation server within 30 days after the end; copies in my encrypted backups are overwritten as the backup cycle runs. Section 14 of the Terms of Service sets this out; the term and the notice for ending the package are in your quote.

Is this legal advice, and does it cover our legal duties?

No. This page is not legal advice, and a workflow does not certify your business against any law. The post-purchase desk includes the withdrawal function, and automatic replies say what they are. Your lawyer approves the final texts.

What do you need from us to start?

A 30-minute call. Then I write the quote. For speed-to-lead you bring your scoring criteria, reply templates, booking link and CRM access. The other packages list what they need on their cards. I start in demo mode, so nothing reaches a customer until you say so.

Tell me which package fits, and I scope it.

The call takes 30 minutes. The written quote follows it.

This clause is the processing contract for a package (Article 28 GDPR). It also sets out how you leave a package: an export of your data with a runbook for each workflow, then deletion from my automation server, with encrypted backups overwritten as the backup cycle runs. The term and notice are in your quote.