Taking new projects

The repetitive part of your week can run itself.

Alzoth builds automation for small businesses, practices, and law firms — missed-call text-backs, intake, follow-ups, invoicing, deadline tracking — on infrastructure you own. Describe what eats your week. You'll have a free written assessment within two business days.

Free assessment, no obligation Fixed prices, published below Built by a lawyer who writes the code

Describe it. Get a free assessment.

Three lines are enough. Within two business days you'll have a written assessment: what can be automated, how, and what it would cost.

No obligation, no mailing list, no sales sequence. Just a written answer from me.

Selected work

Built for my own practice first.

Before Alzoth existed, I built these for my law practice in Germany. Each one takes a visitor from first question to a complete file without a single email being forwarded by hand. The same engine — n8n workflows, hosted where you choose — is what I build for clients.

Why this matters for you. None of these needed a developer on call afterwards. Each runs on a workflow engine you can open, read, and hand to someone else. That is the standard for everything I build — a text-back for a repair shop, an intake flow for a dental practice, a deadline tracker for a law firm.
The problem

The tools work. The fit doesn't.

Every business has now tried something. A chatbot on the website, an AI assistant, an app that promised to answer the phone. Most of it sits unused a quarter later — not because the technology failed, but because nobody connected it to how the work actually moves through the shop, the practice, or the office.

Ninety-five percent of organizations are getting zero return on their investment — not from model quality, but because the tools don't integrate into existing workflows.

MIT — State of AI in Business, 2025

That gap is the entire job. Not choosing a tool. Understanding how a job moves from first contact to paid invoice well enough to know which parts are mechanical, which parts need a human, and which parts must never be automated at all — then building only the first kind.

What I build

One kind of engineering, two kinds of client.

The work is the same underneath. What changes is how much of it is governed by rules you can be disciplined for breaking.

Small businesses & practices

The phone, the inbox, and the paperwork — handled

Missed-call text-back so nobody goes to a competitor while you're under a car or with a patient. Intake forms that land in your software instead of your inbox. Appointment reminders, review responses, invoice follow-ups, and the sorting of everything that arrives as a PDF. Built into the tools you already pay for.

  • Runs on your accounts and your numbers — nothing routes through a third party you don't control
  • Text-message consent handled properly, because a fine costs more than the system
  • Set up once, explained in plain language, documented so it survives staff turnover
Law firms & in-house

Systems that respect the rules you work under

Client intake and conflict screening. Document assembly from your own templates, not generic ones. Deadline and limitation tracking. Discovery and disclosure review. Matter status clients can see without calling. Built inside the practice management system you already pay for.

  • Designed around confidentiality obligations, not retrofitted to them
  • Every automated step leaves a record a partner can audit
  • Written AI use policy and staff training included, not sold separately
Also

Fixing what someone else built

If you have automations that broke, drifted, or were left undocumented when the person who built them moved on — that is its own engagement. Often the fastest return available, because the value was already proven before it stopped working.

How it works

Short engagements, fixed scope, no retainer required.

01

You describe it, I assess it — free

Use the form at the top of this page. Within two business days you get a written assessment: what can be automated now, what shouldn't be, a rough shape for the build, and a price. Yours to keep whether or not we go further.

02

A call, then a written scope

Thirty minutes to establish whether this is worth either of our time. If it is, you get a written scope and a fixed price before anything is signed. If it isn't, I'll say so.

03

Build, in your environment

Systems run in infrastructure you control, on hosting in the jurisdiction you choose. You get documentation, training for the people who will use it, and the ability to hand the whole thing to another engineer.

04

Operate it, or don't

Ongoing care is available monthly and cancellable monthly. It is not a condition of the build. Nothing I deliver depends on my continued involvement to keep running.

Pricing

Published, fixed, and quoted before you commit.

Most firms in this field won't tell you what anything costs until you sit through a sales call. These are real numbers. Smaller automations — a text-back, a reminder flow, a review responder — are scoped in the free assessment and typically start around $500 to set up.

Workflow Review

$3,500 fixed
2 weeks

I map how work moves through your business end to end and deliver a written report: what can be automated now, what should not be, what it would cost, and what it would return. Yours to keep and act on however you like.

Credited in full against a build within 90 days

Ongoing Care

$1,800 / month
Optional

Monitoring, maintenance, model and integration updates, and a standing block of hours for changes. For businesses that would rather not think about it again.

Month to month · cancel any time

If the review isn't useful, you don't pay for it

Read the Workflow Review report and tell me within fourteen days that it gave you nothing you can act on. You get a full refund and keep the report. I would rather carry that risk than ask you to take it on a firm you've never worked with.

Who you'd be working with

Someone who has read the rules and can write the code.

Alzoth is Sven Juergens. I trained as a lawyer in Germany, hold a doctorate in law, and I build software. That combination is the whole reason this firm exists: most people selling automation have never had to think about what happens when an automated step produces the wrong result on a deadline — and most people who understand those problems can't build the system that solves them.

Alzoth is new, and it is one person. That means no account manager between you and the person doing the work, a direct answer when something is outside what I can do well, and limited capacity — I take on a small number of projects at a time. I would rather tell you that than pad this page with logos.

On qualifications. I hold a doctorate in law from a German university and am not admitted to practice law in any United States jurisdiction. Alzoth LLC provides technology services only. Nothing here is legal advice, and no engagement with Alzoth creates an attorney–client relationship. Where a matter calls for legal judgment, that belongs to your own counsel — my job is to build the systems around it.
Contact

Prefer to just write?

The form at the top gets you a written assessment. This one is for everything else — a question, a referral, a project that doesn't fit a box.

Or write directly contact@alzoth.ai

Start a conversation

Everything here goes straight to my inbox.

Your details are used only to answer you. Never shared, never added to a list.