Developed from real service operations

Bookings meet availability.
Work gets coordinated.

Administrators and managers create booking records, compare booked time with employee availability, and assign the work. Employees see their assigned jobs. This operational foundation exists; the broader Keikora platform is in development.

Built in Oulu. Broader platform in development.
Orchestrating service work.
Booking recordAvailable timeAssignmentAssigned work

Real software behind the product direction. Real workflows behind the design.

Implemented operational foundationAdmin, manager and employee workflowsConnected work recordsRule-based assignment support

LESS FRAGMENTATION. MORE FLOW.

A booking doesn’t
end at the calendar.

An administrator or manager captures the customer, configured service, occupied time and work details. Employee availability gives operations the context to assign it.

The implemented system connects those pieces. A booking is part of the operation, rather than another note to copy between tools.

A calendar, work checklist and employee view linked by a blue and teal ribbon.
People, time and work details. Connected.

PRODUCT

One booking.
More than a booking form.

The operational foundation is implemented.
Broader Keikora platform in development

01

Capture → coordinate

An operations user creates the booking with a customer, configured service, date, time and work details.

Customer & serviceBooking record
02

Availability → assignment

Employee time intervals inform the calendar and manual or triggered rule-based assignment checks.

Available timeAssigned work
03

Customer → ongoing work

A customer record connects contact details, bookings, job logs and invoice counts.

Customer recordBookings & record counts
04

Booking → administration

Booking events, configured email updates and invoice PDFs keep the administrative record connected.

Booking recordEvents & invoice PDFs

EXPLORE THE IMPLEMENTED SYSTEM

Different views.
The same connected work.

Source-derived screens with synthetic data.
Keikora styling, not live product access.

FOLLOW ONE FICTIONAL RECORDDEMO-101 · Demo customer AHome cleaning · 12 October · 09:00–11:00

Visible in the operational work queueIllustrative views of connected records, not a live transaction.

Administrator · Manager

Start with the work that needs attention.

Today’s and upcoming bookings sit alongside change requests, inquiries, messages and recurring requests.

Implemented

Review a pending booking, then open its details or assign an employee.

Operations workspaceDemo administratorOperations view

Welcome, Demo administrator!

Today’s bookings and the requests that need attention.

Today’s bookings
View all →
09:00– 11:00
Demo customer AHome cleaningDEMO-101 · Service location withheld
Demo employee 1Confirmed
12:00– 16:00
Demo customer BMove-out cleaningDEMO-102 · Service location withheld
UnassignedPending
14:00– 16:00
Demo customer CTextile cleaningDEMO-103 · Service location withheld
Demo employee 2Confirmed
09:00– 11:00
Demo customer DHome cleaningDEMO-104 · Service location withheld
Demo employee 3Confirmed
09:30– 10:30
Demo customer ETextile cleaningDEMO-105 · Service location withheld
UnassignedPending
Pending requests
Demo queue
Availability change

Demo employee 1 · 15 October

Requested: 09:00–15:00
Pending
Property inquiries

Review service requirements

Pending recurring bookings

Review before generating the series

Contact messages

Reply and track the conversation status

Upcoming bookings
View all →
13 October09:00–11:00Demo customer FHome cleaning · Demo employee 2Confirmed
Based on implemented screensRecreated UI · synthetic data · Keikora styling

HOW IT WORKS

One booking.
Connected operations.

Different people. One operational record.
A workflow derived from the implemented system. Scroll to follow the work

IMPLEMENTED WORKFLOWStep 1 of 5
DEMO-101Home cleaningDemo customer A · 12 October · 09:00–11:00
OPERATIONS

Capture the booking

An administrator or manager selects a customer and configured service, then records the date, time and work details.

CustomerDemo customer AServiceHome cleaningOccupied time09:00–11:00
Pending booking
Illustrative record story · not live product actions
01
OPERATIONS

Capture the booking

An administrator or manager selects a customer and configured service, then records the date, time and work details.

CustomerDemo customer AServiceHome cleaningOccupied time09:00–11:00
Pending booking
02
EMPLOYEE → OPERATIONS

Connect employee availability

Employees save available time independently of bookings. Operations sees those intervals alongside booked time in the calendar.

Demo employee 108:00–16:00
Available timeDEMO-101 · 09:00–11:00
Saved employee availability covers this booking’s occupied time.
Availability recorded
03
OPERATIONS

Assign and confirm the work

Operations triggers checks for active employees, time coverage and conflicts with a 15-minute buffer. Lower priority rank wins; ties use daily workload, then name. No eligible employee means the booking needs attention.

Employee 1Covers 09:00–11:00 · no conflict · priority 1Eligible
×Employee 2Existing work at 10:00–12:00Conflict
Employee 3Covers the time · no conflict · priority 2Eligible
Example result: Employee 1Assigned · Confirmed
Confirmed when assigned
04
EMPLOYEE

Give employees their work view

Assigned bookings appear in the employee’s upcoming-work view with service, time and relevant customer details.

Demo employee 1 · Upcoming jobs
12 October · 09:00–11:00Demo customer A · Home cleaning Relevant customer details stay with the assigned work.
Assigned work visible
05
EMPLOYEE + OPERATIONS

Keep the operational record

Employees record mileage and notes; operations manages booking status. Invoice PDFs use booking details and can be prepared separately when needed.

Mileage & notesEmployee recordsBooking statusOperations controlsInvoice PDFPrepared when needed
Records stay connected

One fictional booking illustrates these relationships. Availability is recorded independently; assignment is triggered by operations, and invoice preparation is a separate action.

PRODUCT DEPTH, WITHOUT THE COMPLEXITY

Built around the operation.

A shared data model connects the interfaces, rather than giving each task its own isolated record.

OPERATIONS

Administrators & managers

Create and review bookings, manage customer records, coordinate assignments and prepare invoices.

One connected booking
CustomerServiceTimeEmployeeStatusJob logInvoice
WORKFORCE

Employees

Publish availability, see assigned work, and record mileage and notes for the jobs they carry out.

Availability informs calendar & assignmentBooking links events, job logs & invoice PDFs

Role-based interfaces, shared records and application logic form the implemented foundation. Public customer booking and broader service configuration remain future product direction.

FOR BUSINESSES

For teams that coordinate
bookings, people and time.

Built first around a cleaning-service business: operations creates bookings, employees provide availability, and work gets assigned. Adapting those workflows for more service businesses is in development.

Operations

Create bookings, compare available time and assign an employee.

Employees

Supply availability and see assigned upcoming work.

Administration

Keep customer records and prepare booking-linked invoice PDFs.

Where it began, and where the product could go

Cleaning services

Originating environment

Property maintenance

Product direction

Installation teams

Product direction

Repair services

Product direction

Home services

Product direction

Small field-service teams

Product direction

OUR STORY

Built around the work.
Shaped in Oulu.

Keikora didn’t begin as a theoretical SaaS idea. It grew from software built around the day-to-day operations of PuhdasFix, a local cleaning-service business in Oulu, Finland.

Booking administration, employee availability, assignment and customer records became parts of one operational system. The software connects the work instead of treating each task as a separate tool.

Keikora is the product direction emerging from that work. The foundation exists; adapting its business-specific workflows for more local service businesses is the next step.

Oulu, Finland See the implemented views
REAL SERVICE BUSINESSPuhdasFixOriginating cleaning-service business · Oulu, Finland
IMPLEMENTED OPERATIONAL FOUNDATIONBookings & customer recordsAvailability & employee assignmentAssigned work & invoice PDFs

The broader product direction emerging from that software

Broader platform in development

THE DIRECTION IS SIMPLE

Less scattered.
More connected.

DISCONNECTED WORKFLOW
Phone callsMessagesSpreadsheetCalendarPaper notesSeparate customer records
IMPLEMENTED OPERATIONAL CONNECTIONS
Connected operations
BookingsCustomersAvailabilityAssignmentsCalendarInvoices

Booking records, employee time and administration are connected in the originating software. Invoices use booking details; specialist accounting tools remain separate.

OUR PRODUCT PHILOSOPHY

Software should remove admin,
not create more of it.

Clarity in everyday work

Keep the information needed for the next operational decision in context.

Connections that matter

Availability informs assignment. The booking connects the customer, employee and service.

Automation with a purpose

Use explicit assignment rules and configured notifications, while retaining operational controls.

A CLEAR DIRECTION. AN HONEST START.

Built foundations.
A clear next chapter.

Implemented does not mean commercially released.
Here is what exists, what is unfinished, and what we’re exploring.

01Implemented

Operations

Booking administration, customers, availability, calendar and assignment.

02Implemented

Communication

Email, Telegram alerts and Google Sheets mirroring. Configuration-dependent.

03Implemented

Calendar

Bookings and employee availability appear together in the operations schedule.

04Product direction

Broader platform

Adapt business-specific service rules for more local service teams.

05Exploring

Customer experience

Explore public booking and a more configurable service catalog.

BUILD THE NEXT CHAPTER WITH US

Help shape Keikora.

Keikora is growing from implemented service-business software. We’re exploring how that foundation can serve more local teams. If you coordinate bookings, people and customer work, we’d like to hear about your working day.

Start a conversation.
No sales pitch. Just a better understanding of your working day.

This opens your email app. You choose when to send. Read our privacy information.

FOLLOW THE CONNECTED WORK

See how the operation connects.
Help shape what comes next.

Join early access Explore Keikora