Custom Corporate Intranet Portal
When your company hits 50 employees, the chaos of scattered information becomes critical. Documents in one place, news in another, CRM in a third—employees waste up to 30% of their time searching for data. Off-the-shelf solutions like SharePoint, Bitrix24, or Confluence work for simple scenarios, but when you need non-standard approval workflows, deep integration with legacy 1C systems, or strict security requirements, you hit a wall. That’s when you need a custom intranet portal. We’ve been building these for over 8 years and have delivered more than 50 projects for companies sized 50 to 5000 employees.
Typical Problems We Solve
Information fragmentation. A custom intranet unifies everything in one interface: news feed, structured knowledge base, universal search across all documents. No more jumping between systems.
Complex approvals. Travel requests, equipment purchases, vacation approvals often require multiple managers. Without automation, the process drags on for days. Our form builder and approval workflow engine cuts processing time to 2–4 hours per request.
No central directory. Active Directory or 1C:ZUP data—employee contacts, org chart, skills—all synchronized into a single searchable directory.
How We Do It: Stack and a Case Study
For one client (IT company, 300 employees), we built a portal using Laravel 11 with React 18. Front-end SSR with Next.js 14. Database: PostgreSQL. Search: Meilisearch. Authentication: SAML 2.0 via ADFS. Implementation took 3.5 months.
The core module was a request builder with dynamic forms and sequential approval stages. For example, a purchase request: employee fills the form, system checks budget, sends to department head, then to financial director. At each step—instant notification to Telegram.
"The portal cut approval time from two days to three hours," said the client’s IT head.
We chose Laravel for its mature ecosystem, built-in queue for notifications, and easy integration with REST APIs. Next.js ensures fast page loads and SEO-friendliness for public parts. Meilisearch provides near-instant full-text search across all documents.
Our Process (Not a Fixed Price)
- Discovery (1–2 weeks). We analyze your business processes, gather requirements from key departments, and define the MVP.
- Design (2–3 weeks). We create prototypes, agree on portal structure, and produce a detailed technical specification.
- Development (2–6 months). Backend, frontend, integrations. We run 2-week sprints with demos at the end of each.
- Testing (2–4 weeks). Functional, load, security testing. We write automated tests.
- Launch and support. Deploy to your server or cloud, train admins, provide ongoing support.
Example Technical Architecture
- Backend: Laravel 11 with SAML2 authentication module, form builder, notification queue.
- Frontend: Next.js 14 SSR, React 18, Tailwind, react-query.
- Integrations: REST API for 1C, Graph API for Exchange, WebSocket for notifications.
- Database: PostgreSQL + read replicas, Redis cache.
- Search: Meilisearch.
- Deployment: Docker, CI/CD via GitLab.
What You Get
- Full documentation: architecture description, admin guide, user manual.
- Source code and all rights to it.
- Server and CI/CD access.
- Team training (2–3 days).
- 3 months of technical support (extendable).
Timeline Estimates
MVP: from 3 months. Full-featured intranet: 5 to 9 months. Cost is determined after analysis—contact us for a project assessment.
| Aspect | Custom Intranet | Off-the-shelf (Bitrix24/SharePoint) |
|---|---|---|
| License | None—you own the code | Annual fee, often per user |
| Flexibility | Any modifications | Limited customization |
| Integration | Any API, legacy | Only vendor-supported |
| Security | Full control, audit, 2FA | Depends on vendor |
| Scale | No limits | Often has feature caps |
Security Measures
All traffic over HTTPS. Sessions with optional IP binding. An audit log records every action: who, when, what changed. Two-factor authentication via TOTP. Access restrictions by IP or VPN. For government organizations—certified cryptography.
Supported Integrations
| System | Integration Method |
|---|---|
| Active Directory | LDAP sync, SAML/OIDC |
| 1C:ZUP | REST API (HTTP services) |
| Email (Exchange/Gmail) | SMTP, Graph API |
| Telegram/Slack | Bot for notifications |
| Jira/GitLab | Webhook for task display |
Integration with 1C
Integration with 1C is done via REST API (HTTP services) or file exchange (CommerceML). We synchronize directories (employees, departments) and documents (requests, vacations) in real time or on schedule. For clients using 1C:ZUP, this reduces manual data entry by 70%.
Mobile Access
As a Progressive Web App (PWA), employees access the intranet from their smartphones without going through an app store. Push notifications via FCM for important announcements and approval reminders.
With over 8 years of experience, we deliver robust portals tailored to your requirements. Contact us for a consultation—we’ll prepare a proposal within two business days. Request a project estimate today.