Prrowess
Book a call
A case study from Purrple Orryx

We couldn't hire an events coordinator fast enough. So we built one.

Tina works in our Teams, has her own inbox, and asks before she sends.

Tina
Events Coordinator (digital assistant)
Purrple Orryx Events
In Teams
  • In Teams
  • Own inbox
  • Asks before she sends
  • Read back a new stand briefTeams, with 6 gaps and 3 questionsDone
  • Posted the 17:30 project linesOne line per live projectDone
  • Added a supplier to the vendor listNoted where she found themDone
Live since 13 Oct 2026Supervised trial to 12 Nov

Why we built her.

  1. 01Our coordinator moved on.
  2. 02Hiring the right person was going to take months.
  3. 03Live projects don't wait. So we built one.

We wrote her a job description.

A real one, with responsibilities, decision rights, targets and a reporting line. Our creative director approves quotes. She signs every email as a digital assistant and never pretends to be a person.

Take a brief

Reads briefs typed or pasted into Teams, including PDFs, Word, Excel and screenshots. Reads each one back with gaps and questions, then sets up the project.

Shortlist suppliers

Proposes a shortlist for each requirement line and explains why. The team adds or removes names before anything is drafted.

Draft and chase

One quote request per supplier in our tone, then a gentle reminder, a last call and a kind closing note. Each waits for Send. “Stop chasing” stops it.

Read the quotes

Each quote is normalised (before VAT, VAT, total, per person or total) and filed against the right line. Anything uncertain is marked check.

Build the comparison

A Word document in the right client folder, with her recommendations clearly marked as hers.

Find new suppliers

Offers to search the web, and searches only after a yes. Up to 5 companies a run, each with a source, website, contact and confidence.

Keep the vendor list

Every supplier she meets goes on the team's vendor list, with a note on where she found them.

She lives inside our Microsoft 365.

Tina is an internal team member, not a public chatbot. She works in Teams with three of us, reads what we give her access to, and only ever emails suppliers. Follow one brief through.

INSIDE OUR MICROSOFT 365Teams chatsBriefs and questionsHer mailboxSupplier repliesOneDrive filesThe handover she readProject boardsDates and ownersWhat she knows11 playbooks, 1,835 suppliersSend gateChecks run in codeApproval cardA person presses SendSupplier inboxQuote requestsClientsNever contactedTinacoordinator
INSIDE OUR MICROSOFT 365Teams chatsBriefs and questionsHer mailboxSupplier repliesOneDrive filesThe handover she readProject boardsDates and ownersWhat she knows11 playbooks1,835 suppliersSend gateChecks run in codeApproval cardA person presses SendSupplier inboxQuote requestsClientsNever contactedTinacoordinator

InteractiveClick the options below. Pick any step to stop on that moment. It also plays on its own.

A brief lands in Teams, typed or pasted, with a PDF, a sheet or a screenshot.

Onboarding: a month, or before day one.

Before go-live she read the whole handover: the role's mailbox, Teams chats, OneDrive files and project boards.

InteractiveClick the options below. Compare a new hire's first weeks with Tina's.

A new hireWeeks 1 to 4
  1. Week 1Laptop, logins and introductions
  2. Week 2Reading old emails and folders
  3. Week 3Learning who the suppliers are
  4. Week 4First quote requests, with help
TinaBefore day one
0suppliers in her database
0playbooks she wrote
Everypast project, read
Rankedby what we actually paid
  1. 11 OctAudit
  2. 11 to 12 OctHandover read
  3. 12 OctTeams bot, mailbox, send gate and approval cards
  4. 13 OctGo-live

No person in week one could take that in.

A brief comes in.

She reads it back the way a good coordinator would: what she heard, the gaps she sees and the questions to ask. Lines can be added at any point, even after quotes are out.

Illustrative example with made-up details. The buttons are a demo and send nothing.

TTina is working on the stand briefDone
CLClient lead
New one. Stand for a tech exhibition, 6x9, two sides open. Meeting room, storage, LED wall. Brief PDF attached, client wants a first design soon.stand-brief.pdf
TTina Events Coordinator (digital assistant)

What I heard

  • Exhibition stand, 6 x 9 m, open on two sides
  • Meeting room for 6, a storage room and an LED wall
  • Three show days, with build and breakdown either side
  • Client wants a first design to review

Gaps I see

  • The organiser's design approval deadline
  • Rigging approval, if anything hangs from the ceiling
  • The venue power order and its cut-off
  • Contractor insurance for the build crew
  • Crew badges for build and breakdown days
  • Storage on the floor during the show

Questions

  • Do we have the organiser's exhibitor manual?
  • Will anything hang from the ceiling?
  • Who signs off the design on the client side?

InteractiveClick the options below. Answer Tina like the team would and see her reply.

Nothing leaves until someone presses Send.

Every outgoing email arrives in Teams as a card: To, Cc, subject and the full text. Send, Change or Hold. Supervision takes seconds.

InteractiveClick the options below. Pick one or several suppliers, tick who gets it, then press Send, Change or Hold. Nothing is really sent.

T
Ready to sendQuote request, stand project
Waiting for you
To
sales@standbuilder-a.example
Cc
Client lead
Subject
Quote request: 6 x 9 m exhibition stand, Dubai

Hello,

We are planning a 6 x 9 m stand, open on two sides, for a tech exhibition in Dubai. It needs a meeting room for 6, a storage room and an LED wall. Could you send a quote with your build and breakdown schedule?

Tina
Events Coordinator (digital assistant)
Purrple Orryx Events

  • Known supplier
  • No client name
  • No other prices
  • No internal files

 

Mock card with invented suppliers. Nothing is sent.

She goes and finds them.

When we don't know a supplier, she offers to look. One run in her first weeks:

  1. 1The ask

    The team asked her to check rates at a landmark Dubai venue for a dinner.

  2. 2The right door

    She found the venue's published contact and noticed it was for dining, not events sales. So the enquiry asked them to pass it to the right team.

  3. 3The draft

    About 250 guests. Capacity, packages, minimum spend and AV access.

  4. Held

    The send gate stopped it. The venue's hotel group is also on our client list, and an address like that needs the founder's one-tap approval the first time.

    Held for the founder's approval

Not that she can do it. That she knows when not to.

The line we drew.

What she does alone, what she asks first, and what she never does.

InteractiveClick the options below. See what she does alone, what she asks first, and what she never does.

Enforced in code, not just written in her instructions.

  • Contact a client, or reply when a client emails her
  • Confirm a booking or a hold, commit money, approve a payment, sign or submit anything
  • Tell a supplier the client's name without the account lead's OK
  • Share one supplier's price with another
  • Attach internal files to supplier emails
  • Search the web without a yes
  • Delete, merge or move anything in the project tools
The send gate. Every outgoing email passes it in code first. It checks:
  • The recipient is a known supplier, not a client.
  • The client's name is absent.
  • No other supplier's prices are included.
  • Only safe attachments are included.
  • The tone is clean.

A day in Tina's week.

She keeps a coordinator's rhythm, Dubai time. In between, she listens: copied on an email, she files the facts on the right project and stays quiet on the thread. What one teammate tells her, she knows in every chat.

  1. 08:30 weekdaysMorning summary for each person
  2. Monday 08:45Countdown of what is late and due
  3. 10:00 and 15:00Follow-up cards
  4. Friday 16:00Supplier report
  5. 17:30 weekdaysOne line per live project

Her first 16 days.

13 to 29 Oct 2026, inside a supervised trial. These show she is real and under control. They are not a claim about scale.

113Inbound emails handled
101Suppliers added to the vendor list
47Approval cards posted
14Emails sent, every one after a person pressed Send
30Drafts the team held, changed or replaced
3.50 USDRoughly the total AI cost for all of the above

Counted from her own records. The AI cost is our operating data for the same 16 days.

The 80 / 20. And why the 20 matters.

I'd say she covers about 80% of the desk side of a coordinator's job. That's my estimate, not a measurement.

The desk side is hers

  • Briefs, shortlists and quote requests
  • Reminders, replies and comparisons
  • Notes, the vendor list and what is late

What stays with us

  • Walking a venue and feeling whether the room works
  • The phone call that settles a nervous client or supplier
  • Supplier relationships built over years
  • Being there on the day
  • Signing, money and clients
  • The judgement calls

During the trial, nothing leaves the company until one of us presses Send on an approval card in Teams. Three of us work with her: me and two teammates.

What she does not do yet

  • Updating deliverable checklists and chasing the team on their own dates. That is the next stage.
  • Run sheets, artwork and print approvals, or coordination on the day.
  • Phone calls, WhatsApp, or meetings outside Teams.
  • Working outside Microsoft 365. She needs Teams and an Exchange mailbox today.

How she gets better.

When she gets stuck, she logs a roadblock herself. 22 of her first 24 were fixed, most within a day. Her build plan comes from real use, not a wish list.

  1. 1She gets stuck.
  2. 2She logs it.
  3. 3The team fixes it, usually within a day.
  4. 4She can do it next time.

Is a role in your business agent-shaped?

Think of one role. Five questions, about twenty seconds.

InteractiveClick the options below. Answer Yes or No to all five. Your result appears underneath.

  1. Is most of it done on a computer?
  2. Does it repeat every week?
  3. Does it follow rules you could write down?
  4. Is the knowledge sitting in your emails, CRM or accounts?
  5. Could a person approve the final step?

Answer all five to see where the role lands.

How we'd set one up for you.

1

Read your history

Your past projects and supplier history, before day one.

2

Build your playbooks

One per kind of job, with unconfirmed rules marked (check).

3

Connect your tools

Teams, a mailbox and your project tool.

4

Run a supervised trial

A person presses Send on everything until you decide otherwise.

The playbook.

How we set Tina up, written as a template you can reuse. 11 short chapters.

  1. Why a digital coordinator
  2. Job description template
  3. Decision rights
  4. The onboarding checklist
  5. Rank suppliers by evidence
  6. Playbooks per event type
  7. The approval card and the send gate
  8. Web research with guardrails
  9. The roadblock log
  10. The first 30 days
  11. Want one for your team?

Get the playbook

It opens on this page straight away, with a PDF to keep.

She's not a chatbot. She's a team member with a very clear job description.

Book a call with Ankur

Built by Prrowess for Purrple Orryx.

Book a call