Three acquisition apps for an employer.

A news item in the paper becomes an assigned lead with a finished email draft.

This is a rebuild. It shows what the apps do, not what they look like at the employer. The interfaces were redesigned for this site, and all data is made up.

Role: Idea, data model, build, operations
Year: 2026
Technology: Cloudflare Worker Cloudflare KV JavaScript without a framework

Try the three apps.

The module below is a rebuild of the three apps with made-up data. The workflows are the same as in real use. The interfaces were redesigned for this site.

Instead of a server, a stand-in inside the browser answers every request from local storage. The three apps share one data set. It is one system, not three tools.

The buttons above switch between Lead Intelligence, Mail-Werkstatt and Funnel-Dashboard. The apps themselves are in German.

This is a demo. Companies, people, news items, references and figures are made up, and the email addresses use example.com. No request leaves the browser, and there is no connection to a live system.

Things to try: Assign a lead to someone, set a status, then check what is ready in the Mail-Werkstatt for the same lead.

Acquisition apps, rebuild with sample data

Open in new tab

The work list. Each lead carries its trigger, its contact person and the reason why now. Assign, set a status, schedule a follow-up.

Rebuild, made-up data. All companies, people, news items, references and figures are made up, and the email addresses use example.com. The interfaces were redesigned for this site. The server has been replaced by a stand-in inside the browser, so not a single request goes out. Changes stay in your browser. The zurücksetzen button at the bottom left of the app restores the starting state.

The problem

New business fails in the gap between noticing and acting. Someone reads that a company has a new managing director and thinks: we should call them. Two weeks later, someone else thinks the same, and nobody has called.

In between lies a lot of small work. Who is responsible? What is the person’s name? What do you write to them? Each question can be answered in five minutes, and that is exactly why it never gets answered.

What I built

I built three interfaces on one shared data set. It is one system, not three tools.

Lead Intelligence is the work list. Each lead carries its trigger, the source and one sentence on why now. Then there is the contact person. The team assigns the leads, sets the status and fixes the date for the follow-up.

The Mail-Werkstatt (mail workshop) keeps a finished draft ready for each lead, including an attachment. Whoever sends it sets a marker, and from then on the draft is read-only.

The Funnel-Dashboard tracks the initiatives along the funnel, each with status, decision and evidence. Next to them are the figures from web analytics and search ads.

Scripts run before all this:

One collects the news items.
One finds the contact person.
One writes the drafts.

Three decisions that make the difference

The daily cap is ten. A list that grows faster than anyone can work through it does not get worked through. It gets ignored.

Assignments sit next to the lead, not in it. Everything that people set lives alongside the lead and survives every new import. Otherwise every import would have to preserve last week’s work, and one day it would not.

A sent email is a record, not a draft. A later run must not rewrite it. Otherwise the system would show something different from what the recipient received.

What it cost me

Silent failures were the most annoying. When the login expires, the server says no to every attempt to save, but the loaded page keeps showing data. The button silently jumps back. Since then, every way of saving has a visible error path.

Then there were two people saving at the same time. Whoever saves last overwrites the other, without anyone noticing. So the dashboard sends the timestamp of the version it read and gets a rejection if the data has changed since. A visible conflict is better than a silent loss.

About the rebuild above: It shows the workflows, not the interfaces used at the employer. The interfaces were redesigned for this site. The server has been replaced by a stand-in inside the browser. All companies, people, news items and figures in it are made up.