Skip to content

About

Tomasz Fordymacki

For over a decade I have led the financial analysis department of a large accounting firm. I make sure that at the negotiating table every number on our side has a source the other party can verify.

I lead a financial analysis team in a large accounting firm, and have done so for well over a decade. It is a place through which the books of several hundred companies pass every year, so I work with source data at a level where most advisers stop at a spreadsheet summary. Running a team taught me something else as well: an analysis that cannot be repeated without its author is worth half of what it appears to be.

I have run restructuring and fundraising projects worth many millions — from conversations with banks and investors, through debt service models, to schedules that had to be delivered week by week. In situations like these there is no room for a cautious “it depends”: either the number stands up in front of a credit committee or it does not.

I build management reporting and BI analytics: dashboards in which the board sees margin by client, by department and by project, instead of waiting a week for a summary. I work from source data — statements filed with the register, ledgers, time records — not from material prepared to support a thesis.

I am also responsible for the analytical side of advisory mandates: valuations, financial models, target screening and profitability analysis. I have built tools that read filings automatically — with them, comparing a dozen companies by one method takes weeks rather than a quarter, and the same number comes out the same way every time, regardless of who calculates it.

I have run valuations and profitability reviews for companies in IT, technical integration, professional services, retail and commercial property — including weekly cash models for businesses under liquidity pressure and segment accounts settling which business line funds which.

Tomasz Fordymacki — portrait

In brief

Based in
Warsaw
Experience
over a decade, including leading a team
Languages
Polish, English, French (B2)
Tools
Excel, Python, SQL, BI, React

About

What this experience rests on

Four things I have done long enough to know where projects like these go wrong.

  1. over adecade

    Leading a financial analysis department

    A team of analysts in a large accounting firm: a repeatable process, a document standard, quality control. That is where I learned that a written method is worth more than a remembered one.

  2. manymillions

    Restructuring and raising finance

    Projects run from conversations with banks and investors through to debt service schedules. A model meant to convince a credit committee has to survive the questions, not merely look good.

  3. reportingand BI

    Management reporting and BI analytics

    Dashboards and reports in which the board sees margin by client, department and project. One definition of a number for the whole organisation instead of three versions of the same truth.

  4. 3valuation methods

    Valuation and transaction analytics

    Valuations, financial models, target screening and the financial side of due diligence. Three methods calculated independently and reconciled into one number, with an explicit bridge to equity value.

What I hold to in this work

A number without a source is an opinion

If I cannot point to the row in the filing or the entry in the ledger that produces an amount, it is not the result of analysis but a guess. The other side has every right to check it.

Three documents, one number

The analysis, the valuation and the presentation of the same company have to say the same thing. A client who receives two contradictory documents is right to stop trusting both.

A rating without a narrative is useless

A score of “C, 66 points” tells the board nothing. Which module drags it down, for what reason, and which single number has to change — that is an answer.

An analysis has to outlive its author

If repeating the calculation requires my presence, it is not a method but a habit. Hence written procedures, checks built into the tool, and a register of mistakes already made.

What I work with

I choose the tool to fit the problem, not the other way round.

Excel

A model the client can open and recalculate. Still the best carrier for a valuation.

Python

Reading filings, generating documents, quality checks. Everything that has to happen more than once.

SQL and BI

Data from accounting and time systems, turned into dashboards the board reads without an interpreter.

React

Applications and tools where the audience is a team rather than one person with a file.

Have a concrete problem with the numbers?

Write two sentences about what it is. I will tell you whether it is my kind of work and roughly how long it takes.

Let’s talk

This site counts visits without cookies. With your consent I will also enable Google Analytics (a cookie for 2 years) to see which calculators and articles are read. Without consent nothing goes to Google. Details in the legal notice.