Industry
Inspection & IT Service Providers
Manage multiple customers with their locations, assets and inspection obligations in one platform — with Organizations as a central customer directory instead of scattered spreadsheets.
Up to 50 objects free forever · no credit card required
Run every customer as its own organization
Set up customers with their own role, contact details and hierarchy — as a central directory instead of scattered spreadsheets.
OrganizationsAssign locations and assets per customer
Link a customer's locations and assets to the relevant organization, with a clear role such as customer, owner or operator.
Locations & Floor PlansKeep contact people at the customer in view
Capture contact people per customer with job title, department and a primary-contact flag.
People & QualificationsTraceable inspection dates per customer
Document inspection and maintenance dates for every customer's assets with a complete history and proof.
Inspections & MaintenanceMaintenance and support contracts per customer
Capture contracts with customers centrally, including term and notice period, and link them to the relevant organization.
ContractsImport existing customer lists
Bring in customer, location and asset lists with AI import instead of re-entering them by hand.
Inventory & AssetsWhy a central customer directory matters for service providers
Inspection providers who inspect equipment on behalf of several customers, and IT service providers who look after several customers' infrastructure, face the same challenge: every customer has their own locations, their own assets and their own inspection or maintenance dates — spread across almost as many spreadsheets as there are customers.
With Organizations, every customer can be run as their own organization in Kernas, with its own role — customer or client, for example — its own locations and its own assets, but on one shared platform instead of separate systems or a separate spreadsheet per customer. That applies just as much to an inspection provider responsible for the recurring inspections of several customers' equipment as to an IT service provider looking after several customers' infrastructure.
Common challenges for inspection and IT service providers
Anyone keeping track of inspection dates, maintenance contracts and contact people across ten, twenty or more customers at once quickly loses the overview without a central structure: which location belongs to which customer? Who's the current contact person? When does the maintenance contract with customer X expire? Often, every field technician or account manager also keeps their own list on top, encouraging duplicate entries and conflicting versions.
A change on your own team — a technician or account manager leaving the company, for example — must not cost knowledge about ongoing customer relationships, open inspection dates or contract details either, since that knowledge only ever existed in their own spreadsheets or in their head.
How Organizations map customers and their assets
Every customer is set up as its own Organization, with a role, contact details and, optionally, a hierarchy — a customer's head office with several locations, for example. A customer's locations and assets are linked to the relevant organization, with a clear role such as customer, owner or operator.
Contact people at the customer can be assigned to the relevant organization through people management, with job title, department and a primary-contact flag — so when a customer calls, it's immediately clear who's responsible there.
Organizing inspections, contracts and proof per customer
Inspection and maintenance dates for a customer's assets run through inspections and maintenance management, with a complete history and proof attached to each inspection carried out — important when a customer demands full inspection records or an audit is coming up.
The contract with a customer — a maintenance or support contract, for example — can be linked to the relevant organization through contract management, including term, notice period and role such as customer or client.
Connecting multiple customers, locations and responsibilities
Because every customer is its own organization, it stays clear even with twenty or more customers which location, which asset and which contract belongs to which customer — without mixing different customers' data into one unmanageable list. A hierarchy within a single customer can be mapped too, for example a customer's head office with several branches as their own, nested organizations.
One important note upfront: restricting individual employees to only see their assigned customers is currently implemented for the organizations overview itself, but not yet consistently across every other module such as assets or contracts. For sensitive customer boundaries, we recommend talking to our support team beforehand.
From customer-specific spreadsheets to a central platform
When every customer has their own spreadsheet with locations, assets and inspection dates, the work becomes less manageable as the customer base grows — and when an employee leaves, knowledge that only existed in their own spreadsheets is often lost.
Existing customer and asset lists can be brought in with AI import, so even a large customer base can be mapped into Kernas without extensive manual re-entry — every customer as its own organization, with its locations, assets, contracts and inspection dates in one place. New customers can then be added as another organization in minutes, instead of setting up a new spreadsheet.
Starting small? Kernas Free lets you manage up to 50 objects free forever. More about Kernas Free
Start for freeFrequently asked questions from inspection and IT service providers
What is an organization in Kernas?
An organization represents a customer, supplier or other business partner — with one or more roles, contact details and an optional hierarchy, independent of the actual tenant structure.
Can several customers be managed at the same time?
Yes. Every customer is run as its own organization, with its own locations, assets, contracts and inspection dates, kept separate from other customers.
Do employees only see the customers assigned to them?
A restriction by assigned organizations exists for the organizations overview itself, but isn't yet consistently implemented across every other module. For sensitive requirements, talk to us beforehand.
Can contact people be captured per customer?
Yes. People can be assigned to an organization with job title, department and validity period, including a primary-contact flag.
Can contracts be linked to a customer?
Yes. Contracts can be linked to one or more organizations with their own role, such as customer, client or insurer.
Is Kernas suitable for inspection or IT service providers with many customers?
Yes. Organizations are specifically designed so a service provider can manage multiple customers with their respective locations, assets and inspection obligations in one structured platform.
Ready to digitize your inventory?
Get started with Kernas today.
- GDPR-compliant
- Swiss-made
- Modern encryption
- Regular backups
Up to 50 objects free forever · no credit card required