From a Signed-Off Process Map to a Live App

By Kirill Stolbushkin

A signed-off BPMN 2.0 map can become a live application: agents plan the build, write the code, scan it, and deploy after you approve. In Vevos that pipeline is Conductor, and it starts on Tempo at $199/month — not on every plan. Mapping is free. Deployment is a separate decision, not a stopwatch.

The other story is draw a box, press go, production by standup. That is how you ship the wrong process faster. A diagram is a photograph of a car.

What does BPMN to automation actually mean?

It does not mean a developer squints at a PNG and writes a script that resembles the boxes. That is the translation tax, and it is how automation projects age into folklore.

BPMN to automation means the same model you signed as the spec is the input to a build. Tasks, lanes, gateways, and exception paths are not inspiration. They are requirements. The output is not another diagram. It is software people can use: forms, approvals, integrations, logs.

Three different products get shoved into this phrase. Keep them apart.

Phrase

What you actually get

What you do not get

Deploy a process map

A picture in a portal, or a file in a repo

Running work

From diagram to workflow

Often a Zapier/n8n-style chain of connectors

BPMN, SOPs, a governed process

BPMN to automation

A model that an engine or a generated app can execute

Magic without sign-off

Visio, Lucidchart, and Miro stop at the picture. Camunda will run BPMN if you have people who speak the engine. iPaaS will glue apps together without ever producing a process map. Vevos maps in BPMN 2.0 on the free and paid modeling plans, then — if you choose Tempo or Symphony — Conductor turns the signed-off model into a generated application.

Conductor is not on Intro, Pulse, or Rhythm. Official pricing: Conductor starts on Tempo; fuller enterprise controls sit on Symphony. Older launch copy that said “every plan” is out of date. Mapping and deploying are not the same purchase.

When is a process map ready to deploy?

Not when it looks tidy. When it is true enough to run.

  1. Someone who does the work has signed it. Not a stakeholder who liked the colors. AP, HR, the coordinator who actually chases the W-9.

  2. Lanes are roles, not continents. If “Finance” owns twelve tasks, you will automate a department-shaped blob.

  3. Gateways have conditions. Amount thresholds. Document present or missing. “Sometimes legal looks at it” is not a condition.

  4. Failure is on the page. Missing W-9. Match fails. I-9 Section 2 still open. A live app with only the happy path will still hit the real path. It will just do it off-camera.

  5. You know what “live” should be. A form and an approval queue. A posting into the ledger. A ticket. If you cannot name the artifact a user will touch, you are not ready to generate one.

Until then, stay on the model. Intro is $0 and holds three process models. Generate documentation. None of that requires Conductor. Deploying a wrong process is worse than a whiteboard.

What happens after sign-off?

In Vevos the build is not a single chat completing your homework. Conductor is a team of agents with jobs, plus humans at the gates.

Human checkpoints are not optional flavor. You sign off the process model, you see a security review, you approve deployment. Preview URLs exist so you can click the thing before it is production. There is a verification gate before go-live. Failed deploys can be sent back to agents to fix. Dev and production are separate environments, with secrets that are not supposed to leak into the diagram.

That is a pipeline. Pipelines take the time the work takes. A simple time-off request is not vendor onboarding with tax forms, contracts, and a PO. Anyone who sells you a universal ten-minute SLA for “any process” is selling a demo. Vevos will not promise one here. Sign-off, review, and approval exist because skipping them is how you automate a mistake.

How do I go from diagram to workflow on purpose?

  1. Get a real model. Describe the process, or upload a SOP, a transcript, a photo of a whiteboard. vevos.ai/free needs no account. Save on Intro ($0, three models) when it is worth keeping.

  2. Make it executable in meaning, even before it runs. Lanes, typed gateways, exception paths, named ends. Export BPMN XML if another engine is the destination — Camunda and Signavio are the named interchange targets. You can stop here. Many teams should.

  3. Sign the model. The person who lives with the work, not only the person who paid for the seats.

  4. Only then open Conductor — which means you are on Tempo ($199/month) or Symphony ($699/month). Foundations (brand, writing style, process standards, glossary, secrets vault) start on Tempo as well. SSO and SCIM are Symphony.

  5. Let Architect and Product Manager show you the plan. If the plan invents a system you do not have, stop. Correct the model or the scope.

  6. Builder produces a preview. Click it. Have AP try an invoice. Have HR try a new hire.

  7. Security scan, then you approve production. Custom domain optional. Default apps on *.app.vevos.ai are blocked from search indexing.

If all you needed was the map, skip steps 4–7. Automation is a choice, not a moral upgrade.

What this is not

Not RPA. Nobody is recording clicks on a fragile UI and hoping the button never moves.

Not iPaaS. Zapier and n8n automate handoffs between apps. They do not give you BPMN, a process repo, or an SOP generated from the same source as the diagram.

Not “the Visio stencil, but hosted.” A shape library does not become an application because you exported PNG.

Not Camunda as a silent swap. If you already have an engine team, keep them and export XML. Vevos is for teams who need the model and a generated app without standing up that engine team.

Not a plan that includes Conductor because you signed up. Intro is mapping. Tempo is where live deploy starts.

From diagram to workflow — a worked path, not a customer story

Take invoice approval, because everyone has one and nobody is a named client in this sentence.

The map: invoice arrives, AP matches to PO, exclusive gateway on amount, controller above $5,000, reject returns to the vendor. You argue about the threshold. You sign it.

What “live” might mean: a screen where AP drops the invoice, a match result, an approval task in the controller’s queue, a record of who decided what. Integrations you actually have — not a fictional ERP. Secrets in the vault, not in the prompt.

Conductor should build toward that map, not toward a generic “invoice app” from the internet. If the preview invents a step you never signed, you caught the translation tax in the act. Send it back.

Vendor onboarding and employee onboarding follow the same discipline. Parallel work has to be in the model as a parallel gateway or the app will serialize it.

Stop drawing. Start executing — when you mean it.

Map first. Sign it. Deploy only when the map is the process you want people to live in. Intro keeps three models at $0. Conductor starts on Tempo at $199/month. There is no stopwatch on that last sentence.

Try it at vevos.ai/free

Free to model · No credit card required

FAQ

What is BPMN to automation? Using a BPMN 2.0 process model as the spec for running work — an engine or a generated application — not redrawing the picture in a developer’s head. The model has to be complete enough to execute: lanes, conditions, exceptions.

Can I deploy a process map? You can publish a picture anywhere. Deploying work means a runtime. In Vevos, a signed-off model can be built and deployed by Conductor as a live app, starting on Tempo at $199/month. Mapping alone does not deploy anything.

How do I go from a diagram to a workflow? Make the diagram a real BPMN model. Sign it with the people who do the work. Then either load the XML into an engine you already run, or use a platform that builds from the model. Skipping sign-off is how you automate fiction.

Does every Vevos plan include live deploy? No. Intro is $0 with three process models. Conductor and live deploy start on Tempo ($199/month). Symphony adds enterprise Conductor capabilities, SSO, and SCIM. Modeling and deploying are different rungs.

How long does it take to go live? It depends on the process and on the reviews you do not skip: model sign-off, preview, security scan, deployment approval. There is no honest ten-minute SLA that covers every workflow. Simple apps finish faster than cross-team onboarding. Anyone who guarantees a clock is selling a demo.

What stack does the live app use? New Vevos apps default to Vite + React on Cloudflare Workers, with a preview URL, then production after the verification gate. That is the published default.

Do I have to automate once I have a BPMN map? No. A signed-off model plus documentation is a valid stopping point. Export XML if another tool needs it. Turn on Conductor only when you want the live app.

Try Vevos

Related