A visio flowchart maker alternative that lives in text

If you searched for a visio flowchart maker, you want a flowchart, and you’re used to Visio, which is Microsoft’s diagram app. The text alternative is to type the decisions instead of dragging a stencil onto a page. This page is that habit. It is not a price list, and it is not a claim that one file format eats the other.

I’m not going to invent a Visio SKU price. I don’t know what your license costs, and a made-up number would be worse than silence. I’m also not going to tell you Visio imports Mermaid. I have no such button to point at. If you need the Visio file to stay the Visio file, keep using Visio. If you need the flowchart in git, next to the change that alters the policy, typing it is the path I use.

The stencil habit, and what it was good at

Visio trained a generation of us to think in shapes on a sheet. You open a template, the stencil has a terminator, a process, a decision, a document, a data store. You drag. You connect. You align. The alignment feels like quality. I liked it. A tidy page is easier to defend in a meeting than a crooked one, and the stencil stops you from inventing a shape that means nothing.

The habit fails in a specific way. The page has no diff. “I moved the diamond” is a binary blob, or a file your reviewer can’t read in a pull request without opening the app. Two people edit two copies. You merge by looking. I have merged by looking. I kept the copy with the nicer fonts and lost the No path that was only on the ugly copy. The ugly copy was right.

Swimlanes are the other gift of that habit, and they’re also how a one-page policy becomes a poster. A lane per department feels responsible. It also freezes the org chart into the flow. Reorg the team and the chart is wrong even when the decisions didn’t change. I still draw a lane when the handoff is the actual risk. I don’t draw one because the stencil had a lane and the page looked empty.

A text flowchart doesn’t give you the stencil. It gives you a diamond when you type a diamond, and a rectangle when you type a rectangle. The flowchart syntax page is the shape list, shorter than a stencil and harder to decorate. That’s the trade. Less furniture. A file you can comment on line by line.

Type the approval you used to drag

Here’s an expense approval the way I want it in the repo. One question that matters: is it over the limit that needs a second person? Under the limit, it goes through. Over the limit, a manager says yes or no. Rejected requests stop. They don’t wander into a “file the form” shape I used to drag because the stencil had a document icon and the page looked unfinished without it.

flowchart TD
    submit[Submit expense] --> limit{"Over the limit?"}
    limit -->|No| pay[Schedule payment]
    limit -->|Yes| mgr{"Manager approves?"}
    mgr -->|Yes| pay
    mgr -->|No| reject[Send it back]

Submit, limit, maybe manager, pay or reject. I can review this in a diff. If finance changes the limit, the diamond’s label changes or it doesn’t. The policy change is not “we moved the green box.” There is no green box. Color was doing the job of the word Yes, and the word is enough.

What I deleted from the Visio version in my head: a start oval, an end oval, a document shape called “PDF receipt,” a data shape called “ERP,” and a lane for the employee, a lane for the manager, and a lane for finance. The receipt is an attachment, not a step. The ERP is where payment is scheduled, and pay already says that. Three lanes would have repeated the same arrows with more ink. If your company truly has finance do something the manager doesn’t, add that step as a box with a name. Don’t add a lane as a picture of the org.

The syntax tutorial is where the punctuation lives when the preview goes blank. Quoted labels, decision braces, no node id called end. I’m not reprinting it. The mistake this page is about is dragging a shape because the stencil offered it, then feeling obliged to connect it.

The same flow with the furniture still on it

This is the version I draw when I haven’t broken the habit yet. It parses. It looks “complete.” It is worse. Every extra box is a claim that someone does that thing, in that order, every time.

flowchart LR
    startOval[Start] --> form[Open the form]
    form --> attach[Attach the PDF]
    attach --> submit[Submit expense]
    submit --> limit{"Over the limit?"}
    limit -->|No| erp[(Write to ERP)]
    limit -->|Yes| email[Email the manager]
    email --> mgr{"Manager approves?"}
    mgr -->|Yes| erp
    mgr -->|No| folder[File the rejection]
    erp --> doneBox[End of process]
    folder --> doneBox

Read it as a spec, because someone will. “Open the form” is the app. Drawing it as a step implies a flowchart of the UI, and the next edit adds a box per field. “Attach the PDF” fails the chart for an expense that has no PDF, like a per diem. “Email the manager” specifies a channel. Maybe you use a queue. The chart just chose email because that’s what I dragged in 2014. “File the rejection” is a clerical fantasy. “End of process” adds nothing the two arrows didn’t already say, and I was careful not to name the node end, because that word will eat a subgraph if you add one later. The label can say end. The id should not.

Left to right is the Visio page talking. Landscape paper, landscape chart. This flow is a decision. Top down, as in the first figure, reads faster. I switch to LR for pipelines. An approval is not a pipeline, even when the ERP box makes it look like one.

If you recognize your last Visio file in that second chart, you don’t have to be embarrassed. You have to delete. The first chart is the deletion. Keep a box only if a reviewer could be wrong about it. Nobody is wrong about “start.” People are wrong about whether the manager sees expenses under the limit. The first chart answers that. The second chart hides the answer under stationery.

What I will not promise you about the move

I won’t promise a converter that reads a .vsdx and emits this Mermaid. I don’t have one to offer you in this post, and I won’t describe a click-path inside Visio that isn’t there. If your archive is a pile of Visio files, the move is a rewrite of the charts you still open. The ones nobody has opened since the reorg can stay where they are. Rewriting dead charts is how a migration becomes a hobby.

I also won’t pretend text is better at posters. A facilities diagram with a floor plate, a scale, and a logo in the corner is a drawing. Visio, or a drawing tool, is the right instrument. A policy with two diamonds is a flowchart. Don’t bring me a floor plate and ask for flowchart TD. Don’t bring me an approval policy and ask for a stencil so you can align it to a grid. The online tool roundup separates those approaches without pretending one vendor ate the others. The five-minute flowchart is the cut I use once you’ve chosen text and the source material is still a paragraph.

Neighboring habits, if your file isn’t Visio at all: draw.io and Mermaid and Lucidchart exports. Those pages are about those tools. I’m not going to launder their behavior into a Visio claim. Different products, different buttons. The shared lesson is only this: a diagram you can’t diff will be merged by taste.

Prices on our side of the page only

MermaidViewer’s editor is usable without an account. Starter is $6.99 a month. Pro is $11.99 a month. PNG exists on every plan. The free PNG is 1x with a small watermark. Starter’s PNG is watermark-free up to 4x. JPG, SVG, and PDF are Pro. I’m listing those because the pricing page is the place this search should land if the real question was “what does the text tool cost,” and because I owe you numbers I can stand behind. I owe you no number for a Visio plan. Ask whoever owns the license. Don’t trust a blog that guessed.

AI on the free plan is five uses total, if you want a draft of the approval chart from a sentence. I’d rather you type the first figure. It’s eight lines. A generated draft will reintroduce the PDF box, because “expense” and “receipt” sit next to each other in the model’s head. You’ll spend the use, then delete the box, which you could have not drawn. The login flowchart template is a reminder that templates are process charts, useful when the flow is login and a trap when you rename the boxes and pretend it’s an expense policy. Start from the approval you have, not from a nearby sample.

Connectors were doing work the words should do

In Visio I spent real time on connector routing. Elbows, a gap so two lines didn’t sit on top of each other, a jump where they crossed. That work felt like design. It was housekeeping. In a text chart the router is the layout, and I stop fighting it. If two edges must cross, the chart is probably too wide, or two decisions are pretending to be one picture. Split the picture. I split an approval into “who must say yes” and “what the payment job does after yes,” and both got shorter. The crossing lines went away without a single elbow drag.

The other connector habit is the unlabeled line. On a Visio page you can hover, or you remember because you drew it. In a repo the next person has only the label. Yes and No go on the diamond’s edges. If the edge is the only path, it doesn’t need a label, and adding “next” to every arrow is noise I used to add because empty connectors looked unfinished. They aren’t unfinished. They’re sequential.

A text chart will also refuse to store your manual nudge. You can’t leave the manager diamond 30 pixels lower because it collided with a title block. There is no title block. If the collision is in your head, shorten the label. “Manager approves?” beats “Does the assigned cost-center manager approve this expense in the portal?” The long form can live under the figure, once. I kept the long form inside the shape for a year because the shape had room. Nobody read it at 100% zoom.

How I review a text chart that used to be a Visio page

I look for the ghost of the stencil. A start oval. An end oval. A document shape that doesn’t change the next step. A datastore that restates the verb in the previous box. A lane name that matches a department that doesn’t make a decision. Each of those can go, and the chart gets truer as it gets smaller. People worry the small chart looks unfinished. Unfinished was the big one. It was finished visually and unfinished as a policy.

I look for the question the Visio page buried in a connector label at 8-point type. “If over $500” written along a line, easy to miss when you zoom to fit. In Mermaid that condition wants to be the diamond, with Yes and No on the edges. If the condition stays only in prose under the figure, the figure will be reused without the prose. I’ve seen that screenshot. The diamond was gone. The $500 rule was in a paragraph the screenshot cropped. Put the rule on the diamond.

Then I ask who edits it the next time finance changes the limit. If the answer is “whoever still has Visio installed,” the chart will rot on the laptops that have the license. If the answer is “whoever can edit the markdown,” the chart rots only if nobody cares. I’ll take the second rot. It’s visible in review.

Open the editor and paste the short approval, not the one with the PDF. If your limit isn’t a manager, rename the diamond to the person who actually says no. Leave the stencil in the other app, for the drawings that need a stencil.