BOLTCAT OÜ — AI Apps and Artificial Intelligence Solutions BOLTCAT OÜ
A Tallinn office at three in the afternoon: a tall window, a brushed-aluminium counter, and a matte slate wall carrying a horizontal metal strip board.

Method and updates

Our method for checking AI claims

Trust comes from method. This page explains how BOLTCAT OÜ selects topics, verifies facts and keeps boltcat.ee useful for business and public-sector readers in Estonia. We write about documented activity, not rumours.

What we choose to cover

The board we keep our eyes on

We write about AI apps and artificial intelligence solutions with a clear operational description and an Estonian connection. Business tools must show a defined töövoog. Public systems must trace to an official source such as RIA.

Every entry below is a row we can stand behind with a source. What you cannot trace does not get a row.

Eight examples, one row each. That boundary keeps coverage concrete and lets a project manager compare options without guessing at what any of them actually does.

Sources we accept

Every sentence gets a source, or it stays out

Company pages and official registers come first. For public-sector items we rely on RIA listings and government service pages. When a fact lives in two places and they disagree, we say so rather than choosing the more convenient version.

For funding or program notes, such as Roleo's reported 2.9 million euro raise or KULG's place in a 2026 AI growth program, we stay with the reported wording and avoid adding dates or totals. If a fact cannot be traced, we leave it out until it can.

Company pages
Product descriptions, feature pages, visible release notes.
Official registers
RIA listings and government service pages for public-sector items.
Reported wording
Funding and program notes kept exactly as reported, without extra dates or totals.
A dim Estonian home office at night: a desk lamp lit over a laptop, a highlighted research paper and a pen.
A short review happens on paper and on screen at the same time. Every factual sentence is checked against the source that carries it.

Verification steps before publishing

Four passes, in this order

Nothing on boltcat.ee goes live until it has walked these four passes. It is a short walk, and it is the same walk every time.

  1. 01

    Does every factual sentence have a source?

    If a reviewer cannot find where a sentence came from, the sentence is rewritten or cut. A claim without a traceable origin does not survive this pass.

  2. 02

    Do names, places and roles match the official wording?

    Company names, town names and job titles are copied across exactly as the source writes them, including Estonian spelling and diacritics.

  3. 03

    Have we left out anything not supplied?

    No integrations, benchmarks, logos, compliance badges or uptime stats that were not supplied by a source. If a supplier did not publish it, we do not print it.

  4. 04

    Does a second reader agree?

    A second reader checks for absolute promises and superlatives, then signs it off. Only then does the page go live on boltcat.ee.

How we handle updates and corrections

We correct the text, not a footnote

AI products change quickly. We review pages on a rolling basis and revise when official sources change. Readers can send corrections to [email protected] with a link to the source. When we fix an error, we correct the text directly so future readers see the right version.

For time-sensitive program references, we keep wording careful rather than precise beyond what is verified. Where a funding figure or a program year sits outside what we can trace, we say so plainly instead of rounding it up to sound dated.

Corrections are the most useful thing a reader can send us. The clearer the source, the faster the row is fixed.

Plain language over prestige labels

Name the mechanism, not the badge

You will not find stacked labels on our pages. We name the mechanism: what it reads, what it drafts, who reviews, how errors are fixed. A row that says "reads incoming invoices and drafts a payable entry for a bookkeeper to approve" is more useful than three tiers of shimmering adjectives.

That choice keeps copy Ads-safe and readable, and it helps managers compare options without decoding slogans. It also means our pages look shorter than some competitors'. Specific beats impressive every time.

What it reads

The input the system actually touches: documents, messages, sensor readings, structured records.

What it drafts

The output that leaves the system and reaches a human desk with a decision to make.

Who reviews

The role that signs off, and how an error is found and fixed once it has been signed.

Limits of what we offer

What this page is not

It is fairer to say this up front than to leave a visitor guessing at the end of a scroll.

  • Not a vendor Boltcat.ee is an informational resource. We do not sell software and we do not broker deals between suppliers and buyers.
  • Not legal advice We do not provide legal advice on vastavus. For regulated decisions, consult qualified advisers and official guidance.
  • Not a live demo We do not run live demos that install software or collect extra data. Our calls to action stay exploratory: review a workflow description, read related guidance, request general information, talk to the team.
  • Not a quiet trap We do not publish invented testimonials, ratings or review quotes, and we do not create before-and-after claims. Nothing on the site blocks normal navigation with popups, auto-play audio or forced downloads.
A Tallinn municipal service hall in the late afternoon: a stone floor, an aluminium counter and two people at a service desk.
A public service counter in Tallinn. When a public system appears on this site, it traces back to the register that describes it.

Keeping content useful for Estonia

Written for readers in Estonia

We write in English, with Estonian terms where they aid clarity: tehisintellekt, automatiseerimine, andmehaldus, töövoog, klienditugi, dokumendihaldus, pilootprojekt, audiitor, vastavus, ettevõtte tarkvara, avalik sektor. A project manager in Tallinn should not have to translate a slogan to compare two tools.

Examples reference Tallinn, Laitse, Saue vald and Harju maakond where relevant. That local anchoring is deliberate. It keeps advice tied to where work happens, so a pilot described on this site matches a workflow someone actually runs here.

Tehisintellekt Automatiseerimine Andmehaldus Töövoog Dokumendihaldus Pilootprojekt Avalik sektor

What we will not publish

Lines we do not cross on this site

These are the rules behind the rows. They apply to every page on boltcat.ee, whether the visitor arrived from a search result or from a link inside a procurement note.

01

No invented social proof

No fabricated testimonials, ratings or review quotes, and no reviewer names we cannot stand behind.

02

No before-and-after claims

We do not stage outcome comparisons we cannot document. Where a supplier publishes one, we say whose comparison it is.

03

No navigation traps

No popups blocking navigation, no auto-play audio, no forced downloads. If a visitor wants to leave, they leave.

04

No hidden words

The words live in the HTML so readers and search tools see the same text. The business name appears plainly on every page.

Where to go next

Read the method, then the practice

The method above is the same whether you run a private workflow or a public service. What changes is the paperwork.

BOLTCAT OÜ

Kastani tee 6-1, Laitse küla,
Saue vald, Harju maakond, 76302, Estonia

Monday to Friday, 9:00–18:00

[email protected] +372 5619 3113