Deal.ee runs a company-data platform from roadmap to invoice in one system

The platform

Deal.ee publishes the Estonian Business Register in a form people can actually use: every company and the people connected to it, annual reports, quarterly tax figures, sector rankings and risk lists. On top of the data sits a marketplace where Estonian companies list their services, jobs, products, real estate and events.

That is a lot of moving parts for a small team. New features ship every few weeks, the data pipeline runs every night, and the platform sells paid plans and listing promotions. Since May 2026, the business side of all of it runs on ERPFlow: projects, expenses and sales invoices.

Work is organised as projects

Deal.ee ships in releases. Recent ones added a jobs board, public CV profiles, an events marketplace and paid listing promotions. In ERPFlow the work is organised as projects, so what is being built, by when, and what went into it sit in one place instead of being scattered across chat threads and notes.

When something ships, the record of it is already there. When the next thing is planned, the last one is right there to learn from.

Running costs are on the books as they happen

A data platform has steady running costs: hosting, storage, the payment provider's fees and the services around them. Deal.ee records them as expenses in ERPFlow as they come in, so the month's spending is never a pile of unsorted documents waiting for the end of the year.

Most of those costs arrive as PDF bills. Deal.ee hands each one to Claude, which is connected to ERPFlow through MCP; it reads the bill and files it as an expense with the supplier, date, amounts and category filled in, so nobody types the bills in by hand.

The question every small platform asks — what does it actually cost to keep this running? — has an answer at any time.

Sales invoices without a spreadsheet

Deal.ee issues sales invoices from ERPFlow. The customer, the lines, Estonian VAT and the numbering are all handled there, and each invoice's status shows whether it has been paid. No invoice template kept in a spreadsheet, and no guessing which number comes next.

Next: from a company list to the pipeline

Deal.ee's company lists — new companies, sector rankings, risk lists — already download as CSV files, with the header row in English whatever language the site is in, so an import set up once keeps working. ERPFlow's lead import reads that file today: each column is mapped to a lead field, and every company on the list becomes a new lead.

The next step is a direct integration. Deal.ee plans to send a list straight to ERPFlow without a file in between, and to enrich leads already in ERPFlow with what the register knows about the company — so finding prospects on Deal.ee and working them in ERPFlow becomes one motion.

Why this loop matters

Projects, expenses and invoices in one system close the loop a small product team usually leaves open: what is being built, what the platform spends, and what it has invoiced. With the business side handled in one place, Deal.ee's team can spend its time where it matters most — on the data and the product.