openmasu
solutions · technology
One base for launches, feedback and accounts, shared with your agents.
Plan each release across product, marketing and sales, turn bug reports and feedback into linked records, and see customer accounts next to their synced Stripe subscriptions. Agents in Cursor, Codex or Claude Code work on the same base over MCP.
- Launch timeline shared by product, marketing, sales
- Bug and feedback intake through a public form
- Stripe subscriptions synced every 15 minutes
| Summary | Type | Priority | Launch | Reported | Status |
|---|---|---|---|---|---|
| Export to CSV times out on large tables | Bug | High | v2.4 Reports | Oct 15 | In progress |
| Dark mode for the dashboard page | Request | Low | v2.5 Themes | Oct 9 | Planned |
| SSO login loops on Safari | Bug | Urgent | v2.4 Reports | Oct 17 | New |
| Weekly digest is confusing | Feedback | Medium | v2.5 Themes | Oct 3 | Done |
| API rate limit header missing | Bug | Medium | v2.4 Reports | Oct 12 | In review |
Everyday workflows
One launch plan for product, marketing and sales
Each launch links to its tasks, and every task has a team (Product, Marketing, Sales), an owner, a start and a due date. A timeline view lines up the release across teams, and a Gantt view with dependencies shows that the blog post waits on the docs. A filter «Status is not Done and Due is before today» lists what's late.
Bug and feedback intake
Put a form link in your app's help menu: summary, steps, type, email and a URL to a screen recording. Every submission arrives live as a new record in a triage kanban stacked by status. Engineers link it to the launch that fixes it and @mention the reporter's account owner in a comment.
Customer accounts with Stripe subscriptions
Connect Stripe and OpenMasu syncs Customers, Subscriptions, Invoices, Payments and Products into their own base every 15 minutes, read-only. Add your fields next to the synced ones, like «Health» rating or «Plan notes», and they're never overwritten. Group subscriptions by status to see who is past due this week.
Coding agents on the same base
Connect Cursor, Codex or Claude Code to the MCP server with a token limited to one workspace. The agent reads open bugs with query_records, updates their status when a fix lands, and adds release notes as records. Its edits show up live and are marked in history with the token's name, and undo reverts its own session.
Views & structure
Key views
- Launch timeline Every team's tasks laid out from start to due date.
- Release plan Task dependencies, so blockers are visible before launch day.
- Report a bug Public intake link; each submission becomes a feedback record.
- Triage Bugs and requests stacked by status; drag as they move.
- Past due subscriptions Synced Stripe subscriptions filtered and grouped by status.
Recommended fields
- Launch (Link to another record) Connects tasks and feedback to the release they belong to.
- Type (Single select) Bug, request or feedback, each with its own color.
- Team (Multiple select) Product, marketing, sales: one task can involve several.
- Recording (URL) Link to the screen recording or log wherever it lives.
- Ticket (Autonumber) A stable number to reference in commits and comments.
- Days open (Formula) DATETIME_DIFF(TODAY(), {Reported}, 'days') to spot stale reports.
Your agent over MCP
OpenMasu exposes a remote MCP server with 55 tools. Point Claude Code, Codex, Cursor or ChatGPT at it and your agent can build tables, triage feedback and update records with your token's permissions, while the team watches the changes arrive live.
query_records update_records create_table create_view aggregate_records
Ship your next release from one base
Plan the launch, open a feedback form, sync Stripe and connect your coding agent.