Staff contributor - Feb 13, 2026


I thought I had a knowledge system.
In reality, I had a graveyard.

Decks in Drive. “Important” Slack threads. Client context buried in Gmail. Notes across Notion and Apple Notes. Every new project started with the same thought: I’ve solved this before. Then I’d spend 45 minutes trying to find it.

That changed when I ran my first “Dump your knowledge day” in Qiri.

The real problem: experience that doesn’t compound
I’ve spent the last decade in B2B SaaS product and GTM. I’m the person people DM about positioning, packaging, and pricing. I didn’t lack content. I lacked leverage.

Before Qiri:
🔹 Every new project started from a blank page
🔹 The same pricing questions came up again and again
🔹 My best thinking was locked in specific decks, emails, and client contexts
🔹 I had no way to see how my thinking had evolved

I didn’t need another note-taking app. I needed a living, searchable twin of my own brain.

The idea: Dump your knowledge day
Instead of organizing everything, I picked one domain: B2B SaaS pricing and packaging.

My goal was simple: If someone talks to my pricing twin, they should get 80% of the value of a real call with me. The constraint created clarity. If a document didn’t help explain how I think about pricing, it could wait.

Step 1: Set intent before uploading anything
I wrote two lines inside Qiri: “This twin is for B2B SaaS pricing and packaging.” and “It should explain my real pricing process, with examples.” That filter made every decision easier.

Step 2: Gather raw material fast
‍For the first hour, I just collected:
🔹Client pricing decks
🔹Internal memos on pricing changes
🔹Workshop notes
🔹Long founder emails
🔹Slack threads explaining trade-offs
🔹LinkedIn posts and talk outlines

No sorting. Just one “Knowledge” folder.

Step 3: Curate for signal, not volume
‍Before uploading, I asked:
‍
1. Is this still how I think?
2. Am I comfortable reusing this logic?
3. Does it show my process, not just the answer?

Only “yes” made it in. I also marked a few thought leadership pieces:
‍
🔹“How I think about pricing new modules”
🔹“Playbook: moving from per-seat to usage-based”
🔹“When not to change pricing”

These became the backbone of my twin.

Step 4: Organize by outcome, not folders
‍Inside Qiri, I didn’t recreate my file system. I created an outcome-based collection I call my QBrain:
‍
🔹Pricing philosophy
🔹New product pricing process
🔹Pricing change rollouts
🔹Mistakes and anti-patterns
🔹Examples and case studies

For messy documents, I added short context notes so rough ideas wouldn’t outweigh solid principles.

Step 5: Add what only lived in my head
This mattered more than I expected. I wrote down:

🔹My four pricing levers
🔹The 5 to 6 questions I always ask before suggesting a pricing change
🔹My “no-go” moves
🔹A churn vs pricing diagnostic checklist

Short. Direct. In my voice.

Now Qiri had my artifacts and my decision rules.

Step 6: Stress-test the twin
I asked it real questions:
‍
"How would you price a new add-on module?"
"What pricing mistakes do early-stage SaaS companies make?"
"How do I communicate a price increase?"
"When should you move from seat-based to usage-based?"
‍
The responses sounded like me. They referenced my decks and memos. When answers were generic, I improved the source:

🔹Added a missing rule of thumb
🔹Uploaded a better example
🔹Refined a framework
‍
By the end of the day, I hadn’t just built a twin. I had sharpened my own thinking.

What changed after?
Qiri became part of my workflow.

🔹Before client calls
I ask: “How did I price similar products before?” and get summaries with links.

🔹After calls
I drop notes straight into the pricing collections so the twin stays current.

🔹When drafting pricing docs
Qiri generates an outline based on my frameworks. The first draft comes from my own history, not a generic template.

🔹For mentoring
When a junior PM asks about pricing a feature, I send them to my twin first, then we discuss.

I’m not replacing myself.
I’m just not repeating myself.

Turning this into a repeatable challenge
You can run this monthly:

1. Pick a theme. Pricing. GTM. Onboarding.
2. Share a before and after story like this.
3. Provide the same checklist as a one-pager or in-app flow.
4. Show real queries and what they unlock.
5. Invite participants to share their own results.

This isn’t about AI hype. It’s about compounding expertise. Dump your knowledge day works because it turns everything you’ve already learned into something you can actually use.