Skip to content
looma

Software studio

Internal systems that get finished, then actually used.

Most enterprise software projects fail not because the system was never built, but because it was finished and then abandoned. Looma builds internal AI and business web apps that are handed over complete — documented, trained on, and used.

Services

Two kinds of work, both finished.

Selected work

What we have built.

How we work

Four stages, and the second is the most decisive.

  1. 01

    Map the problem

    We start from the problem, not the technology: which rules are scattered, which procedures are unread, which repeated work is still manual. This mapping is free.

  2. 02

    Written scope

    The agreement is written before the code is: what will be built and — just as important — what will deliberately not be built.

  3. 03

    Build with regular review

    One person builds it directly and shows progress regularly, so the project does not drift off course.

  4. 04

    Full handover

    The system is handed over with documentation, brief training, and full access to the code. A maintenance retainer is offered, never required.

What we do not do

Limits we state up front.

Not an outsourcing provider

We take on scoped projects, not supplying staff for an indefinite period.

No project without a written scope

Projects without a written scope tend to balloon and never get delivered. We do not take them.

No 24/7 support

No promise of midnight support. A retainer provides monitoring and fixes, not full stand-by.

A sole proprietorship

Looma is run by one person. Procurement that requires a registered company needs to be discussed first.

Discuss your needs

Tell us the problem. If it is not our field, we will say so.

The first reply contains questions, not a sales pitch. If your problem does not fit the work we do, we will tell you.

Discuss your needs