The inbox comes first
Before thinking, before the work that counts. The same manual sorting every morning.
Lucid OS for owner-led companies
A system that follows through.
It sorts your inbox, turns the important mails into daily to-dos and resurfaces them until they are done.
- May 2026
- live in production since
- 1,300+
- mails processed at the first client
- 30+
- automations running my own business
The problem
You run the business.
But the business runs on you.
Three patterns that look the same almost everywhere.
The same proposal, five times
Same structure, same two hours. None of it gets faster next time.
The inquiry drowns
Between newsletters and CC threads sits the one that means revenue. Sometimes for a week.
On every project, I end up being the last one who has to do everything.
The system at work
A mail slips through.
The system pulls it back.
Your tools wait for someone to ask them. The system does not wait.
- 01
It spots
The inquiry gets pulled out of newsletters, CC threads and invoices before you open your inbox.
- 02
It drafts
The mail becomes a to-do with the next step, written in your voice, with the open question inside.
- 03
It follows through
The to-do is back tomorrow, and the day after, until it is done. Nothing disappears quietly.
Your tools stay where they are. The system holds them together.
- Gmail
- Slack
- Mattermost
- Notion
- Calendar
- your CRM
A day with the system
It works while you work.
- 07:00
Before you wake up
The briefing is ready: pipeline, open commitments, what needs an answer today.
- 09:20
The inquiry arrives
It gets spotted, becomes a to-do, and comes back tomorrow if it stays open.
- 14:00
The proposal is due
The draft is waiting, written in your voice. You read it and approve it.
- 18:30
You call it a day
The system stays on it. Follow-ups keep running, none of them need you.
Running in production
At a client.
And in mine, every day.
A web agency in Berlin
1,300+
mails processed, since May 2026
- Starting point
- A quote request sat unseen in the inbox for a week.
- What runs
- The system pulls requests like that out and turns them into a to-do.
- Today
- It resurfaces them daily until they are done.
My own business
30+
automations, around the clock
- Starting point
- The first building blocks came out of the event operation at DXB LIVE in Dubai.
- What runs
- Briefings, follow-ups and bookkeeping run on Lucid OS.
- Today
- You get the system I work with myself.
The path
Three steps, each with a net.
Step 01
First call
15 minutes. We look at where your time disappears, and whether a system changes that.
Costs you nothing beyond the time.
Step 02
Audit
I go through your workflows and show where a system gives you real hours back.
500 euros, credited toward the setup. Fewer than five levers found, it is free.
Step 03
Setup and operation
Built into the tools your team already uses. After that I stay on it so it keeps running.
Live in 30 days, or the setup fee comes back.
Who builds this
Lucas von Puttkamer
I am Lucas, 22, based in Berlin. I automate internal operations inside companies so the day to day neither hangs on the owner nor slows the growth down. The first systems came out of the event operation at DXB LIVE in Dubai, and they grew into Lucid OS.
You get no hype slides here. You get a system that connects the tools you already use, knows what you know, and keeps learning on its own. And someone who stays on it, because his own business sits on the same stack.
- Data processing agreement under Art. 28 GDPR before the project starts
- Read-only access for the first two weeks, then dedicated accounts instead of admin passwords
- You approve every outgoing message
- Everything built belongs to you: code, documentation, access
Honest questions
You are probably wondering.
Our last AI demo died in daily business. Why would this go differently?
Because the project does not end at go-live here: running it is the product. If nothing runs after 30 days, the setup fee comes back.
We already use AI tools.
Good, then your team knows the basics. On the first call I show you what your tools still leave on the table.
What about data protection?
Before the project starts you get a data processing agreement under Art. 28 GDPR. Everything is built inside your systems, your data moves into no new tool. Read-only access for the first two weeks, then dedicated accounts instead of admin passwords. You approve every outgoing message.
I have no capacity for this right now.
Your part: one call and one mapping session. I build the rest, starting with whatever eats most of your time today.
What does it cost?
The audit costs 500 euros and is credited toward the setup. Setup and operation depend on what gets built, and we settle that on the call. As a frame: measure it against the hire you would otherwise need.
And if I want out again?
Cancel anytime. Everything built belongs to you: code, documentation, access. Your system keeps running without me.
The next step
15 minutes. Then you know
how this looks for you.
A system that sorts your inbox, tracks the to-dos and runs inside your tools. Built in 30 days, or the setup fee comes back.
Lucas von Puttkamer
Founder, LLucid