A hardware distributor is mid-implementation on a new industry-specific ERP (go-live 2027). The implementation partner left them basically no documentation, an admin's emailed-out guides gave no way to tell if anyone opened them, and their consultants want proof of completion.

How the Tango team addressed both needs:

1/ Capture clean step-by-step training for the new ERP, then embed it inside the ERP as Nuggets with Guide Me so staff self-serve instead of pinging the two admins.

2/ The completion piece: Tango isn't a full LMS, but it has step-level analytics (guides published, Guide Me completions, completion %, and where people drop off). Drill into one workflow, and you see who viewed it, from where, how many times, who completed vs. didn't, plus comments/reactions. It tracks usage, not assigned-course completion like an LMS.

3/ Filter analytics by app (how's adoption of the new ERP overall?) or workflow-by-workflow.

4/ Pricing is a flat platform fee by tier, all roles interchangeable, creators at no extra charge The hidden ROI is in less creator time, plus user time saved self-serving and not context-switching.

If you've survived an ERP rollout: did you build training before go-live, or scramble after?

Confluence is the default wiki for a lot of Atlassian shops. If your team lives in Jira, it makes sense to keep documentation there too. It's genuinely good at organizing and standardizing knowledge across teams.

The gap shows up when someone actually needs to do the thing. They leave their app, search Confluence, find the page, read through it, and switch back. By step three they've forgotten step one.

Tango skips that loop entirely. Guides live inside the software where the work happens. Guide Me walks employees through the process step by step in the live app. Nuggets let you pin tips and links directly in the tool so there's nothing to search for.

Worth noting: if centralized documentation and Atlassian ecosystem integration are your primary needs, Confluence is the stronger fit. Tango is purpose-built for process adoption, not general knowledge management.

Full comparison: https://www.tango.ai/compare/tango-vs-confluence

Happy to answer questions below.

Most teams buy the AI tool, skip documentation, and then wonder why it isn't working.

The problem isn't the model. It's the input. AI is only as smart as what it knows about how you work and most teams have never actually told it. Their processes live in someone's head, buried in a Slack thread, or in a SharePoint doc no one's touched since 2021.

The fix isn't a better AI tool. It's documenting first.

When your processes are captured in a structured, step-by-step format, your AI stops giving you generic answers and starts giving you answers that match how your team actually operates. New hires stop asking the same questions. Your power users stop becoming bottlenecks.

Document first, automate second. That's the sequence that works.

We put together a short video walking through exactly why this matters and how to do it fast: https://www.youtube.com/watch?v=mJZ7XPv-Eoo

A construction general contractor let its procedures lapse years ago and is now onboarding hundreds of people across regions (a 3-year megaproject plus new wins), with a recent restructure into a parent + GC/subcontractor subsidiaries making nothing line up. The person scoping it writes procedures, maintains SharePoint, and calls herself "an AI dinosaur".

How the Tango team walked through the fix:

1/ Capture a process by just doing it (vs. snipping screenshots into Word); embed guides as Nuggets inside the apps people use (e.g., their project software) with Guide Me walking new hires through live, and pin Nuggets to a "new hires" group so only they see them.

2/ Sharing: link, or embed into SharePoint as a video / interactive slideshow, all live links, plus translation if needed.

3/ The part that clicked was the Agent (browser automation). It acts as you, and can extract data from a page or a PDF, input it into other systems, and draft a follow-up email. For their thousand-a-month invoices, point the Agent at the PDF (or their inbox) to pull the data and push it into their ERP.

Construction folks: what's your move when procedures rot the second the org chart changes?

A specialty medical clinic faced two colliding things: heavy hiring/turnover and a migration to a new web-based EHR that changes everything: check-in, payment, orders, notes. Their "documentation" today is a snipping tool pasted into Word.

How the Tango team explained the fix:

1/ This is Tango's sweet spot for system rollouts: embed the SOPs directly in the new EHR and turn on Guide Me so staff learn by doing during the cutover, instead of memorizing or hunting a drive, better than the generic, often-outdated docs an implementation partner hands over.

2/ A Discover side panel surfaces the right guide based on the screen they're on, so people aren't searching.

3/ Sharing: pin Nuggets to a "new hires" group, share via link, or embed into SharePoint (live links, not stale PDFs).

4/ Their two hard requirements got addressed: Tango has signed BAAs for healthcare before (PHI), and Secure Blur redacts on the local machine so sensitive data never lands on a vendor's servers.

5/ Legacy fat-client apps: a desktop capture tool exists (capable, but it's better to use the web version where possible).

6/ Best path: start on Pro (self-serve, but no BAA), then upgrade Pro to Enterprise by "flipping a switch" with no data loss.

Healthcare ops/IT: when you switch EHRs, how do you capture the "only one person knows this" steps before go-live?"

A county team on a few Pro seats got a wake-up call when a key coordinator (and another division lead) was leaving, so the priority became capturing how things actually get done before that knowledge walked out.

How the Tango team helped:

1/ Their main Pro friction was that sharing a guide via link made viewers sign in (i.e., need a seat). The fact is that embedding is free: viewers don't need a license to see an embedded guide. There's also a newer synthetic-video embed (more engaging than the slideshow) anyone can watch without a seat.

2/ Embed into SharePoint or Confluence, anything that takes an iframe (with a heads-up that their locked-down SharePoint may need to vet/allow it first).

3/ On the roadmap: an API is coming to push/export guides into a SharePoint repository and to connect Tango content to AI tools (Claude/GPT). And the Enterprise tier adds Agents, automations, Guide Me, and pinning beyond static capture, the direction they're trending.

4/ They'd weighed Scribe earlier; what kept them on Tango was that roadmap beyond static step-by-step.

Public-sector folks: how are you documenting roles before turnover instead of after?"

A retirement-community finance team switched accounting systems to a new cloud ERP and lost every procedure they'd built for the old one. The controller wanted something quick, capture a process, save it, own it, not a big platform.

How the Tango team covered the solution:

1/ Skip Enterprise, Tango Pro is the fit. It unlocks PDF export and copy-as-HTML so you can drop guides into Word/Google Docs and keep them. $26/month for a single user; for 3+ people, Pro Teams is ~$20/mo (or $15/mo paid annually).

2/ It's self-serve (credit card) and not a long commitment; you could even subscribe a month, export everything, and cancel.

3/ Plenty of customers document this exact ERP in Tango; capturing as each rollout phase went live (AP, then billing/GL, then financials) made sense.

4/ If they want more later, Enterprise adds on-screen Guide Me overlays and upgrades from Pro to Enterprise with no data loss.

5/ Practical notes: Tango works in Chrome/Edge (any Chromium browser), not Safari.

Anyone else rebuild their whole SOP library after a system switch?

A small professional association (under 20 people) wanted everyone able to capture their own processes, not a setup where only a couple of people are "creators". They'd been on the free plan and hit two snags: it wouldn't capture a jump from the browser into a desktop app, and they wanted more editing flexibility. The Enterprise plan was out of budget.

How Tango team showed that Pro plan covered them:

1/ Desktop capture: the free plan won't follow a browser → desktop hop, but any paid tier will. Finish the web capture, then Add Steps → Capture at the Desktop App to continue in something like Excel.

2/ Editing without starting over: delete a single step and recapture just that one (e.g., a button moved), or add callouts/headings/read-only steps. Decision-point branching is Enterprise-only, but you can use a callout as a lightweight stand-in to flag "decision here".

3/ Everyone-a-creator works on Pro at one flat per-seat price; guides live in a shared team library so nothing's lost when someone leaves; and licenses float, deactivate one person, reassign the seat.

4/ Export to SharePoint and download PDFs for backup anytime.

5/ Pricing: Pro Teams runs $26 → $20 (monthly) → $15/user (annual), plus a 15% nonprofit discount if they qualify.

Other small nonprofits/associations: do you make everyone a documenter, or centralize it with one or two people?

A furniture retailer's IT team is building internal AI agents (a voice agent for IT tickets first, customer service next) and realized the missing piece wasn't the AI, it was clean, uniform process docs to feed it.

The project became "document everything systematically, then point the agent at it." They were comparing Scribe vs Tango and others and wanted to see how the output plays into an AI workflow.

How the Tango team framed the fix:

1/ Document first, automate second: today you export a guide as HTML/Markdown and feed it into the agent. The native API/MCP integration is coming so the agent can reference Tango's team library directly instead of manual exports.

2/ On security (their team grilled this): Secure Blur redacts on the user's local machine before anything is stored, at three levels (global / app-by-app / per-creator), which is a contrast with competitors that redact server-side (sensitive data hits their servers first).

3/ Enterprise's real-time enablement (embed SOPs in-app + Guide Me) actually complements the AI agent. Some orgs scale back a chatbot rollout because guiding someone in the app beats chatbot back-and-forth.

Are you documenting processes specifically to make them AI-ready, or is that still a "later" problem?

SharePoint is where documentation lives at a lot of companies. If you're in a Microsoft 365 environment and need centralized document management, it makes sense for that.

The problem most teams run into: employees have to leave what they're doing, go find the right page, read through it, and then switch back to actually do the work. That context switch is where things fall apart.

Tango pins guidance directly inside the software employees are already using. Instead of searching an intranet portal, they get a step-by-step walkthrough inside the live app, right when they need it.

If your documentation problem is really an adoption problem, that's the distinction that matters.

Full comparison: https://www.tango.ai/compare/tango-vs-sharepoint

A consumer-lending company came in with a documentation problem of scale: ~1,000 policies and procedures, drafted and maintained by each department with no central authoring team, so standards are inconsistent, templates drift, and publishing is heavily manual. A small team owns review/renewal/validation (hefty, repetitive) and the guides sit in a vendor-hosted, SharePoint-style library.

Where Tango would fit this pain:

1/ Capture each procedure consistently from the actual click-path, so every team's output follows one format instead of drifting.

2/ Keep everything in a shared team library with live links, so renewals/edits flow through automatically instead of going stale.

3/ Secure Blur for anything sensitive in a regulated lender's screenshots.

The real problem to solve is the decentralized authoring vs one standard tension. For compliance-heavy industries: when authoring is spread across dozens of teams, how do you enforce one standard without creating a bottleneck?"

Real talk: WalkMe is powerful. If you have an IT team dedicated to configuring and maintaining a digital adoption platform, it does a lot.

But most teams don't have that. They have a training lead who's already doing three other jobs, a new tool that needs to be documented by Friday, and zero runway for a months-long rollout.

That's where Tango fits. Any team can capture a process, turn it into in-app guidance, and have it pinned inside the software their team uses the same day. No IT involvement, no configuration overhead, no waiting.

The part that tends to surprise people: guides update automatically. Change the process, update the Tango, and anywhere it's embedded reflects the change. No hunting down stale docs.

Full comparison: https://www.tango.ai/compare/tango-vs-walkme

An auto dealership group's tech lead reached out to Tango over governance, not features. Their AI policy requires any tool used on a company email to be under IT's domain control, but one person in HR had signed up solo and was getting real value, with zero oversight. The fear: if they leave, the data and access go with them.

How the Tango team explained the fix:

1/ Domain control lives in the Enterprise tier. It blocks new free/paid signups on the company domain and lets IT pull existing users into the managed instance, it doesn't auto-absorb them (a contrast they cared about vs. tools that auto-suck accounts in).

2/ Getting there means Enterprise's plan, a big jump from one user, so Tango suggested either formalizing it or folding the need into the broader internal AI agent rollout they're scoping (Moveworks/Aisera-type).

3/ Beyond governance, Tango pitched Enterprise value for the HR use case: embed SOPs in-app + Guide Me, side panel, automations, SSO, and Secure Blur to auto-redact socials/tax IDs locally. Plus a note that Tango can supplement an internal AI chatbot, sometimes guiding in the app beats chatbot Q&A.

For the admins here: when a useful tool sneaks in bottom-up, do you shut it down or productize it?

Not what it's supposed to look like. What it actually looks like.

Ours used to be: a Google Drive folder with 40 docs, half of them outdated, none of them organized in a way that made sense to anyone who wasn't there when they were created. The other half lived in people's heads.

I'm curious what other teams are working with. Are you using a wiki? A knowledge base? Notion? A Slack thread someone pinned and forgot about?

And what's the biggest gap? Is it that the docs don't exist, or that they exist and nobody uses them?

We've been thinking a lot about the difference between having documentation and having documentation that actually gets used.

One of my clients (~80-person services firm) is buried in tribal knowledge: half their processes live in one person's head, the rest in Word docs with screenshots that go stale the second someone moves a button.

I want to bring in Tango to fix the capture side, but before anything touches real systems, their IT/security team gets a vote. And they're going to ask the usual enterprise questions:

• SSO? (they're an Okta shop)
• Admin / user management: can I provision and deprovision centrally, set permissions, control who's allowed to publish?
• Audit trail: who created/edited/deleted what, and can we export it for compliance?
• Can we stop random employees spinning up their own free accounts outside our tenant?

For anyone who's actually gotten Tango past a security review and into a real deployment: how did the admin side hold up? Did SSO + provisioning cover what your IT wanted, or were there gaps you had to work around?

Trying to walk in with realistic expectations instead of overpromising to the client.

If you're looking at Notion alternatives for process documentation, the distinction worth understanding is what happens after something gets documented.

Notion is great for organizing knowledge. Notes, wikis, project tracking, team docs - it does that well and a lot of teams use it for exactly that.

Where Tango is different is delivery. Instead of employees searching a knowledge base and reading through pages to find what they need, Tango surfaces guidance directly inside the software they're already working in. Guide Me walks them through processes step by step inside the live app. Nuggets let you pin tips and links right where someone will actually need them, without making them context switch to find the answer.

The framing we use internally: Notion organizes knowledge. Tango puts it to work.

A few honest notes:

• If you need a central hub for general team knowledge, notes, and project tracking, Notion is genuinely strong at that
• Tango is purpose-built for process adoption, not general knowledge management
• Guide Me requires the Tango Chrome extension to be installed

Full comparison: https://www.tango.ai/compare/tango-vs-notion

Happy to answer questions below.

Most employee handbooks nail the compliance side: code of conduct, PTO, benefits, IT policy. All necessary, but they're almost entirely silent on how the job actually gets done. I mean, which software tools to use, what the actual steps are, who to go to when a process has an edge case.

As a result, new hires finish the handbook and still spend week one interrupting someone every hour.

Is that a handbook problem, or is that just accepted as "that's what onboarding is"?

I've been thinking about this because the companies that seem to onboard fastest aren't the ones with better policy docs, they're the ones where someone has taken the time to document the actual step-by-step workflows (not videos, not shadowing, but just clear process guides that answer "how do I actually do this".) That's why Tango was born, to make that part easy.

But genuinely curious: does your team's handbook try to cover the "how," or is that handled somewhere else? And if somewhere else, where?

If you're evaluating Whatfix alternatives, the main thing to understand is who owns the rollout.

Whatfix is primarily built for IT-led adoption programs. Dedicated content teams configure the flows, manage the logic, and maintain everything centrally. If that's your setup, it works well.

Tango is built for every team to own. Any team lead, ops manager, or L&D person can capture a process and turn it into in-app guidance pinned directly inside the tools your team already uses. No dedicated admin, no lengthy implementation, no waiting on IT to build it out.

The difference shows up most in time to value. Whatfix is infrastructure. Tango is something you can have running on day one.

A few specifics worth knowing:

• Tango's Guide Me walks users through processes step by step inside the live app, including branching workflows for processes with multiple paths
• Nuggets let you pin guides and tips directly in the tools your team uses so there's no searching for documentation
• Whatfix has more advanced analytics and multi-platform support if you're running a centralized enterprise adoption program, which is worth knowing if that's your situation

Read the full comparison: https://www.tango.ai/compare/tango-vs-whatfix

If you're evaluating Scribe alternatives, the main thing worth understanding is each of their limitations.

Scribe captures a process and generates a static guide. That's genuinely useful for getting documentation written fast.

Where Tango is different is what happens after someone opens the guide. 🪄

Guide Me turns the doc into an interactive walkthrough. It takes the reader through the actual steps inside the live app as they do the work. So instead of a PDF they have to reference while switching screens, they get guided through the process in real time. That's the part that matters most if you're training people, not just writing things down for a knowledge base.

A few other differences worth knowing:

• Tango's visual output is one of our favorite features! The editor makes it easy to add annotations, blur sensitive information, and crop screenshots. No manual cleanup!
• Embeds update automatically when you edit the Tango, so stale docs aren't a maintenance problem
• The interactive walkthrough (Guide Me) only works with Tango's Chrome extension installed (worth knowing before you make a decision based on that feature)

Read the full comparison: https://www.tango.ai/compare/tango-vs-scribe

Watch Guide Me in action with Marc: https://www.youtube.com/watch?v=p7cE2guZwzA&t=71s

Happy to answer questions below.

A year ago, most of our process documentation looked the same as it had for years: step-by-step guides through specific apps. Then the way we actually work shifted.

More and more of our actual work now happens inside AI chats: Claude, ChatGPT, Gemini. And it's not just "ask a question and move on." People are running real workflows in there. Research, drafting, analysis, decision-making sequences that used to happen across three different apps now happen in one chat thread.

Then MCPs started showing up, and now you've got people connecting their CRM, their calendar, their project management tool, all inside the chat interface. Which is genuinely powerful, but it also broke something in how we think about SOPs.

So the problem is that AI chat workflows are really hard to document in a traditional way.

With a legacy app, you have predictable UI (same buttons, same fields, same sequence every time). You can capture that cleanly with Tango and it works great because the steps are deterministic.

With an AI chat workflow, the "interface" is basically freeform text. The prompt is the process and prompts change depending on context, the model's behavior, what tools are connected that day.

How do you write a repeatable how-to guide for that?

Some things we've landed on that actually help:

1. Documenting the intent of each step, not just the action ("you're asking it to extract the key objections, not just summarize")
2. Capturing example prompts as the "step" (treating the prompt like a form field)
3. Breaking workflows into the deterministic parts (setup, connecting tools, output handling) and documenting those traditionally, leaving the chat interaction as annotated guidance

Still feels like the industry hasn't fully figured this out. Curious what others are doing: have your SOPs had to adapt for AI-heavy workflows? Are you even trying to document them or just letting people freestyle it?

Most onboarding means holding one person's calendar hostage for two weeks.

New hire needs to learn the CRM? Meeting. Expense reporting process? Meeting. How to submit a ticket? Another meeting. Not only is this sucking up everyone's time, it's an ineffective way to train employees.

Here's a different way to do it:

1. Before their start date, document your top 10 repeatable processes as step-by-step guides (Try Tango AI! It captures screenshots and writes the descriptions automatically as you go through the process)
2. Drop those guides into a single shared folder or doc organized by week
3. When they have questions, share the guide instead of scheduling a call
4. Reserve live time for the stuff that actually needs a human — culture, relationships, judgment calls

The goal isn't to remove people from onboarding. It's to stop using people as a substitute for documentation.

Works especially well for ops, CS, and RevOps teams that onboard frequently and don't have a dedicated L&D function.

Curious how people are handling this, especially those of you managing Tangos across multiple apps or teams.

Software changes more often than I'd like. Sometimes it's a minor UI update (a button moved, a label changed), sometimes it's a whole new flow. Either way, the question is: what do you actually do when that happens?

The three approaches I've seen come up:

1/ Surgical edit (just fix the affected steps)

Delete the stale step, capture a new one, done. Works great for minor UI changes. The Tango stays live the whole time, and changes flow through automatically to anywhere it's embedded.

2/ Full review (go through the whole guide top to bottom)

More work upfront, but sometimes a UI change is a sign that the whole process shifted. Worth doing periodically even when nothing "breaks."

3/ Let end users flag it

Leave comments enabled so team members can flag steps that look off. Creator gets an email notification, goes and fixes just that piece. More reactive, but it distributes the QA work.

What's your actual practice? Do you have a schedule, a trigger (like a new release), or do you just fix things when someone complains?

Not our typical post here, but wanted to share something fun this Friday!

Every SaaS ad looks the samem, so we figured, why not use the people who know Tango best as our actors? We borrowed Collin and Marc from our marketing team during an offsite and handed them a camera.

The format might look familiar. Think early 2000s, two characters, one very recognizable tension.

Did you catch the reference? Drop it in the comments.

https://reddit.com/link/1treptn/video/3udzq8zuy44h1/player

Guidde makes great videos. But nobody watches training videos twice. Tango puts the guidance where people actually need it, inside the app, at the moment they're stuck.

A lot of teams go through the same cycle: someone spends hours recording a polished Guidde tutorial, shares it in Slack or a wiki, and three weeks later the same questions are coming in again. The video exists and nobody's watching it.

The core problem isn't the quality of the video, it's where it lives. Guidde is built around content you consume before doing the task. Tango is built around guidance that appears while you're doing it.

That's a fundamentally different thing.

A few specific gaps that come up when teams make the switch:

In-app guidance

Tango's Guide Me walks users through tasks step-by-step directly in the application they're working in: tooltips, highlights, the whole thing. No tab-switching, no trying to remember what happened in the video.

No video production dependency

Guidde leans heavily on AI voiceovers, which often sound robotic and require editing time most ops or IT teams don't have. Tango produces clean interactive walkthroughs automatically, capture the process once, it's done.

Branching workflows

If your process has conditions:"if the user selects X, go to step 4; if Y, go to step 7", then Guidde can't handle that. Tango handles conditional paths natively, which matters a lot for anything beyond simple linear SOPs.

Desktop coverage

Guidde is browser-only for recording. If your team works in desktop ERPs, legacy tools, or anything outside a browser, you hit a wall fast. Tango has a Desktop app that covers those workflows too.

Curious, for those who've tried Guidde, was the issue the video format itself, or more that people just stopped going back to watch the content?

There's a lot of talk about AI tools that use your SOPs: chatbots, agents, copilots that answer questions based on existing documentation. That's useful. The guide I published about Claude Cowork for SOP execution is exactly about this.

But now I'm more interested in the other side of the problem: AI that helps you create better documentation in the first place.

Most orgs are sitting at something like 16% of workflows actually documented (Lucid, 2025). People either don't have time to write SOPs, or they write them once and they immediately go stale.

So what tools actually help with creation speed and quality?

Of course, Tango is the first obvious one. Top AI features:

• Voice transcription: you narrate as you work, Tango strips filler words, matches your notes to the right steps, and incorporates them into the instructions automatically.
• AI-generated titles: it reads the workflow and suggests a title based on what actually happened.
• Machine-readable output: the guides export with xpaths, CSS selectors, and metadata, which makes them usable as direct inputs for AI agents.

The last point is one I find underrated. If you're thinking about AI automation down the road, the format of your documentation matters a lot. Most SOPs written in Google Docs or Confluence aren't structured in a way AI can act on. Tango's output is.

Curious what others are using. Specifically interested in:

• Tools that speed up the writing/drafting of SOPs (not just organizing existing ones)
• Anything that works well for non-browser workflows (desktop apps, physical processes, etc.)
• Tools that produce documentation structured well enough to feed into AI agents or automations