Why Twiggy

A process tool that does the work for you

Many process tools make you work for them: modelling, maintaining, tidying layouts, keeping content clean and building reports is a constant job. Twiggy is built to help you model properly and well, with methods that work, so modelling is simple, review is easy, and processes become a living part of how people work.

Proven methods, built in

Value chain, decomposition and BPMN, the way good process teams already work: a process map of what the organisation does, chains inside it, and flows below. Every model has its place in the estate, not a drawing made for one problem.

Layout that does itself

Lanes, decisions, parallel paths and hand-offs placed for you, every time, in one readable style. No hours nudging boxes or tidying diagrams, and a sharp image for slides when you need one.

Small models, connected

The framework keeps each model small by design: detail goes a level down, not into a bigger diagram. Hand-offs link one process to the next across teams, and search finds any step, system or risk in any model.

Review made easy

Owners of each part comment and approve from a link on any device, with their part picked out and no licence needed. Anything not yet confirmed is marked until someone who knows does, and review dates and reminders keep it current.

Everything linked to the work

Risks, controls, systems, KPIs, SLAs, rules and requirements sit on the steps they belong to, from shared registers: one item, used everywhere, changed in one place, with no reports to build by hand.

Knowledge and training in one place

How each step is done, the exceptions and who knows how to handle them, procedure guides and presentation mode for training: all from the same models, so the documentation people use is the one that is signed off.

AI that helps along the way

It can interview your experts, draft a first model, write how a step is done, and review a model or a whole map against good practice, explaining every change. Useful, optional, and off with one switch: Twiggy is a capable tool without it.

Affordable for the whole organisation

Reviewers and readers don’t need a paid seat, and modellers are priced to spread, so processes can reach everyone who does the work instead of staying with a central team.

The intent

Process knowledge only stays true if the people who do the work can see it, use it and correct it.

Twiggy exists to make the process a living thing: modelled with well-established methods, connected across the organisation rather than drawn for one problem, reviewed by the people responsible, and used every day for knowledge and training.

Every design decision leads the same way: automatic layout, small connected models, review from a link, procedures from the models themselves. AI helps along the way, but the tool stands on its own.

And it is priced to be within reach of the whole organisation, so processes are embedded in the way people work, not locked away with a few specialists.

Complexity made understandable, not hidden

Real operations are messy: agreements, exceptions and arrangements built up over years. A clean diagram that leaves them out is wrong. Twiggy keeps the flow simple and puts the rest where it belongs.

  1. 1.Model the work as it is done

    Keep the exceptions and workarounds that matter. Simplify by grouping steps, not by leaving things out.

  2. 2.Keep the flow for the order of work

    Rules, exceptions, controls and requirements sit on the steps, so the diagram stays readable.

  3. 3.Make the boundaries clear

    Every hand-off links to the process it comes from or goes to.

  4. 4.Tell what’s needed from what could go

    Some complexity the business needs; some is left over from the past. Mark it, so change doesn’t just copy it.

  5. 5.Write down what only people know

    Record who knows how the awkward cases are handled, before they move on.

How Twiggy compares

A broad comparison with the kinds of tools teams use to model processes today, including where others go further. Products within each kind differ, so treat it as a guide and check the ones you use.

How Twiggy compares on what it was built for
CapabilityTwiggyEnterprise BPM suitese.g. SAP Signavio, ARISBPMN modellerse.g. Bizagi, Camunda ModelerDiagramming toolse.g. Visio, LucidchartWhiteboardse.g. Miro, Mural
AI-guided modellingInterviews experts, asks for the scope first, applies modelling standards and reviews quality
Built for AIA text language with automatic layout: small, exact edits and low token spend
Process map, chains and flows, linkedA catalogue of every process, chains drawn from the hand-offs between flows, sub-processes for detail
Many views of one modelLanes by role, system or your own properties, and lenses for risk, systems and sign-off; edit in any of them
Automatic layoutReadable, consistent diagrams without arranging shapes by hand
Linked risks, controls, systems, roles and your own propertiesShared libraries and workspace properties, attached to the steps they belong to
Review and sign-offInferred steps flagged; owners comment and approve from a link, no licence
GovernanceRoles and permissions, owned folders, review cycles by risk, version history and an audit log
Experts take part without trainingInterviews in plain language, sign-off from a link
Search inside every modelAny step, lane, system, risk or rule, across every model
First model in minutesSign in, describe the process, and the model draws itself
Try it with no sign-upA free shared demo that follows the modelling guide, to explore and change
BPMN 2.0 import and exportBring models in from other BPMN tools; take them out with lanes and layout intact
Priced for small teamsPlans for one person or a small team; reviewers always free
Single sign-onSign in with your company account: Entra ID, Okta, Google Workspace (Twiggy Corporate)
Your models stay portableOpen packages of plain-text models, with folders and registers, that import back exactly; scheduled backups to your own storage
Process mining and automationAnalysing event logs, or running processes in an engine. Not our focus: export BPMN to the engine you use
Yes Partly, in some products, or with add-ons No, or not the focus

Based on publicly available information about each kind of tool, as of 2026. Product names are trademarks of their owners and are given only as examples of each kind; no endorsement or affiliation is implied. Twiggy is for capturing, improving and agreeing how work is done; for process mining or running processes in an engine, a specialist tool sits alongside it. Spotted something out of date? Tell us through the contact page.

See it on a real process

Take the tour of a small bank's processes, mapped, chained and flowed as in the modelling guide, or open the live demo and model one yourself.

See it working Open the live demo