The everyday problem
An enquiry arrives. What happens next?
Copy a message, create a contact, ask someone in the team: much of the work happens between tools. That is where I start. We take one workflow, connect its steps and make the exceptions manageable too.
The goal is a clearly scoped, verifiable workflow: collect information, organise it and move it to the right place. Consequential decisions have an approval step, and failures remain visible.
What we will work on together.
The scope follows your project.- 01
Understand the workflow
Analysis of a concrete workflow and a scoped first implementation
- 02
Connect the steps
Integrations, data validation and traceable processing steps
- 03
Run it day to day
An interface, error handling and a handover that fit your team
From my work
See what this looks like in practice.
Research and outreach automation
Find the right brand. Reach the right person. Keep the thread.
From relevant brands to the right contact and a deliberate follow-up. A daily view keeps the next steps visible.
- Find brands from real opportunities
- Connect research and contact sequences
- Keep follow-ups visible
- Next.js
- TypeScript
- PostgreSQL
- +3
Shop research and contact pipeline
From a shop directory to contacts a sales team can use.
Public shop directories become usable data: cleaned, enriched, searchable and ready to export.
- Separate discovery and enrichment
- Deduplicate returning shops
- Search and export contacts
- Python
- Next.js
- MongoDB
- +3
Content intelligence and production platform
A custom algorithm. Clear plans. Your content agent.
A custom-built algorithm, an editorial planner and an agent tailored to your content goals. From research to production.
- A custom algorithm for your topics
- A planning tool for the entire workflow
- A content agent that fits your strategy
- Next.js
- TypeScript
- MongoDB
- +1
Our first conversation
Show me where the manual work happens.
You do not need a finished technical specification. Your idea, an example or a look at the current workflow is enough to start.
Let us talk it through- 01
Which task repeats, and how does your team recognise a good result?
- 02
Where is the data, which interfaces exist and what may the system change?
- 03
Which exceptions need a person, and who maintains the workflow after launch?
You might also be wondering:
Felix SchumannAI automation engineerName it, I build it.
If something here looks like the problem you have, write to me. A short description of what is not working is enough to start.