Skip to content
Financial analytics with AI
Finance · 2025DuckDB · OpenAI · React · FastAPI

FinancialanalyticswithAI

We deployed an AI system that unified financial data from multiple sources, automated management reporting and accelerated CFO decision-making. Instead of stitching reports by hand, the team got a single analytical loop with dashboards, deviations and ready-made conclusions.

Brief

NovaCapital — a holding with 6 legal entities. The finance team spent a week on a monthly report. We plugged in an AI analyst: data assembles itself, conclusions write themselves, the CFO reads the brief and decides.

Context

The problem

Reports were assembled by hand from 1C, Excel and bank exports. A week of work for 3 analysts.

Risk

A mistake in a manual reconciliation = a mistake in the CFO's decision. Too expensive.

Goal

A daily CFO brief in 10 minutes. A weekly one in half an hour. With no manual work.

Before → After

Speed of financial decisions

Before launch
  • 3 analysts — a week per monthly report
  • Decisions made on week-old data
  • 7 fragmented data sources
  • Errors in manual reconciliation
6 weeks
After 5 weeks
  • +A report assembles in 30 minutes
  • +CFO gets the brief by 9 a.m.
  • +7 sources → one window
  • +The model catches anomalies, not people
Project timeline

Shipped in 5 weeks

From first call to first production launch. No phase two, no endless iterations.

Week 1—2

Discovery

Mapped 7 sources. Built a unified schema and a quality baseline.

Week 3

Design

CFO panel: one screen, one decision lane, drill-down to source.

Week 4

Build

Built the analyst agent, alerts and the nightly data rebuild.

Week 5

Launch

Shipped the daily CFO/board brief. Locked the target data-freshness SLA.

What we did

How we built it

01

Data layer

DuckDB on top of 1C, ERP, bank exports. One schema, daily rebuild.

02

Analyst agent

Reads the data, finds anomalies, builds forecasts, writes commentary in business language.

03

CFO panel

A dashboard with one lane of "what changed" and "what to do". No 40 charts.

04

Alerts

Plan deviations land in the CFO's messenger — with a proposed action, not just a number.

Daily brief

The CFO opens one page and knows: what changed, why, what to do.

01Day summary — key changes
02Drill-down — any metric to the source
03Forecast and action — the agent suggests the next step

Data layer and alerts

DuckDB on top of 1C, ERP, bank exports. One schema, a nightly rebuild, an SLA on data freshness. Alerts arrive with a proposed action, not just a number.

01DuckDB — one schema over 7 sources
02Nightly rebuild — the CFO gets a fresh brief in the morning
03Anomaly → CFO's Telegram → ready-to-act proposal
04Target data freshness ≤ 4 hours
Results

What came out

faster decisions

−82%

less time on report preparation

7

data sources in one system

5 weeks

to first launch

“The weekly report now takes half an hour. The board decides on fresh numbers, not week-old ones.”

Yuki Tanaka

CFO, NovaCapital

Project team
VK

Vitaly Kust

Tech

JP

James Park

AI

MG

Mariia Golikova

Design

Next case

AI-CRM for a dry-cleaning network

A CRM that calls clients, reminds, cross-sells and closes tickets on its own. Before — 3 operators. After — one operator plus an agent.

AI-CRM for a dry-cleaning network