A B2B SaaS company tied every blog post to pipeline in 9 days.

The company sells a client-portal platform to design and marketing agencies. Organic search is its largest acquisition channel: the blog drives 38% of all site sessions, and the team had been publishing three to four articles a week for five years. What nobody could do was connect an article to revenue. Search Console knew about clicks, GA4 knew about sessions, the product database knew about trials, and HubSpot knew about deals. The four never met.

The gaps were not just organizational. Roughly 27% of sessions arrived without analytics consent, UTM parameters had drifted across three CMS migrations, and trials were created in the product before anyone appeared in HubSpot. Every quarter, the growth team exported CSVs from four tools, stitched them in a spreadsheet that took a full week to assemble, and still ended up ranking articles by pageviews.

That ranking was quietly steering the editorial calendar toward traffic, not customers. Writers were rewarded for posts like “How to price retainers”, which brought 15,000 visits a month and almost no trials. Meanwhile the leadership team was preparing to cut a €260k content budget nobody could defend with numbers.

The team connected Search Console, GA4, a read replica of its Postgres product database and HubSpot in a single afternoon. Kimo profiled each source, detected that the users table already stored a first-touch landing path for signups, and proposed a join between that path and the GA4 page dimension. Where consent was missing, the model falls back to query-level estimates from Search Console, clearly flagged as modelled rather than observed.

On top of that join, the team built a single “Content → pipeline” model with five measures everyone agreed on in one meeting: organic clicks, trials, activated trials (three projects created within seven days), sales-qualified leads and pipeline value. Articles were grouped into clusters such as comparison pages, templates, guides and opinion, so the editorial team could reason about formats rather than individual URLs.

The growth lead now opens the week with Ask Kimo: “Which posts drove trials that became SQLs last quarter?” returns a ranked table with the SQL behind it. An alert fires when any article in the top 50 loses more than 20% of its clicks week over week, which turned content refreshes from a yearly project into a weekly habit.