Knowledge is scattered across chats, email and personal folders
A knowledge base with search that actually finds what you need.
Documents, policies, requests and company news in one place. New hires find answers themselves, and approvals move without forwarding emails.
Three worries people usually bring with a project — and how we handle them.
Knowledge is scattered across chats, email and personal folders
A knowledge base with search that actually finds what you need.
Approvals get stuck in email threads
Requests with a clear route and status.
New hires keep interrupting colleagues with the same questions
An onboarding programme with documents and steps for the first weeks.
Up-to-date instructions in one searchable place.
In every planAccess by department, role and project.
In every planLeave, purchases or access — with a route and status.
In every planWho is responsible for what and how to reach them.
In every planImportant updates reach everyone instead of getting lost in group chat.
In every planA step-by-step plan and materials for the first weeks.
In every planChoose the type, the features you need, the design tier and the timeline — you’ll see a preliminary price range and duration. We fix the exact estimate after a short brief.
Chat messages: goals, users, the features you need.
We fix scope, timeline and cost before work starts.
A prototype and design of the key screens — agreed with you.
We show the result of every stage, and payment is by stage too.
We publish, test and stay in touch for further improvements.
Yes. We review the current structure, remove duplicates and outdated files, and move the materials into new sections with the right access permissions.
Yes. We adapt the interface for mobile devices, so employees in the field or on shift can open instructions or submit a request.
Access is restricted by role, the connection is encrypted and backups are made regularly. Requirements for data storage and hosting location are discussed before development begins.
The price depends on the scope: we estimate by features, design and timeline. Describe the task in the calculator on this page to get a “from–to” range, and after the brief we fix the exact estimate. Payment in stages.
The domain and all content are yours from day one. After 12 paid months the website itself is yours too — on request we hand over the source files, access and documentation. Support and further development can stay with us.
We reply during business hours on weekdays — no calls, no pressure.
We reply during business hours on weekdays
Corporate intranet portal development: a searchable knowledge base, documents with permissions, requests and approvals, news and onboarding for new hires.
A small team is often fine with a cloud office suite with shared folders and a work messenger: it’s inexpensive and clear to everyone. We won’t talk you into a portal if your problem can be solved by tidying up folders and a couple of written procedures. Development is justified where fragmentation is already costing the company time, money and mistakes. For example, when the same questions are asked again and again and it takes half a day to find the right file.
Signs that it’s time: employees work across several departments or shifts, there are approvals with a chain of responsible people, documents need strict access control, and data has to be connected to your accounting system or CRM. Your own portal mirrors the company’s structure and processes instead of bending your work to fit someone else’s service. Sections and permissions are easy to change as the team grows and new departments appear.
The main factors are the number of sections and scenarios: a knowledge base, document workflow, requests, training, news. The access model takes a lot of work: the finer the permissions by department, role and project, the more thorough the design and testing. We separately estimate approval workflows if they include conditions, stand-ins during holidays and deadline tracking. We describe each workflow together with you so that no disputed situation is left without someone responsible.
Integrations also affect the estimate: single sign-on with corporate accounts, a connection to your HR or accounting system, email and calendar. Migrating existing documents and instructions is a task in its own right, and its scope depends on the current state of the materials. We go through all of this during the brief and fix it in the estimate. If there’s a lot of material, the migration can be done in stages, starting with the most-used sections.
A portal nobody visits quickly turns into a dump of outdated files. That’s why we start with one or two scenarios that save employees time every day — for example, requests or finding instructions. Once people get used to opening the portal because it’s genuinely useful, the other sections catch on much more easily. Employees avoid a portal with no obvious benefit, however neatly it’s been built.
We assign someone responsible for each section and agree on how to keep materials up to date. We run a short training session for the team and gather feedback in the first weeks. From there we provide technical support for the portal and add new modules as the company changes. New departments, approval workflows and integrations are connected without interrupting work or retraining the whole team.
This is custom development, done for you: we run a brief, describe the features, design around your business logic, and agree the design, timeline and estimate before work starts. We take on the architecture, development, integrations and launch.
Cost and timeline depend on the scope — we estimate individually for the task, not from a single price list. After launch we stay in touch: support, improvements and product development.