Loading page
The Ojas ecosystem
Every page here publishes what this software does not do yet, in full and without burying it. This is the record of which of those lines stopped being true, quoting the limit as we published it and what replaced it. It is past tense only: nothing here is a plan, a date or a promise.
We saidIt doesn't have a browsable directory of venues, caterers or decorators to choose from yet — you bring the vendors, Ojas runs the day.
Nowfrom directories on this site and send a quote request from a vendor's own page without an account
Browse the vendor directoryWe saidA campaign ROI / cost-per-lead dashboard (every lead's source is logged today; the reporting view is pending)
Nowthen sit beside the orders actually attributed to that spend
What the platform claims vs what you bookedWe saidOjas runs the event, the capture and the deal pipeline. Matchmaking is run by your team through the CRM today — automated buyer↔supplier matching isn't shipped.
Nowa solver allocates the pairings across the whole floor, maximising useful conversations inside each side's meeting caps and the venue's capacity
How a sourcing show runsWe saidLater · The Venture Blueprint — package a working events operation (playbook, catalogue, supply, brand) into a design you deploy in one purchase.
NowStart a venture from a published Blueprint in your console and the whole thing is built for you
What a Blueprint deploysAn entry is only allowed if the limit was published here before it was fixed. That rules out the flattering cases on purpose. If we shipped something we never admitted was missing, it does not appear here — this is not a list of features. And if we discovered our own copy was out of date and corrected it, that does not appear either: the product had not moved, our description of it had.
Which means the only way this page grows is if we keep being specific about what is missing. That is the trade, and it is deliberate.