- When
- Friday afternoon: the weekly report for each of twelve clients is due
- What's ready
- A draft report per client from the week's emails, meetings and files, with the figures computed from the client's spreadsheet
- Who decides
- The account lead reads each one, edits it and approves the send
Your team's repeat work, run as a process.
Pick one of more than thirty ready-made workflows or describe your own in plain words. AUGMTD runs it every week, and anything that goes out waits for your approval.
- 30+
- ready-made workflows to start from
- 8
- departments covered, from HR to support
- 3 days
- until a reminder is ready when a client has not answered
A workflow is a piece of repeat work your team already does, written down once and run the same way every time.
Start from a template or from your own words.
If your operations lead has explained the month-end close to three new people this year, each time from memory, it came out a little differently each time.
Pick one of more than thirty ready-made workflows across HR, sales, finance, operations, legal, marketing, IT and support. If yours is not there, describe it the way you would brief a new colleague, at whatever length it takes, and AUGMTD builds the workflow from that.
You choose which piece of work to hand over first, and you read the steps before the first run.
It starts when the work does.
The client call ends at 16:40. By the time anyone thinks about the follow-up, it is Thursday.
A workflow runs by hand, on a schedule, or when an email, a file or a meeting arrives. Where meetings are switched on, a follow-up for client calls can start as soon as the meeting is filed. AHK Portugal's tender search starts every Monday at 08:00, before the team is in.
You set what starts it and when. Each workflow has one schedule.
It asks the client for what is missing.
The report is half done because the client never sent last month's figures. Someone is writing the third chaser.
When a step needs something only a client or supplier has, AUGMTD prepares a request on a secure link. You send it from your own mailbox. They open it without an account, answer or upload a scan, a PDF or a spreadsheet, and their reply lands on the case. After three days a reminder is ready, and it goes only if you click.
You send the request and any reminder. The work carries on when you say so.
The figures come from your spreadsheet.
One column added twice is all it takes for the client to spot the error before you do.
Hand a workflow a spreadsheet and the totals are computed in code from your columns. The verdict and the key figure sit at the top of the result, and the draft is written around them.
You check the figure at the top before anything goes to a client.
One process for the team, one setup per client.
Two account managers write the same report two different ways, and the client can tell who was on holiday.
Share a process and everyone on the team hands it work the same way. Each client or team keeps its own setup, with its own documents and standing answers, so one client's report reads as if it was written for them. Any finished case can be run again.
You decide who on the team uses a process. Every share tells you what it means before you confirm it.
Test it before it counts.
Nobody wants the first run to be the one the client sees.
Test runs never send anything, so you can read exactly what a workflow would produce. Every real run leaves a record you can open and run again.
You decide when it goes live. Anything meant for a client or supplier still waits for your approval.
Three pieces of repeat work, in a normal week.
- When
- Monday 08:00: last week's new public tenders have been read
- What's ready
- One report of the tenders that could suit each member, with a short reason for each and the link to the official notice
- Who decides
- Staff keep, drop or add matches before any member hears about a tender
- When
- Sixty CVs arrive for one role
- What's ready
- Each CV checked against the must-haves with the line that proves it, all of them ranked in one view
- Who decides
- The hiring manager decides who moves on. Invitations and declines wait to be sent
Good to know before you start.
- Runs started by an email, file or meeting are capped at 20 a day by default; extra runs wait in a queue.
- Asking a client or supplier on a link needs a workspace with email switched on.
- Each workflow has one schedule.
Questions people ask.
Do I need to know how to build automations?+
No. You pick a template or describe the work in plain words. We set up the first one with you, on your own example.
Can a workflow send email on its own?+
Only if you say so. A workflow cannot send to anyone else unless an approval step comes first or you have given it standing permission for named recipients.
Where do the numbers in a report come from?+
Scores and sums are computed from the weights you set and the spreadsheets you hand it. They are not guessed by the model.
Read next
See it on your own work.
Show us one process your team repeats every week. We'll show you how it would run.
