IMtech

Service

SaaS products

We build products used by many companies or people: accounts and groups, roles, apps for phone, browser and desktop, and preparation for release in the app stores. We also build our own products — Vatra for venues and Flowi for projects, finance and health — and bring that experience to yours.

Animation: the product's core sits in the centre, with modules for different customers around it and data constantly moving between them.

When you need it

Situations that bring people to us for this service.

  • A system for one doesn't scale

    The product was built for one customer, and for the second everything has to be copied.

  • Customers need different roles

    Each company has its own people and permissions, and the system doesn't separate them.

  • Different devices

    Users work from phone, browser and desktop — and expect everything to sync.

  • App stores have their requirements

    Without a privacy notice and an account deletion page, release won't get through.

What's included

  1. Product discovery

    Who the product is for, which roles there are, what's shared by all customers and what's configurable.

  2. Accounts and groups

    Account owner, group members joining with a short code, an administrator.

  3. Roles and permissions

    A role builder and the same rules on every screen.

  4. Every device

    Apps for phone, browser and desktop with sync and offline work.

  5. Release

    Preparation for the App Store and Google Play, a privacy notice, an account deletion page.

  6. Product page

    A description of the product for customers and a form to become one.

  7. R&D partnership

    Industry knowledge from you, development from us; rights shared, by contract.

What you get

  • A description of the product, roles and account model
  • A prototype of the key scenario
  • Apps for the devices you need
  • Release materials
  • Code and documentation that are open to you

The project path

From the first conversation to daily use

Every step ends with a decision: go on or stop. We don't start the next one until the previous one has given its answer.

  1. 01

    Getting to know the task

    You describe the process and what gets in the way. We reply by email with questions and arrange a call.

  2. 02

    Discovery

    We study the process with the people who work in it and write down what the system must change and how we will check it.

  3. 03

    Prototype

    We build a working prototype of the key scenario to test the idea on real data rather than on polished screens.

  4. 04

    Pilot

    We run the system in your real environment with agreed outcome criteria and a deadline. After the pilot we decide together whether to go further.

  5. 05

    Launch and growth

    We bring it to daily use: reliability, access rights, links to other software, documentation, support. Then we develop it based on user feedback.

Systems where we have already done this kind of work.

Technology in these case studies

  • Expo
  • React Native
  • Next.js
  • Django
  • Tauri
  • WebSocket
  • Apple Health
  • Google Calendar

Questions about this service

Have you built your own products?

Yes: Vatra, a system for venues whose apps are being prepared for release on the App Store and Google Play, and Flowi, a prototype already used every day.

Can we build a product together?

Yes, that's an R&D partnership: industry knowledge and market access from you, development from us. Rights are shared; terms are set case by case and fixed in a contract.

Where does a product start?

With discovery and a prototype of the key scenario on real data — to test the idea before building everything.

Have a project with no ready-made solution?

Describe it in a few sentences: how things work today and what gets in the way. We reply by email with questions on the next business day.

Get in touch