Every process in a different tool. No view of where anything stands.
Onboarding sits in a document, contracts on a file share, the campaign on a board and the application in an application of its own. Anyone who wants to know the status asks around.
The renewal date is known only to whoever filed the contract.
On day one the access is missing, because a task belonged to nobody.
A process status sits in four tools and nowhere together.
A directory, a flow, an approval. That covers almost any business process.
Directories with your own fields
Contracts, assets, people or campaigns as a Registry directory, with the fields your process actually needs.
Flows instead of checklists
Onboarding, renewal or campaign launch run as an automation. Tasks appear with an owner and a deadline, not as rows in a document.
Approvals with roles and deadlines
Who has to agree is part of the flow. The approval hangs off the work item and stays traceable afterwards.
Reminders from a date field
A date in the directory is the trigger. A contract deadline announces itself before it passes.
Status at a glance
Which items are running, which are waiting on an approval and which are overdue is read from the items themselves.
Someone new starts on Monday. From the triggered flow to the onboarding closed after thirty days.
Entry in the directory
The person is created as an entry with role, start date and location. The entry triggers the flow.
Tasks distribute themselves
Desk, accounts, introduction meetings. Every task has a person and a deadline; none is collectively owned.
Everything is ready
The introduction page sits in the space, the accounts are confirmed, the buddy is on record.
The flow closes
The end-of-onboarding conversation is a task. Once it has happened, the item is closed and stays traceable.
The apps behind it. All in the same space, no second tool.
Registry carries the directories, Automation the flows, Docs the templates and Time the effort wherever it gets billed.
Registry
Asset and infrastructure management for IT teams, with custom fields per directory.
Automation
Workflows without code, triggered by events from any app.
Docs
The wiki for your team's knowledge, with version history and export to PDF, DOCX and Markdown.
Time
Time tracking and billing, directly on tasks and projects.
Connected to your line-of-business systems. Six connections from everyday process work.
People data from the HR system, documents into accounting, files on the drive, meetings in the calendar, campaigns in the marketing system.
One product, one vendor. Directory, flow and approval belong together.
A business process needs data, steps and agreement. In Collabase all three sit in the same product instead of spreading across a directory, a board and an inbox.
One contract, one contact, one roadmap.
No marketplace and no third-party add-ons to run.
Operated in a Swiss data centre or on your own hardware.
Questions from the business side. Five that come up in almost every first conversation.
Can we plug in electronic signatures?
A signing service can be connected through the HTTP integration; a ready-made integration is not included today. Which service you use is something we check during the proof of concept.
How does a reminder before a deadline work?
A date field in the directory is the trigger. The automation notifies the responsible person at the lead time you choose, or creates the task straight away.
Is Collabase suitable for personnel data?
The data sits in a Swiss data centre or on your own hardware, and access follows roles and directories. The legal position is set out on the sovereignty page.
Can people without an account submit something?
Submissions from outside can be taken in through the HTTP integration; the entry becomes a work item in the responsible space. How far that may be opened depends on your operating model.
Can approvals have several stages?
Yes, with order, roles and a deadline per stage. Every stage stays traceable on the work item.
Evidence for the compliance review
Information security is certified to ISO 27001 and processing meets the nFADP and the GDPR. The documents are ready before you ask for them.
Other disciplines in the same system.
Test it against your own content.
A proof of concept is ready within days.
We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.