Question 1

What is Vittna?

Accepted Answer

Vittna is the layer where two kinds of urgency find each other. On the buy side, specialists building account arcs hit technology gaps, problems their customers have that none of their current vendors can solve. On the sell side, technology vendors, particularly early-stage ones entering a new region, have solutions that haven’t yet reached the right conversations. Vittna’s MCP server connects these two: when a specialist’s agent queries for something that matches a vendor’s connected knowledge base, both sides get signal. The specialist gets intelligence. The vendor gets a pre-pipeline intent signal attributed to the right partner. No cold calls. No 18-month wait.

Question 2

What is an account arc?

Accepted Answer

An account arc is a structured intelligence record of a customer relationship: their technology stack, purchase history, open projects, identified gaps, and emerging opportunities. Sales specialists build these inside AI agent sessions like Cowork, ingesting years of email, bids, quotes, and meeting notes. When the agent identifies a gap, it queries Vittna for vendor intelligence that addresses it.

Question 3

What is an intent signal?

Accepted Answer

An intent signal is generated every time a specialist’s account arc query matches a vendor’s connected knowledge base. The vendor sees the signal, the problem category, the sector, the originating partner, without seeing the buyer’s identity. It fires when a practitioner with a real customer opportunity is actively querying for a solution in your category. Not when someone visits a review site.

Question 4

What data actually travels to Vittna?

Accepted Answer

Less than you might expect, on both sides. A specialist’s company data never leaves their own environment. What their agent sends to Vittna is a query context: a structured description of the gap being researched, not the underlying customer data behind it. On the vendor side, their knowledge base stays in their own infrastructure. Vittna’s MCP server routes queries to it and returns authorised responses. It does not copy or store the content. Buyer identity is never exposed to vendors.