8 min read

Examples of Flow Charts: 6 Business Workflow Charts

Examples of Flow Charts: 6 Business Workflow Charts

Examples of flow charts for a business all do the same job: they show one process from its trigger to its finish, with every decision drawn as a fork, so anyone can see who does what next. Below are six process flowcharts a small service business runs every week, each with the code to redraw it and the standard operating procedure it maps to.

A business process flowchart uses four main symbols: an oval for start and end, a rectangle for each step, a diamond for each yes or no decision, and a parallelogram for information coming in or going out. Write the process down first, then have Claude turn it into Mermaid code that draws the chart.

Start with the symbols, then copy any of the six charts.

Standard flowchart symbols

The common symbols trace back to standards first set by ANSI in the 1960s and later adopted as ISO 5807:1985, as Lucidchart's flowchart symbols guide explains. For business processes you need only a handful.

SymbolShapeUse it forMermaid code
TerminatorOval or rounded rectangleStart and end of the processA([Start])
ProcessRectangleOne step or actionB[Send welcome email]
DecisionDiamondA yes or no question that splits the pathC{Paid?}
Input or outputParallelogramData coming in or going out, like a formD[/Lead form/]
DatabaseCylinderWhere records are stored, like the CRME[(CRM)]
DocumentRectangle with a wavy baseA report, proposal or contractF@{ shape: doc, label: "Proposal" }

The last row uses the newer shape syntax that the Mermaid flowchart docs say arrived in version 11.3.0. Older Mermaid tools may not draw it, so the six charts below stick to the classic shapes.

  1. 1

    Trigger

    name the event that starts the process

  2. 2

    Steps

    list every action, one per box

  3. 3

    Decisions

    mark each yes or no fork

  4. 4

    Owners

    note who does each step

  5. 5

    Finish

    name the end state

How to make any process flowchart

How to read the six business flowchart examples

Each example has three parts: a simple on-page diagram of the main path, the Mermaid source with every decision branch, and the matching SOP from my sample standard operating procedures. These are samples built for a typical small service business, not copies of a client's documents. The SOP numbers follow my SOP template format.

To draw any of them, paste the code into the Mermaid Live Editor or any tool that supports Mermaid.

1. Lead to sale flowchart

  1. 1

    Lead form

    a new enquiry comes in

  2. 2

    Follow-up

    call and email within the hour

  3. 3

    Discovery call

    qualify the lead

  4. 4

    Proposal

    send price and scope

  5. 5

    Signed

    hand over to onboarding

Lead to sale, main path
flowchart TD
    A([New lead form]) --> B[(Add to CRM)]
    B --> C[Call and email within the hour]
    C --> D{Replied?}
    D -->|No| E[Follow-up sequence, 5 touches]
    E --> F{Replied?}
    F -->|No| G([Mark as cold])
    F -->|Yes| H
    D -->|Yes| H[Book discovery call]
    H --> I{Qualified?}
    I -->|No| J([Refer out or nurture])
    I -->|Yes| K[Send proposal]
    K --> L{Signed?}
    L -->|No| M[Follow up in 2 days]
    M --> L
    L -->|Yes| N([Start onboarding])

Maps to: P001 New lead follow-up and P002 Proposal and follow-up in the SOP examples.

2. Client onboarding flowchart

  1. 1

    Signed

    proposal accepted

  2. 2

    Invoice

    first payment requested

  3. 3

    Welcome

    email, folders and access

  4. 4

    Kickoff

    brief and first-week plan

  5. 5

    Live

    work starts

Client onboarding, main path
flowchart TD
    A([Proposal signed]) --> B[Send first invoice]
    B --> C{Paid?}
    C -->|No| D[Reminder after 3 days]
    D --> C
    C -->|Yes| E[Send welcome email]
    E --> F[Create client folder and tasks]
    F --> G[/Client sends logins and assets/]
    G --> H{Everything received?}
    H -->|No| I[Chase missing items]
    I --> H
    H -->|Yes| J[Kickoff call]
    J --> K([Work starts])

Maps to: P003 New client onboarding. In my agency, onboarding ran through the account manager, campaign manager, copywriter and client success, so the chart shows each handoff.

3. Content approval flowchart

flowchart TD
    A([Idea approved]) --> B[Write draft]
    B --> C[Editor review]
    C --> D{Changes needed?}
    D -->|Yes| B
    D -->|No| E[Owner approval]
    E --> F{Approved?}
    F -->|No| B
    F -->|Yes| G[Schedule or publish]
    G --> H([Link added to content board])

Maps to: P004 Content publishing and P005 Weekly social scheduling. The loop back to the draft is the part most teams never write down, which is why posts stall in review.

  1. 1

    Draft

    the writer finishes a version

  2. 2

    Review

    the editor checks it

  3. 3

    Approve

    the owner says yes or sends notes

  4. 4

    Publish

    scheduled and linked on the board

Changes go back to the writer, not into a chat thread

The content approval loop

4. Refund request flowchart

flowchart TD
    A([Refund request received]) --> B[/Order details/]
    B --> C{Within refund window?}
    C -->|Yes| D[Issue refund]
    D --> E[Confirm by email]
    E --> F([Log reason in CRM])
    C -->|No| G[Send to owner]
    G --> H{Owner approves?}
    H -->|Yes| D
    H -->|No| I[Explain policy kindly]
    I --> F

Maps to: P009 Refund request. The refund window is your policy. The chart only makes sure the same question gets asked every time.

5. Hiring flowchart

  1. 1

    Role

    write the job and test task

  2. 2

    Post

    share the listing

  3. 3

    Test

    shortlist does a paid test task

  4. 4

    Interview

    top candidates only

  5. 5

    Start

    tools, SOPs and first week

Hiring a virtual assistant, main path
flowchart TD
    A([Role needed]) --> B[Write job post and test task]
    B --> C[Post listing]
    C --> D[/Applications/]
    D --> E{Meets must-haves?}
    E -->|No| F([Polite decline])
    E -->|Yes| G[Paid test task]
    G --> H{Passed?}
    H -->|No| F
    H -->|Yes| I[Interview]
    I --> J{Offer?}
    J -->|No| F
    J -->|Yes| K[Set up tools and access]
    K --> L([First week from the SOP library])

Maps to: P010 Hiring a virtual assistant. A written SOP library is what lets a new hire learn the job from the library instead of from you. Before you post a role, it is worth checking hire a virtual assistant vs AI.

6. Month-end close flowchart

flowchart TD
    A([Last working day of month]) --> B[Export bank and card transactions]
    B --> C[Match to invoices and receipts]
    C --> D{Anything unmatched?}
    D -->|Yes| E[Ask the owner or chase receipt]
    E --> C
    D -->|No| F[Check unpaid invoices]
    F --> G[Write one-page summary]
    G --> H[(Save to finance folder)]
    H --> I([Send to owner and bookkeeper])

Maps to: P006 Invoicing and collections and P007 Month-end close.

How to make a flowchart with AI

Drawing boxes by hand is the slow part. Write the process in plain words, or take an existing SOP, and ask Claude for the Mermaid code. The same approach works for any process you already have written down in step-by-step instructions.

> Here is a process from my business. Turn it into a Mermaid flowchart using flowchart TD. Use ([ ]) for start and end, [ ] for steps, { } for yes or no decisions with the answers on the arrows, [/ /] for information coming in, and [( )] for the CRM or any database. Keep each label under six words. After the code, list any decision I did not say how to handle.

Three things make the output better:

  1. Give it the real process, not a summary. An SOP or a transcript of you doing the task works best.
  2. Ask for the missing branches. The list of decisions you did not cover is the part to read first. Each one is a gap in the process.
  3. Check the code renders in the Mermaid Live Editor before you share it. If a shape does not draw, ask Claude to use only the classic shapes above.

Keep each chart next to its SOP in the company folder, so Claude Code reads the process and the chart before it works on a task. I run each company from a folder like that, as I explain in Claude Code for founders.

From flowchart to automation

A flowchart is the clearest spec you can give an automation. Every rectangle is a step a person, a workflow tool or an AI agent could do. Every diamond is a rule or a judgment call. Fixed rules like "within refund window?" belong in a workflow tool; judgment calls like "qualified?" are where an AI agent or a person comes in. I cover the split in AI business process automation and which tool runs what in n8n vs Claude Code. For agents that handle the judgment steps, see AI agents for business.

Examples of flow charts: FAQ

What is a process flowchart?

A process flowchart is a diagram of one process from start to finish, with each step as a box, each decision as a diamond and arrows for the order. It shows who does what next and where the path splits.

What are the basic flowchart symbols?

The basic flowchart symbols are an oval for start and end, a rectangle for a process step, a diamond for a decision, and a parallelogram for input or output. Arrows connect them. Many charts also use a cylinder for a database.

What is an example of a business process flowchart?

A lead to sale flowchart is a common business example: a lead form comes in, the lead is added to the CRM and called, a decision checks if they replied, qualified leads get a proposal, and signed deals go to onboarding.

Can AI make a flowchart?

Yes. Claude can turn a written process into Mermaid code, which tools like the Mermaid Live Editor draw as a flowchart. Give it the real steps, the symbols you want, and ask it to list any decisions you did not cover.

What is the difference between a flowchart and an SOP?

A flowchart shows the shape of a process: the order, the decisions and the handoffs. An SOP gives the detail: purpose, owner, timing, tools and each step. Most teams need both, with the chart linked at the top of the SOP.

Get the processes already written

The AI Operator Kit gives you five ready systems for content, leads, outreach, sales and building, a daily operator plan and 107 prompts sorted by job, so the processes behind these flowcharts are already set up for Claude.

More on automation

View all