Work · In-house system
An operations system that keeps clients, tasks and responsibilities in one place.
Kolosseum's own operations software. A client and its contacts form one account, every task has a named owner, visibility follows role and client, and every change leaves an audit trail. Development continues module by module.
In production
Kolosseum Atrium
- Owner
- Kolosseum, internal use
- Our role
- Definition, architecture, build and testing
- Status
- In production, ongoing development
Starting point
Client work, tasks and decisions easily scatter across email, calendars and separate tools. Then it is hard to see who owns what, what the client was promised and who changed what.
Who it is for
Kolosseum's own client work and day-to-day operations.
Our responsibility
Kolosseum owns the whole system: definition, architecture, data model, build and testing. Every change passes automated checks and review before it goes into use.
Use path
From client account to task and audit trail.
How an account, a task and its owner move through the system.
- 02.1AccountAn organisation and its contact person are joined into one client account.
- 02.2TaskA task is created on the account and given a named owner.
- 02.3VisibilityRole and client-level access decide who can see the account and the task.
- 02.4ActionBefore a change, the system checks that the user is allowed to perform that specific action.
- 02.5Audit trailThe change is logged, and the log supports a controlled audit export.
Shown with example data.
Kolosseum Atrium
The system
Data structure
Client and contact are separate records joined into an account. Tasks link to the account and to their owner, and every change leaves an audit trail.
Access
Visibility is limited by role and client, and permitted actions are checked on every change. Changes and controlled audit exports are logged.
Current use
In production in Kolosseum's own operations.
Ongoing development
Development moves module by module, and each module goes into use once it has passed its checks.
Kolosseum Atrium
Highlights
- 04.1Access, ownership and the audit trail designed into the structure from the start.
- 04.2Every change passes automated checks and review.
Work
Other work
In-house system · In production
Notion CRM
The data behind sales and partnerships: segmentation, qualification, source and verification, contact status and message history.
Shown with example data. Client project · In production
Tikkituote ERP
A custom ERP for a client. In sales, customer, contact, quote, approval and order run as one path.
Own product · Pre-launch development
Finance software
A pre-launch product for Finnish companies. Every figure stays tied to its source, and every suggestion waits for a person's approval.
Contact
Need a system like this?
Tell us how the work flows today. You get a proposal for a scoped first phase.
Opens in your email as a ready draft.