The first part, running
The first part of your process as working software on the laptop at the end of day two, with real cases from the room entered.
Workshops
You know your process; your software does not. In two days with the people who run it, the first part of your process becomes software that runs: on day two on the laptop, within a week in the cloud.
The workshop is the first paid step on the path: after the free call comes the workshop, then the next parts, going live in your own cloud account, and care. Everything after it follows from what the room decided.
The workshop exists to answer one question with running software instead of slides: does this fit your business? The first part is chosen on day one by two rules: your people touch it every day, and it depends on as little as possible of the rest. A booking that gets confirmed, an order that gets picked, a request that gets assigned.
The screens are generated, so nobody designs anything in the room. That is what makes running software possible in a day, and it means the second day is spent on your rules and your cases, not on layout.
Everything the room produces is yours: the model, the code in your repository and the book, on a framework that is open source.
The first part of your process as working software on the laptop at the end of day two, with real cases from the room entered.
Reachable by a link for thirty days, within a week of the workshop, so the people who run the process can use it with real cases.
Your process written down in your own words: what happens, what is decided, who sees what. The document you forward to everyone who was not in the room.
The next three to five parts of your process, named in your words, with a written offer for them within a week.
Thirty minutes: which process hurts, who knows it end to end, and whether a workshop makes sense.
No software words. What the software is for, how the process runs today, how it should run with the new software as the people who run it decide, and which part comes first.
The first part is built while the room watches, checked against examples in your words, and the people who run the process enter their first real cases.
The part in the cloud, the book, the map of the next parts and a written offer.
The people who know the process end to end and the person who decides. Up to six people. Nobody needs a laptop and nobody needs to know anything about software.
Day one on site at your place in Austria, Germany or Switzerland, because the story is told at a wall. Day two on site or remote.
Domain storytelling, Event Storming and Event Modeling, as methods of requirements analysis. You do not need to know any of them; the workshop is designed for people who have never heard of them.
No. You and your people decide how your process should run. We ask, model it and turn it into software.
If you cannot say the first part back in one sentence at the end of day one, day two does not happen and only day one is invoiced.
Not ready to commit? Talk to us first — free.
Book a free 30-minute intro callFree 30-minute intro call — no obligation.
A short conversation is enough to see whether your business process and Reventless are a match — no obligation.
Free 30-minute intro call — no obligation.