If you’ve ever tried building a product demo with your team and wound up in a tangle of Slack messages and conflicting edits, you’re not alone. This guide’s for marketers, product folks, and sales teams who want to actually get things done in Navattic—without tripping over each other or dealing with a mess of “final_v2_reallyfinal” files.
Navattic (navattic.html) is a no-code demo builder. It’s good at what it does—letting you string together interactive product walkthroughs that you can share anywhere. But even with the right tool, collaborating can get messy fast if you don’t have a plan. Here’s how to keep your team (and your demos) on track.
Step 1: Set Some Ground Rules Before Anyone Touches Navattic
It’s tempting to just jump in and start clicking around, but a little upfront planning saves you from chaos later. Here’s what to sort out before you even open Navattic:
- Decide who owns what. If everyone’s responsible, nobody’s responsible. Assign a point person for each demo, or at least for the project overall.
- Pick your workflow. Will you build out the whole demo first and then edit, or work in drafts and iterate? Decide now so people don’t step on each other’s toes.
- Agree on your goal. Are you making a sales leave-behind, an onboarding flow, or a quick teaser for the homepage? Be clear. Otherwise, you’ll end up with a demo that tries to do everything and does nothing well.
Pro tip: Write this stuff down, even if it’s just in a Google Doc or Notion page. Reference it later when people forget.
Step 2: Set Up Your Navattic Team and Permissions
Navattic supports inviting teammates to your workspace. But before you start firing off invites, understand what each role actually means—and why it matters.
- Admins can do pretty much anything, including adding/removing users and publishing demos. Don’t make everyone an admin. Too many cooks and all that.
- Editors can create and edit demos, but can’t change billing or kick people out. This is where most contributors should land.
- Viewers can only see demos. Good for stakeholders who like to watch but not touch.
What works: Keeping a tight group of editors and giving everyone else viewer access. This reduces accidental overwrites and “wait, who changed this?” moments.
What doesn’t: Making everyone an admin because “it’s just easier.” It’s not easier when someone accidentally deletes your best demo.
Step 3: Build a Rough Draft—Together or Solo
There are two schools of thought here:
- Collaborative build: Everyone jumps in and builds sections in parallel.
- Solo draft, team review: One person builds a first pass, then hands it off for feedback.
Be honest about your team’s style. If you’re a small team that works well live, go for it. But if you’ve got more than three people or strong opinions, it’s usually smoother to have one person build the draft and others weigh in.
How to avoid version hell:
- Navattic saves changes in real-time, but there’s no “track changes” like Google Docs. You can overwrite each other’s work if you’re not careful.
- If you must work at the same time, split up by sections or scenes. Communicate about who’s editing what.
- For most teams, async review is less stressful and leads to a cleaner final product.
Step 4: Use Comments and Annotations (But Don’t Expect Miracles)
Navattic has basic commenting features for leaving feedback on individual demo steps or scenes. It’s handy, but don’t expect the rich collaboration tools you’d find in something like Figma or Google Docs.
What works: Leaving clear, actionable comments like “Let’s shorten this tooltip” or “Can we swap in the new logo here?”
What doesn’t: Using comments for big-picture discussions, or assuming people will see every note you leave. For major feedback, hop on a call or use your team’s main chat tool.
Pro tip: If you’re juggling lots of feedback, keep a running task list outside Navattic. It’s just easier.
Step 5: Handle Edits and Feedback Without Losing Your Mind
This is where most teams trip up: endless rounds of feedback, conflicting edits, and everyone thinking their version is the “right” one.
How to keep it sane:
- Batch feedback. Set a deadline for everyone to review, then tackle edits in one go. Avoid endless trickle-in feedback.
- Assign an “editor-in-chief.” One person should have final say on what gets changed. This keeps the demo coherent and stops bikeshedding.
- Use version duplicates for big changes. If you want to try a major overhaul, duplicate the demo instead of nuking the original. Navattic makes this easy—just duplicate and rename.
What to ignore: Nitpicking copy or button colors in the demo builder. Final polish can wait until everything else is locked down.
Step 6: Test and Share—But Don’t Share Too Soon
Navattic demos can be previewed and shared as live links. You’ll be tempted to start sharing early, but resist the urge. Half-baked demos confuse stakeholders and eat up time with “not quite ready” feedback.
Do this instead:
- Test internally first. Run through the demo as a new user. Note any confusing steps or typos.
- Get sign-off from your core team. Only after your main reviewers have blessed it should you share more widely.
- Use share links wisely. Navattic lets you create unique links for different audiences (sales, marketing, etc.). Use this to control who sees what.
What works: Sharing targeted demos with specific teams or prospects, not blasting out a “one demo fits all.”
What doesn’t: Letting the demo link float around in Slack or email before it’s ready.
Step 7: Publish, Embed, and Track—But Keep Iterating
Once your team’s happy, it’s time to unleash your demo. Navattic lets you embed demos on your site, include them in emails, or use direct links.
But don’t treat it as “done.” The best teams treat demos as living docs. Track performance (Navattic gives you basic analytics), gather real user feedback, and keep iterating.
- Collect feedback from real users, not just your team. Sales calls, support chats, or prospects will spot issues you missed.
- Tweak and update regularly. Don’t wait for a “big relaunch.” Tiny improvements add up.
Pro tip: Set a reminder to revisit your demos every month or quarter. Products change. So should your demos.
Honest Takes: What Actually Matters (and What Doesn’t)
Worth your time:
- Clear roles and responsibilities
- Using drafts and duplicating for big changes
- Short, focused feedback cycles
Not worth stressing over:
- Getting every pixel perfect before sharing internally
- Fancy comments or “collaboration features” (Navattic keeps it simple)
- Making the demo do everything—focus on one use case per demo
Keep It Simple and Keep Moving
Collaboration on Navattic demos doesn’t have to be a mess. Most headaches come from unclear ownership and too many cooks in the kitchen. Get your process down, use the features that matter, and don’t sweat the rest. Your first demo won’t be perfect, and that’s fine—iterate and improve as you go.
The best teams keep it simple, talk to each other, and don’t let the tool get in the way. Now go build something your users (and your team) will actually want to click through.