For companies and departments from about 20 people · DACH
First find where it actually breaks.
Then the software that fixes it.
The cause rarely sits where the trouble shows up. So I look at your operation before I build anything — commercially, psychologically and technically. What comes out of it fits your process, instead of you bending your process around standard software.
30 minutesfreeno sales pitch
Prefer writing? contact@balane.tech
How you notice
Does any of this sound familiar?
Tick whatever you recognise.
00 / 05 ticked
That is normal, and it is not a leadership failure. It is what every company looks like once it grows faster than its own routines. The problem is not that something is going wrong — it is that nobody has put a number on it yet.
Where is your bottleneck?
Three questions, no email address. At the end you get a hypothesis you can use — even if you never talk to me.
Bottleneck audit, short form
01 / 03
What tells you first that something is stuck?
The method
From a hunch to something that runs.
Six steps, six tools. Five of them you can open right now — no signup, no email address. So you see how I work beforehand instead of finding out afterwards.
01
Hunch
You can tell something is stuck — but not where. Three questions narrow down which lens your problem most likely sits under.
02
Do the maths
What does the bottleneck cost per month, and what does it cost to leave it alone? Without that number every solution stays an opinion.
03
Prove it
A hunch convinces nobody in the building. A simulated process that produces the same pile-up across hundreds of days does.
04
Write it down
One conversation, seven days, then a system map with prioritised bottlenecks and an implementation plan you could work through without me.
05
Build
If software is the right lever, I build it. What that looks like when an entire operation depends on it, you can go and look at.
06
Automate
Whatever should run by itself afterwards, runs by itself. Before/after and ROI to read up on before you commit.
Who you talk to
You talk to the person who also builds it.
No account manager, no hand-off to a team you never met. Where consulting projects need more heads, I bring them in — people running their own businesses, whom I have worked with for years. Your point of contact stays me, from the first call until after go-live.
So you keep a name and a number, not a shared inbox.
30 minutesfreeno sales pitch
Prefer writing? contact@balane.tech
Jonas Höttler
Founder. M.Sc. Digital Psychology, B.Sc. Business Psychology.
The model behind it
Three activities, three lenses.
I look at every problem from three directions. Not because that sounds more thorough, but because a problem you only examine from one side reappears on the other. You know the pattern: new software goes in, and six months later half the team works around it again.
advise × Business
- Business
What does the bottleneck cost?
- Psychology
Why does everyone route around it?
- IT
Where does the system break?
advise × 3 lenses
Notes
All notesWhat a Change Really Costs: Process, Data and Systems Belong Together
Automating a way of working always changes three things at once: the process itself, the data underneath it, and the systems that carry both. When those sit in three separate documents, every cost estimate is a guess. A simpler way to do it, and what AI is allowed to do here.
Automation · IT Landscape · Cost Estimation · Data Quality
Automating Processes: What Pays Off and What Doesn't
Almost anything can be automated technically. So the arithmetic decides, not the feasibility: five variables, one case worked through in full.
Process Automation · Automation · ROI · Business Case
We Reviewed 134 European Alternatives, and Our Own Site Fails the Test
Digital dependency can be measured instead of lamented. What reviewing 134 European products teaches you, why the location of the server is the wrong question, and why the tool we built gives a poor score to the very site it runs on.
Digital Sovereignty · Europe · Open Source · Cloud