Platforms

Start with one module.
Add the next when it earns its keep.

You don't need a new stack. Turn on Time Tracking — clean exports, no Friday spreadsheet, no Slack threads about hours. Week two is a handbook in Documents & Knowledge Base . Day thirty is Riley, our AI assistant answering across both.

Time to value

What the first month actually looks like.

Not a feature list — an operator's first four moves.

Day 1
Turn on Time Tracking. Import the team from a CSV. Workers clock in on web or mobile, breaks deduct automatically, and managers approve in bulk before payroll runs.
Day 3
First timesheets approved. Payroll exports clean — one CSV, every line reconciled by default because the data was never separate. The Google Sheet someone’s been maintaining gets archived.
Day 14
Turn on Documents. Upload the handbook, the onboarding checklist, the PTO policy. Anyone on the team can find them without asking — searchable from web or mobile, no version-tracking spreadsheet required.
Day 30
Turn on Riley. Ask how many hours the team logged on a project. Riley answers, citing the time entries it pulled from.

Riley

How many hours on Project-4472 this week?

62 hours across three time entries, logged by Sam, Maria, and Devon. Want the breakdown by day?

Triggers, not tiles

Each row is an operational moment a small business actually has. The right column is what to turn on when it does.

You’re paying three people to track hours in three different places.: Time Tracking
You’ve written the same email six times explaining the same policy.: Documents & Knowledge Base
You want answers across projects, documents, and time data without building a report.: Riley
You’re onboarding franchisees and the process is in one person’s head.: Launchpad + Playbooks
Clients keep asking for status updates by email.: Platforms Portal
You outgrew the built-in fields for how your business tracks things.: Data Tables + Custom Fields