Vantaa Tax, day 1: Day 1: the first three fixes, drafted for the company

Vantaa Tax, day 1 of 30

The whole run: day 0 record, plan and log. Live

Delivery lead: Priya Nair, Management Consultant.

Day 1 of 30, 20 Oct 2026

Day 1: the first three fixes, drafted for the company

Day 1 of 30. The plan on this page names three fixes, and today we drafted each one for Vantaa Tax to approve.

Fix 1, the g2.com sales tax and VAT compliance category page the answers cite on the comparison question: we drafted the profile description, from the company's own words.
Fix 2, the taxcloud.com guide the answers cite on the quick setup question: we drafted a note to its editor for the company to send.
Fix 3, the buyer checklist question answered on the company's own profile, instagram.com/vantaa_tax: we drafted a five point post.

Nothing has gone live yet. Each draft goes to the company first, and each one appears here with its link once it is live. The company's website is not yet on file, so no website change is in this plan; website fixes start once it is.

Nothing in this entry changes a day 0 number. The day 30 measurement uses the same ten questions on ChatGPT, Claude, Perplexity, Google AI Overviews and Google AI Mode, three runs.

What we changed

Profile description for the G2 category page. Where: g2.com sales tax and VAT compliance category. By: our team. Drafted.
Note to the guide editor. Where: taxcloud.com sales tax compliance software guide. By: our team. Drafted.
Five point answer post. Where: instagram.com/vantaa_tax. By: our team. Drafted.

What is next

Send each draft to Vantaa Tax for approval.
Report each fix here with its link once it is live.

At day 30 we schedule the same ten buyer questions on ChatGPT, Claude, Perplexity, Google AI Overviews and Google AI Mode, three runs, 150 planned observations, under method v1.1. The three measured rates are named count, cited-as-a-source count and record accuracy. Named and cited counts compare the same question, engine and run cells answered in both measurements; a cell lost on either side is excluded from both. An increase in either measured count passes; a tie does not. Record accuracy compares wrong or stale totals only when reviewed statement sets from one existing Sprint link to the same company and both measurements; only statements within the common cells count. A lower reviewed total passes. If no measured rate passes and those reviewed sets are unavailable, the result stays in review. The common valid base, exclusions and receipts are reported separately.

See the Vantaa Tax run