Document management & enterprise search engineering
We design, build, integrate and operate knowledge systems — document management, enterprise search, Microsoft 365 estates, retention and archiving — built around the repositories your organisation already runs on.
- Enterprise Search
- Document Management
- Metadata & Taxonomy
- SharePoint
- Microsoft 365
- Intranets
- Power Platform
- Access Models
- Classification
- Retention & Disposal
- Legal Hold
- Content Migration
Trusted by
- Engineering since
- 1992
- Technical specialists
- 200+
- European countries
- 6
- Quality management
- ISO 9001
What we do
Six services covering the full life cycle of an information estate — from finding what already exists to governing it and switching off what it replaced.
Information platform development
Custom and platform-based systems for organisations whose content, permissions or retention rules exceed what a product does out of the box.
Read moreEnterprise search
Search that reaches into the systems holding the answer, not only the document store — including ones without a modern API.
Read moreDocument management
Libraries, versioning, metadata and taxonomy designed around the questions people actually ask.
Read moreMicrosoft 365 and SharePoint
Intranets, team spaces and collaboration estates on the platform you already pay for.
Read moreGovernance and retention
Role-based access, classification, retention and legal hold that actually run rather than being documented.
Read moreContent migration
Twenty years of content moved in waves, with the legacy repository genuinely switched off at the end.
Read more
The content problems that don't fit a standard rollout
Knowledge across legacy systems
The answer sitting in a system nobody is going to replace this decade.
Optional metadata
Fields that are skipped at the end of a long day, making a taxonomy decorative.
Permissions by accretion
Access granted case by case for ten years, with nobody able to say who can see what.
Permission-aware search
Results filtered by each user's real access in each source, evaluated at query time.
Retention never executed
Disposal defined as policy and then quietly never run.
Migrations that stall
The bulk moves, a long tail remains, and the old system runs for another five years.
Chat, library or record
A distinction most Microsoft 365 estates never actually make.
Legal hold and eDiscovery
Freezing and producing a defined set of content, tested before it is needed.
Custom governance logic
Classification and lifecycle rules specific to a regulated organisation.
Don’t see your challenge here? Talk to us about your project
Search across what you have beats waiting for a migration
The usual answer to scattered knowledge is consolidation, and the usual outcome is a programme that never quite finishes. Reaching into systems where they stand delivers the result sooner — and the search analytics then tell you which content is actually worth moving.
- SharePoint & Microsoft 365
- Sites, libraries, Teams and the permissions behind them.
- File shares
- Decades of network drives, profiled before anything moves.
- Legacy repositories
- Connectors for systems with no modern API.
- Project systems
- Deliverables and correspondence held outside the DMS.
- Line-of-business apps
- The records that are the answer but were never documents.
- Identity providers
- Entra ID, SSO and group membership driving access.
- Electronic signature
- Signing inside the flow, with the artefact filed automatically.
- Records and archives
- Retention, disposal and long-term preservation.
Information platforms we have delivered
Swipe to see all three projects.
SINTEF: Enterprise search across legacy systems
Knowledge spread across systems that were not going to be replaced soon, so the search had to reach into them rather than wait for a consolidation that might never happen. The connectors and permission-aware results were the project.
Enterprise Estonia: A document management system for a public body
Documents as the record of public decisions, which raises the stakes on version history, approval trails and retention — so the design concentrated on making correct filing the easiest path.
Technopolis Group: Collaboration systems across an international organisation
An organisation with the platform already in place and a need for it to be usable — structure, permissions and the conventions that decide whether people put their work in it.
Organisations we understand
Information governance carries the obligations of the organisation it serves. These are the settings whose obligations we have already had to model.
Public sector
Documents as the record of public decisions, with statutory retention.
Research organisations
Knowledge spread across systems that will not be replaced soon.
Professional services
Client confidentiality, matter structure and access boundaries.
Real estate & facilities
Collaboration across sites, tenants and partner organisations.
Manufacturing
Specifications, drawings, revisions and controlled documents.
Energy & utilities
Regulated records, asset documentation and audit obligations.
Financial services
Classification, legal hold, eDiscovery and supervision.
Healthcare
Clinical documents, consent records and retention by category.
Trusted by European enterprises since 1992
Microsoft Partner since 1998. ISO 9001:2015 certified quality management.
- 30+ years of engineering
- Software development since 1992 — from traditional enterprise systems to composable, headless commerce.
- Proven client base
- Serving enterprises across Scandinavia, the Baltics, Central Europe and the US.
- 6-country European presence
- Offices in Estonia, Denmark, Norway, Poland, Switzerland and Spain.
- 200+ technical specialists
- Developers, analysts, architects and project managers across multiple technologies.
- Deep tech stack knowledge
- .NET, Java, Node.js, React, Next.js, Vue.js, Angular, Python and the major cloud platforms.
- European regulatory expertise
- Direct experience with GDPR, EU accessibility rules, e-invoicing and emerging AI legislation.
From first analysis to long-term operation
Inventory and analysis
What exists, what is used, who owns it and what people search for and fail to find. Almost every estate turns out to contain a large share nobody will claim.
You getA written picture of today and tomorrow, with the problems ranked by business impact.
Architecture & roadmap
Information architecture, the permission model and retention policy agreed before content moves, so the new system does not inherit the old problem.
You getA phase-one scope and estimate, agreed before any build starts.
Build & migrate
Delivery in waves by content category, each validated against a clear expectation, with the legacy repository readable but not writable during cutover.
You getWorking software running on your own data from the first weeks, shown in regular demos. No mock-ups.
Operate & govern
Automated permission review, disposal runs, search analytics and a switch-off date for what was replaced — with an owner against it.
You getPermission reviews, disposal runs and search analytics we keep together as the estate grows.
How we deliver — not what we sell
We are platform-agnostic by conviction rather than by slogan, and in this area that usually means recommending the platform you already own. Custom document management is justified when the workflow or compliance requirement genuinely exceeds what Microsoft 365 does — and we will say when we think it does not.
SharePoint and Microsoft 365 work is mostly architecture, permissions and search configuration: the parts Microsoft deliberately leaves to the customer, and the parts that decide whether people put their work in the estate or beside it.
Search is built with connectors to the systems that hold the answer, with relevance measured against real queries and tuned again — relevance is not configured once and left.
Behind it we work across .NET, Node.js and the Power Platform, with governance and lifecycle policies automated rather than left to administrators, because manual governance reliably lapses.
Key questions answered
Do we have to migrate content first?
No, and in most cases you should not. Federated search across the systems you already run delivers the result sooner, and the analytics then tell you which content is worth migrating — which is better than deciding up front.
Will people see documents they should not?
No. Permissions are evaluated against each source system at query time, so a change of access in the source takes effect immediately rather than at the next index run.
Should we build custom or configure SharePoint?
Configure, unless there is a specific requirement the platform genuinely cannot meet. Custom work on top of Microsoft 365 carries an upgrade cost that lasts as long as the system does.
How do you get people to file things correctly?
By reducing what has to be decided. Fewer mandatory fields, values derived from context and templates that pre-fill correctly do more than training — if correct filing takes effort, it will not happen consistently.
Can you help with governance rather than building?
Yes. Naming, provisioning, ownership review and archival policy — plus the automation to enforce them — is often the most valuable work, and it does not require a new system.
Let's talk about your information estate
Tell us what people cannot find today and which system nobody wants to own. We will come back with an honest read on whether the answer is search, governance or migration — and what a realistic first phase looks like.
