Workspace — AI command center v1
Natural-language queries across every module, grounded citations, reviewable action chains.
Most vendors show you a roadmap under NDA, in a slide, once, in April. Ours is a URL you can send to your board. It's updated as we ship, and it's honest about the difference between committed work and things we currently think are a good idea.
What we're actively building.
Natural-language queries across every module, grounded citations, reviewable action chains.
Half-fields, sheets, courts as first-class sub-spaces with inherited availability rules.
Threaded replies landing in a shared inbox per department; assign, resolve, audit.
A shareable URL per event with directions, schedule, teams, brackets, and contact.
Committed for the upcoming quarter.
Two-way SMS with the same targeting as email; per-org sending numbers.
Scorecards, multi-evaluator averaging, tiered placement, offer letters.
Approved action chains that run on a schedule (e.g., Monday morning balance reminders).
Rent open ice or field time to outside groups with automatic holds and payment collection.
Per-program installment schedules with dunning, retries, and family-visible balances.
On the horizon. Directions, not dates.
A focused mobile app for coaches (roster, schedule, attendance) and parents (schedule, balance, messages).
Cross-org reporting and standings for leagues that sit above multiple clubs.
Read-write API for the organizations that want to build on top of OrgFrame.
Starting with French-Canadian and Spanish; every surface translatable, every email multi-lingual.
One directory, nested programs and divisions, role-based access. The foundation every other module reads from.
Per-team, per-facility, and per-person views with conflict detection and public subscribe links.
Conditional logic, saved-in-progress submissions, Stripe-native checkout, approval flows.
Self-serve Connect onboarding; orgs own their Stripe accounts; payouts and reporting in-app.
Paste any export; AI proposes field mappings, flags duplicates, previews before commit. Transactional rollback.
Block-based editor with live data blocks (schedule, staff, registration) and custom domains.
Then tell us, because this list is shaped almost entirely by partner organizations arguing with it. Being wrong early is cheap. Being wrong in October is not.