I take the manual work out of your business.
I come to you, record how your work actually gets done, and tell you in black and white what is worth automating with AI — and what isn't. Whatever you prioritise, I then build.
Rather call?+49 157 50145132 · 10:00–20:00 (CET)
I come to you: Frankfurt am Main and the surrounding area, anything further by arrangement.
After the analysis you know:
Where the time goes
Measured while I watch — not estimated.
What can be automated — and what can't
With the reason, for every single process.
What it costs and when it pays off
With the build price and the month it starts saving money.
All of it in black and white, in the potential report.
- €0
- First call, 30 minutes
- €2,500
- Analysis at a fixed price
- 4–6 weeks
- until the first automation runs
Every week, hours disappear into work nobody ever booked.
Manual work does not only cost time. It costs accuracy, oversight, and people who are frankly too expensive for it.
Time nobody counts
Quotes written after hours, invoices retyped, the same number entered into three systems. Five minutes each, half a day a week together.
Mistakes the customer finds first
A transposed digit in an order, last year's price list. Manual work goes wrong — and is the last to notice.
Knowledge tied to one person
If only one person knows how a process runs, it stops the day they are ill or hand in their notice.
None of this is an IT problem. These are processes — and processes can be recorded, costed and rebuilt.
Measure first. Build second. Not the other way round.
Most AI projects fail on the business case, not the technology: nobody counted beforehand what the process actually costs today.
The findings before the quote
1 day in your business, then a report with numbers. What gets built is your call, made on that basis — not on a presentation.
Whoever advises also builds
From the first minute you talk to me — and I do the work myself afterwards. No salesperson making promises, no delivery team reinterpreting them later.
The no goes in the report too
Wherever the effort does not justify the saving, it says so. Otherwise I would be selling you work instead of value.
Four things. One goal: less manual work.
What actually gets built is decided by the report. Usually it is one of these four.
Automating processes
Reading documents, preparing quotes, moving data between systems. The process runs without anyone starting it.
Saves the hours nobody currently books
An AI assistant on your own documents
Queries your price lists, contracts and minutes, and names the source for every answer. No guessing, no inventing.
An answer in seconds instead of half an hour of searching
Reports that write themselves
Figures pulled from your systems automatically and kept current. No exports, no spreadsheets by hand.
Deciding instead of collecting
Catching customer enquiries
A chatbot on the website, enquiries pre-sorted, appointments booked directly. Exactly what Helpsy does — fitted to your business.
No enquiry sits unanswered for two days
Point four is what Helpsy does as a finished product. Here it is fitted to your business and wired into your processes — if the off-the-shelf version is enough for you, I will say so in the first call.
“AI” is not one product. It is five different things.
When people say AI they usually mean one of these five — and surprisingly often the honest answer is the last one. Which one pays off for which process is what the report tells you.
Assistant
Answers questions from your own documents and names the source for every answer.
Agent
Decides within set limits what happens next. Anything that reaches the outside world goes for approval first.
AI inside an existing process
Not a project of its own, but the one step where things used to stall: reading, sorting, summarising.
AI on the phone and in chat
Picks up when nobody can, notes the request and the callback number, and files the case in the right system.
No AI at all
Often the same process is faster, cheaper and more reliable with a blunt rule. I say so beforehand, not afterwards.
Five steps to less manual work
After the third step you know where you stand — and you can walk away at any point.
- 0130 min, free
First call
What do you do, where does it hurt most? Then I tell you honestly whether an analysis is worth it for you at all.
- 021 day
On site
I walk along, watch and write it down: who does what, with what, how often and for how long. I need no access to your systems for that.
- 03a week later
Potential report
Every recorded process with today's effort, the expected result, feasibility and a clear recommendation — including where it reads “not worth it”.
- 042 hours
Prioritising together
I go through the report with you, and you decide what gets built first, what comes later, and what never does.
- 05as agreed
Build and run
I build the prioritised process, introduce it in your business and hand it over — and look after it afterwards.
When does the first result run?
From the first phone call to the first automation running takes around 4–6 weeks.
- Day 0
First call, 30 minutes, free
- Week 1
On site, 1 day
- Week 2
Report and joint prioritisation
- Week 4–6
The first process is live in your business
Bigger rebuilds take longer. What gets built first is chosen deliberately so that it pays off quickly.
What the potential report contains
Not a slide deck, but a calculation you can decide from. Every row says what it costs, what it saves and when it has paid for itself. What you see below is an example: it shows what such a report looks like — your processes and your figures only come out of the day on site.
Example
Writing quotes
first- Today
- 6 hrs/wk
- After
- 1 hr/wk
- Saves per year
- €10,100
- Build once
- €6,000
- Pays for itself in
- 7 months
Recording incoming invoices
first- Today
- 4 hrs/wk
- After
- 0.5 hrs/wk
- Saves per year
- €7,100
- Build once
- €5,000
- Pays for itself in
- 8 months
Searching price lists and contracts
later- Today
- 5 hrs/wk
- After
- 1 hr/wk
- Saves per year
- €8,100
- Build once
- €9,500
- Pays for itself in
- 14 months
Customer onboarding
later- Today
- 2 hrs/wk
- After
- 0.5 hrs/wk
- Saves per year
- €3,000
- Build once
- €5,000
- Pays for itself in
- 20 months
Holiday requests
not worth it- Today
- 1 hr/wk
- After
- 0.25 hrs/wk
- Saves per year
- €1,500
- Build once
- €3,500
- Pays for itself in
- 28 months
Calculated at €45 per working hour and 45 working weeks a year. In the real report I set both together with you.
An example that shows the structure. What ends up in yours — and whether anything does — comes out of the analysis.
The last row matters as much as the first. €1,500 saved a year against €3,500 to build only pays off after more than two years — and by then the process will have changed anyway. That is exactly what the report says, and the report is yours even if you never hear from me again.
What it costs
The first call costs nothing. After that, fixed prices rather than timesheets — you know up front where you stand.
First call
30 minutes on the phone. You describe where things stick, I tell you honestly whether the next step is worth it.
Analysis
1 day in your business, a full record of your processes, a written potential report, joint prioritisation.
Build
The prioritised process gets built, introduced and handed over. Your fixed price is in the report before you commit — the range shows where most single processes land.
Care
Monitoring, repairs, small adjustments, a named contact you can reach. Graded by everything built for you so far. Fixed for the first 12 months after handover, then cancellable monthly. Running costs for AI and hosting are billed separately by usage – or you host it yourself and pay your provider directly.
All prices are final prices. Under § 19 of the German VAT Act (UStG), the small business scheme, no VAT applies.
I only build what I run myself.

I'm Karim Benziane, a full-stack developer from Frankfurt. For over six years I have been building software that runs in real businesses — and running it myself.
- Trained as a certified application developer, over six years building and running web applications.
- Most recently senior developer for Microsoft Azure and AI integrations in client projects.
- Helped build GA-Lotse, the case software for the Frankfurt public health authority — recording how the office actually worked and turning it into requirements. Exactly the work this engagement starts with.
- Built and runs helpsy.ai single-handed: language model in the EU, GDPR-compliant, deletion after 90 days, billing, WordPress plugin.
- Consulting in German, English and Italian.
I work alone, and I say so: you get no assigned project manager, you work directly with the developer. If you want twenty sites converted at once, a large agency will serve you better.
Take a look at Helpsy.ai(opens in a new window)Your questions, my answers
- Which businesses is this worth it for?
- Any sector, as long as there is recurring manual work — trades, law and tax firms, agencies, retail. Rule of thumb: if the same data regularly travels from A to B by hand, the conversation is worth having.
- What if there is nothing to find?
- Then that is exactly what the report says. You are paying for an honest answer rather than a foregone conclusion — and you have saved yourself an investment that would have returned nothing.
- Others analyse for free — why don't you?
- The conversation beforehand, where it becomes clear whether this is a fit, is free here too. What you pay for is the on-site work itself: 1 day in your business and a report you keep. An analysis that costs nothing is really a sales appointment — and it rarely ends in “not worth it”.
- Do we need technical knowledge?
- No. You explain your processes, I handle the rest — recording, assessment, build, handover. Whoever knows the process needs to know nothing about AI.
- What happens to our data?
- For the on-site work I need no access to your systems; I watch and take notes. Where the build requires data, I sign a data processing agreement with you first, and processing happens in the EU.
- How long does the whole thing take?
- First call 30 minutes, on site 1 day, report a week later, prioritisation two hours. The first piece runs around 4–6 weeks after the first call.
- How is this different from the Helpsy subscription?
- The subscription is the finished product: a chatbot for your website that you set up yourself, from €0. The consulting starts one step earlier, with your processes. What gets built afterwards may be a chatbot — often it is something else entirely. If the finished product is all you need, I will tell you so in the first call.
Ready to lose the manual work?
In a free first call I look at the potential in your processes with you — and whether the next step is worth it for you.
Rather call?+49 157 50145132 · 10:00–20:00 (CET)
