Turning a Dead Intranet into a Tool People Actually Use
The Situation
The dealership had a Bitrix24 intranet that nobody used. Engagement was below 10%. The system had been set up years earlier with good intentions, but the default interface was cluttered and had nothing department-specific. Employees treated it as "that HR portal we ignore" and did everything through email, group texts, or paper.
The real cost wasn't the unused software license. It was the scattered communication, the manual processes that should have been automated, and the complete lack of centralized KPI visibility for leadership.
What Was Wrong
Generic interface: Every department saw the same cluttered default Bitrix24 layout. Nothing was tailored to how individual teams actually worked.
Data scattered everywhere: KPIs lived in personal spreadsheets. Meeting notes lived in email threads. Training documents lived on a shared drive somewhere.
Zero department tools: No dashboards, no team-specific landing pages, no quick-access tools for daily workflows.
What We Built
Phase 1: Modernize the Foundation
Rewrote the frontend in vanilla JavaScript and CSS. No jQuery, no bloated libraries. The result loaded in about 1.2 seconds with a clean layout and straightforward navigation.
Built PHP middleware to fetch and sync data through Bitrix24's REST API: tasks, employee directories, calendars, and custom fields.
Phase 2: Department Landing Pages
Each department got a tailored landing page with the tools and information their team actually uses daily.
Service Department: Active work orders, technician availability, shop schedule, safety alerts.
Parts Department: Open order status, daily invoicing numbers, vendor contact quick-links.
Sales: Pipeline overview, upcoming customer appointments, commission tracking.
HR: Onboarding checklists, document library, PTO requests, training schedule.
Safety: Incident reporting form, certification tracking, compliance documents, safety meeting schedule.
Phase 3: KPI Dashboards
Built real-time dashboards for leadership using PHP cron jobs pulling task completion data from Bitrix24 and business metrics from internal systems. Visualizations with Chart.js showing department performance trends.
Role-based access so managers see their team's metrics while leadership gets the cross-department view.
Technical Implementation
- Frontend: Vanilla JS + CSS3, fast rendering
- Backend: PHP middleware for Bitrix24 REST API integration
- Data sync: Cron jobs pulling metrics on schedule
- Visualization: Chart.js for KPI dashboards
- Auth: Tied to existing Bitrix24 user accounts and roles
Results
| Metric | Before | After |
|---|---|---|
| Active users | ~10% | ~89% |
| Avg. time per visit | 0.8 min | 6.2 min |
| KPI reporting time | 2+ hours/week (manual) | ~5 min/week (automated) |
The dashboards alone saved leadership hundreds of hours per year in manual reporting. But the bigger win was adoption. Employees actually open the intranet now because it has things they need: their schedule, their team's numbers, their department's tools.
The shift happened fast. Once the first department (service) launched and techs started using it to check work orders, other departments asked when theirs was coming.
What Made It Work
Department-specific, not one-size-fits-all. The default Bitrix24 layout tries to be everything for everyone. By building focused landing pages for each team, every employee sees tools relevant to their actual job.
Fast. Nobody will use a slow intranet. The 1.2-second load time meant people could check it quickly between tasks instead of waiting around.
Incremental rollout. Launched one department at a time, gathered feedback, and adjusted before moving to the next. This built internal momentum and let each department shape their own tools.
Have a system that nobody uses? Let's talk about making it useful.