Explain the why
Keep commercial reasoning beside the approved guidance.
Them AI for Sales
Give every seller a place to check what the company knows before the next conversation. Bring pricing rationale, objections, and handoff context into shared rooms, with sources and owners behind the answers your team reuses.
Mac-only for now. Free during the beta (invite-only).
Can we include onboarding in this offer?
Them AI with company contextOnboarding is scoped separately in the pricing policy. Confirm the delivery requirements with the services owner, then bring any proposed inclusion to the commercial reviewer as an exception.
↗ Example pricing policyA useful record for the next person.
Illustrative workflow. Not a live conversation.
The work gets better when the context stays.
Keep commercial reasoning beside the approved guidance.
Know who can clarify an ambiguous policy.
Give the next teammate more than notes.
In the day-to-day
Start with the question. Keep the source. Make a person responsible for what comes next.
What does the base offer include?
The base offer covers the documented service scope. Onboarding is separate. Explain that distinction first, then bring the proposed delivery requirements to the services owner for review.
↗ Example offer scopeStart with the policy behind an offer. Ask about scope, exclusions, and exception handling in a room, then let the responsible teammate review any interpretation before it reaches a prospect.
How should we discuss this limitation?
Describe the supported workflow first, then name the limitation plainly. The product brief makes no commitment to the requested capability; product owns the followup question.
↗ Example product briefTurn recurring buyer questions into answers with evidence. Keep the claim, its supporting source, and any qualification together so sellers can explain the product without extending promises beyond approved material.
What should we establish before proposing?
Establish the current process, the person responsible for the decision, and the constraint that matters most. The qualification guide uses those answers to shape the next conversation.
↗ Example qualification guideMake your qualification approach reusable without pretending every opportunity is alike. Store agreed questions and reasoning as a skill, then ask a teammate to assess the evidence and missing context.
What needs checking before delivery starts?
Separate agreed scope from unresolved assumptions. Confirm who owns onboarding, which commitments were approved, and what delivery still needs to establish before the receiving team accepts the handoff.
↗ Example handoff guideKeep the reasoning behind a commitment available after the deal conversation. Bring approved scope and open questions into a handoff room, then review what the receiving team actually needs next.
These are example workflows to evaluate, not customer results. Connected agents use their own tools; Them AI is the shared context and review workspace.
From useful work to reusable knowledge
Memory keeps the facts and decisions. Skills keep a way of working. People decide what deserves to become a shared reference.
Meet Rooms and the CollectiveExample pricing policy
Revenue operations reviews the sources and proposed record.
Offer review
Make it real
Bring one approved offer, its owner, and the questions sellers keep asking.
Discuss a design partnership
Before you begin
Bring one real workflow
Start with a question your team keeps answering. Bring the sources, the people who know, and the decisions worth keeping.
Mac-only for now. Free during the beta (invite-only).