Internal system · In production

Management finance loop

The management finance loop of a trading company: cash flow, budget with variances, payment requests on an approval route, «Day summary», reconciliation and reference books. Built in one month by the company’s finance analyst and one engineer.

The pain

The numbers lived in ten spreadsheets, private chats and the heads of three people. When key people left, both access and context left with them.

Now

One source: cash flow, budget, payment requests, reconciliation and reference books in a single application with roles and permissions.

Effect across the steps

01 · From chaos to system: Pulled every financial number into one source with roles and permissions
02 · Transparent finances: Balance, profit and reconciliation are visible on one screen
05 · Faster processes: Reporting comes together in half an hour instead of weeks
06 · Freer resources: The finance analyst develops the system: 43 % of the changes are theirs

What the business gets

The real account balance is visible at any moment, not after exports are merged.
A payment request travels an approval route instead of getting lost in a chat.
Budget variances show up the moment they appear.
Growing the system no longer depends on hiring a developer.

From source to result

Bank statements
Cash-flow and budget reference books
Finance loop
Requests and approvals
Reporting and «Day summary»

Automated tests on calculations and approval routes stand between input and report: a number in the report cannot silently diverge from its source.

How it works

The production delivery pipeline was ready the day after the first commit: CI, tests and deployment to two environments existed before the domain part did.

The domain part is run by the finance analyst through Claude Code within a strict stack; code reaches production only through engineering review.

Who maintains it now

The company’s finance analyst. The engineer owns review, data, failures and the release to production.

Other cases for this step

Internal system · In production

Data platform

One source of truth instead of everyone’s own report

The pain: Every department exported marketplace data its own way, so meetings started with an argument about whose spreadsheet was right. Last year’s history did not exist at all.
Now: The platform collects data on a schedule and takes it through layers up to ready-made data marts. From there everyone - people, applications and agents - takes the numbers from the same marts.

Collection
Coverage
Replaced: manual exports in every department

The same system pays off across 2 more steps

Internal system · In production

IT infrastructure inventory

Services, access and owners - in one place

The pain: The inventory lived in a legacy panel and scattered notes: who is connected to what, what runs where, who owns it. When a person left, access and context left with them.
Now: One panel: a service tree, the «who has access to what» matrix, keys and portals, tasks, problems, changes and an audit log. Login under your own account, sections visible by role.

Sections
Timeline
Replaced: a legacy panel of 35 tabs

Internal system · In production

Map of the legacy warehouse

What sits in the legacy database is now known

The pain: The legacy warehouse arrived as a black box: several databases, hundreds of tables and views, an OLAP cube, no description at all. Every question started with excavation.
Now: A reusable client, a CLI for queries and a data map rebuilt by one command: databases, tables, views, columns, with a map of the cube beside it. Plus a check that the data can be trusted.

Map coverage
Updating: the map is rebuilt by one command
Data check: cube freshness and cube-against-SQL reconciliation

Type: Internal system
Status: In production
Timeline: one month to a working system
Maintained by: a finance analyst
Replaced: ten spreadsheets and a chat thread

Next.jsReactTypeScriptPrismaPostgreSQLPlaywrightGitHub ActionsPM2