Work

Proof of execution

Real operations, real constraints, real outcomes — and the systems built from them.

Real operations

Hospitality

Cadet Residence

Problem: Guest stays, access, follow-up, payments and reporting were spread across files, calls and front-desk memory.
System: A clearer operating flow for guest follow-up, access, issues and reporting, supported by Ops Core workflow structure.
Outcome: 7.6 → 9.2 / 10 guest satisfaction · ~10h/week admin work reduced
Status: Real operation

Logistics

Kepler Express

Problem: Mission follow-up, driver costs, invoicing and payments moved separately, making daily control harder.
System: A logistics workflow system connecting mission status, cost capture and billing.
Outcome: +50% revenue in a new operating segment
Status: Real operation

Built systems

Hospitality / PMS

Product in development

StayOps Core

Problem: Small hospitality teams need reservations, rooms, balances, housekeeping and daily blockers in one focused workspace.
System: A hospitality operations system connecting reservations, rooms, housekeeping, incidents and operational visibility in one focused workspace.
Outcome: Demo product. No real hotel, guest or payment data is implied.
Status: Product in development

View system Open StayOps

Business operating system

Prototype

MyBi

Problem: Client work, project progress, invoicing and payment follow-up are difficult to control when they live in separate places.
System: A business operations OS connecting clients, missions, invoices, payments and revenue visibility.
Outcome: Prototype workspace for testing clearer payment follow-up, client concentration and activity visibility.
Status: Prototype

View system Open MyBi

Logistics / internal tools

Operational workflow system

Kepler Ops / internal tools

Problem: Operational teams need mission status, cost capture, invoicing and payment movement visible in one flow.
System: Internal tooling shaped around Kepler Express operating logic and logistics follow-up.
Outcome: A visible workflow for connecting executed work, costs and billing.
Status: Field-tested internal system

View workflow Open Kepler

Concept explorations

Retail

Concept exploration

StorePilot

Problem: Retail operators need daily execution, exceptions and margin signals in one operating layer.
System: A concept product for store-level visibility and operational control.
Outcome: Concept exploration used to test retail workflow and margin visibility logic.
Status: Concept exploration

Service operations

Internal prototype

Ops Core

Problem: Tasks, blockers and follow-up lose momentum when ownership is unclear.
System: An internal prototype for task ownership, blockers and status tracking.
Outcome: Prototype logic for making operational work easier to see and run.
Status: Prototype

Explore products & systems