Loading page
One catalogue for the whole platform, filtered to what applies to ojas.events. The page also publishes what the software does not do yet, in full and without burying it.
5 capabilities
Buying and deploying a Blueprint works; publishing your own is still not a shipped path.
We saidLater · The Venture Blueprint — package a working events operation (playbook, catalogue, supply, brand) into a design you deploy in one purchase.
Ventures · blueprints
What a Blueprint deploysOpenings, applicants and applications are managed in the console, with interviews, scorecards, offers and talent pools served by the backend.
People and work · ats
Billing configuration, invoices and commission schedules are managed in the console; subscriptions, usage and settlements are served by the backend without a screen traced for each.
Money and books · billing
A nightly reconcile builds task flow and project health facts that feed dashboards and metrics; the package serves no route of its own.
People and work · work-analytics
Timesheets are managed from the console; the time-log routes behind them were not traced to a screen of their own.
People and work · worklog
Live means a route, a screen and the data behind it are all reachable today. Live in part says what is and is not covered. Coming soon only appears with the work package that owns it, and any quarter shown is a target, not a promise. Not started carries no date.
Where a row replaces a limit we once published, it quotes that limit as we wrote it and dates the day the capability became reachable.