Them AI for Consulting

Let the next engagement benefit from hard-earned judgment.

A previous proposal can show the estimate without explaining its assumptions. Them AI helps consulting teams discuss the reasoning, keep reviewed decisions, and reuse approved methods without treating every client detail as shared firm knowledge.

Mac-only for now. Free during the beta (invite-only).

Scope reviewShared room
You with your team

What should we clarify before estimating this migration?

Them AI with company context

Confirm ownership of data mapping, acceptance sign-off, and rollback before estimating. The delivery lead needs a named owner and evidence for each dependency, plus a clear list of assumptions still awaiting agreement.

↗ Illustrative scoping review
Review with Delivery lead
After human approvalScope assumptions and open questions

A useful record for the next person.

Illustrative workflow. Not a live conversation.

The work gets better when the context stays.

Good judgment belongs
with the whole team.

01

Make assumptions visible

Keep the conditions behind an estimate beside the recommendation itself.

02

Reuse the method

Separate transferable judgment from the client evidence that produced it.

03

Share reviewer context

Give a second delivery lead the sources needed to challenge a recommendation.

In the day-to-day

Work your team can bring to Them AI.

Start with the question. Keep the source. Make a person responsible for what comes next.

Consulting room Example 01

Which assumption could change this estimate?

Data mapping and acceptance sign-off remain unassigned. Confirm who supplies the mapping, who checks it, and when it is available before the delivery lead approves the estimate.

↗ Illustrative scope assumptions

Review the next scope

Bring approved general precedents into a scoping discussion. Compare assumptions, ownership, and exclusions before drafting an estimate, and name the person responsible for resolving remaining uncertainty.

See how the workflow fits
Bring
Authorized scoping precedents
Review
Delivery lead checks assumptions
Keep
Reviewed scope questions
Consulting room Example 02

What can another engagement reuse?

Reuse the questions about dependency ownership, acceptance evidence, and rollback readiness. Remove supplier names, prices, and project details, then ask the practice lead to approve the general checklist.

↗ Illustrative method review

Separate method from client detail

After a delivery review, propose a general checklist using neutral examples. Have an authorized reviewer decide what can become firm knowledge and what must remain outside it.

See how the workflow fits
Bring
Approved non-sensitive lessons
Review
Practice lead checks sharing authority
Keep
Reviewed general delivery skill
Consulting room Example 03

When would we choose a different approach?

Revisit the phased migration if the customer cannot support parallel operation or provide a rollback window. Keep those constraints beside the recommendation for the technical review.

↗ Illustrative technical review

Give a recommendation a second reading

Ask another consultant to check a technical recommendation against its sources. Capture disagreements and exceptions so the final record explains both the chosen approach and its limits.

See how the workflow fits
Bring
Recommendation and supporting evidence
Review
Technical reviewer resolves contradictions
Keep
Sourced recommendation with limits
Consulting room Example 04

What still needs a decision?

The migration approach is approved, but acceptance criteria still need the customer's sign-off. The incoming delivery lead owns that follow-up; keep it separate from the settled technical decision.

↗ Illustrative delivery handoff

Hand over the open judgments

Prepare an internal handoff that distinguishes decisions, assumptions, and unanswered questions. The incoming lead checks the evidence and accepts ownership of the items that still need judgment.

See how the workflow fits
Bring
Authorized delivery handoff notes
Review
Incoming lead checks responsibilities
Keep
Reviewed handoff record

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

The conversation is
only the beginning.

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 Collective
  1. 01

    Bring the context

    Illustrative scoping review

  2. 02

    Make the human call

    Delivery lead reviews the sources and proposed record.

  3. 03

    Keep the method

    Dependency ownership review

Make it real

Start with one recurring scope question

Choose a practice lead and a synthetic brief. Check whether a colleague can apply the reviewed method without reconstructing its origin. Mac-only for now. Free during the beta (invite-only).

Discuss a design partnership
Them AI product demonstration of people and agents working in a room
Product demonstration with illustrative people and data.

Before you begin

A few things
worth knowing.

Are client rooms private to their members?
No. Human access is organization-wide. Client-scoped MCP feeds include that client's approved records and approved firm-wide material. Import only material authorized for workspace members.
Will a successful project become a skill automatically?
Treat a proposed method as a draft. A person decides whether it generalizes and whether its contents may be shared.
Can we begin without client documents?
Yes. Test a synthetic engagement using approved general methods before deciding whether any client-specific material belongs in the workspace.
What does the current beta include?
Shared rooms, memory with sources and review status, reusable skills, and MCP access for connected agents. Mac-only for now. Free during the beta (invite-only). Human room and memory access is organization-wide. Client-scoped MCP feeds restrict agent retrieval to that client's approved records plus approved firm-wide material. Do not treat a room as a private boundary for individual members. Read the access boundaries.

Bring one real workflow

Make the next project
better informed than the last.

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).