In the words they get asked in, answered without hedging. If something you need is not here, ask us and we will add it.
Pricing is set against what the system actually saves you. Founding customers establish that baseline with us during the engagement, and terms are locked for a defined period afterward. We’d rather agree a number we can both defend than publish one we can’t.
Minutes, not a six-month project. Venues come in from their addresses, spaces and departments come in from lists you already keep, and the catalog carries over between events. There is no configuration phase you have to finish before anyone can do anything useful — founding customers get walked through the setup with us, but it is a call, not an implementation.
It replaces the spreadsheets and email threads that departments use to request material. It sits alongside finance and ERP systems, and alongside whatever you use for scheduling people. It is not trying to be your ERP.
It stays yours, and you can export all of it in an open format at any time — during the event, at closeout, or two years later. The catalog carries over to your next event, which is usually the point at which the second event costs less than the first.
Receiving and counting work on a phone in the places where connectivity is bad, and sync when the signal comes back. Planning and approval assume a connection.
Department heads asking for what they need, one or two planners deciding, and procurement reading the consolidated list. On site, crew chiefs receiving deliveries. Most people touch it a few times a week; the planners live in it.
If your question isn't here, this is the fastest way to get it answered by the person who built the thing.
Not ready to be contacted? Just send me the overview — email only, nothing else.