How It Works

From business signup to live restaurant operations.

Crimini starts with the owner creating a business workspace, then moves through setup, onboarding, scheduling, and daily service.

Kitchen team coordinating service

Built as a launch path, not just a dashboard

The owner sets the business foundation, managers configure operations, employees join through onboarding, and the team runs service from one workspace.

| Business workspace || Employee onboarding || Daily operations |

Guided Walkthrough

Preview the path from setup to daily use

Manager dashboard with workspace controls

Workspace launch (1/7)

Owner workspace

After signup, the owner lands in a business-scoped workspace where admin setup begins.

Workflow

Three practical launch phases

Manager dashboard overview

Step 01

Create The Business Workspace

Register the restaurant and create its isolated app environment.

  • Enter owner and business information
  • Choose plan path
  • Create the first owner or manager account
Schedule builder interface

Step 02

Configure The Operation

Turn on the app areas the business needs and set the operating structure.

  • Set business profile, logo, and enabled features
  • Build departments, roles, lists, menus, recipes, and docs
  • Install or customize the onboarding packet
Employee homepage with shift info

Step 03

Invite Staff + Go Live

Bring employees into the workspace and start running the restaurant through Crimini.

  • Send employee invites
  • Review completed onboarding packets
  • Publish schedules and run daily execution from the homepage

First Week

A clean first-week rollout

Day 1

Workspace setup

  • Register business details
  • Set branding and feature visibility
  • Create departments and roles

Day 2-3

Employees + scheduling

  • Install onboarding packet
  • Invite staff
  • Build and publish first weekly schedule

Day 4-7

Daily operation

  • Move lists, docs, recipes, and menus into the app
  • Use tasks and updates daily
  • Connect monitoring when hardware is ready

App Areas

What the business controls and uses

  • Workspace Setup Business profile, branding, feature visibility, departments, roles, and tenant-scoped records.
  • Employee Launch Invites, account setup, onboarding packet requirements, and admin review.
  • Scheduling + Labor Schedule builder, publishing, My Schedule, availability, time off, shift offers, swaps, and approval.
  • Daily Execution Homepage, tasks, prep, checklists, inventory, orders, docs, recipes, menus, specials, and announcements.
  • Monitoring + Reports Temperature readiness, vendors, history, exports, and operational review.

FAQ

Common questions

  • Does each restaurant get its own workspace? Yes. Each business workspace keeps its users, schedules, documents, uploads, and app settings separate.
  • Can owners control which features show up? Yes. Managers can enable or hide app areas so the workspace matches the business needs.
  • How do employees join? Managers send an invite. The employee creates their account, completes the assigned onboarding packet, and then uses the app once approved.
  • What onboarding packet items are included? The base packet includes personal information, emergency contact, payroll setup, I-9, W-4, state withholding when available, handbook acknowledgement, and policy acknowledgement.
  • Can we launch before sensors are connected? Yes. Scheduling, onboarding, lists, docs, menus, recipes, tasks, and communication can launch first.
  • Can we start small and add more later? Yes. Workspaces can begin with core operations and expand with temperature monitoring and deeper workflows over time.

Rollout Notes

Launch scope

  • The owner account creates the business workspace first.
  • Employee onboarding is controlled from admin after workspace setup.
  • Temperature systems can be connected after the core app is running.
  • Store billing and mobile store release remain part of the final production launch path.

Ready to launch the workspace?

Create the business, configure the app, onboard staff, and move daily execution into one clean flow.