What questions should you ask an intranet vendor before buying?

Every intranet vendor's sales demo is built to answer the same set of questions well: is it easy to use, does it look modern, can it hold company content. Those are the easy questions, and most platforms clear that bar without much trouble. The questions that actually predict whether an implementation succeeds or quietly fails a year later rarely come up unless the buyer asks them directly, because the honest answers don't always make the platform look its best.

Here's what's worth asking before signing anything, and why each question tends to reveal more than it seems to on the surface.

Does the platform inherit identity and permissions, or build its own?

This is the single most revealing technical question, and it's worth asking early. Every intranet needs to know who its users are and what they're allowed to access. Some platforms build their own separate user directory that has to be populated, maintained, and kept synchronized with reality. Others inherit that information directly from a company's existing Google Workspace or Microsoft 365 setup, so there's no second system running in parallel.

The difference sounds technical, but it has real, ongoing consequences. A platform with its own identity system means someone has to remember to provision every new hire and deprovision every departure, a task that quietly becomes IT's problem even if that wasn't the plan going in. A vendor who describes this process as simplified rather than eliminated is still describing ongoing overhead, just with softer language attached to it.

What does search actually cover?

Ask specifically whether search spans only the intranet's own content, or whether it reaches into tools like Gmail and Drive from the same search bar. This distinction separates a genuinely integrated platform from one that simply displays embedded files inside its own walls. A platform where search stays siloed within the intranet still leaves employees needing to remember which system holds the answer to their question, which defeats much of the point of consolidating information in the first place.

A useful, concrete test here is to ask for a live demonstration rather than a description. Have the vendor search for something that would plausibly live in an email or a shared file, and watch whether the result surfaces automatically or requires switching to a different tool first.

How long does implementation realistically take, for a company our size?

Every vendor has a flagship customer story with an impressively fast rollout, and it's worth asking directly whether that timeline reflects typical implementations or an outlier. The more useful version of this question specifies your own company's size and complexity: how long has implementation taken, on average, for companies with a similar headcount and a similar starting point, not the vendor's single best case.

This matters because the average corporate intranet project takes close to a year to go from decision to launch, according to implementation benchmarking that includes a wide range of platforms and company sizes. A vendor whose typical timeline sits dramatically below that average should be able to explain specifically why, whether that's native identity inheritance, pre-built content templates, or a structured implementation process, rather than simply asserting speed as a general claim.

Can ownership be assigned to specific content, and what happens when it goes stale?

This is the question most buyers forget to ask, because it's not something that shows up clearly in a product demo. A platform can look complete and well-organized on launch day and still degrade within a year if nobody's specifically responsible for keeping any given page accurate once the initial project energy fades.

Ask directly whether ownership of individual pages or spaces can be assigned within the platform, whether that ownership survives when the original author changes roles, and whether anything in the system flags content that hasn't been reviewed in a defined period. A vendor without a clear answer to these questions is describing a platform that will likely accumulate the same kind of stale, untrustworthy content as whatever it's replacing, just with a better interface around it.

Is pricing published, or does it require a custom quote?

Published, transparent pricing removes a source of friction that growing companies often hit when evaluating enterprise software, and it's worth asking directly why a vendor's pricing isn't public if it isn't. A custom quote isn't necessarily a red flag on its own, since it sometimes reflects genuine variation in company size or feature needs, but it's worth pressing for a clear breakdown of what's included in a base price versus what triggers an additional cost, since add-on fees that only surface after a few sales calls are a common source of budget surprises later.

It's also worth asking directly whether the quoted price includes implementation support, or whether that's billed separately. A platform that looks affordable on a per-seat basis can end up considerably more expensive once implementation, training, and ongoing support are added as separate line items.

What does real usage look like after launch, not just at signup?

Adoption after the sale is the metric vendors are least likely to volunteer unprompted, since it's also the one most likely to expose a weak spot. Ask directly for average usage rates across the vendor's customer base, not just logo counts or the number of contracts signed, and ask how that compares to the broader category.

There's a real, well-documented gap in this category worth knowing about before evaluating any specific vendor's numbers: social intranet platforms see a global average adoption rate of around 31%, meaning a majority of employees at a typical company with a typical intranet aren't checking it in a given week. A vendor with usage data significantly above that average has a genuine differentiator worth verifying. A vendor unable or unwilling to share usage data at all is a signal worth taking seriously on its own.

What happens as the company grows or changes?

A platform that works well for a company's current size doesn't automatically keep working as headcount grows, teams reorganize, or the company acquires another business. Ask specifically how the platform handles a growing number of departments, a merger bringing in a new set of employees and content, or a structure that needs to flex without requiring a full rebuild.

This question matters more than it might seem, because most companies underestimate how much their tool stack sprawls as they grow. Okta's 2025 Businesses at Work report found that the average company now runs 101 separate software applications, a number that climbs steadily as companies scale. An intranet vendor should have a clear, specific answer for how their platform avoids becoming one more disconnected tool in that pile as the company expands, rather than a vague assurance that it scales well.

Can we talk to reference customers our own size, not just your biggest names?

Case studies featuring a vendor's largest, most heavily supported enterprise customers make for impressive marketing, but they don't necessarily reflect what implementation looks like for a company with a fraction of that resourcing. Ask specifically for reference customers similar in size, industry, and internal technical capacity to your own company, and be direct that the vendor's flagship logos aren't what's being asked for.

A platform that works brilliantly for an organization with a dedicated intranet team doesn't necessarily behave the same way for a company running the whole thing with one internal comms generalist. Getting an honest read from a comparable customer is one of the more reliable ways to validate whether the vendor's claims will actually hold up in your specific situation.

Where Happeo can help

Asking these questions of Happeo specifically yields fairly direct answers. Identity and permissions inherit from a company's existing Google Workspace or Microsoft 365 setup rather than building a separate system. Search spans Gmail, Drive, and the intranet from a single bar. Ownership can be assigned to individual pages and spaces, with automated content health tools flagging what's gone stale.

Implementation typically lands between six and eight weeks for most customers, guided by a structured process with a dedicated deployment consultant. Average weekly usage sits around 78% across the customer base, well above the industry's roughly 31% average, and the platform holds a 4.5 out of 5 rating on G2 across more than 150 reviews, a figure that's independently verifiable rather than self-reported.

A partner in asking the right questions, not just answering them

Buyers who've never gone through an intranet evaluation before often don't know which questions matter most until they've already made a decision and discovered the gap the hard way. This is exactly the kind of guidance Happeo tries to offer upfront rather than waiting for a prospective customer to stumble onto the right questions independently.

Having worked with companies across a wide range of sizes and starting points, Happeo understands which questions genuinely predict a successful implementation and which ones sound important but don't actually correlate with long-term success. That perspective gets shared directly during the evaluation process, including pointing prospective customers toward the specific reference conversations and implementation details most relevant to their own situation, rather than only responding to questions that happen to get asked. A vendor confident in its own answers has every reason to make the hard questions easier to ask, not harder.

Buying with your eyes open

The questions above share a common thread: each one tests whether a platform's ease-of-use claim, speed claim, or integration claim holds up in specifics rather than in general marketing language. Vendors who answer these questions directly, with real numbers and honest tradeoffs rather than reassurance, tend to be the ones whose platforms actually deliver on what the sales conversation promised.

The cost of skipping this step isn't usually visible until well after the contract is signed, once the platform's real limitations show up in a rollout that takes longer than expected, or an adoption rate that falls short of what the demo implied. Asking these questions upfront is a small amount of friction that saves considerably more further down the road.

Frequently asked questions

What's the single most important question to ask an intranet vendor? Whether the platform inherits identity and permissions from an existing system or builds its own. This single design choice determines a large share of the ongoing technical overhead a company will carry after launch, more than almost any other feature.

Should a company be worried if a vendor doesn't publish pricing?
Not automatically, but it's worth pressing for a clear, specific breakdown of what's included and what triggers additional costs. Custom pricing sometimes reflects genuine variation in company needs, but it can also hide add-on fees that only become clear after several sales conversations.

How can a buyer verify a vendor's adoption claims before signing?

Ask for reference customers similar in size and technical resourcing to your own company, and ask those references directly about usage after the initial rollout excitement faded. A vendor's own reported figures are useful context, but an independent conversation with a comparable customer is a more reliable check.

Why does asking about content ownership matter more than it seems to? Because ownership is what determines whether an intranet stays accurate over time, and it's rarely visible in a product demo. A platform that looks complete on launch day can still degrade within a year if nobody's specifically responsible for keeping content current, which is a maintenance problem rather than a feature gap.

Is it reasonable to ask a vendor how their platform handles company growth or acquisitions?

Yes, and it's a question many buyers skip because it feels premature during an initial evaluation. A platform that works well at a company's current size can become unwieldy as headcount grows or a merger brings in new teams and content, so asking about this upfront avoids a costly surprise later.