Capture the booking
An administrator or manager selects a customer and configured service, then records the date, time and work details.
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.

Real software behind the product direction. Real workflows behind the design.
LESS FRAGMENTATION. MORE FLOW.
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.

PRODUCT
The operational foundation is implemented.
Broader Keikora platform in development
An operations user creates the booking with a customer, configured service, date, time and work details.
Employee time intervals inform the calendar and manual or triggered rule-based assignment checks.
A customer record connects contact details, bookings, job logs and invoice counts.
Booking events, configured email updates and invoice PDFs keep the administrative record connected.
EXPLORE THE IMPLEMENTED SYSTEM
Source-derived screens with synthetic data.
Keikora styling, not live product access.
Visible in the operational work queueIllustrative views of connected records, not a live transaction.
Today’s and upcoming bookings sit alongside change requests, inquiries, messages and recurring requests.
Review a pending booking, then open its details or assign an employee.
Today’s bookings and the requests that need attention.
Demo employee 1 · 15 October
Requested: 09:00–15:00Review service requirements
Review before generating the series
Reply and track the conversation status
HOW IT WORKS
Different people. One operational record.
A workflow derived from the implemented system. Scroll to follow the work
An administrator or manager selects a customer and configured service, then records the date, time and work details.
An administrator or manager selects a customer and configured service, then records the date, time and work details.
Employees save available time independently of bookings. Operations sees those intervals alongside booked time in the calendar.
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.
Assigned bookings appear in the employee’s upcoming-work view with service, time and relevant customer details.
Employees record mileage and notes; operations manages booking status. Invoice PDFs use booking details and can be prepared separately when needed.
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
A shared data model connects the interfaces, rather than giving each task its own isolated record.
Create and review bookings, manage customer records, coordinate assignments and prepare invoices.
One connected bookingPublish availability, see assigned work, and record mileage and notes for the jobs they carry out.
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
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.
Create bookings, compare available time and assign an employee.
Supply availability and see assigned upcoming work.
Keep customer records and prepare booking-linked invoice PDFs.
Where it began, and where the product could go
OUR STORY
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.


The broader product direction emerging from that software
Broader platform in developmentTHE DIRECTION IS SIMPLE
Connected operationsBooking records, employee time and administration are connected in the originating software. Invoices use booking details; specialist accounting tools remain separate.
OUR PRODUCT PHILOSOPHY
Keep the information needed for the next operational decision in context.
Availability informs assignment. The booking connects the customer, employee and service.
Use explicit assignment rules and configured notifications, while retaining operational controls.
A CLEAR DIRECTION. AN HONEST START.
Implemented does not mean commercially released.
Here is what exists, what is unfinished, and what we’re exploring.
Booking administration, customers, availability, calendar and assignment.
Email, Telegram alerts and Google Sheets mirroring. Configuration-dependent.
Bookings and employee availability appear together in the operations schedule.
Adapt business-specific service rules for more local service teams.
Explore public booking and a more configurable service catalog.
BUILD THE NEXT CHAPTER WITH US
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.
FOLLOW THE CONNECTED WORK