Davuud Ghani
AI workflow automation

AI workflow automation for professional services.

Built around the work your team already does. Much of a professional services firm's week goes on the work around the work: chasing briefs through inboxes, rebuilding documents by hand and checking every draft by eye. I build AI workflows that take those steps on, to your rules, and measure them from the first week. Each one below runs at Pivitt today.

The problemWhere the hours go

Where a small team loses its week.

Briefs arrive by email

Requests land across inboxes with files attached in pieces, and someone has to turn each one into a brief before work can start.

Documents built by hand

Proposals, reports and decks are rebuilt from old versions, with figures and names copied across and checked by eye.

Checks that depend on memory

House rules live in people's heads, so the same mistake comes back whenever someone new picks up the work.

Mornings start from the inbox

Each day begins by reading back through email and the calendar to work out what matters.

Four workflowsRunning at Pivitt

Four workflows Pivitt runs on, with what they changed.

  1. One

    Brief capture

    Every client request becomes a tracked brief, and nothing is lost.

  2. Two

    Document production

    Decks, reports and web pages produced from one source and checked before they leave.

  3. Three

    Checks on every draft

    Every draft passes four checks before anyone outside the business sees it.

  4. Four

    A daily brief

    Each weekday starts with one page and one priority.

Workflow 1 of 4

Brief capture

Every client request becomes a tracked brief, and nothing is lost.

An email arrives and becomes a brief card with the full thread, the client's own words and every attached file. Replies land on the same card, amends are recognised as amends, and approvals are kept on record.

36 of 36 client conversations captured · 1 hour median response, June to July 2026

Client emailcaptured on its ownBrief cardCapturedRequested byDeadlineFormatsIn their wordsbrief.pdflogo.svgphotos.zipClient replylands on the right cardChange requestflagged as an amendApproval on recordwho and when, kept36 of 36 conversations captured · 1 hour median response, June to July · 28 of 28 tables secured

Swipe to see the whole model

Workflow 2 of 4

Document production

Decks, reports and web pages produced from one source and checked before they leave.

Content is written once and produced in every format the work needs, then checked automatically for fonts, figures, page breaks and approved claims.

A 34-page tender bid built in four days

One sourceDeckReportWeb pageFontsFiguresPage breaksClaimsTravels

Swipe to see the whole model

Workflow 3 of 4

Checks on every draft

Every draft passes four checks before anyone outside the business sees it.

Voice, approved claims, banned words, and names and figures. Each draft comes out ready, ready after fixes, or held, with the reason written down.

15 mistakes caught in the first five days · 73% of tracked briefs approved first time, June to July 2026

DraftVoiceApproved claimsBanned wordsNames and figuresReadyReady after fixesHoldEvery problem located and rewritten before anything leaves.

Swipe to see the whole model

Workflow 4 of 4

A daily brief

Each weekday starts with one page and one priority.

Calendar, inboxes and call transcripts are read each morning into a one-page brief, so the day starts from what matters.

61 morning briefs composed, emailed and filed, 20 July to 16 October 2026

MonTueWedThuFriSatSun07:00 Morning sensesCalendar, both inboxes andcall transcripts read.Anything to file is marked.07:20 Morning briefComposed from the memory.One page, one priority,emailed and filed.Tue and Fri: radarTender feeds, namedaccounts and sectorsweeps, ranked.Fri 16:00 ReviewWhat moved, what stalled,predicted against whathappened. 17:30 check.1st Saturday: distilStale items retired,repeated correctionspromoted to rules.Company memoryevery run writes back to the memory

Swipe to see the whole model

How it worksMap, build, run

Mapped, built and run on your live work.

One

Map

Sit with the team's real week and find the steps that repeat, stall or go wrong.

Two

Build

Write your rules down and build each workflow around the tools the team already uses.

Three

Run

Use it on live work, measure it from the first week and adjust it as the business changes.

All fourteen systems Pivitt runs on

QuestionsAI workflow automation

What people ask about automation.

What is AI workflow automation?

Using AI to carry out the repeatable steps of a team's work, such as turning an email into a brief, producing a document or checking a draft, to the business's own written rules, with a person approving what leaves the business.

Which workflows suit a professional services firm?

The ones that repeat every week and depend on getting details right: capturing client requests, producing proposals and reports, checking work against house rules, and keeping track of what needs doing next.

Will it work with the tools we already use?

Each workflow is designed around the tools the team already uses for email, documents and files. Mapping those tools is the first step of every project.

How do you measure whether it works?

Each workflow is measured from the first week against a figure agreed at the start, such as response time to a brief, the share of work approved first time, or the mistakes caught before a client sees them.

Contact

Tell me what you are trying to change, in the brand or in the way the work gets made.

It is about optional
Goes straight to my inbox