Draft: abaccounting.ee trial-ending email

Hi,

You set up ClearPost on abaccounting.ee on 31 July and switched the plugin off about forty minutes later, so you never saw anything it produced. If you have a minute, I would like to know what put you off.

One thing you did not get to see: the keyword research had already finished. It picked up what people are actually searching for in Estonian, including "aastaaruande esitamise kohustus", "aastaaruande hind" and "aastaaruande allkirjastamine". Deadline, pricing and signing questions like those are a reasonable way to reach the non-resident and e-resident clients your site is aimed at.

Your trial ends tomorrow morning. If you tell me what went wrong I will reset it and give you a fresh week to actually try it. If it is simply not for you, that is fine too and I will leave it there.

Either way I would rather hear the real reason than guess at it.

Christian

Verification behind every claim

"31 July ... about forty minutes later." Trial created_at 2026-07-31T07:00:02Z. Render log: 07:38:37 [reportPluginDeactivated] domain=abaccounting.ee can_activate=true plugins=21. That is 38 minutes. I wrote "switched off" not "removed" deliberately: can_activate=true means it is still installed, just deactivated.
"never saw anything it produced." content_calendar for site b835b14a has 0 rows. No posts were ever generated or delivered.
The Estonian keywords are real and quoted verbatim from site_keywords: 8 rows stored, all Estonian, all on annual-report themes. I picked the three without a stale year in them and left out "aastaaruande esitamise tähtaeg 2022".
"non-resident and e-resident clients" is their own positioning, from their site: "Mitteresidentide, e-residentide teenused". Their wizard target_audience says the same thing.
Trial expiry expires_at 2026-08-07T07:00:02Z. welcome_email_sent_at 07-31, reminder_email_sent_at 08-04. No winback has fired.

What I deliberately did not claim

No apology for a bug, because I could not prove one. The stored setup_error says "Unexpected end of JSON input", but the logs show the actual abort was "plugin is not active" at 07:42, four minutes after they deactivated it. On the evidence, setup aborted because the plugin was off, not the other way round. Saying "sorry, we broke it" would be inventing a cause.
No claim about Estonian SEO competition. My first pass said nobody in Estonian accounting writes about these topics. I have not checked that, so it is out.
No mention of Clarence. They used it twice, both answers landed in under 15 seconds. Nothing to apologise for and raising it invites confusion.

If you approve

The offer to "reset it and give you a fresh week" is a promise I have not pre-honoured. Extending means updating expires_at on the trial row, and re-running setup needs them to reactivate the plugin first, which only they can do. Tell me whether to extend now or only if they reply.