eventuley VS JavaScript Tutorial

eventuley's answer

Every feature is on every plan, including the free one — financial reporting, inventory, multi-currency and export included. The limits are on active events, seats and contacts, not on capability, so you pay for scale rather than for features being unlocked.

The free plan is not a trial. One active event, one seat, 100 contacts, no card, no countdown. Complete the event and start the next, indefinitely.

It was built from a real events team's operations workbook, read line by line, rather than from a feature list. The five failures the site describes came out of that file: business profit and per-event profit drifting apart because some costs belong to no event, a utilisation metric computed against expected instead of actual revenue, money kept as decimals and rounding away, a "most profitable event" label with no formula behind it, and an equipment sheet with headers and no rows. A data model can make those impossible; a grid of cells cannot.

Money is held as whole minor units with the currency's own number of decimal places, so yen and dinar are both correct — never an assumed two. Every ISO 4217 currency and every IANA timezone are supported, and an event shows in its venue's timezone with the zone named, not in yours.

eventuley's answer

Price and model, and both are published rather than demo-gated.

Pro is USD 19/month for 5 seats and 10 active events. Planning Pod's comparable tier is USD 74 for 10 events, HoneyBook Essentials is USD 59 for 2 seats, and the general-purpose tools people otherwise assemble — Notion, Airtable — are per seat, so a five-person team pays USD 50–100/month before anything is configured. Curate does not publish a price at all.

It is also one product rather than an assembly. Guest list, tasks, money and equipment sit in the same data model, so headcount and per-event profit are worked out from the records instead of typed into a summary tab twice.

Data is hosted in the EU, export is on every plan including Free, and a workspace that lapses becomes read-only rather than closed — so cancelling never locks you out of your own records.

eventuley's answer

Small teams — one to ten people — who run events as their business: supper clubs, pop-ups, workshops, tastings, and independent caterers and venues.

They are past the point where one spreadsheet works and well short of needing enterprise event software. Typically they run a handful of events at a time, handle their own guest lists and money, own equipment that leaves the building and has to come back, and work from a phone in a kitchen as often as from a laptop at a desk.

eventuley's answer

It started with somebody else's spreadsheet.

A working events team shared their operations workbook — the real one, with permission — and it was read line by line rather than skimmed. It was a good spreadsheet. It had still failed in eight specific ways, and the interesting part was that none of them was a discipline problem: each was something a spreadsheet cannot make impossible. Costs that belong to no event have nowhere to sit. A metric gets computed once against the wrong denominator and stays wrong. A label gets made and the formula behind it never does.

eventuley is those failures turned into a data model. The workbook itself is not published and never will be — it contains real guests' names and contact details — but the shape of each failure is written up at eventuley.com/writing.