Michael Kaas · Germany
Web appsAI workflowsIntegrations

Software your team willactually use

Web apps, AI workflows, and the integrations between them. Built one project at a time, by one specialist, for small teams that need software they can rely on.

4+
Years shipping
20+
Production systems
99.9%
Avg. uptime
Services

Three things I do well

Web apps and internal tools

Next.js apps, dashboards, admin panels, marketing sites with a real backend. The kind your team uses every day, not the kind that looks good in a screenshot.

  • Next.js front end, typed end to end
  • Backend, database, auth, the lot
  • Designed to be edited later, by future you or someone new
  • Deployed, monitored, documented

AI agents and workflows

Agents that read documents, draft replies, summarise meetings, or triage tickets. Built with an evaluation set, validation, and a human-review fallback so 'mostly works' never reaches your customers.

  • Agent built around your real data, not a generic template
  • Evaluation set so you know its accuracy before launch
  • Validation, retries, human review for low confidence
  • Plugged into Slack, Notion, your CRM, whatever you use

Automations and integrations

Make.com, n8n, and the custom backend glue when no-code can't do the job. For replacing copy-paste between tools, syncing data across stacks, or fixing a workflow that keeps falling over.

  • End-to-end scenarios built from your real workflow
  • Error handling so nothing fails silently
  • Custom apps or backend services when needed
  • A runbook your team can edit without a developer
0+
Years building software
0+
Projects shipped
< 0h
Avg. reply to a new email
0%
Projects with a written runbook
Work

Recent work

The process

How a project actually goes

01

Initial contact

You tell me what your team is trying to do and where the friction is. I ask questions to understand the work. Plain English, no pitch.

02

Plan and quote

I send back a written plan: what gets built, what's deliberately out of scope, the price, and a timeline scoped to your actual project. If it doesn't fit, we stop here. No obligation.

03

Build in slices

I build the work in vertical slices and share progress at regular check-ins. You can change direction at any point without it costing more.

04

Hand-over and free fixes

You get the runbook, a recorded walkthrough, and a follow-up period for free bug fixes after launch. After that, you can run it yourself or send the occasional task.

The difference

Why work with me instead of an agency

One specialist, not a team

You reach me directly. I do the work. I do the hand-over. No PMs, no junior devs, no game of telephone between you and the person actually building it.

Practical, not theoretical

I build things that ship. If something is risky or unlikely to work on your data, you'll hear about it before you've paid for the full build, not after.

AI that ships, not AI that demos

Every AI workflow I build comes with an evaluation set and a fallback path. If accuracy isn't good enough on your real data, you'll know before launch.

Written so your team can run it

Every project ends with a runbook plain enough that a non-developer can change a webhook URL, swap an API key, or read the logs when something looks off.

Michael Kaas
4+
Years Exp.

About me

Michael Kaas

I'm a software engineer based in Germany. For the last four years I've built web apps, AI workflows, and the automations that connect them, mostly for small teams that need software they can rely on without keeping a developer on payroll. I work one project at a time, directly with the person who hired me. The work I'm proudest of is what runs quietly in production for years and never needs me again.

MigrationWiz for Goog…Building AI Agents wi…AI Agent BuilderBuilding Production-R…Ultimate Prompt Engin…View All

Three ways to work together

Single project

Fixed price
  • One scoped build, web app, AI workflow, or integration
  • Initial contact, then a written plan and a fixed quote
  • Regular check-ins with working pieces
  • Runbook plus free fixes for a follow-up period after launch
Most Popular

Monthly retainer

Most teams choose this
  • Ongoing work as your part-time engineer
  • Set hours per month, rollover for one cycle
  • Slack-level responsiveness during your working day
  • Cancel anytime with 14 days notice, no minimum term

Quick audit

Flat fee
  • A focused deep-dive on your existing app or workflow
  • Written report ranking the top issues by impact and effort
  • Specific fixes you can hand to your team, or to me
  • No build commitment afterwards

Honest answers to questions I actually get

What software could your team actually use?

Tell me what your team is doing today and where the friction is. I'll send back a written assessment of whether it's a software problem worth solving and what it would realistically take to build. No commitment, no pitch.

See my work