15 Questions to Ask in an Intranet Software Demo

There’s no doubt about it: intranet demos are built to impress. You will almost always see a polished homepage, a couple of news posts, and a search bar that “works great in most cases,” followed by a quick shift to procurement steps.

But the intranet solutions that succeed are not the ones that look good in a controlled intranet demo. They are the ones that hold up under daily pressure, when HR needs to publish something quickly without breaking governance, when employees need an answer in under a minute, and when IT needs identity and permissions to be secure without turning the intranet into a ticket factory. They are communication hubs and collaboration tools that bind an organization together as part of a larger intranet strategy.

This guide turns the most important intranet software questions into an intranet demo scorecard you can actually use. Each question tells you what to ask, what a strong answer sounds like, and which responses should make you pause before you sign a contract. They cover the key intranet features you should look out for, and the vendor approaches that are best to avoid.

How to Use These Intranet Software Questions as a Demo Scorecard

If you want an intranet demo that ends with an informed decision, run it like a structured working session. Ask the vendor to show the product live and complete real scenarios to form a complete picture, instead of describing what the platform can do in theory.

For each question below, score the intranet vendor from 1 to 5 on usability, admin effort, governance strength, and proof. Proof matters because “we can do that” and “here it is in the product” are two very different futures for your intranet team.

To avoid the desk-based bias that affects how many employees connect, require the vendor to demo three perspectives. Ask them to show a non-specialist publisher creating content, a frontline employee using mobile devices, and an IT department admin setting up access and permissions quickly.

Content and Governance Questions

Intranet governance is what prevents your intranet solution from turning into a content landfill. The best platforms make it easy for many teams to contribute while keeping ownership, quality, and compliance under control.

1. What roles and permissions can we configure, and how granular are they?

Ask the vendor to demonstrate real roles, not just explain them for other systems. Request a walkthrough that shows corporate comms, HR systems, and local site owners with different permission levels, then compare that to what a standard employee can do.

In a strong platform, permissions are role-based and granular. You should be able to control who can create, edit, publish, approve, manage taxonomy, and manage audiences, ideally at the site, channel, and page level.

If the vendor tells you they only support “admin” and “editor,” or that granularity requires custom development, treat it as a warning. Permission shortcuts almost always create bottlenecks later, because teams either cannot publish at all or can publish too freely.

2. Can non-specialists publish confidently without breaking design or governance?

The most revealing demo move here is to ask the vendor to roleplay a brand-new contributor. Have them create a post, add an image, embed a file, and schedule the post, then ask how the platform prevents off-brand layouts and chaotic formatting.

Good looks like structured components, templates, and clear guardrails that keep quality consistent across teams. The experience should feel similar to filling out a well-designed form, not wrestling with a mini web builder.

Red flags show up when vendors lean on training as the main solution, or when they imply contributors can edit HTML or CSS. That approach scales poorly and makes brand consistency dependent on who happens to be publishing that week.

3. What editorial workflow options exist for review, approval, and legal or compliance checks?

Ask the vendor to show draft, review, approval, and publish states inside the product. Then ask whether approvals can be required only for specific channels, such as policy pages, legal updates, or executive communications.

Strong platforms offer configurable workflows by content type or channel. You should also see an audit trail that makes ownership and history clear, because “who approved this” becomes a real question the moment something goes wrong.

If approvals happen through email chains, if there is no audit history, or if workflow is gated behind an expensive add-on, expect governance to become fragile and slow.

4. How do you handle content lifecycle: expiry, recertification, and archiving?

A working intranet solution is never “done.” Ask the vendor to show automatic expiry, reminders to content owners, and a way to prove that a policy page was reviewed quarterly or annually.

Good looks like expiration dates, review notifications, owner assignment, and reporting that helps you find stale content fast. The point is to prevent employees from trusting outdated information because “it was on the intranet, so it must be correct.”

A weak answer sounds like manual audits twice a year, spreadsheets, or vague advice about “best practice.” That is how intranets quietly decay, even when teams have the best intentions.

Information Findability Questions

If employees cannot find what they need quickly, they stop using the intranet and start using workarounds. That usually means repeated Teams pings, duplicated documents, and critical knowledge sharing trapped in chat threads.

5. How strong is search, and what influences ranking?

Ask for three searches live: “expense policy,” “payslip,” and a colleague’s name. Then ask what influences ranking and how an admin can tune results when employees keep clicking the wrong thing.

A strong answer includes relevance ranking, filters, synonym support, typo tolerance, and search analytics that expose failed searches. You want visibility into what employees are trying to do, not just the ability to guess.

Red flags include “search works if your metadata is perfect” or any platform that cannot show zero-result queries. If the new intranet cannot tell you what employees fail to find, you will never fix the real problems.

6. How do taxonomy and metadata work in practice?

Ask the vendor to tag content by region, function, and content type, then ask who can create new tags. This question reveals whether governance is real or imaginary.

Good looks like governed taxonomy with controlled vocabularies, inheritance, and rules that prevent tag sprawl. Metadata should make content easier to find and easier to target, not become another layer of admin complexity.

A red flag is a free-for-all tagging model with no guardrails, or a platform that effectively uses folders as its only organizational system. Folders create the illusion of order until your content volume grows and everything becomes “final_v7.”

Also read

Intranet Taxonomy: A Complete Guide

Your intranet taxonomy development doesn’t need to be an obstacle. In fact, it can be pretty straightforward. In this article,…

7. How does personalization work without creating filter bubbles?

Ask to see two homepages: one for a frontline employee and one for a manager. Then ask what is personalized, what is mandatory, and whether employees can understand why they are seeing certain content.

Good personalization combines targeted content with unavoidable global announcements. It should also be transparent enough that admins can explain, and employees can trust, why specific updates appear in their feed.

A red flag is personalization that is fully manual, which creates ongoing admin burden, or fully algorithmic, which creates a loss of control and can hide important information from the people who need it most.

Communication Effectiveness Questions

An intranet is not just a library. It is also an internal communication solution, and most intranets fail when everything becomes urgent, everyone gets spammed, and employees stop paying attention.

8. How do you target audiences, and how is targeting maintained over time?

Ask the vendor to target a specific audience segment such as “France, Retail, Store managers,” then ask how that audience updates when organizational structures change.

Good looks like audiences driven by identity attributes such as department, location, and role. You should also be able to create practical overrides, because real organizations always have edge cases.

If targeting relies on static lists that must be updated manually, you are looking at an inevitable future of outdated segments, incorrect targeting, and frustrated local teams.

9. What notification channels exist, and can we avoid over-notifying?

Ask the vendor to publish two messages during the demo. One should be a critical alert, and the other should be a nice-to-know story, because your platform must respect attention as a limited resource.

Good looks like tiered urgency, digests, and multiple channels such as email, mobile push, Teams, and in-app notifications. The best systems also let intranet users control preferences so the intranet feels helpful instead of intrusive.

In Sociabble, multi-channel delivery is designed for this exact reality, because employees do not all “work” in the same place. Some are on email, some live in Teams, and many frontline employees rely on mobile-first access for timely updates. Your solution must address this.

A red flag is email-only blasting, or an inability to control frequency by content type. If every message is delivered the same way, employees will treat all messages the same way, which is to ignore them.

10. How do you measure whether communication landed and drove action?

Ask the vendor to show intranet analytics for reach, opens, clicks, completion, and actions taken. Then ask whether you can break results down by audience segment, because averages hide the truth from clients.

Good looks like content performance, employee engagement trends, segment reporting, and search analytics that comms and HR teams can use without exporting raw logs every time. In strong platforms, analytics help you improve behavior, not just count page views.

A red flag is “we track page views only,” because views are exposure, not understanding or action. Another red flag is analytics that only work if you constantly export data to BI, which tends to kill momentum for comms teams that need fast feedback loops.

Employee Experience and Adoption Questions

Adoption is not something you fix with a launch campaign. Adoption is what happens on a normal Tuesday when an employee is busy, slightly impatient, and trying to solve a real problem quickly.

11. How intuitive is the UX on day one for different employee groups?

Ask the vendor to demo three journeys on both desktop and mobile: find a policy, complete a task, and catch up on company news. Then ask what the platform assumes about employee context, because “works on desktop” is not a frontline intranet strategy.

Good looks like clean information architecture, fast load times, consistent navigation, and a low training requirement. Most employees will not sit through an onboarding course to learn where HR forms live.

A red flag is any claim that users need hours of training, or that mobile is a reduced version of the product. Modern intranets should be a mobile-first system, not mobile-later, right out of the box, for all clients.

12. Can we brand the experience, and can local teams adapt without fragmenting the intranet?

Ask to see global brand control, plus exactly what a local site owner can customize. This is where many intranets quietly break, because either nothing can be adapted, or everything can be changed until the experience becomes inconsistent.

Good looks like central governance with local flexibility inside clear guardrails. Local teams should be able to add relevant local content and navigation without creating a “different intranet” in each country.

If branding requires developer work, or if local teams can change layouts and structures in ways that break consistency, expect either bottlenecks or fragmentation.

13. How do you support frontline, remote, and hybrid workers equally?

Ask the vendor to demo the full experience for a non-desk employee, including authentication, mobile access, and consumption of key communications. This is not a niche use case anymore, and most intranet failures trace back to excluding large workforce segments.

Good looks like mobile-first access, low-friction login, and internal communications that do not assume a laptop or even a corporate email address. Modern intranets are built to reach the full organization, not just headquarters.

A red flag is any suggestion that frontline teams should use shared kiosks, or that key features are missing on mobile. Kiosks do not create habit, and partial access does not create trust.

14. What multilingual and accessibility capabilities are built in?

Ask for a live walkthrough of language switching, translation workflows, and accessibility support. Then ask how translated content is governed, because multilingual without governance becomes duplicated and outdated fast.

Good looks like multilingual publishing workflows, clear ownership for translated versions, and inclusive design that supports global rollouts. Accessibility should be documented, not treated as a vague claim.

A red flag is translation by copy-pasting content into new pages, because that creates version chaos. Another red flag is a platform that cannot clearly explain accessibility standards and controls for its tools.

15. How strong is the people directory and “find colleagues” experience?

Ask the vendor to find a colleague by skill, location, and team, then request a demo of org charts, profiles, and where the data comes from. This feature sounds basic, but in large organizations, it becomes one of the highest ROI capabilities.

Good looks like rich profiles, attribute-based search, and clear integration with identity or HR data. Employees should be able to find expertise fast, and owners should not need to constantly chase people to update profiles manually in the system.

A red flag is a static directory list, or profiles that rely only on employees to maintain their own information. Voluntary upkeep tends to drop, which makes the directory less useful over time.

Integrations and Digital Workplace Fit Questions

The fastest way to kill intranet adoption is to make it feel like “another place to check,” or just another digital tool. The strongest platforms behave like a gateway to daily work, with integrations that reduce friction instead of adding complexity, and that work with existing systems.

Microsoft 365 and Teams Fit

Ask the vendor to show Teams integration and how Microsoft 365 or SharePoint content is surfaced. Then ask whether employees can access key intranet elements from Teams in a way that feels native, because embedded iframes rarely become a daily habit in the digital workplace.

Good looks like a seamless experience that respects how employees already work with their digital tools. Sociabble is often used as a modern layer the intranet integrates with Microsoft 365 while not requiring every employee to have a Microsoft license, which is particularly important for frontline populations.

A red flag is “we can build a custom connector,” especially when ownership and maintenance are unclear. If integration success depends on custom work, it tends to become a future problem for IT teams and comms teams alike.

Also read

How to Use Microsoft Teams for Internal Communications and Enhance Your Experience

Microsoft Teams is a powerful collaboration tool, there’s no denying it. But what if you’re interested in using Microsoft Teams…

SSO, Identity, and Security

Ask the vendor to show SSO setup, identity sources, and how permissions map to groups and attributes. Then ask what “least privilege” looks like in their platform, because intranet security issues are usually permission issues.

Good looks like clear enterprise identity support, auditable access controls, and a setup process that does not require professional services for basics. Strong security should be built-in, not negotiated case by case.

A red flag is “we handle security on request,” or a platform that cannot clearly explain how auditing works.

HR, IT, Payroll, and App Ecosystem

Ask the vendor to show how an employee completes common tasks such as requesting PTO, accessing payslips, submitting an IT ticket, and finding onboarding resources. These are the workflows that turn an intranet into a daily destination.

Good looks like the intranet acting as a clean gateway to tools, documents, data, and workflows, with simplified navigation and clear ownership. The point is to reduce tool switching and make work feel easier.

A red flag is an experience where employees must remember multiple URLs and logins with no unified access. That is how intranets become “nice to have” instead of “used.”

Roadmap and Vendor Differentiation

Ask what is shipping in the next 6 to 12 months, and what shipped in the last 6 months. This business question forces credibility because real product velocity leaves footprints.

Good looks like a transparent roadmap, a consistent future release cadence, and evidence that customer feedback influences priorities. Look for concrete examples.

A red flag is heavy reliance on future promises for needs you have today. Roadmaps are useful, but they are not a substitute for shipping product.

Implementation and Measurement Mini-Checklist

Before you end the demo, shift the conversation to the real work. Strong vendors welcome this part because it prevents failed launches and sets expectations correctly, both for implementation time and the capabilities immediately available to potential customers.

Implementation and Rollout

Start by asking what internal roles you need for a successful rollout of an intranet strategy, including comms, HR, and IT, and how many hours per week those stakeholders should plan to contribute during implementation. This helps you avoid the classic trap of under-resourcing the project.

Then ask the vendor to show a realistic timeline for a pilot, a phased rollout, and any global expansion using relevant information. You want to understand where risk sits, where training is needed, and what the vendor has seen work in business-based organizations similar to yours.

Finally, ask for a clear governance model example after launch. You should know who owns publishing, taxonomy, analytics, and platform administration, and how responsibilities are shared between central and local teams.

Close this section by clarifying both additional costs and recurring costs. Ask what is included versus extra for integrations, migration, training, premium analytics, and support, because hidden “implementation extras” can derail internal alignment fast.

Measurement and KPIs

Ask which KPIs the vendor recommends and why, then compare those to what leadership at your organization will actually care about. Strong KPI sets typically include reach, active users, contribution rate, search success rate, task completion, and communication effectiveness by audience.

Ask the vendor to show dashboards live, including segmentation, and ask how easily data can be exported if you need to integrate with BI. Measurement only works when it is frequent and accessible, not when it is trapped in monthly business spreadsheets.

The Intranet Solution that Sociabble Provides

Most intranet buying mistakes happen when teams overvalue what looks good in a demo and undervalue what drives daily use. That is why Sociabble is designed as a modern intranet and employee communication hub built around reach, relevance, and measurable adoption across both desk-based and frontline populations.

To reduce governance chaos and improve communication, Sociabble:

• Supports structured publishing experiences that help non-specialists contribute without turning your intranet into a formatting free-for-all. AI-supported content generation puts a full content studio in the hands of every employee.

• Helps comms and HR scale intranet content creation while keeping brand consistency and editorial control.

• Comes with single sign-on access and multi-channel delivery across web, mobile devices, email, and integrations such as Microsoft Teams.

• Includes analytics that go beyond basic views, helping teams understand reach, employee engagement, and behavior so they can improve employee intranet content, targeting, and delivery over time.

• Full integrations with the Microsoft ecosystem to meld seamlessly with your existing digital tools. Teams, SharePoint, Microsoft 365, it’s all covered.

All of these contribute to make Sociabble a complete intranet solution, capable of connecting and reaching every employee at your organization.

Final Thoughts

The best intranet demo is not the one with the flashiest homepage. It is the one that proves, live, how governance holds up at scale, how employees find answers quickly in a user-friendly environment, how targeting reduces noise, and how integrations simplify daily work in the digital workplace.

If you bring these 15 intranet software questions into every new intranet vendor meeting, you will leave with comparable answers, a clearer implementation plan, and far fewer surprises after signature. Not to mention the right solution, one that’s worth investing in.

At Sociabble, we’ve already partnered with industry leaders around the world, including brands like Primark, Coca-Cola CCEP, and L’Occitane Group, to enhance their intranet platforms and intranet strategy. And we’d love to do the same for you.

Sign up for a free, personalized demo today and discover how Sociabble can help your company establish a successful intranet, while also helping you to achieve your broader communications goals.

We’re ready to chat!

FAQs on Intranet Demos

When evaluating intranet platforms, the same practical questions come up in almost every buying process regarding intranet vendors. Here are the most frequently asked questions about intranet software demos and selection.

What should I ask in an intranet software demo?

You should ask about governance, search, user-friendly UX, targeting, mobile and frontline access, deep integrations such as with Microsoft 365, Teams and SSO, and analytics. You should also require live demos of each area, because slides rarely reveal admin burden or user friction that only a trial period can uncover. Don’t rely on a Twitter feed-style canned response. Dig deeper.

How many intranet vendors should we demo for intranet software?

Three to five vendors is usually the best range. Fewer makes it hard to compare, while more often creates decision fatigue. A scorecard helps ensure every demo answers the same intranet software questions in the same order, using the same information.

What is a red flag in intranet software?

Common red flags include weak permissions, no content lifecycle controls, search with no reporting on failed queries, targeting based on manual lists, and “custom development” requirements for basic capabilities.

How do you measure intranet success?

You should track active usage, reach by audience, search success rate, top failed queries, completion and action metrics on key content, and signals that repetitive email or Teams questions are decreasing. The best intranet KPIs reflect behavior change, not just traffic.

Do we need Microsoft 365 for a modern intranet?

No. Many organizations integrate their intranet with Microsoft 365, but you can run a modern intranet without every employee having a Microsoft license, especially when your workforce includes frontline employees.