Customers and applicants
Submit a request, send documents, pay and check progress.
Products / operational systems
Digital products for customers and teams.
We build systems around your workflow: requests, orders, documents and services. Every action has an owner, a history and a next step.
Discuss a productCustom development. Capabilities and rollout scope are defined after discovery.
Users
Shared data, different tasks
Staff
Process the queue, verify data and assign the task.
Management
See workloads, unfinished actions and workflow status.
Municipal workflows
A resident service and an operator workspace
We connect the resident-facing service with public-service delivery and existing accounting.
- RequestsData, documents, an assignee and statuses.
- Payment and notificationsCharges, payment results and the next step.
- Data exchangeExisting systems, checks and error correction.
Applied product / beta
SKPP: video-stream analysis
SKPP analyses video streams to produce staff activity reports. The project, supported by FRiO, is in beta testing.
A pilot requires sample data, an event list and evaluation criteria. Suitability and limitations are established using the actual material.
Pilots and researchHow we launch the first release
- 01
Workflow
Participants, actions and the service outcome.
- 02
First release
One complete scenario and acceptance criteria.
- 03
Data
Sources, APIs, migration and reconciliation.
- 04
Launch
Tests with users, instructions and the next phase.
Questions
Before we start
Are these ready-made products or custom development?
Systems for customers and staff are designed for a specific process. SKPP is a separate applied development project in beta. For each area, we define available capabilities, terms of use and implementation scope separately.
Can we keep our existing accounting system?
Yes, if it supports the required exchange. We check the available interfaces, data format and constraints. This determines which functions stay in the accounting system and which move to the new product.
How is staff access organised?
We agree on roles and permissions to view, create and change data. We separately define administrative actions and report access rules. The system checks permissions when operations are performed.
What is needed to discuss an SKPP pilot?
A description of the work process, a sample of available video data, the expected report contents and validation criteria. After reviewing the task, we can define the experiment's scope and required conditions.
Can the product be implemented in stages?
Yes. The first release should cover the agreed workflow in full. Roles, reports and connections can then be added. This approach requires data compatibility and participants' work during the transition to be defined in advance.
Which workflow are we building?
Tell us who starts the work, who carries it out and where the data is stored.
Discuss a product