Skip to main content
Approval workflowsNew

Stop asking who still has to approve this.
Draw it once, and it runs itself.

Draw how a document should travel through your company - who approves, who signs, who only needs to see it - and DocMe walks every document down that path. People answer from WhatsApp, the AI tells you what is stuck, and an approved invoice posts its own journal entry.

See the blocks
Asks everyone at once
Full audit trail
Ends in a journal entry
Nine blocks

Any approval your company has, drawn in nine blocks

Drag a block onto the canvas and join the dot under one to the top of the next. That is the whole language - there is nothing else to learn.

Start

Where every run of this design begins. Exactly one per design.

Approval

The assignee approves or rejects, with an optional comment.

Signature

The assignee signs the document itself, where you placed their box.

Review

The assignee must open the document and acknowledge it. No verdict.

Assign approvers

A person names who comes next, then presses the run onward.

Condition

Splits on the run's amount or category - the yes arm and the no arm.

Join

Waits for the branches that feed it: all of them, any one, or a quorum.

Notify

Sends a WhatsApp, Telegram or email message and moves straight on.

End

Closes the branch it sits on. A rejected ending stops everything.

What it does

A workflow engine that knows what a document is

Every other approval tool starts with an empty form. This one starts with the invoice you already uploaded, the vendor it already recognised, and the ledger it is already going to post to.

Nine blocks, one canvas

Drag a block on, join it to the next, and the design is done. The same canvas draws a two-step expense sign-off and a fifteen-step board process.

Everyone asked at the same time

An email chain is a queue: each person waits for the one above. Here the run drops on the CEO, the CFO and legal at once, and a join passes only when the last verdict is in - or when a quorum is, if that is what you drew.

An AI overview of every run in the company

You do not open twelve boards to find the stuck one. The AI reads every live run and tells you in a sentence what is moving, what is not, and who to nudge - then offers to send the nudge.

Rules, not exceptions

A condition splits the run on the amount or the category the AI already read off the document. Small invoices go straight through; big ones find the CEO.

Approved from WhatsApp

The step arrives on the channel that person already uses. Two buttons, a comment if they want one, and the run moves. No app, no login.

Signed where you said

Draw the boxes on the document before it goes out. Each box belongs to a step, so whoever that step reaches is the person who fills it.

Assign a chair, not a name

Point a step at a role and whoever holds it that day is asked. Designs survive people joining, leaving and swapping desks.

An approval that ends in a journal entry

The run does not finish on a green tick. An approved invoice becomes a balanced entry against the accounts you use, ready for the ledger export - because DocMe already read the document that started the run.

Who said yes, when, and why

Every verdict keeps the person, the timestamp and the comment they left. A rejection is not a dead end - it is a recorded reason you can answer and send round again.

Runs that start without anyone opening the app

Name the vendors a design belongs to. The next invoice from one of them is recognised on arrival, claimed by that design, and already sitting with the first approver before anybody knew it landed.

For the person who signs off

Your whole company's approvals, in one paragraph.

A CEO does not want twelve boards. They want to know what is stuck and whose desk it is on. The AI reads every live run - the design it is walking, the step it is parked on, how long it has been there - and writes the answer.

It reads the runs, not a status field

The summary is written from the boards themselves, so it cannot drift out of date the way a spreadsheet does.

It offers the nudge

One tap sends the reminder on whatever channel that person is actually reachable on.

It scales down as well as up

Two people and one approval, or four hundred people and nine hundred a month - the overview reads the same.

Approvals · company overview

LIVE

12

Live runs

3

Waiting on you

47

Cleared this week

1

Stuck 3+ days

THIS MORNING

Twelve runs are live and eleven are moving. INV-4471 has sat with Amir Cohen for four days - it is the only thing holding the month close. Everything else is inside its usual time.

INV-4471 · BezeqWaiting on Amir Cohenstuck4 days
CON-118 · Supplier termsWaiting on Legal1 day
PO-9032 · HardwareApproved · entry posted—
EXP-771 · TravelRejected · wrong cost centre2 days
How it works

Four things to do once

01

Draw the design

Drop the blocks your process needs and join them up. Name who acts at each step, or name the role and let whoever holds it answer.

02

Say where it gets signed

Before a document goes out, draw the boxes on the page itself - a signature here, a name there, the date. Each box belongs to a step.

03

Send a document round

Pick a file from your desktop and start it, or name the vendors whose invoices should start it on their own. The first approver is asked immediately.

04

Watch it - or do not

The board repaints itself as people answer. When the run ends approved, the document is filed, sealed, and its journal entry is waiting in the export.

Why DocMe Flow

An approval should not be a group chat

The old way
Forward the invoice and hope somebody answers
One person at a time, because a thread is a queue
Nobody can say whose desk it is on right now
"Approved" is a message in a chat, not a record
Someone retypes the approved invoice into the books
With DocMe Flow
The document walks the path you drew, on its own
Everyone on that step is asked at the same moment
The board shows exactly who is being waited on
Every verdict keeps the person, the time and the comment
The approved invoice posts its own balanced entry
Frequently asked questions

Questions & Answers

No. The same canvas draws a one-step expense sign-off for a two-person firm and a fifteen-step board process for a group. Small teams usually run two or three designs and never touch them again.

People inside your organization do, because their verdict is recorded against them. What they do not need is to be at a desk - the step reaches them on WhatsApp, Telegram or email and they answer from there.

The rejection is recorded with the comment they left, and a rejected ending stops the run wherever it is. You fix what they objected to and send it round again - the old attempt stays in the trail.

Yes, and that is the point. Wire several blocks under one and the run drops on all of them together. A join block then waits for all of them, any one of them, or a quorum you set.

DocMe has already read the document that started the run - the vendor, the amount, the VAT. When the run ends approved, that reading becomes a balanced entry against your accounts, ready in the ledger export. Nobody retypes it.

Yes. Name the vendors a design belongs to, and the next invoice recognised from one of them is claimed by that design automatically and sent to its first approver.

Point the step at a role instead of a name. Whoever holds that role on the day the run gets there is asked, and if several people hold it they are all asked at once - the first answer settles the step.

Draw your first approval in an afternoon.

Bring us the process you already run by email and we will draw it on the canvas with you, on the call.

Every verdict recorded
From two people to thousands and more