Hi, I'm Sarah.

Automation engineer

I connect the tools small businesses already use and put the automation on top.

CRMs, accounting, mailboxes, industry portals — most back-office work is copying data between them. I build the layer in between: connectors, bots and one clear view. Three of those tools are public, with demos you can click through without an account.

📍 Leipzig, Germany · remoteAvailable for freelance projects

Hire me See the work

Sarah Vogel at her desk

About

I have worked full-time as a software and automation engineer for two years — the kind of work where every project touches a CRM, an accounting tool, a shared inbox and some industry portal, and nothing talks to anything. That experience is what my freelance work is built on: I built birdie for solar back offices, a bot platform for a client, a commission engine for a sales team. The thread is always the same — connect what exists, automate the repetitive part, keep a person in the loop.

Based in Leipzig, working remotely in English and German, and taking on freelance integration and automation projects alongside my day job. If you have tools that don't talk to each other, that's usually where I start.

Projects

birdie

The transparency layer for solar installers

A solar installer runs the business across a CRM, accounting, mailboxes, a calendar and dozens of grid-operator portals with their own logins and PDF forms. None of them talk to each other, and grid connections stall because a utility’s follow-up question sits unread in a shared inbox.

  • Connector SDK with 11 adapters (CRM, accounting, Google Workspace, WhatsApp, tariffs, battery IoT) and a polling scheduler with retries and error isolation
  • Utility registration on autopilot: forms prefilled from project data, utility e-mails matched to projects, portal drafts prepared by a Playwright bot and released by a human
  • CRM demo in English and German that runs entirely on mock data — no accounts, no keys

Next.js · TypeScript · Supabase · Playwright · n8n · Anthropic API · vitest · GitHub Actions

Dashboard, pipeline, interconnection tracking, crew schedule, German switch, workflows — recorded from the hosted demo.

botworks

A modular AI bot platform for small businesses

Every “AI assistant” built for one customer ends up as a one-off script nobody can operate, monitor or reuse. botworks treats each task as a bot with a contract and runs all of them on one shared runtime, per tenant.

  • 13 bots (inbox triage, document extraction, dunning, tax prep, reviews…) on one runtime: validation, queue with priorities and retries, connector injection, structured logging
  • Multi-tenant admin panel: bot fleet, connector health, sync logs, billing, compliance — with a database stand-in so it runs without infrastructure
  • Every AI call ships a deterministic offline answer that still passes the bot’s real response schema; the queue falls back to memory when no Redis is configured

TypeScript · Hono · BullMQ / Redis · zod · Next.js · Supabase · Anthropic SDK · vitest · GitHub Actions

Platform dashboard, bot fleet, connectors, route bot, German switch, analytics — recorded from the hosted demo.

commission-engine

Sales commissions with tiers, team pools and monthly statements

Commission rules are never “x % of the price”: they run on margin, discounts cost the seller more than their face value, rates depend on tiers, team leads take the rest of a pool, partner teams settle themselves, salaried staff get a different formula — and it all lives in a spreadsheet one person understands. I rebuilt the logic of a production tool as one tested engine.

  • Pure TypeScript engine: commission base, tier and override rates, pool split, partner-team settlement, salaried rates, own-lead bonuses, clawbacks — every constant is configuration, every edge case a test
  • Payout lifecycle: open → payable when the customer paid → paid, monthly statements per recipient, negative clawback entries instead of deleted history
  • Role-based demo app with a live calculation preview and a line-by-line breakdown, so a rep can verify their number

TypeScript · Next.js · Tailwind CSS · vitest · GitHub Actions

Overview, deals, new deal with live preview, approvals, payout run, statements, German switch — recorded from the hosted demo.

How I work

Runs before it’s wired up

All three start with two commands and no credentials. Mock transports and offline answers go through the real parsing code, so what you see in the demo is what ships.

Tested, in CI, documented

Vitest suites, GitHub Actions on every push, READMEs that explain the problem and the architecture, not just the commands. Writing the tests found a real API bug — that’s the point of them.

Automation with a person in the loop

Bots prepare drafts, classify and prefill; a human releases. I’d rather build something an office actually trusts than a demo that submits forms on its own.

Contact

Available for freelance integration and automation projects — remote, in English or German. If you have tools that don’t talk to each other, that’s usually where I start.