Skip to content

Case studies

What the team actually does

Three duties from our first deployment, an engineering consultancy running Deltek Vantagepoint, and a set of standing duties from the roster we built for real estate brokerages. Each one names the team member, what it does on every job, and what stays with people.

Accounts payable

Two team members, one invoice: intake and review

Before

Supplier invoices arrived as PDFs by email. Someone in finance keyed each one into the ERP, attached the file, and pushed it to an approver, who then had to look up the vendor history and the project budget by hand before signing off.

What stays with people

The approver still approves. What changes is that every invoice arrives with the vendor history, the budget position and a recommendation already attached, and the routine ones need only a glance.

Controls

  • A repeat of the same vendor and invoice number is recognised and never posted twice.
  • Amounts above the threshold are blocked in code before the request is built, not by an instruction the model might miss.
  • Every ERP call is logged against the job, with what was sent and what came back.

Vera

AP intake

“If it’s in Vantagepoint, I can find it.”

On every job

  1. 1 Reads each invoice, including scanned ones, and extracts vendor, invoice number, dates, line items and totals. A field it cannot read is left empty, never guessed.
  2. 2 Checks that the lines add up to the subtotal and that subtotal plus tax equals the total. A mismatch is reported, not posted.
  3. 3 Looks up the vendor, posts the invoice into the ERP and attaches the source PDF to the record it just created.
  4. 4 Holds anything above the duty’s review threshold, anything uncertain, and anything the ERP rejected, and says why.

Rae

AP reviewer

“Approve with evidence, never with a shrug.”

On every job

  1. 1 Runs on a schedule and picks up every pending approval that has no review yet.
  2. 2 For each one, pulls the approval lines, the vendor’s history and the spend to date on every project the lines touch.
  3. 3 Applies the firm’s limits: an auto-approve ceiling, a lower ceiling for vendors with no history, a bound against the vendor’s largest prior invoice, and a check that project cost stays inside its compensation.
  4. 4 Records one recommendation with the numbers behind it. Anything outside the limits is marked for a person, with the reason on a single line.

Timesheets and expenses

Tess: hours and receipts, from an email

Before

Field staff finished the week with hours to log across several projects and a pocket of receipts. Entering time by phase and building an expense report with the right categories and attachments was the job nobody got to until Friday night.

What stays with people

Tess never submits. The timesheet and the expense report are left open for the person to check and submit themselves. When a receipt cannot be categorised or a project cannot be matched, she asks once, precisely, rather than guessing.

Controls

  • Identity comes from the sending address, so nobody can log time for someone else.
  • A submitted timesheet, an inactive project or more hours than a day holds is a question back to the requester, not a workaround.
  • One search, one status read, one write. An error is final for that call, never retried unchanged.

Tess

Time and expense

“Nothing closes late on my calendar.”

On every job

  1. 1 Starts every job by identifying the requester from their email address in the ERP. It acts only for that person, never for someone named in the message.
  2. 2 Finds the project from a number, a name, a client or even a street address, and says how confident the match is. It charges time at the lowest level the project has, phase or task.
  3. 3 Adds a whole week of hours in one write and reports exactly what the ERP accepted, day by day.
  4. 4 Turns photographed receipts into an expense report: merchant, date and total from each image, a category chosen from the firm’s list, the project where one is named, and each receipt image attached to its own line.
  5. 5 Answers budget questions on the same channel: planned against actual by project, over-budget flags, and a spreadsheet when the list is long.

Project initiation

Kel and the Approver: a clean form, then a defensible yes

Before

Starting a project meant a project initiation form with dozens of required fields, child records and calculated values, then an approval that had to confirm the client’s authorisation actually covered the budget on the form.

What stays with people

A person still owns the relationship and the decision to proceed. The Approver’s job is to make sure nothing gets a yes without the paperwork to back it.

Controls

  • Each team member holds a grant to only the operations it needs. The Approver cannot edit a form; Kel cannot approve one.
  • Approval is a decision with a written reason, kept on the request thread.

Kel

Initiation forms

“A clean form is a fast project.”

On every job

  1. 1 Takes the request from a form or an email, looks up client, contacts and the project manager, and populates the initiation form with its child records and calculated fields.
  2. 2 Runs the ERP’s own validation and fixes what it can. Reports progress as a checklist and stops to ask when a required value is genuinely unknown.

Approver

Initiation approval

“Measure twice, approve once.”

On every job

  1. 1 Is triggered when a form is ready. Reads the form, its unprocessed budget total and the client’s authorisation document attached to it.
  2. 2 Approves only when the authorisation covers the budget, the form validates and the required fields are right. Otherwise it holds the form and states exactly what is off, with the approved-versus-budget comparison on one line.

Standing duties

A brokerage morning, on a schedule: Finn, Remy and Marco

  • Finn: New listings match

    Weekdays, 06:30

  • Remy: Morning brief

    Weekdays, 07:00

  • Marco: Market pulse

    Mondays, 07:00

Before

Nobody asks for this work. It has to happen before the agent starts the day, every day: what came on the market overnight and who it suits, where rates and the market sit, which clients have gone quiet, and which deadlines are close. This is what standing duties are for: a duty with a schedule and a recipient list, run by the team member that owns it, with the result emailed when it finishes.

What stays with people

The agent reads one screen at seven and sends the follow-ups they agree with. The three team members never contact a client themselves. If a source is unreachable, the report says so in a caveat line rather than quoting a number nobody saw.

Controls

  • Each duty has a fixed schedule, a fixed recipient list and an owner who can pause it, edit its instructions or run it now.
  • Every run is a job on the request hub with its full thread, so a wrong figure can be traced to the call that produced it.
  • Search and lookup calls are capped per run in the playbook, so a bad morning cannot become an expensive one.

Finn

Listing scout

“It hit the market an hour ago. Here’s who it’s for.”

On every job

  1. 1 Scans the MLS feed for listings that came on in the last 24 hours, 72 on a Monday, within the brokerage’s area.
  2. 2 Matches each one against every buyer’s brief and the firm’s flip criteria, and writes the morning report into the shared workspace.
  3. 3 If the MLS connector is not configured, says so in one line and stops. It never fills the gap with guesses.

Remy

Agent’s assistant

“Your day, already sorted.”

On every job

  1. 1 Opens with the rates that matter: Bank of Canada posted, prime and policy, each with its change.
  2. 2 Adds the market lines for each geography the brokerage follows, from published indices, with year-over-year change.
  3. 3 Reads the pipeline list and drafts a follow-up for every client whose last touch is a week old or whose next step is due today. Drafts only; the agent sends.
  4. 4 Lists conditions and closings due in the next three days, points to Finn’s overnight report, and closes with the three things to do before lunch. One screen, no more.

Marco

Market analyst

“Markets move slowly, then all at once. I watch the slow part.”

On every job

  1. 1 Every Monday, assembles the market pulse from public data: Bank of Canada, Statistics Canada, CMHC and the census, each figure with its as-of month and publisher.
  2. 2 Opens with the call in three sentences, compares it with what he reported last week from his own memory, and names a streak where there is one.
  3. 3 Names at most three things to watch, each tied to the release that will show it and the reading that would change the call.

Have a duty like one of these?

Bring it to a demo and we will sketch the team member: its playbook, the access it needs, and where the review sits.

Book a demo