For small and mid-sized businesses

Automate a workflow with AI

What you do by hand every week, such as reports, receipts, bank reconciliation or marketing posts, becomes automatic.

  • Runs on your side, not ours
  • Trial run alongside your current routine
  • Approval stays with you

Who it's for

For small and mid-sized businesses and freelancers with a recurring workflow that costs time every week and follows the same pattern each time.

How we automate

Inside your tools
We connect to the calendars, spreadsheets, mail and templates you already have. Nobody has to learn a new program, and nothing moves into a proprietary format.
Numbers instead of names
The AI only receives what the task needs. Where people are involved, it sees numbers instead of names.

What you get

  • One automated workflow with a fixed scope
  • Marketing workflows too, such as preparing posts and publishing content on a regular schedule
  • Amounts and deadlines from fixed rules, not from the AI

How it works

  1. 1We look at how the workflow runs today and agree scope and price.
  2. 2We build the automation and connect it to your tools.
  3. 3Trial run alongside your current routine until both agree.
  4. 4Handover to you or your team.

What we work with

  • Claude API and Agent SDK
  • OpenAI or Google Gemini where they fit
  • MCP connections to your tools

Work

Where we've done this before.

One workflow at a client, three in our own business.

  • Client project

    Automation

    Invoicing automation

    In use at a psychotherapy practice since June 2026. This client project grew into our product of the same name.

    Billable sessions come from the calendar, and every invoice carries a GiroCode (an EPC QR code) so it can be paid from a banking app. After the weekly approval, invoices go out overnight and the system matches incoming payments against the bank account. The data stays on the practice's own computer.

    What it shows

    Where a mistake costs money, code does the maths. Amounts and invoice numbers never come from the AI, and the practice signs off every week.

  • In-house system

    Automation · Claude Code for teams

    Daily briefing

    The briefing we run our own business on. Every morning, one email with everything that needs attention.

    The system reads several mailboxes, queries platforms through their APIs and captures invoices with text recognition. A language model sorts and summarises it all. Built with Claude Code, rules files, skills and hooks.

    What it shows

    Many sources become one overview, with nobody lifting a finger.

  • In-house system

    Automation

    Daily marketing

    A routine that drafts posts and comments for our brands Panthera Metamorphic, WakeWin, Nalurio and Bookscape Atelier, on LinkedIn, Facebook, Instagram and in communities such as Indie Hackers. Nothing is published without approval.

    To do that, it watches those communities and our own pages and collects the drafts in one place.

    What it shows

    AI in marketing, without giving up control of what goes out under your name.

  • Our app

    Automation · Apps and MVPs

    LeadGrid

    B2B contact lists from a single search. Its marketing runs on its own, with three guide articles a week that ChatGPT already cites as a source.

    LeadGrid pulls companies and their phone numbers from Google Maps, then adds email addresses and contact names from their own websites. Lists come as CSV, Excel or straight into HubSpot, with the first five rows free as a preview. The guides are written and published on a fixed schedule via GitHub Actions.

    What it shows

    Marketing as a scheduled process rather than a constant chore, and visible in ChatGPT's answers.

Working together

How we work.

  1. Fixed price or day rate, agreed upfront

    Before any work starts, we agree together what will be delivered.

  2. Remote, or on site in and around Munich

    Most of the work happens remotely, in English or German, on Munich time. For the kick-off or the handover we can also come to you in and around Munich.

  3. Your code, your accounts

    We work in your repository and your accounts. We don't keep access to your production systems once the project ends.

  4. After handover, it runs without us

    You get a written description of how everything fits together. With the code, the accounts and that description, someone else can carry on if we're ever unavailable.

Contact

Tell us what you're planning.

A few sentences are enough.

What happens next

  1. 1Tim Leonsteyn reads your message himself and replies within two working days.
  2. 2If useful, we follow up with a short call about goals and scope, not a sales pitch.

We use your details only to answer your enquiry. Details in our privacy policy.