Supplier profile · Espoo, Finland
Kolosseum as a supplier.
Kolosseum on one page: who contracts, who is accountable for delivery, what is already built and how the work continues after handover.
Kolosseum
Company and contact
- Public name
- Kolosseum
- Contracting party
- Impact Node Oy. Kolosseum is an auxiliary company name of Impact Node Oy.
- Business ID
- 3624870-2
- VAT number
- FI36248702
- Registered office
- Espoo, Finland
- Contact person
- Jami Ojala, founder. Accountable for architecture and delivery.
- Services
- Business systems · Websites & digital services · Integrations & AI automation
- Working languages
- Finnish and English
- Contact
- ops@kolosseum.eu
Download the supplier profile (PDF)
The same content on two pages, ready to attach to procurement documents.
Contact person
A named owner of the delivery.
Jami Ojala is accountable for the architecture and delivery of Kolosseum's engagements. He is the client's direct contact from scoping to handover.
The specialists a project needs are named before work starts. Their roles, responsibilities and available time are written into the scope, and overall accountability for the delivery is Kolosseum's.
The team is sized to the scope and length of the engagement, multi-year agreements included. Team members and their onboarding are agreed as part of the delivery plan.
Supplier profile
Delivery model.
The same model applies to a scoped review and to multi-year development. The size changes; the line of responsibility does not.
Scope
A written scope: goal, deliverables, acceptance criteria, timeline and price.
Phases
The build moves in visible phases, and each phase is reviewed in working software.
Acceptance
Each phase is accepted against the agreed criteria before the next begins.
Handover
The system, documentation and user guidance are handed over as agreed, and users are onboarded.
Continuation
Support and further development continue at the agreed scope and response times.
Supplier profile
Continuity, built in.
Documentation, version control and agreed approvals keep the system manageable for its whole life.
Documentation
Technical decisions, the data model, access rights and operating guidance are written down so another developer can carry on the work.
Version control
The source code and its change history are always handed over to the client. Depending on the project, they live in the client's own version control from the start or move there at an agreed stage, and ownership is set out in the agreement.
Approval
Changes reach production only after the agreed approval, and every release can be traced back to version control.
Handover
The system is handed over with guidance, and the client's access to its own data and environments is agreed.
Support responsibility
Who fixes what, how fast and within which service hours is written into the agreement.
Backup
An engagement can have a named backup person, onboarded to the system and its upkeep.
Work
What is already built.
In-house system · In production
Notion CRM
The data behind sales and partnerships: segmentation, qualification, source and verification, contact status and message history.
In-house system · In production
Kolosseum Atrium
Clients and contacts, owned tasks, shared access control and an audit trail in one application.
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 more for your procurement?
Send the tender documents or your questions. You get the answers in writing.