Membership business software
Kimura
A conversation on the mats became a working product.
My coach was describing the work it took to run the gym. I started asking questions. That conversation became Kimura: one system for the front desk and the work behind it.
Open Kimura
What was happening
The problem behind the product.
Check-ins, memberships, waivers, billing, ranks, events, and family access all touch the same people. When those jobs live in separate tools, the coach becomes the connection between them.
My role
I listened to the workflow, shaped the product, designed and built the application, connected payments, and launched the live service.
What I built
- 01Fast class check-ins and attendance
- 02Memberships, billing, and waivers
- 03Ranks, events, households, and parent access
- 04A staff console for everyday gym operations
What this work demonstrates
- 01Finding the product inside a real conversation
- 02Turning connected business rules into one clear system
- 03Taking a product from idea to a live, supported service
Current state
Kimura is live with public pricing, account creation, and a working product experience.
Have a problem like this?
Tell me how the work happens now.
A rough description, screenshot, or screen recording is enough to start.