For PMs, researchers, GTM

Your strategy work doesn't compound.
It vanishes.

Three hours of pricing yesterday. A morning of competitive analysis last week. A quarter of customer research before that — all in agent sessions you can't reach.

Sapwood keeps it. Crafted artifacts the team can use, ambered sessions you can branch from, and agents you can interrogate weeks later for the why.

See the skills →

01 · The skills Beta

Strategy work, structured.

Sapwood ships skills that wrap the work you're already doing in Claude Code. Each one produces a crafted artifact — for the future call you can't predict: Future-you, the CEO who asks, and the new hire who'll inherit it.

/domain-research
Map a new domain you don't know yet. ICP boundaries, terminology, the players, the non-obvious adjacencies. You get a domain memo and the ambered session that wrote it.
/personas-distill
Synthesize personas from interview transcripts, support tickets, sales calls. You get a personas doc and the trail of evidence behind each one.
/comp-analyze
Run a structured competitive analysis. You get a battlecard the team can branch from, plus the ambered session that produced it.
/pricing-explore
Walk through pricing tradeoffs. You get a pricing memo with rejected alternatives preserved, and a session anyone can pick up.
/exec-brief
Compose an executive briefing from prior amber sessions in your tree. You get a polished brief and the trail of where each claim came from.

A skill is a markdown file. The magic isn't the skill — it's the infrastructure that captures, structures, and lets you come back.

02 · How it shows up

Branch in. No deck.

When the work is structured, sharing it is one paste. Drop a Sapwood URL in any thread and your teammate is in the session two clicks later — same agent, same context, same rejected directions visible in the conversation.

#pricing-launch

Amir 9:42 AM

ok the pricing investigation is wrapped — branch in:
https://sapwood.ai/a/4f2b6e7c

Sara 9:51 AM

Jess, ask this session about the SMB tier. The unit economics against the regional carve-outs are where it gets weird.

Jess 10:03 AM

walked through it with the agent. my deep-dive's here:
https://sapwood.ai/a/9a2c1f8b — let's align on the verdict.

Instead of flattening two weeks of work into a deck before anyone can engage with it, you let the team branch into the investigation.

03 · Ask the agent

The agent already knows how she thinks.

When your teammate finishes a hard piece of work with an agent, the agent didn't just produce output. It spent two hours being her interlocutor — modeling her priorities, her vocabulary, what she'd push back on, what she'd reject. That cognitive work shaped every response.

When you warm her session, you inherit it.

You can ask, in conversation:

“Why did we kill the free tier?”
“What did the customer interviews actually rule out?”
“Which competitive carve-outs did she rule against, and why?”

The agent answers as the stranger who spent the afternoon with her. Because that's what it is.

04 · The records save you

When the call comes, the work is there.

A session-end hook captures every productive Claude Code session into your team's tree, automatically. No “now go save it.” No “did anyone write this down.”

When the CEO asks for the pricing rationale by EOD. When the customer escalates and you need to know what we promised six weeks ago. When sales asks about the carve-outs you debated last quarter. The records are in your tree, ambered, searchable, branchable.

You don't have to remember to keep your strategy work. The system does it for you.

05 · The whole setup

Capture the wins you're already working for.

The agentic tools are good now. MCP integrations actually work. File context holds. The models are sharper than the consumer chat. Most PMs convert to Claude Code because of that, not because of Sapwood. We meet you there today — Codex, Cursor, and Gemini are coming.

But the wins from agentic work aren't automatic. The PMs who actually win aren't running more sessions — they're running opinionated combinations of tools that produce real signal. The skills bake those choices in: which sources to ask, which inputs to lean on, which artifacts to leave behind. You bring the work; Sapwood brings the opinions, captures the value, and makes it durable.

sap install
sap tap claude-code

That's it. Run /comp-analyze or /pricing-explore next time you're starting a strategy push. The wins you'd already be working for stick from there.

Stop losing the work that compounds.

Sapwood is in private development. We're onboarding PMs and strategy teams whose work is already happening inside agent sessions. Tell us about yours.

For engineers →