People
Persons, organizations, teams, roles and relationships.
Explore PeopleSeven perspectives. One connected reality. Give every person the information and responsibility they need to do their work — without making work harder.
Everyone manages. Everyone matters.
CRM knows a person. Planning knows their schedule. Finance knows their costs. Files knows their documents. But in reality, it's still the same person.
ManageR starts with reality, not software categories. Information exists once as a meaningful record, then becomes available through every relevant perspective — always within the user's permissions.
See how one record travels ↗Not seven disconnected products. Seven natural ways to access the same business reality.
Persons, organizations, teams, roles and relationships.
Explore PeopleTasks, actions, forms, inspections and workflows.
Explore WorkEquipment, locations, inventory, drawings and BIM.
Explore AssetsQuotes, transactions, invoices, costs and value.
Explore FinanceTime, capacity, schedules, bookings and resources.
Explore PlanningCommunication, email, opportunities and campaigns.
Explore MarketingDocuments, knowledge, media, records and evidence.
Explore FilesA shared identity, typed relationships, understandable rules and context.
Click a domain to see how the same person remains connected to different parts of the organization.
Different information for different responsibilities.
See the organizations, teams and responsibilities connected to this person — only where access is granted.
Identity and organizational context
Information is linked by meaning, not duplicated to match a menu.
UBIM / Relationship semanticsTake a real-world inspection process. The work moves across domains while its meaning and history stay connected.
Every connection should be explainable. Every permission should have a reason. Every action should leave a meaningful trace.
Stable record identities, explicit relation types, provenance and seven linked perspectives. A business reality that doesn't need to be copied into seven different databases.
A proposed human-readable way to describe objects, permissions and workflows — with the goal of turning business rules into verifiable system behavior.
relation assigned_to {
from People.Person
to Work.Item
permission view
temporal true
}A coherent experience — powered by different technologies where appropriate. Explore integrations ↗
Capture work without a connection. Review changes and sign for synchronization using the active, authorized role.
OFFLINE REGISTRATIONCollaborate between independent organizations with explicit sharing agreements and controlled synchronization.
FEDERATED COLLABORATIONRights follow role, action and context. Being a director never automatically grants access to every record.
ROLE + ATTRIBUTE ACCESSConfigure stages, statuses, conditions, aggregations, reviewers and meaningful sign-offs through visual workflows.
WORKFLOW ENGINEDocs, spreadsheets, PDFs, drawings and media belong to Files, with secure integration to suitable editors and providers.
DOCUMENTS + INTEGRATIONSUse API and MCP capabilities to surface authorized information and propose traceable actions — without bypassing human control.
AI + API + MCPUse-case illustrations, not customer success claims. Every scenario begins with people, assets, work, time, communication and evidence.
Keep a blueprint pin, a corrective action, its assigned team, the evidence and the associated costs in one connected trail.
Connect equipment, maintenance, people, certificates, planning and supplier communication around one physical asset.
Move from a client relationship to scope, tasks, hours, invoices and relevant correspondence without recreating the same facts.
A title describes a role. It doesn't define someone's human worth. The best system makes useful hierarchies visible without turning people into layers.
Read our principles ↗Everyone manages information, wherever they work.
Hierarchy is for responsibility, not human value.
Share the right information, protect what is personal.
Make every rule, relationship and decision understandable.
Let people work together across organizational borders.
The architectural direction is defined. Production functionality must be demonstrated through actual implementation, security verification and reproducible tests. This website exploration is not the finished software.