Worked example — a central kitchen
One kitchen cooking for several outlets. Which flows does it actually need?
Connect a few flows and the kitchen runs leaner — demand and stock stay in sync, staff and pay are handled, and bots take the busywork. The colour tells you what to switch on first: green is core (you can't run without it); gold-dashed is value-added (optional — turn it on when it pays for itself, like delivery APIs).
Inventory & supply
People & HR
Automation — bots
~6 core flows run the whole kitchen. Everything else — delivery APIs like Lalamove and Grab, an online store, payroll, AI bots — you switch on only when it earns its place. That's the point: not 100 features, just the few that connect into one efficient kitchen.
User & Access
Who gets in, how they prove it, and what they can do.
User management
FlagshipThe full invite-to-active journey on one trail — happy path, every negative branch, and four-eyes approval.
Secure login
Every login runs IP rate-limit → lockout → credentials → device check, all audited.
Team & roles
Invite teammates with scoped roles; capability matrix gates who can read, write, and report.
Commerce & Ops
Orders, stock, and the data pipelines that keep them in sync.
Sale → inventory
Place an order; line prices lock at sale time, inventory decrements, sale lands in purchase history.
Shopify sync
Resumable queue/worker sync pulls Shopify records, maps fields, lands them downstream idempotently.
Bulk import
FlagshipUpload, auto-map columns, validate every row, preview a zero-write dry-run — then commit, deduplicate, audit, and notify.
People & HR
Paying, rewarding, and directing the team.
Payroll run
FlagshipDraft a run, compute every payslip, get a different person to approve, pay — then notify each member.
Commission rules
Define basis per member, accrue against real orders, feed the summary into payroll.
Goals & tasks
Assign KPI goals and work tasks to members, evaluate against live orders, track to done.
Growth & Messaging
Reaching customers and handling what comes back.
Campaign launch
Create a campaign, activate it, apply codes at checkout, track every redemption — role-gated throughout.
Customer broadcast
Compose a message, target a segment, preview recipients, send — tracked across in-app and email channels.
Customer inbox
One feed merges system notifications and customer threads; reply, assign, resolve — with read receipts.
Governance & Trust
Approvals, evidence, receipts, and the trail no one can rewrite.
Four-eyes sign-off
FlagshipA maker requests, a different checker approves — separation of duties enforced in the API guard, a DB CHECK, and an append-only trail.
KYC review
FlagshipRegister, upload ID, pass document review — every file checked for what it really is, every decision on a record nobody can change.
Insurance / employee claim
FlagshipFile a claim through a guided wizard; a person reconciles it, a certificate is issued, the handoff is emailed — locked after you declare.
Secure certificate
FlagshipSize, MIME, and magic-byte verified before any byte is stored; SHA-256 over the bytes; a QR certificate anyone can verify offline.
PDF receipt
Turn a settled payout or sale into a verifiable PDF receipt — rendered, hashed, stored where it can't be altered, then delivered.
Audit trail
Every mutation writes exactly one audit row; UPDATE/DELETE blocked for everyone, exportable under Object-Lock.
Data/AI & Platform
Agent-driven control, grounded AI, and live dashboards.
Agent-operable
FlagshipAn AI agent drives the system over MCP with a scoped token — and is still stopped at the four-eyes gate. Operable is not trusted.
AI onboarding
FlagshipAI is fuel, not a science project — buy it cheap, pour it into tools that already work, keep the gates.
Ask-your-data AI
Answers from your real records, with sources — and it says so when there's nothing to find.
Role dashboard
KPI cards, trends, and donuts that change with the viewer's role, period, and currency — via one injected adapter.