We name what we cannot do yet

No testimonials yet

We have clients and are asking them for written reviews. We do not publish invented ones.

Instead: We take three companies into a discounted pilot — in exchange for the right to publish the results. Terms at the bottom of the page.

One case study, anonymised

It proves the stock report understates conversion. Sales growth after us is still being measured.

Instead: The stock “Sales analysis” on the same account shows 66% where the real conversion is 84%. Comparison

We do not count revenue growth

On the pilot only 10% of deals have a budget and the stock amounts are broken. We do not compute ROI out of thin air.

Instead: We show the fill rate of every field and say plainly where a breakdown cannot be built. On the pilot, deal budget is filled in for 10% of deals.

Not in the amoCRM marketplace yet

The listing is under review; amoCRM does not publish timelines.

Instead: The technical account was obtained on 26.08.2026; the public build passed the validator. Until it is published we install the widget as a private integration — together with you.

No automatic card payments

We issue the key manually within a business day and invoice your company.

Instead: We take crypto too — through support. How invoicing and closing documents work

No webhook receiver yet

Data freshness runs on a schedule: an incremental sync every five minutes.

Instead: Each incremental run, every 5 minutes, takes 12 seconds.

No permanent sync worker

The sync runs on a temporary setup.

Instead: We will add a service status page once the setup is permanent: we will not publish uptime backed by a laptop.

The trial is enabled manually

The trial itself exists — 14 days with no card, and the remaining time is shown in the “Licence” tab. What is missing is a “start trial” button and a counter in the account: support sets the end date at connection.

Instead: The second guarantee is financial: we refund the first paid month on request, and reports keep working for 3 days after the paid period ends.

Only one account for calibration

Thresholds tuned on a one-month export drifted on the full history of the same account: 7 stages were declared parking instead of 3.

Instead: The heuristic proposes, a person confirms. There will be no “developers usually…” here until there are more accounts. How we count

KLASTER Routing

Hands out leads by rule and answers “why does he have this deal” with a log entry.

in development

Developer module

Breaks the funnel down by development, building and unit instead of one overall total.

in development

Calls and activity reports

Who got through and what happened to the deal next — calls and messages next to the stages.

planned

Manager digest

A weekly funnel summary in Telegram: what changed and where it dropped.

planned

A source under every number

Account, period and method — as a footnote, like in this section. Estimates are marked separately from measurements so they cannot be confused.

A review of our own mistake

We published how our own markup went wrong on the full history and what it cost in percentage points. Read the review

One language of labels

The labels “live”, “in development” and “estimate” are the same on the site and inside the purchased product. What you bought does not start sounding more upbeat than the storefront.