Project management built for hospitality teams.
Plan an opening, a menu launch or an audit with Kimchi. When the project is finished, it becomes procedures and a template you start the next one from.
From the plan to the procedures it leaves behind.
Describe the work, Kimchi drafts the plan
An opening, a menu launch, an audit. Say what it is, add the documents you already have, and Kimchi proposes the tasks and their subtasks. Nothing is created until you confirm it.
Every task has a name, date and owner
Each task carries an owner, a due date, a priority and a status. Blocked is a status you can see, not a surprise you find out about.
Questions go on the task
Comments and updates live on the task they are about, with the activity under them. The question about the supplier is answered where the task is, not in a group chat.
Watch it land
Every project on one list with its locations, its target date and how far along it is. A halfway check is a glance, not a status meeting.
When a project is done, Kimchi writes the procedures
Kimchi turns the finished tasks into SOPs, one per department, and saves the plan as a template. Next time, you start from what worked.
Why a rollout lands here and not in a spreadsheet.
Rollouts that land.
Roll out a new standard to twenty locations and see exactly who followed it.
Owned, not assumed.
Every task has a name and a date against it.
Update the standard without breaking the flow.
Not another tool people forget to open on Tuesday.
It ends as a procedure, not a folder.
The finished tasks become SOPs and the plan becomes a template, so the next opening starts from the one that worked.