Questions about eventman, answered straight

It is early, and we would rather say so. The pipeline, the checklist, the crew, the money and the client page are built and in daily use by the mobile bar business it was built alongside — which pays for it, and that is the nearest thing we have to a reference. If you want something that has been running for ten years, this is not it yet.

If your work happens on a date, at a site, with people and gear that travel, probably. Nothing about bars is built into the software: what your clients choose from is a catalogue you define, and the checklist every new event starts with is one you write. A caterer, a hire company and a bar run on the same thing configured differently.

Import it. Getting your existing bookings in is a file upload, not a migration project. People switch in the quiet months and want it done in an afternoon, so that is what it is built for.

No. Crew logins are free and always will be. Charging per login for a business that runs on casuals is the one thing we set out not to do.

Not yet. It records what was agreed, what was invoiced and what has actually been paid, and exports all of it. Taking card payments is on the list once the rest has proven itself.

Not in this version. When there is, the rule is already set: it reads and drafts, a person sends. Nothing goes to your client that one of your people has not read.

In Australia. Each business has its own database, so yours is kept apart from everyone else’s by design rather than by a setting. You can export everything, any time, as CSV.

Nothing. No contract, no notice period, and your data comes out in the same formats it went in. Software that is hard to leave is software that has stopped trying.