Setups

AgentSpot, with personal memory, shared company facts, and workflows he can see

François Lopitaux

François Lopitaux

SVP of Product Management at ThoughtSpot. He uses AgentSpot, the product his team is building, to prepare for customers and spot problems before they escalate.

Watch the clips

François builds agents around the work he already does. AgentSpot connects to the company’s tools, adds his personal context and shared company facts, and turns a conversation into a workflow he can inspect. The results arrive in his calendar, his inbox, or a customer visit plan.

How it fits together

The setup, line by line

Front door
AgentSpot, where he chats to create and change agents, workflows, and apps.
Personal memory
His role, preferences, time zone, and the people he meets. It is created and updated from conversations and connected tools.
Company memory
Shared, verified facts about product names, terminology, conventions, and acronyms, managed by admins. Automatic learning for company memory was not turned on in the demonstration.
Connected to
Google Calendar, Salesforce, Slack, Gong, product usage from Mixpanel, and customer story and marketing repositories.
Permissions
Each workflow runs with the credentials of the person using it. People can share an agent while keeping their own access to the underlying tools.
Structured data
ThoughtSpot semantic models help agents query company data. During the visit-planner demo, he reconnects the agent to a model and Salesforce when an older connection no longer works.
Who builds it
François describes the job in chat. AgentSpot builds the workflow and asks clarifying questions. He can inspect the steps, refine them through conversation, and schedule the result.

Personal context, shared company facts

His personal memory learns from conversations and connected tools. Company memory gives everyone the same starting context, including product names and terminology an outsider would not know.

Those company facts are managed by admins. Agents can be shared across the company, but when someone runs one, it uses that person’s credentials and permissions.

A workflow he can inspect and improve

François starts by describing the outcome. AgentSpot asks clarifying questions and builds a visible workflow. Each step can use a specialized agent, while the workflow gives the process a defined structure, including conditions and parallel steps.

He keeps refining it in conversation: add source links, make the email format consistent, scan only fresh Gong calls, and simplify slow Slack searches. Building the first version is the beginning; feedback makes it useful.

What he uses it for

Put the result where he will use it

The meeting briefing appears in a calendar event beside the customer meeting. François borrowed that placement from his assistant Monique’s process: the prep is already there when he opens the meeting, instead of buried in a message thread.

The briefing combines account details, previous conversations, internal chatter, company news, adoption metrics, and relevant customer stories approved to share. He estimates that doing this preparation by hand would take at least an hour per meeting.

What he is exploring next

At the time of the conversation, people could already share agents and company memory. His next focus was bringing more people and agents into the same conversation, so they could work together with the right context and permissions.

From my conversation with François, September 11, 2026.