Skip to content
Kolosseum, home
EnglishSuomiSvenska

Contact · Espoo, Finland

Tell us what has to work.

Bring a spec, an existing system or a problem nobody has solved yet. You get a straight answer on whether Kolosseum is the right builder and what the first step is.

Contact

Request a proposal.

Describe the need briefly and attach a spec or tender document if you have one. You get an assessment of how to deliver it and a proposed first phase.

Three questions to start with

  1. 01.1What should be built, replaced or connected?
  2. 01.2Who uses it, and what has to run faster or more reliably?
  3. 01.3Which systems, data, deadlines or constraints are involved?

Request a proposal

ops@kolosseum.eu

Opens in your email as a ready draft.

Jami Ojala answers every request personally.

Find Jami on LinkedInSupplier profile

Jami Ojala · Founder · Software, web & AI

Contact

Three ways to start.

A first engagement can be a scoped review or a full system delivery. Every engagement is priced against a written scope before work starts.

  1. Technical review or fix

    Typical situation
    A system or integration is struggling, a new system has to be chosen, or a tender needs a technical assessment.
    What we need from you
    A description of the problem, access to or screenshots of the current system, and who decides what happens next.
    What you get
    A written assessment of what is wrong or what is worth building, the options and a recommended next step. A scoped fix is done at the same time if agreed.
    Scope and price
    A fixed price or an agreed cap on hours before work starts.

  2. Phased system delivery

    Typical situation
    You need a new system, are replacing an old one or are joining several systems into one working whole.
    What we need from you
    A process description or spec, the user groups, current systems and data, and the timeline constraints.
    What you get
    A scope, a phased delivery plan, working software phase by phase, documentation and handover.
    Scope and price
    Priced per phase against the written scope. Each phase is accepted before the next begins.

  3. Support and ongoing development

    Typical situation
    The system is in use and has to stay healthy and keep improving, often over several years.
    What we need from you
    Access to the system and its documentation, and a shared view of what is critical.
    What you get
    Service at the agreed scope: fixes, updates, small improvements and planning of further development.
    Scope and price
    A monthly fee for the agreed service or a block of hours. Larger changes are scoped separately.

Contact

What ongoing service covers.

The content of the service is written into the agreement. This is the typical split.

Typically included

  1. 03.1Bug fixes within the agreed response time.
  2. 03.2Monitoring and applying dependency and security updates.
  3. 03.3Small improvements within an agreed number of hours.
  4. 03.4A regular status review and prioritisation of the backlog.

Agreed separately

  1. 03.5Large new features and integrations.
  2. 03.6Service hours, response times and backup arrangements.
  3. 03.7Infrastructure and third-party licence costs.
  4. 03.8On-call cover outside service hours.

Request a proposal