Forward Deployed Operators
for Finance
A full-time HKR employee for the finance role you want to fill. On day 1, they do collections, reconciliation and close support by hand. By day 90, AI watches every payment and matches the clear ones, and they make the calls.


Who does the job.
For ten years and 900+ hires, we have placed people like Talida and Claudia inside client teams to do the job by hand. These interviews are from then. Forward Deployed Operators are the same people, trained to be fluent in AI.

From day 1 to day 90.
A Forward Deployed Operator joins your finance team, does the work, maps it, then runs the AI we build around it.

- Day 1
Give us the role.
Your Forward Deployed Operator joins full-time, inside your books, your banks and your Slack. They do collections, reconciliation and close support by hand, and they report to your finance lead.
- Day 30
The job is mapped. We build the AI.
The operator writes down every task as they do it: which wire clears which invoice, who chases what, which steps of the close repeat each month. We build the AI from that list, at no cost to you. By day 60, AI does the routine work and the operator checks and tunes it.
What the role covers.
Five parts of a finance job. A Forward Deployed Operator takes them on from day 1; AI takes over the routine by day 90.

01.
AR and collections
Who owes what, in one list. Every day of DSO is cash trapped on the balance sheet. The operator does the chasing and owns each follow-up until the invoice is paid.
02.
Payment reconciliation
Every incoming wire matched to the invoice it clears. Oldest invoice first when several match. Anything uncertain is flagged and reviewed by a person.
03.
Month-end close support
The operator runs the cutoff and the days up to the close. They read each bank statement as it arrives and give every number one owner.
04.
Expense audit
Every bill and expense checked each month against vendor history and the category list. Exceptions come back ranked, and a person decides each one.
05.
Treasury reporting
One cash view across every bank, entity and currency. Each balance shows its age: some refresh every working hour, others come from the bank’s daily statement. The question “how much do we have” gets one answer.
The AI your Forward Deployed Operator runs.
We ran it on ourselves first. Jamie is the finance agent that watches HKR’s three banks and its books every day, and Sebastian makes the calls. Here is the story, and the blueprints we built for it.

The mess
Finance lived in too many places at once.
For years our finance lived in too many places at once. Invoices in Zoho Books. Balances across three banks in four currencies. The rest in Google Sheets. Payments that fired and never got written down anywhere.
If I wanted a straight answer (how much do we have, who hasn’t paid) I had to go assemble it myself, from five places, hoping each one was current.
One set of numbers
Every report reads the same numbers.
Nobody at HKR copies numbers out of the books for a report anymore. Four times a day, Jamie copies the invoices, expenses, customers and payments from Zoho Books into one database, and every report reads from it.
When two of us ask what a client owes, we get the same number. Sebastian still keeps the books, and Jamie only reads them. Until September, the copy also posted what changed in Slack. This post is from 1 May, at 7:00 in the morning.
Zoho sync: 13 invoices, 0 expenses updated
Invoices:
- Waystar RoyCo — USD 18,400.00 (sent)
- GoJo — USD 9,750.00 (draft)
- Pierce Global Media — USD 12,200.00 (draft)
- Vaulter — USD 6,300.00 (draft)
- ATN — USD 24,600.00 (draft)
The showpiece
The bank that texts my phone.
Banca Transilvania gives us no live feed of company payments. It sends a text to my phone when money lands. So nobody at HKR checks that bank for payments anymore. The text goes to Jamie, and at the next hourly check Jamie reads it, finds the open invoices it clears and posts the match to Slack.
When one payment could clear more than one invoice, Jamie takes the oldest first. When the amount doesn’t match an invoice total, it says so and asks a person to confirm before anyone marks it paid.
📥 +$24,000.00 USD incoming into BT USD
Likely match (FIFO, partial): clears the two oldest unpaid invoices of this client in full, INV-000412 (Apr) and INV-000468 (May), leaving $4,500.00 toward INV-000523 (Jun).
Amount doesn’t match a clean invoice total; the client is a known partial payer. FIFO allocation above — confirm before marking paid in Zoho (mark-paid is manual).
The safety net
The thing I’d never give up.
Nobody at HKR re-reads the month’s bills for surprises anymore. On the 18th of each month, Jamie re-reads three months of expenses, so late bills count, and ranks what moved, with the reason. A cost category jumped: here is the line, here is by how much. Sebastian decides what each change means.
On the 5th and the 15th, Jamie lists every overdue invoice in Slack, and the whole team sees it. People do the chasing.
It’s the safety net I used to assume we had and didn’t.
🔍 Expense Audit — Mar 2026
Total: $148,320.00
MoM: -2.1% | YoY: +47.4%
🚨 Alerts:
- $6,840.00 — Living+ ([OpEx] Office) on 2026-03-20
⚠️ Warnings:
- Capital Expenditures up 145% MoM ($3,200.00 → $7,840.00)
The human
Sebastian still owns the work.
He runs invoicing, keeps the books honest and makes the judgment calls Jamie surfaces. Jamie does the watching and the matching. Sebastian does the deciding.
When a payment comes in, Jamie matches it and says how sure it is, but a person still marks it paid in Zoho Books. That is the one step we have not handed over yet.

Sebastian Popa
COO and General Counsel, HKR
- Runs invoicing and keeps the books honest.
- Confirms each match Jamie proposes.
- Marks each payment paid in Zoho Books.
- Makes the judgment calls.
The AI workflow blueprints.
Jamie does these eleven finance chores at HKR today. Open a card to see what Jamie does and what a person decides.
Checking the bank for payments
Incoming Wise transfers — HKR MEDIA SRL
- Waystar RoyCo — $18,400.00 USD — 2026-10-05 16:39 → likely INV-000692 (2026-09-01, $18,400.00, exact amount match)
- VAULTER LLC — $6,300.00 USD — 2026-10-05 16:40 → likely INV-000695 (2026-09-01, $6,300.00, exact amount match)
Likely matches only — mark-paid is manual.
Nobody at HKR checks the bank for new payments. Every hour from 7:00 to 20:00, the AI checks Wise and Banca Transilvania and tells the team who paid. A person still marks each payment paid.
Every hour from 7:00 to 20:00, the AI checks Wise for new incoming transfers. Banca Transilvania sends a text when money lands, and the AI reads those texts in the same pass. Each payment is checked against the open invoices.
The result goes to the team’s Slack channel: who paid, how much, and which invoices it clears. On Wise, a transfer between two HKR companies is named as an internal transfer and matched to no invoice. A person still marks each payment paid in Zoho Books.
Matching payments to invoices
We'll go FIFO, so INV-000689 stays open in full + $4.2k of INV-000688
Yes, FIFO works. The $24,600.00 payment on 2026-09-29 from ATN (ROYCO MEDIA on the wire) splits like this:
- INV-000641 (2026-08-10) — $4,180.00 — applied $4,180.00 — open after $0.00
- INV-000688 (2026-09-01) — $24,600.00 — applied $20,420.00 — open after $4,180.00
- INV-000689 (2026-09-01) — $2,950.00 — applied $0.00 — open after $2,950.00
- TOTAL — $31,730.00 — applied $24,600.00 — open after $7,130.00
Open after this payment: $7,130.00. That is $4,180.00 on INV-000688 and all of INV-000689.
… Record it in Zoho by hand, because I cannot mark invoices paid.
Nobody at HKR works out by hand which invoices a payment clears. The AI clears the oldest invoice first and asks a person about any amount that does not fit. A person marks each payment paid.
A payer’s name rarely matches the name on the invoice, and a partial payment rarely matches an invoice total. The AI keeps a copy of the open invoices, refreshed four times a day, and finds the client who sent each payment. When the payment could clear several invoices, the oldest goes first.
When the amount does not fit an invoice total, the AI shows how it would split the payment and asks a person to confirm. When it cannot tell who paid, it says so and leaves the payment for a person to place. A person marks each payment paid in Zoho Books.
Collecting balances bank by bank
Jamie, how much USD do we have (just USD as currency, don't aggregate/convert) and where do we hold it (which bank/provider)
USD holdings — HKR MEDIA SRL only (the other two entities show $0):
- Wise · Main — $186,420.35 — 2026-05-05 15:00
- Wise · Savings — $61,300.00 — 2026-05-05 15:00
- Revolut · Main — $9,812.60 — 2026-05-05 15:00
- BT · Main — $8,240.15 — 2026-05-05 12:00
- Payoneer · Main — $3,415.00 — 2026-04-07 (stale)
Total USD: $269,188.10
Nobody at HKR collects balances bank by bank. The AI refreshes Wise and Revolut each working hour, reads Banca Transilvania’s statement when it arrives each day, and shows the age of every balance. A person names the owner of any account it does not know.
HKR banks with Wise, Revolut and Banca Transilvania, across three companies and four currencies. Wise and Revolut balances refresh every working hour. Banca Transilvania sends one statement a day, and the AI reads it when it arrives. A few accounts are typed in by hand. Every balance shows how old it is, so nobody reads yesterday’s number as today’s.
Each account belongs to one HKR company. When the AI finds an account it does not know, it holds that account until a person names its owner. The question “how much do we have” gets one answer.
Copying numbers out of the books
Zoho sync: 3 invoices, 1 expenses updated
Invoices:
- Pierce Global Media — USD 12,200.00 (paid)
- Vaulter — USD 6,300.00 (paid)
- Vaulter — USD 2,150.00 (overdue)
Expenses:
- GoJo — USD 12.00 (Software)
Nobody at HKR copies numbers out of the books for a report. Four times a day, the AI copies invoices, expenses, customers and payments from Zoho Books, so every report reads the same numbers. People still keep the books and decide what goes in them.
HKR keeps its accounts in Zoho Books. Four times a day, the AI copies the new and changed invoices, expenses, customers and payments into one database. Reports read from that copy, so two people who ask the same question get the same number.
The copy only reads the books. Invoices, corrections and every other entry stay in Zoho Books, with the people who keep them.
Building the overdue list
🚨 4 Overdue Invoice(s)
- Pierce Global Media (INV-000581) — USD 12,200.00 — due 2026-07-20 (16d late)
- ATN (INV-000586) — USD 24,600.00 — due 2026-07-30 (6d late)
- Vaulter (INV-000587) — USD 6,300.00 — due 2026-07-30 (6d late)
- Waystar Studios (INV-000612) — USD 4,210.00 — due 2026-08-01 (4d late)
Note: ATN accounts for ≈52% of total overdue exposure ($24,600.00 of $47,310.00).
Nobody at HKR builds the overdue list by hand. On the 5th and the 15th, the AI shows the whole team every overdue invoice and how late it is. People do the chasing.
Twice a month, on the 5th and the 15th, the AI posts every invoice past its due date in the team’s Slack channel, with how many days late each one is. Everyone sees the same list on the same day.
The AI only lists. People decide who to chase, when and how, and a person records each payment when it arrives.
Reading every bill for surprises
🔍 Expense Audit — Aug 2026
🚨 Alerts:
- $7,240 — GoJo ([OpEx] Software) on 2026-08-23 — paid only 1/6 prior months (≈$12 when present)
- $4,940 — Brightstar (S&M) ([S&M] Protocol) on 2026-08-26 — paid only 2/6 prior months (≈$4,615 when present)
⚠️ Warnings:
- Sales and Marketing up 31% MoM ($9,420 → $12,340; YoY -21%) — driven by Protocol +$3,830, Affiliate Commissions -$910
Nobody at HKR reads every bill for surprises. On the 18th of each month, the AI checks each expense against what that vendor usually charges and lists what stands out, with the reason. A person decides what each one means.
A large bill tells you nothing until you know what that vendor usually charges. On the 18th of every month, the AI checks each expense in the books against the vendor’s own history: a single bill far above its usual size, a vendor that was not there in the last six months, a software tool that stopped charging.
The flags come back in Slack as one list, alerts first, then warnings, each with its reason. A person decides what each one means. The AI reads the books and never writes to them.
Re-reading past months for late bills
Trailing resync: 53 new expenses recovered from last 3 months
🔍 Expense Audit — Jun 2026
Total: $145,430
MoM: -2.2% | YoY: +9.3%
⚠️ Warnings:
- Sales and Marketing up 176% MoM ($6,068 → $16,747; YoY +143%) — driven by Protocol +$11,159, Personnel Costs -$480
- Protocol up 645% MoM ($1,730 → $12,889) — Brightstar (S&M) +$8,210 (new), Royco Parks (S&M) +$2,949 (new)
Nobody at HKR re-reads past months for bills that came in late. On the 18th, the AI fetches three months of expenses again, so late bills count, and ranks what moved, with the reason. A person decides what each change means.
A bill booked late changes a month that already looked finished. On the 18th of every month, the AI fetches the last three months of expenses again and scores them on nine checks: category swings, large single bills, capital spending that drifts, expenses without a category label and more.
The result lands in Slack: the total, the change month on month and year on year, and the lines that moved, each with its reason. A person decides what each change means. The AI reads the books and never writes to them.
Digging through records for answers
@Jamie how many days overdue was invoice INV-000527 at the time of the payment receipt (AUG 3rd)?
Payment #1207 ($24,600.00, matching INV-000527 exactly) landed 2026-08-03.
Due date on the invoice was 2026-06-30.
Days overdue at payment = 34 days (Jun 30 → Aug 3).
Nobody on HKR’s finance team digs through folders and the books for an answer. They ask the AI in Slack, and it answers from the company’s records: contracts, payments, spend and payroll rules. The person who asked decides what to do with the answer.
The finance team asks in Slack, in plain words: what a contract says, whether a client has paid, what we spend on a vendor, what a payroll rule allows. The AI looks it up in the books, the signed contracts and the company’s other records, and replies in the same thread.
Contracts come up most often, then payments, follow-up tasks, spend and payroll rules. The AI finds and reports. The person who asked decides what the answer means.
Matching payouts to people
Vendor↔employee reconcile — could not attribute these payments
COULD NOT MAP (employee/contractor-tagged vendors)
- Greg Hirsch — CTR — last paid 2026-08-31 — no employee match
- Willa Ferreyra — CTR — last paid 2026-08-31 — no employee match
Awaiting first payment — 4 hire(s) in the last 45 days with no vendor yet (benign, watching): …
Nobody at HKR ties salary and contractor payments to people by hand. Every week, the AI ties each payment to a person and lists the ones that do not tie. A person resolves each one on the list.
Every Monday, the AI goes through the salary and contractor payments in the books and ties each one to the person it paid, using the HR records.
A payment it cannot tie goes on a short list, and a person resolves each one. When every payment ties, no list is sent, so a list arrives only when there is work on it.
Searching folders for contracts
Do you have the contract with Stewy Hosseini (MSC)?
Yes. The vault has 3 documents with Stewy Hosseini's company.
The company is MCS Strategy SRL, which trades as Maesbury Capital. You wrote "MSC", but the legal name is "MCS".
All 3 files are in Legal/02 Vendors/Maesbury Capital (MCS Strategy SRL) - Stewy Hosseini/:
- MSA HKR _ Maesbury Capital.pdf — 01.03.2024 — Master Services Agreement
- SOW 1 Maesbury Capital _ HKR.pdf — 01.03.2024 — Marketing ops & strategy retainer
- SOW 2 Maesbury Capital (MCS ...).pdf — 15.09.2026 — SEO audit …
The record does not show: signed or unsigned status, expiry date, renewal terms or notice period.
Nobody at HKR searches folders for a signed contract. Every signed document is in one index, so “what did we sign with this client” is a question the AI answers. A person decides what the contract means.
Every day, the AI walks the folders where HKR files its signed documents and adds each new one to a single index, with who signed it and what kind of document it is.
So “what did we sign with this client” is one question in Slack, with no folder search. The AI finds the documents and says where they are. A person reads them and decides what they mean.
Rebuilding the forecast by hand
Rebuild the forecast from today's books and lay both cost-cut plans over it.
📈 Reforecast 22 — base rebuilt from the books as of 12 Oct; both plans laid over it
FY26 revenue $2,184,000 · expenses $1,792,000 · still to cut $96,400 Plan A / $41,800 Plan B
Report: Finance tab → Reforecast → report (run 22)
Nobody at HKR rebuilds the forecast by hand. On request, the AI rebuilds it from the books and lays cost-cut scenarios over it on one chart. A person picks the plan.
The forecast is rebuilt only when someone asks for it, from the books as they stand that day.
Cost-cut scenarios sit over the forecast on one chart, so each option is compared on the same numbers. The AI lays out the options. A person picks the plan.
Who does what.
Jamie watches the money. Sebastian makes the calls.
What Jamie (AI agent) does
- Checks for new payments every hour, from 7:00 to 20:00.
- Reads each payment and proposes the invoices it clears.
- Says when a match is uncertain, and asks a person to confirm.
- Audits every month’s expenses and ranks the exceptions.
What Sebastian decides
- Reviews each match and records the payment in Zoho Books.
- Runs invoicing and keeps the books honest.
- Takes every call with high stakes.
- Decides what the audit’s exceptions mean.
“Jamie took over most of the grinding I used to do in Zoho Books. I can finally finish more meaningful projects.”

