Where this engagement started
For an F&B group running 13 outlets across prime mall locations, every outlet sent revenue and discount
data through email: a different format per outlet, a different cut-off rhythm, a different attachment
shape. The finance team rebuilt outlet performance manually each Monday. By the time the owner read
last week's outlet-level margin, suppliers had already repriced twice. The data was too old to act on.
The legacy automation platform the group had been running on did some of the work, but its annual cost
was eating most of the savings, and its economics did not scale with outlet count. Adding a 14th outlet
meant either another finance hire or another configuration that nobody on the team owned.
The brief was simple: rebuild the nightly reconciliation path so the owner could read outlet activity in
the morning, on yesterday's numbers, not last month's.
Phase 1: the nightly reconciliation path
The new system reads operator emails overnight. Per outlet, it picks up the revenue file and the
discount-by-department file, extracts the structured data, builds a three-period view of the day, and
drops a clean reconciled file into the finance team's workspace. By the time the team logs in, every
outlet has been read, structured, and output overnight without anyone watching it.
The operational win is simple: every outlet runs on the same template. Adding outlet 14 became a
configuration step, not a project. Adding outlets stopped meaning more headcount.
The owner's morning now starts on yesterday's data. Margin reactions happen on this week's prices. The
weekly close is a review, not a rebuild.
Phase 2: the system grew past the operator
Phase 1 set the foundation. The next workflow, supplier AP keyed straight into the accounting system,
was scoped from the start as a process the client's internal team would learn and run. The migration ran
while the team was learning the new toolchain, not after it. By the time the operator stepped back, the
team owned it.
Most operating improvements revert because the team was never trained on the new process. If the team
is not running it by the time the operator steps back, the work did not transfer. Phase 2 is the design
constraint made literal: build it so I can leave. Supplier AP into the accounting system is now a
hands-off process for the team. Adding vendors, running the workflow, handling the exceptions: the team
owns all of it. The system grew past me.
What this looks like for your outlets
Your finance team should not rebuild outlet numbers manually each week. Adding an outlet should not mean
hiring more finance staff. If you read margin two weeks late while suppliers reprice weekly, the nightly
reconciliation path is the first system to fix.
The first call tells you whether the architecture above fits your outlets, what the first 60 days would
cost, and whether your team learns to run it or I stay deep across systems is the right shape.
