openmasu
solutions · operations
Run requests, vendors and inventory from one base the whole team trusts.
Take every request through one public form, move it across a kanban board, and keep vendors, assets and stock linked in the same base. Everyone sees the same numbers, updated live, without chasing spreadsheets.
- Public form that turns answers into records
- Kanban board of request status
- Vendors, assets and stock linked together
| Request | Category | Vendor | Needed by | Cost | Status |
|---|---|---|---|---|---|
| Replace 2nd floor printer | Equipment | Northside Office Supply | Oct 24 | $640 | Approved |
| Laptop for new hire | IT | Brightline Tech | Nov 3 | $1,450 | Ordered |
| Fix meeting room AC | Facilities | Coolair Services | Oct 21 | $280 | In progress |
| Restock coffee and snacks | Supplies | Northside Office Supply | Oct 23 | $190 | New |
| Badge access for contractors | Facilities | Oct 30 | $0 | Waiting |
Everyday workflows
One front door for every request
Share a form view of the «Requests» table as a public link. Anyone fills in what they need, the category and a «Needed by» date, and each answer lands as a new record the moment it's sent. No inbox to triage: new requests show up live in the ops team's grid, sorted by date.
A status board the team works from
A kanban view stacks requests by «Status»: New, Approved, Ordered, In progress, Waiting, Done. Drag a card when it moves. Use an @mention in the record comments to ask the requester for details, and check the field-by-field history to see who approved what and when.
Vendors linked to the work they do
Keep a «Vendors» table with contact email, phone, website and a «Reliability» rating. Link each request to its vendor, and every vendor record lists its requests automatically. Group the requests grid by vendor and let the summary bar total the cost of what you see.
Inventory that tells you when to reorder
In «Inventory», track «On hand» and «Reorder at» as numbers and add a formula, IF({On hand} <= {Reorder at}, "Reorder", "OK"). A saved view filtered to «Stock is Reorder» becomes your weekly shopping list. Assets get their own table with serial number, location and a «Warranty ends» date on a calendar.
Front-desk sales next to operations
If you take card payments with SumUp or Stripe, connect the integration and your sales and payouts sync into their own base every 15 minutes. OpenMasu only reads them. Add your own «Reconciled» checkbox or notes beside the synced fields; they are never overwritten by the sync.
Views & structure
Key views
- Form A public link anyone can use to send a request; each answer becomes a record.
- Kanban See every request by status and drag it forward.
- Grid Filter by category or vendor and total costs in the summary bar.
- Calendar Plan deliveries, maintenance and warranty end dates by day.
Recommended fields
- Status (Single select) Colored stages that become the kanban columns.
- Vendor (Link to another record) Connects requests and assets to the supplier behind them.
- Needed by (Date) Sort and filter the queue by what's due first.
- Cost (Currency) Lets the summary bar total spend for any filtered view.
- Stock (Formula) Compares on-hand quantity with the reorder point.
- Request # (Autonumber) A stable reference number to quote in comments and chats.
Your agent over MCP
Connect your own agent (Claude, ChatGPT, Codex or Cursor) over MCP. Ask for spend totals by category or vendor, find stale requests, or bulk-update stock after a count. It works with your token's permissions and its edits show up live and in history.
aggregate_records query_records update_records upsert_records
Give your operations one source of truth
Create the base, share the request form and run the queue from a kanban board.