Kumiko Studio
How an engagement works

You describe the process. We deliver the running application.

No requirements document, no project that drags on for months. We start with what costs you time today and deliver in small, verified steps. Every step has a clear sign-off on your side.

  1. 1
    30 minutes, free of charge

    Show us the process

    You show us how it works today: the Excel list, the form, the mail chain. We ask who decides what and where it gets stuck. At the end we tell you plainly whether software makes sense here and what the first version should contain.

    You get
    One page with the scope of the first version, the timeline and a fixed price for the build.
  2. 2
    2 to 4 weeks

    First version

    We build the application in Kumiko Studio: your data, your roles, your checkpoints. Sign-in, permissions, files, notifications and history come with Kumiko. From day one the application runs on your own address with its own database.

    You get
    Access to the application with your master data, to try out with your team.
  3. 3
    with your team

    Acceptance

    Your team works with it and we refine it. Whatever is missing or should work differently, you write down directly as a request. The application only goes live for everyone once you have accepted it.

    You get
    An accepted version, training for the first users, takeover of your existing data.
  4. 4
    ongoing, monthly

    Operations and changes

    We host, back up and monitor the application and keep it on the current Kumiko version. Change requests always follow the same path: request, proposal, approval, live.

    You get
    A running application and a fixed contact person. No price per user.
One change, step by step

“Calibration interval for calipers: 6 instead of 12 months.”

  1. Mon 09:10 · Q. Lehmann, QA

    Request

    Written directly in the Studio, the way you would tell a colleague.

  2. Mon 11:40 · Kumiko Studio

    Proposal

    We present the change in words and as a preview: which gauges are affected, which due dates move.

  3. Mon 14:05 · Q. Lehmann, QA

    Approval

    You approve or write back. Without approval nothing happens.

  4. Mon 14:07 · Release 15

    Live

    Verified, delivered, documented in the history. If needed, back to release 14 with one click.

What is verified before every version

Show us your process.

Discuss our process