GRUENCY  /  Quantitative research

Quantitative research
with a paper trail.

Econometrics, time-series analysis, Monte Carlo simulation and forecasting — the same methodology Sebastian published sole-author in Physica A (Elsevier) and applied at the National Bank of Poland, available for client problems that have to survive scrutiny.

A · Scope

What the practice takes on

  • 01Time-series and long-memory analysis — DFA, Hurst estimation, spectral methods
  • 02Monte Carlo simulation studies — estimator bias, variance, robustness
  • 03Forecasting models with honest uncertainty, not theatre
  • 04Methodology review and replication of existing analyses
  • 05Decision-support modelling for founders and research teams
  • 06Second opinions on models and data work — see Technical advisory
B · Method

How the work is delivered

  • 01Brief — the question, the data, the decision it feeds
  • 02Methodology and fixed scope agreed in writing before work starts
  • 03Analysis with reproducible code and explicit assumptions
  • 04Written findings plus a walkthrough call — argue with the reasoning, not a slide
Proof

Published,
awarded.

Elsevier / Physica A

Sole-author, peer-reviewed

Monte Carlo study reducing bias and variance in Detrended Fluctuation Analysis — used across econometrics, biomedical signals and climate research.

NBP — National Bank of Poland

First-degree award from Prof. Balcerowicz

Cash-circulation optimisation and economic modelling at Poland's central bank.

SGH / PWN

Rector's First-Degree Award

Contribution to Econometrics and Operations Research — PWN Polish Scientific Publishers.

FAQ

Asked before
engaging.

What fields do you take on?

Econometrics and finance-adjacent problems by background — and any domain with hard time-series, simulation or estimation questions by method.

Can the work support publication?

Yes — the methodology standard is the one Sebastian publishes under himself: reproducible code, explicit assumptions, written reasoning.

How does confidentiality work?

Standard NDA on request; findings and code belong to you. The practice trades on judgement, not on your data.

Contact

A problem worth
modelling.

Describe the question, the data and the decision behind it. Sebastian answers every enquiry personally — within two working days.

Prefer email? [email protected]