Hello everyone,
I’ve been tasked with overseeing the rollout and adoption of Claw (the customer data platform) for our marketing team, and I’m currently deep in the planning phase for our internal training materials. As we all know, Claw comes with a fairly extensive set of built-in tutorials and a knowledge base directly within the platform. However, our IT and enablement teams have a strong preference for building out a custom internal wiki (using our existing Confluence instance) with tailored guides, screenshots from our own account, and specific use cases.
Before I commit significant resources to building a parallel wiki, I’m trying to gather some real-world data on what actually gets used. I have a natural inclination to want to document everything ourselves for control and specificity, but I’m worried about creating redundant resources that will just confuse the team or, worse, go completely unused.
Could those of you who have gone through a similar rollout share your experiences? I’m particularly interested in the concrete details of what worked and what didn’t.
* **Which resource did your team gravitate towards for day-to-day “how do I…” questions?** Was it the in-app tutorials, or an external wiki/guide?
* **If you built a custom wiki, what specific content formats were most valuable?** For example:
* Step-by-step guides for our exact campaign structures?
* Annotated screenshots of our specific segment definitions?
* Troubleshooting flows for common sync issues we encounter?
* **Did you find the built-in tutorials lacked critical context for your specific business logic or data model?** Or were they sufficient for the core platform mechanics?
* **How did you handle the maintenance burden?** When Claw releases a new feature or UI change, do you update both the internal wiki *and* direct the team to the updated official tutorials?
My primary concerns are adoption and accuracy. I want to avoid a situation where our wiki is beautifully detailed but immediately outdated, or where the team finds the official tutorials too generic and gives up. Any insights on your change management approach, how you introduced these resources during training, and any early-warning metrics you tracked (like support ticket volume for basic how-to questions) would be incredibly helpful.
Thank you in advance for sharing your detailed experiences.
~Heidi
I'm a marketing ops lead at a 300-person SaaS company. We've had Claw in production for about 18 months, managing all customer segmentation and campaign triggers.
* **Adoption reality:** Our team uses the Claw tutorials for the first 2-3 weeks, then permanently switches to our wiki. Logs show wiki page views are 10x higher than clicks on Claw's "Learn" pane after the onboarding period.
* **Update latency:** Claw's tutorials lag behind major UI updates by 3-6 months. When they changed their journey builder last fall, our wiki had corrected screenshots live the same week.
* **Search and context:** Confluence search wins because we title pages with our internal jargon ("How to build the Q3 nurture list") vs. Claw's generic titles ("Creating a Segment"). Finding the specific field mapping for our Salesforce integration is impossible in their generic docs.
* **Maintenance burden:** The custom wiki requires about 4-5 hours a week from a power user to keep current. The hidden cost is making that person's time non-negotiable; if they leave, the wiki rots in 90 days.
You should build the custom wiki, but only if you can dedicate a single owner from the power-user team to maintain it as part of their core responsibilities. If you can't guarantee that ongoing commitment, you're better off trying to force-feed the built-in tutorials despite their flaws.
-- bb