Consulting · Software · Automation — for mid-sized companies

Less friction.Measured.

Somewhere in your operation, time and money leak away — usually not where the trouble shows up. I find the spot and change what fixes it: your process, your software, your automation. Afterwards you see from your own metric whether it worked.

30 minutesfreeno sales pitch

Prefer writing? contact@balane.tech

010203
Phase 01 / 03Find

How you notice

Trouble rarely sits where it shows up.

On the left: situations almost every company knows. On the right: what usually sits behind them. Tick what sounds familiar — below you see where it points for you.

00 / 05

  • Business0
  • Psychology0
  • IT0

Reading

Nothing ticked yet. That is a finding too — or you have not looked yet.

Where the cause sits for you, three questions narrow down: Start phase 01 →

How a project runs

Find. Change. Measure.

Your project is not done when the software goes live. It is done when the number that made you start has moved. That is why the work runs in a loop rather than a line — and whatever the measurement shows becomes the starting point of your next round.

  1. Diagnosis · advise

    Find where it actually breaks.

    Trouble rarely shows up where its cause sits. I look at your processes, talk to the people who run them every day, and work out what the bottleneck costs you per month. Without that number, every solution stays an opinion.

    What you have in hand afterwards

    A map of your processes with bottlenecks ranked by cost — and the one metric you will later read success from.

    Tools for it

    Fig. 01One process, a pile-up before approvalSchematic
  2. Delivery · build, automate

    Change what fixes the bottleneck. Nothing more.

    Sometimes that is new software, sometimes an automation, often a different process first. I adjust the process, build what is missing and automate what repeats — in the order that pays off for you fastest. Your people are involved from day one, so nobody ends up working around the new path.

    What you have in hand afterwards

    A changed process that holds up in daily work — with software you own and that someone can explain to you.

    Tools for it

    Fig. 02Same process: standard case rerouted, approval automatedSchematic
  3. Effect · measure

    Measure whether it worked.

    Before the start you decide how you will recognise success: lead time, error rate, hours per week. After go-live it gets measured again at fixed intervals. If your number moved, the project is done. If it did not, you see why — and it gets adjusted, not explained away.

    What you have in hand afterwards

    In black and white, what the change brought you — and where the next round starts.

    Tools for it

    Fig. 03Before, target, measured courseSchematic

Feedback

Whatever the measurement shows is the finding for the next round. That is how a project turns into an operation that keeps tuning itself — even without me.

↑ Back to 01

Phase 01 — start right here

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?

Reading

  • Business0/3
  • Psychology0/3
  • IT0/3

Every answer moves the reading. Read it off instead of guessing.

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

Clicking starts the video on YouTube. No cookies or trackers load before that.
Jonas Höttler

Jonas Höttler

Founder. M.Sc. Digital Psychology, B.Sc. Business Psychology.

In every phase

Three activities, three lenses.

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. So every question gets asked three times — commercially, psychologically, technically. Pick a cell.

  • Business

    What does the bottleneck cost?

    Hours, errors and waiting time get converted into euros per month — before anyone talks about solutions.

  • Psychology

    Why does everyone route around it?

    Conversations with the people who run the process every day. Their unofficial path shows where the official one asks too much.

  • IT

    Where does the system break?

    The data between your tools gets traced until the spot where someone retypes by hand becomes visible.

advise × 3 lenses