Beautiful launch day. Leadership sent the announcement email. Two months later, your SharePoint intranet is a ghost town. Employees still email documents. Nobody checks the news feed. The investment sits there, gathering digital dust, while your team stays disconnected. This isn't an employee problem. It's a design problem. And it's fixable.
Every dead intranet I've resurrected had at least three of these symptoms. They're not random failures. They're predictable outcomes of building for technology instead of building for people.
The information architecture reflects how your IT department thinks about content, not how employees actually search for it. Departments have sites. But nobody asked whether departments are even how people organize their work. The result: a perfectly logical structure that nobody can navigate.
Leadership posts announcements. Nobody reads them. The news section feels like a one-way broadcast channel, not a communication tool. There's no relevance filtering, no personalization, no reason for someone in Engineering to scroll past a post about the Diwali party in the Pune office.
You type "travel policy" and get 300 results. Three different versions of the policy from three different years. Meeting notes that mention the word "travel." A PowerPoint from 2019. The one document you actually need? Page four, if you're lucky. Your team gave up on search months ago.
Half your workforce is on the floor, in the field, or between meetings. They access everything from their phone. Your intranet was built for desktop browsers. On mobile, it's a mess of tiny text, broken layouts, and horizontal scrolling. So they open WhatsApp instead.
The HR policy page still references the old leave system. The IT support section has a phone number that was disconnected two years ago. Nobody knows who's responsible for updating what. Content owners were never designated. Now the intranet feels unreliable, so people don't trust it.
No branding. No visual identity. The intranet looks like every other uncustomized SharePoint site. It doesn't feel like your company's space. Employees feel no ownership over it. Compare that to the tools they actually use daily. Slack looks great. Your CRM looks professional. Your intranet looks abandoned.
Your intranet isn't failing because of SharePoint. It's failing because of how it was built. That's exactly what I fix.
This isn't a redesign. It's a rethinking. Every decision, from the homepage layout to the metadata behind every document, is made to answer one question: will employees actually use this tomorrow morning?
Most agencies hand you a pretty homepage and call it an intranet. That's a poster, not a platform. A real intranet is an ecosystem of interconnected components, each designed for a specific function and a specific audience.
The central hub. News, quick links, targeted announcements, leadership messages, and a search bar that actually works. Designed to be the first tab every employee opens.
Each department gets its own structured space. HR, Finance, IT, Operations, Sales. Connected to the main hub but tailored to departmental needs, workflows, and content types.
Policies, SOPs, templates, forms. All organized with consistent metadata, version control, and retention policies. Users find what they need without asking IT or emailing colleagues.
New hires open a structured, step-by-step portal on day one. IT setup instructions, HR forms, team introductions, company culture docs, training links. Everything in one place instead of a 14-email chain.
The invisible engine that makes or breaks an intranet. I configure search with promoted results, custom verticals, acronym definitions, and result types so employees find the right content on the first try.
You can't improve what you can't measure. I set up dashboards that show which pages get traffic, which get ignored, where users drop off, and what they search for but can't find.
"Darshana rebuilt our SharePoint intranet from a page nobody visited into the first thing our 800+ employees open every morning. She understood our business before touching a single configuration. The governance framework she left behind means we can evolve it ourselves."
Every intranet project follows a structured path. No guesswork. No "let's figure it out as we go." You know what's happening, why, and when.
I talk to the people who will actually use this every day. Not just IT. Not just leadership. The operations manager who needs the SOP. The new hire who can't find the insurance form. The field engineer checking something on their phone. Their input shapes every design decision.
The blueprint for how content is organized, labeled, and connected. This determines whether someone can find the travel policy in two clicks or gives up after five. I design navigation structures, hub-site hierarchies, metadata schemas, and content type definitions based on how your people actually think about information.
Your intranet should feel like your company. Brand colors, typography, custom headers, team photography instead of stock images. When employees open the intranet, it should feel familiar and owned, not like a generic Microsoft template with your logo pasted in the corner.
Pages built in Modern SharePoint with SPFx customizations where needed. Hub sites configured. Department sites connected. Search tuned. Navigation finalized. Power Automate workflows set up for content approval and publishing. Teams integration for notifications. Everything wired together.
Before company-wide rollout, a group of 20 to 30 "intranet champions" across departments test everything. They find the edge cases, the confusing labels, the missing links. Their feedback shapes the final refinements. When you launch company-wide, it's already been validated by real users.
Coordinated rollout with leadership communication, short video walkthroughs, and live training sessions for content owners. Every department knows what's changed, where to find things, and who to contact. The intranet launches not as a surprise, but as something people are already expecting and curious about.
Complete governance documentation. Content ownership matrix. Editorial calendar template. Training materials for future content owners. Your team takes full ownership of the intranet with confidence. Optional 90-day support retainer covers questions, optimizations, and any tweaks needed as usage patterns emerge.
Employees wasting 20 minutes a day looking for documents. That's 1.5 hours per person, per week. Multiply by your headcount. That's the cost of an intranet that doesn't work. A 30-minute conversation with me could be the start of fixing that permanently.