Moving off Walnut: What changes when video generation becomes automatic

Walnut’s sandbox demos, deeply integrated with Salesforce and tuned for presales workflows, serve sales engineering teams well. This isn’t really about “moving off” Walnut in the sense of replacing it, presales teams with that specific need should keep using it. This is about a different, genuinely separate content need that often emerges elsewhere in the same organization: narrated video generated directly from existing documentation, for training, onboarding, and procedural content that has nothing to do with sandbox demos or CRM personalization.

The Pattern That Signals It’s Time

The clearest signal isn’t dissatisfaction with Walnut for presales, which remains genuinely well-suited to that specific workflow. It’s a recognition that other parts of the organization, Learning and Development, Knowledge Management, Human Resources, have content needs that a sandbox-and-CRM-focused platform was never built to address, and those needs have been going unaddressed or handled through an ad hoc process because the organization’s primary video-adjacent tool investment has been in a presales-specific platform.

What This Doesn’t Mean

Recognizing this pattern doesn’t mean Walnut was the wrong investment for presales. It remains a strong, purpose-built tool for exactly that function. The realization here is organizational rather than a critique of any single tool: different functions within the same company often have genuinely different content needs, and a tool that serves one function excellently doesn’t automatically serve every other function’s needs too.

What a Document-Aware Addition Looks Like

Identify which functions have unaddressed content needs. Training, onboarding, and documentation content that has nothing to do with presales sandbox demos is the clearest starting point.

Confirm existing written documentation as the source. SOPs, policies, training scripts, this becomes the material a document-aware tool generates from directly.

Keep Walnut entirely intact for presales. This addition doesn’t touch or replace the sandbox demo workflow sales engineering relies on.

Introduce the new tool to the specific team that needs it. Learning and Development or Knowledge Management, not sales engineering, typically owns this addition.

Why This Gap Often Goes Unnoticed for a While

A presales team’s Walnut investment is highly visible, since it directly supports revenue-generating sales activity that leadership tracks closely. A gap in training or documentation tooling elsewhere in the organization, by contrast, often persists quietly, handled through informal workarounds, a shared folder of screen recordings, ad hoc written guides, without ever triggering the same level of attention a revenue-facing tool gap would. This asymmetry in visibility is exactly why the training and documentation gap can persist for a surprisingly long time even in an organization that’s otherwise well-resourced on the sales tooling side, simply because nobody with sufficient visibility into both functions has connected the dots between the two separate, unaddressed needs.

What Changes Once You Make This Addition

The most immediate change is that a previously unaddressed content need finally gets a properly-suited tool. Training and documentation content that may have been handled informally, through a general-purpose recording tool or not produced as video at all, now generates directly from existing written material with narrated, paced guidance. Walnut continues serving presales exactly as before, entirely unaffected by this separate addition elsewhere in the organization.

Building the Case Internally for This Addition

If you’re identifying this gap and proposing a fix, the case is usually strongest when framed around a specific, concrete pain point already being felt, new hires taking longer than they should to ramp up because onboarding relies on informal, inconsistent materials, or a growing SOP library that nobody has found time to convert into a more engaging, retainable format. Pointing to Walnut’s clear, well-justified investment in presales as a useful reference point, this is the kind of purpose-built tooling investment training and documentation deserve too, tends to help stakeholders understand the request by analogy to something they already recognize as valuable, rather than needing to evaluate an entirely unfamiliar category of need from scratch.

What Organizations Typically Discover After Making This Addition

Organizations that address this gap often find that once training and documentation content has a properly-suited tool, adoption grows faster than initially anticipated, since teams that previously worked around the gap informally, HR building onboarding materials manually, engineering writing SOPs that never got converted into more accessible formats, quickly recognize the value once a genuinely well-fitted tool becomes available. This tends to surface additional latent content needs that hadn’t been explicitly identified as a gap before, simply because no reasonable tool existed to address them, which is a common pattern whenever an organization finally closes a long-standing tooling gap that multiple teams had been separately, quietly working around.

A Practical Starting Point for This Addition

Rather than attempting to address every unaddressed content need across the organization simultaneously, identify the single function with the clearest, most acute gap, often Learning and Development or Knowledge Management, and pilot a document-aware tool there first. Convert a handful of high-priority pieces of content, an onboarding sequence, a frequently-referenced SOP, and use the concrete result to build the case for extending the same capability to other functions facing similar, previously unaddressed gaps. This targeted starting point delivers visible value quickly, which tends to build more momentum for broader adoption than attempting a comprehensive, organization-wide rollout before any single team has demonstrated the approach working well in practice.

A Final Note on Keeping Tool Investments Aligned With Actual Needs

The broader lesson worth taking from this specific situation extends beyond just Walnut and training content: any organization that’s invested well in a purpose-built tool for one function should periodically check whether other functions have equally real, if less visible, needs that remain unaddressed simply because no one has evaluated tooling specifically for them. A presales team’s Walnut investment being well-justified doesn’t mean the organization’s video and content tooling needs are fully covered, and treating each function’s needs as worth its own dedicated evaluation, rather than assuming one successful tool investment implies broad coverage, tends to surface these gaps before they persist for years as informal workarounds.

Where to Start This Conversation Internally

If you’re the one recognizing this gap, the most effective first step is often a brief, informal conversation with whoever owns Learning and Development or Knowledge Management, simply asking how they currently handle training and documentation content and whether they’ve felt a gap in tooling for it. This conversation frequently surfaces a need that’s been quietly present but never formally raised, since the team experiencing the gap may not have realized a purpose-built solution exists, or may have assumed addressing it wasn’t a priority given other, more visible tooling investments elsewhere in the organization. A short conversation like this costs little and often reveals whether this addition is worth pursuing further.

Frequently Asked Questions

Does moving off Walnut mean abandoning presales sandbox demos entirely?

Not necessarily, and not for the presales use case itself. This is specifically about teams needing training or documentation content that falls outside what a sandbox demo platform was built for.

What’s the clearest sign it’s time to add a document-aware tool?

A pattern where your organization needs narrated training, onboarding, or SOP content, needs that a sandbox-and-CRM-focused platform like Walnut was never built to address.

Should presales teams stop using Walnut if the organization adds this?

No. Presales and sales engineering should continue using Walnut for exactly what it’s built for, sandbox demos tied to CRM data. This addition serves a genuinely different function elsewhere in the organization.

Does this addition require different skills on the team?

Not substantially. A document-aware tool generates from written material most teams already produce, an SOP, a policy, a training script, without requiring sandbox setup.

How do we know which content needs this new capability?

Training, onboarding, and documentation content that doesn’t need CRM personalization or a controlled sandbox environment is the clearest fit.

What’s a realistic timeline for adding this capability?

Most organizations can add a document-aware tool for training and documentation content immediately, without touching or disrupting their existing Walnut-based presales workflow.

See Document-Aware Video for Your Training and Documentation Needs

For content outside the presales demo use case, generating directly from existing documentation addresses a genuinely different, often unaddressed need. See how Velo handles this.

Try Velo for free · See how it works

Related reading

• Velo vs Walnut: Which tool keeps video content current without manual re-work?
• Moving off Navattic: What changes when video generation becomes automatic
• Moving off Reprise: What changes when video generation becomes automatic
• Video template library for HR, L&D, and Compliance teams

---

About the author

Ritu Parakh is Growth Lead at Velo, the AI video messaging platform that turns a screen recording, a deck, or a URL into a polished, narrated video - and an editable written doc. She writes about video for demos, onboarding, training, and enablement. Connect on LinkedIn