What We Shipped This Week

One of the things I keep coming back to with Arkweaver is that shipping the feature is only half the job.

The other half is making sure the people who need to know about it actually know, that Sales and Customer Success have something useful to work with, and that the context behind why the feature got built doesn’t disappear the second it launches.

A few things we shipped this week move us closer to that.

CFO View

Our CFO view: now you can identify, to the dollar, whether you have a product gap, you're building the wrong things, a marketing gap (people don't know about the things), or a sales gap (you're selling the things wrong).

Launch presentations

You can now create PowerPoint presentations directly from a feature in Arkweaver. Upload one of your existing decks, and Arkweaver uses that as the design foundation while building the presentation from what it already knows about the feature: what shipped, why it matters, who asked for it, customer quotes, screenshots and the problems it solves.

The part I care about most is that this isn’t just a fixed “launch deck” generator. You can change the prompt and ask for a one-slide sales battlecard, an enablement deck or something else entirely. The underlying context stays the same; the output can change depending on what the team actually needs.

That feels much closer to how this should work. Product ships something, and the materials around it should be generated from the same source of truth rather than recreated from scratch by every GTM team.

Close the Loop without stepping on a deal

We also made Close the Loop smarter.

The basic idea behind Close the Loop is straightforward: if a customer or prospect asked for something and you ship it, tell them. But automation gets dangerous when it ignores what your team is already doing.

You do not want an automated product email going out right after an AE had an important call, while a contract is being negotiated, or while a CSM is handling a sensitive issue.

Arkweaver now checks your CRM before sending that follow-up. You can tell it not to email a person, account or company if someone on your team has contacted them within the last 15, 30, 60 or 90 days.

It works with HubSpot, Salesforce and Attio.

The point is not to automate every interaction. It is to automate the things software is good at without getting in the way of the people who actually own the relationship.

Features can now be upgrades

Another thing we shipped this week is the concept of an upgrade.

This sounds small, but I think it matters a lot.

Products do not evolve as a flat list of unrelated features. You build something, customers use it, they ask for changes, and eventually you ship a better version. The new thing is connected to the old thing.

Arkweaver can now understand that relationship explicitly.

If a new feature is an upgrade of an older one, the customer evidence tied to the original feature can still matter. That history can help explain why the upgrade exists, who might care about it and what should go into the launch materials.

Over time, I think this kind of product lineage becomes important. You want to understand not just what exists today, but how the product got there and which customers influenced that path.

Faster feature search

And finally, we fixed something much more basic.

Arkweaver’s search was good at finding things that were conceptually similar, but weirdly bad when you already knew the actual name of the feature.

Now it combines semantic search with direct feature-name matching. If you type part of the feature name, the thing you are looking for should show up much faster.

Not a profound feature. Just one of those things that should work the way you expect it to.

The common thread across all of this is pretty simple: when Product ships something, the rest of the company should not have to reconstruct the story around it.

Arkweaver should already know what changed, why it mattered, who cared, what came before it and what should happen next.