The "before vs. after" of a demo recording
If you record demos every week — for prospects, training, or recap videos — this is the workflow change that pays for itself in week one.
Without RedactPro
1
Try to remember which tabs are openYou'll forget at least one
2
Manually edit the dashboard dataSlow, error-prone, breaks if you scroll
3
Record the demoSidebar still shows recently-viewed customers
4
Watch back, find leaks, re-recordOr worse — send it without watching back
5
Get an awkward email next week"You showed our metrics to another customer"
With RedactPro
1
Open your dashboardDon't bother editing data
2
Press Alt+Shift+EAuto-detects emails, IDs, IPs in 1 second
3
Click extra items if neededCustomer names, account balances, etc
4
Record the demoRedactions persist through scrolling, tab switches
5
Send the Loom and move onOne less thing to anxiety-check at midnight
What sales engineers redact, in practice
Five categories of "stuff visible in the dashboard that shouldn't be in the Loom" that we've seen most often.
Customer-identifying data
- Customer names visible in account headers
- Email addresses in the "recently viewed" sidebar
- Customer IDs and tenant slugs in URLs
- Domain names like "acme.com" in workspace dropdowns
- Subdomain naming hints ("globex-dev.app.example.com")
Financial & usage data
- Account balances and MRR figures
- Plan and seat counts visible in billing widgets
- Usage graphs on customer-specific accounts
- Invoice line items and PO numbers
- Card last-4s in payment method panels
Internal data
- Stripe / Salesforce admin URLs
- Internal Slack channel names in autocomplete
- Notion page names in browser history dropdown
- Internal tool URLs from previous tabs
Personal data
- Your own email and account name
- Calendar invites peeking through notifications
- Email previews in the corner of Gmail
- Personal task list items in side panels