Make your business processes clear.
Describe what happens in your business, who is responsible, and which rules apply. With FlowMade you understand how your business really works, improve it, and automate the steps that allow it — without modelling the process a second time.
Picture this example
A customer requests a quote. An employee prepares it. Quotes above a fixed amount go to a manager for approval. Almost every business runs this kind of flow.
- Event
A customer requests a quote
Something happens: the customer sends a request.
- Action
An employee prepares the quote
Someone deliberately does something, within the company's rules.
- Action
A manager approves only the larger quotes
A rule bounds the action: only above a fixed amount.
In FlowMade you sketch exactly this: every moment something happens, every action, the responsible role, and the rules that apply. That gives you a picture your whole team shares — and the base on which improvements, automation, and software later build.
From describing, to improving, to automating
Three things — and always the same model.
Describe
Spell out what happens, who does it, and which rules apply. One clear model your whole business can share.
Improve
See where things slow down, where work is done twice, or where responsibility is fuzzy. Discuss it with your team — from the same model.
Automate
The steps that lend themselves to automation become automation and software that grows out of the same model. You don't model your process a second time.
Why process first?
A loose flowchart shows steps, but says little about what actually happens: which events occur, which actions who performs, and which rules bound them? FlowMade captures events, actions, responsibilities, and rules explicitly. That shared understanding is the base that improvements — and later automation — build on. And unlike starting with screen sketches of software, you start with the work you already do.
Learn the essentials
FlowMade works with four core concepts. The terms stay in English — the explanations are in your language.
Event
Something that has happened, and that the process reacts to. For example: "Quote approved".
Action
Something someone does on purpose. For example: "Prepare the quote".
Role
The person or function that performs an action. For example: "Employee" or "Manager".
Automation
A rule that automatically reacts to an event. For example: "Apply the loyalty discount when the customer ordered before".
And if you want to go deeper?
Entity
The things and data your process revolves around — a quote, an order.
Boundary
The edge of a coherent part of your business — not just a visual grouping, but where one whole ends and the next begins.
Business Area
A larger area of your business, made of several coherent parts.
These simple terms correspond to the professional terms of EventStorming and DDD. If you already know those, FlowMade will feel familiar fast:
| Simplified | EventStorming / DDD |
|---|---|
| Business Area | Bounded Context |
| Boundary | Aggregate |
| Entity | Entity |
| Action | Command |
| Event | Domain Event |
| Automation | Policy |
| View | Read Model |
| Role | Actor |
| Question | Hotspot |
| Integration | External System |
Not every rule in the model is automated — some deliberately stay human decisions.
Start with a process you actually have
Think of a flow that runs daily in your business: a quote, an order, an application. Describe it the way it really goes — FlowMade takes it from there.
Describe your first process