Websome Services
ERP Project Knowledge Base
Project documentation and ERP system knowledge often scatter across emails and files. We build dedicated knowledge bases that organise information about system configuration, client processes and project history. Accessible to the implementation team and client, easy to search and update.
Common solutions
A simple, open-source wiki platform that organises content into books and chapters. We use it internally to manage technical and process documentation across ERP projects.
Atlassian's commercial wiki platform, the enterprise standard. Integrates tightly with Jira and the broader Atlassian DevOps toolchain.
A flexible tool combining notes, databases and documents in one workspace. Popular with smaller teams and easy to roll out quickly.
A modern open-source wiki with a clean interface. Supports Markdown, Slack integration and SSO out of the box.
A feature-rich open-source wiki supporting multiple storage backends: Git, database or S3. Can be fully self-hosted on-premise.
Wiki built into GitLab repositories. A practical choice for technical documentation kept close to the project codebase.
Full DevOps platform: code hosting, CI/CD, wikis and issue tracking on your own infrastructure. The Community Edition is open source and free to self-host.
Cloud-based code management platforms with built-in collaboration tools, code review and CI/CD integrations. The right choice when you don't want to maintain your own infrastructure.
Structured process maps are especially important for organisations moving in an AI-first direction. Well-documented processes are the foundation of effective automation and the starting point for AI deployments — a model can only work with what it understands about the organisation's structure.
Why choose us
- ✓Searchable knowledge base covering system configuration
- ✓Access for the entire implementation team and client
- ✓Change history and documentation versioning
- ✓Integration with project management tools
- ✓We know how important organisational memory is
- ✓We don't reinvent the wheel
- ✓We eliminate frustration in the project
- ✓Prepared for different stakeholders
How we build it
Audit and content inventory
We review existing documentation: emails, files, wikis and tribal knowledge. We identify what exists, what's missing and what's out of date.
Platform setup
We configure and customise the chosen KB platform, set up access control and connect it to your project tools.
Migration and structure
We import existing content, create a logical structure and write initial documentation for the most critical areas.
Handover and training
We show the team how to maintain and expand the KB and set up processes to keep it current after handover.
Frequently asked questions
Won't a knowledge base just go out of date immediately?
Only if it's treated as a one-off deliverable. We build processes around the KB — lightweight update habits, reminders and ownership — so it stays current without becoming a burden.
How do we control who sees sensitive project documentation?
Every platform we work with supports role-based access control. We configure it so internal teams, clients and vendors each see exactly what they need — nothing more.
Can we migrate content from an existing tool like Confluence or Notion?
Yes. All major KB platforms have import paths from common tools. We handle the migration, clean up formatting inconsistencies and structure the content in the new platform.