Floture
WorkbenchWhere your company flows: policies, onboarding and HR answers in one intranet, with AI search.
The problem
Floture is for the people who keep a company running: HR and People Ops, internal comms, IT and managers, and the employees who need answers from them. Distributed teams most of all.
People teams spend hours answering questions they’ve answered before. Onboarding gets stitched together from email, Slack, a shared doc and hope. And pages go stale while policies go out of date.
What we’re trying
One intranet for the whole company: announcements, a people directory and org chart, documents, versioned pages and policies, the handbook, policy sign-offs, surveys, and 90-day onboarding journeys.
Press Cmd+K to search everything, or ask the AI assistant, which answers with links to the pages it used.
It runs on Cloudflare, and the plan is one Worker, database and storage bucket for each company. It’s live on a test site with a made-up 23-person company for demos. Next: spotting policies that contradict each other, reviews for stale pages, forms and approvals, and a weekly digest.
What we’ve learned
Practical beat abstract. The line that stuck is “Where your company flows.”
We went through five stacks in seven weeks: WordPress blocks, a WordPress theme, Next.js for a day, plain HTML on a Worker, then React. That’s where it stayed.
A green check in GitHub Actions doesn’t mean the front end deployed. A TypeScript error can stop the Pages build while the Worker still ships.
When an editor library crashed, we swapped it the same day.
A 16-page browser test turned up 22 problems. Seven fixes later, 31 browser tests pass.
From the log
Stage changes, launches and the things that broke. We write it all down.
Read the whole logFloture clears its test findings
A 16-page browser test found 22 problems. The fixes are merged and deployed.
Floture finds its line
“Where your company flows.” Practical beat abstract.
Onboarding journeys
First-90-days plans for new hires, with a timeline, a builder and manager assignments.
Floture learns to search
Cmd+K search, and an AI assistant that answers with its sources.
Floture goes live on a test site
Automatic deploys and single sign-on, on a test domain.
Floture moves to React
The front end is rebuilt in React, and the older ones are retired.
Floture leaves WordPress
A fresh start on Cloudflare: a front end on a Worker, with its own database.
WikiHRO becomes Floture
The first dashboard blocks, and a new name.
Where it’s headed
- Napkin
Sketch it
An idea on paper, a problem worth chasing. Nothing built yet.
- Workbench
Build it
The crew is building. Not public yet, but the log is.
We’re here - Sea trial
Test it for real
Real people are using it. Expect rough edges, and tell us about them.
- Set sail
Ship it
It graduates into an Awesome Cause product, with support behind it.
- Scuttled
Or stop it
Any stage can end here, on purpose. The log says what we learned.