Start from one of these
Pick the one that costs you the most. It builds it now.
What changes
The same week, with and without it.
| When | The tool you have | Gobuso |
|---|---|---|
| Four years of crew bookings in messages | Retype 90 crew before day one | Upload it as-is, review what it read |
| A festival and a launch load differently | One kit list for both | Describe each one, read it back, change it |
| A client queries what was delivered in August | Go and find the kit list | Open the event, read its history |
Questions
What events owners ask before they start.
Our crew are casual and they change every week.
Which is the reason the form is four fields. Anyone who only fills it in needs no training session: the crew chief opens the load-out, counts, and signs.
Do we have to barcode 1,410 items first?
No. It counts lines, the way a kit list already does: ten radios out, eight back. That is enough to tell you which event lost them. Tagging individual items is a job you can do later, on the kit that is worth it.
We already have four years of data.
That is the starting point, not the obstacle. Import the spreadsheets you keep as they are: each one opens with every doubtful cell marked, and nothing is added until you have seen it.
What if the AI gets it wrong?
It will, sometimes. That is why nothing is saved until you have read it and said yes. Checking its work is a step in the product, not an afterthought.