Bricksta

Comparison

Every path solves a part. None solves it all.

Not Bricksta either. Here you can see point by point what the usual paths can do when a process runs across several departments, and when you should stay with yours.

One piece of track per requirement from the table below. Where one is missing, the process doesn't get through.

The chaser is the real process.

Email chains, Excel, status meetings and one person who asks, reminds and forwards. That works until they fall ill, leave or the orders double.

What they answer every day

  • Who's doing this?
  • What was agreed?
  • Where is it stuck?
  • When does it move on?

89 %want transparency into their processes

30 %have it

The gap is the chaser's job.

BPM Compass 2024, TH Mittelhessen, HU Berlin and DGQ; mostly larger companies

Five paths, nine requirements. One honest table.

Measured against what a process across several departments needs.
Bricksta loses the last row, and it says so here.

What a process needsCarry on as beforeExcel, email chains, meetings and a chaserTask toolsBoards, to-do lists and project toolsBPM toolsModel and document how processes runYet another specialist systemCRM, ERP or one more specialist systemWorkflow platformsLow-code and BPM platforms, set up by ITBusiness team builds, team works, managers see status
The business team builds and changes the process itselfcan do itcan do itpartlycan't do itpartlycan do it
Up and running in days, no implementation projectcan do itcan do itpartlycan't do itcan't do itcan do it
Working through a task is as easy as a to-do listcan't do itcan do itcan't do itcan't do itpartlycan do it
Handovers between departments are part of itcan't do itpartlycan't do itcan't do itcan do itcan do it
When a step is done, the next one gets its task automaticallycan't do itcan't do itcan't do itpartlycan do itcan do it
Managers see what is stuck without askingcan't do itpartlycan't do itpartlycan do itcan do it
Every step has an owner and a deadlinecan't do itcan do itcan't do itcan do itcan do itcan do it
The process on paper is the one people actually work incan't do itcan't do itcan't do itcan't do itcan do itcan do it
Already there, nothing new to roll outcan do itcan do itpartlycan't do itcan't do itcan't do it
Meets3 of 95 of 90 of 91 of 95 of 98 of 9
VerdictFamiliar and seemingly free. Beyond 5 to 10 parallel cases the person who chases becomes the bottleneck: only whoever asks knows where things stand.Good for handing out work. But tasks instead of a process: no dependencies, every board on its own.Neatly documented. Shows how it should run, not where a case stands right now.Strong at its own part: the CRM knows the sale, the ERP the invoice. That the technicians should start on Monday is in an email. And one more system.Can run the process. But months of project work, and every change needs specialists.Your business team builds the process itself, your team works right in it. The first one runs in days instead of months.
1 of 5
Carry on as before

Excel, email chains, meetings and a chaser

What a process needs
Carry on as before
Bricksta
The business team builds and changes the process itself
can do it
can do it
Up and running in days, no implementation project
can do it
can do it
Working through a task is as easy as a to-do list
can't do it
can do it
Handovers between departments are part of it
can't do it
can do it
When a step is done, the next one gets its task automatically
can't do it
can do it
Managers see what is stuck without asking
can't do it
can do it
Every step has an owner and a deadline
can't do it
can do it
The process on paper is the one people actually work in
can't do it
can do it
Already there, nothing new to roll out
can do it
can't do it
Meets
3 of 9
8 of 9
Verdict: Carry on as beforeFamiliar and seemingly free. Beyond 5 to 10 parallel cases the person who chases becomes the bottleneck: only whoever asks knows where things stand.
Verdict: BrickstaYour business team builds the process itself, your team works right in it. The first one runs in days instead of months.
can do itpartlycan't do it

Bricksta is new. You still have to roll it out; the goal is days instead of months.

What each path does well and where it ends.

Each of these paths is built for something. Check for yourself whether it's your problem.

Carry on as before

Excel, email chains, meetings and a chaser

Meets 3/9

Good at
Already there and everyone can use it. The business team changes the process tomorrow without asking anyone.
Where it ends
Only whoever asks knows where things stand. Beyond 5 to 10 parallel cases the chaser becomes the bottleneck, and if they're out, everything stops.
What Bricksta does differently
Once project management is done, the technicians get their task automatically, with everything sales promised. Nobody has to forward anything.
Stay with it if …
… the process stays in one department, rarely happens and your chaser isn't retiring soon.

Task tools

Boards, to-do lists and project tools

Meets 5/9

Good at
Quick to set up, pleasant to use, every task has an owner and a deadline.
Where it ends
It knows tasks, not a process. When a card is done, the next department knows nothing about it. Every board stands alone.
What Bricksta does differently
Just as easy to work through as a to-do list, but the tasks are connected: done, and the next step starts.
Stay with it if …
… a team does project work with no fixed order, for example planning a trade fair or a campaign.

BPM tools

Model and document how processes run

Meets 0/9

Good at
Neatly described processes, provable for audits and certification.
Where it ends
They show how it should run, not where Mrs Berger's order is right now. Nobody works in the diagram.
What Bricksta does differently
Your process description becomes a process people work in. Paper and daily work are then the same process.
Stay with it if …
… you mainly need to describe processes for auditors. You can keep the description; Bricksta makes it run.

Yet another specialist system

CRM, ERP or one more specialist system

Meets 1/9

Good at
Strong at its own part. The CRM knows the sale, the ERP the invoice, the HR system the contract.
Where it ends
That the technicians should start on Monday after the deal is in neither of them. It's in an email. And where a system dictates processes, they're fixed.
What Bricksta does differently
Bricksta runs the process across your departments, from the order through the technicians to the invoice, and connects to the systems you already have.
Stay with it if …
… your process stays entirely within one department and one system.

Workflow platforms

Low-code and BPM platforms, set up by IT

Meets 5/9

Good at
They really can run the process: handovers, automatic next steps, status for managers. For handovers and next steps the strongest path in the table.
Where it ends
It takes months until it stands, and every change needs specialists. The business team itself can't build on it.
What Bricksta does differently
Your head of quality decides herself that material defects now go to purchasing. No IT project, only with the right to do so, and recorded as a new version.
Stay with it if …
… you have your own IT team and want to automate processes deep into your systems that rarely change.

A route you'd like isn't a track yet.

Bricksta lays the track exactly where your route runs, and you can reroute it yourself at any time. On rails, nobody takes a wrong turn.

  1. The next step starts by itself.

    In the morning project management finds “Plan project”. It already holds what sales promised. Done, and it's the technicians' turn.

  2. You see where things are stuck.

    You see for every case whether it's on track, due soon, blocked or overdue. If a step is left lying, Bricksta reminds the people responsible.

  3. Your business team lays the track itself.

    Describe the process, answer a few questions or upload your process description. The AI builds a draft, you approve it.

The same work, fewer people.

What a chaser carries in their head today leaves with them.

  • 13.3 millionpeople in Germany's workforce retire by 2040, almost one in three.Destatis, Microcensus 2025
  • 1 in 3industrial companies fear their knowledge leaves with retirements and departures.DIHK Skilled Labour Report 2025/26
  • 25%of working time is lost searching for answers.Atlassian, State of Teams 2025; vendor study, international
  • 38%of companies still handle half of their office processes on paper.Bitkom Digital Office Index 2024
Christoph Klett
Christoph KlettFounder of Bricksta

Documented processes don't run. Managed processes do.

Until 2026 I was managing director of a process software vendor. Sales knew what they had promised the customer. Project management, technicians and accounting didn't. Deadlines slipped, customers left. And our own processes? Neatly documented.

Why Bricksta exists

One process, one week. That's the goal.

You don't start with every process, but with the one that causes the most trouble.

  1. MonChoose a process
  2. TueThe AI builds it with you
  3. WedAdapt
  4. ThuTest
  5. FriYour team works in it
A workflow projectMonths
With Bricksta, as a goal5 days

One week is the goal for a clearly scoped first process, not yet measured with customers.

Two questions for your current path.

  1. 1

    Can you say right now where your most important order stands, without asking anyone?

  2. 2

    What happens to that order if your chaser is out for three weeks?

Answered both without hesitating? Then stay with your path. Otherwise it's worth looking at your process.

Bring your most annoying process.

In the call I'll show you on your own example how it would run in Bricksta, and where your current path fits better.

  • Database in Frankfurt (EU)
  • Default AI provider doesn't train on your data
  • Developed in Germany
  • Security in detail