gobuso
[ FOR EVENTS AND CREW STAFFING ]

Get the kit back after the show.

Your crew chiefs already load the van and unload it again. The problem is that the unloading happens at two in the morning with whoever is left, and by Monday a radio and two stands are gone with no event to pin them to. Describe how your company runs and you get the tables, the forms, a phone app for the bay and the reports, already filled with events and crew like yours.

Build yours, freeSee how it runs
NO CARDNO REAL DATA NEEDED
[ THE PROBLEM ]

Every tool you tried made you work its way.

Somebody had to retype every name and certificate before it did anything at all, and that job never got finished. The big suite was too rigid, the build-it-yourself tools were too empty, and you went back to the spreadsheet that at least already had everything in it.

Gobuso starts from the other end. Your files first. Then a plan in plain English you can change. Then working software, the same day.

0
staff to retype before it works
4
questions, then it builds
1
afternoon from your files to working software
1
set of data under every tool you add
[ START FROM ONE OF THESE ]

Pick the one that costs you the most. It builds it now.

No sign-up and no data of yours. It designs the tables, builds the app and fills it with a company that looks like yours.

“Staffing each event is arranged ad hoc”Build this →“Kit goes out and does not all come back”Build this →“Incident reports are written days later”Build this →“Client sign-off is verbal”Build this →“Cost per event is never clear”Build this →
[ HOW IT RUNS ]

From one sentence to the number you needed.

Five moments, in order. Nothing here is a mock-up of a different product: it is the same builder the button above opens.

STAGE 01

One sentence, typed by the owner.

[ WHAT DOES YOUR COMPANY DO, AND WHAT DO YOU NEED TO FIX? ]

We run 2 to 5 events a week with a pool of 90 casual crew. Kit goes into a van on Friday and comes back out by whoever is left. By Monday a radio and two stands are gone and no event owns them. Kit goes out and does not come back.

EventsSecurityRestaurantsFacilities
Build it →
No form to fillShe describes the purchase order she signed on Monday. No template.
Four questions, then it buildsThe trade chip is the only thing she taps. The rest it works out.
STAGE 02

It says what it will build, then opens it.

THE DRAFT · 4 TABLES · ~40 SECONDS
Kit Movements
THE RECORD · 2 FORMS
Events
so a venue and its dock times are stored once, not per item
Kit
so one item keeps one history, event to event
Crew and the roles they are booked for, set up for you and ready to edit
KIT MOVEMENTS · 22,400 RECORDS
Kit Movements
EventItemOutBack
Harbour LightsRadio × 1218 SepAll 12
Harbour LightsLED bar × 818 SepAll 8
Kilbeggan FairRadio × 1013 Sep2 short
Dockyard LaunchSpeaker × 411 SepAll 4
Plain English firstNothing exists yet. Type crew confirm before the load-out and it rebuilds.
Separate on purposeKit stands on its own, so one radio keeps one history across events.
STAGE 03

The crew chief counts it back in at the bay.

KIT MOVEMENTS / KILBEGGAN FAIR
Check the kit back in
Nkechi, on a phone, at the loading bay · 01:40
Event
Kilbeggan Fair
Went out
10 radios
Came back
8 radios
Condition
One handset cracked
Crew chief signature
→ 2 SHORT · LOGGED AGAINST THIS EVENT
Her form, not everyone’sFour fields, at the bay, at twenty to two in the morning.
The shortfall lands somewhereTwo radios short, against this event, before anyone goes home.
STAGE 04

Every item lands on the event that took it.

EVENTS / KILBEGGAN FAIR · 2026-09-13
Kilbeggan Fair

Every line out to this event

31 LINES
Radio × 102 short
LED bar × 6All back
Speaker × 4All back
Stand × 121 damaged
Not a message in a groupA record with a history behind it. That is how a loss gets a cause.
The finding shows itselfTwo lines short on one event, both off the same late load-out.
STAGE 05

And the losses have an event beside them.

WHAT DID NOT COME BACK, AND FROM WHERE?
€3,410

of kit lost or damaged this quarter.

Before this, it turned up as a purchase order in March.

Kilbeggan1,980
Harbour820
Dockyard410
Other 24200

Most of Kilbeggan is radios off one load-out with no crew chief on the bay. That is a rota, not a theft problem, and she would have staffed the bay.

Chosen before it was builtShe said what she needed to know in stage one, so the report already exists.
It shows its workingEvery number opens into the load-outs behind it, with the crew named.
[ WHAT CHANGES ]

What actually changes on Monday.

Four years of crew bookings in messages
SUITERetype 90 crew before day one
GOBUSOUpload it as-is, review what it read
A festival and a launch load differently
SUITEOne kit list for both
GOBUSODescribe each one, read it back, change it
The loading bay is underground
SUITEShe writes it on the kit list again
GOBUSOFill offline, syncs when she surfaces
A client queries what was delivered in August
SUITEGo and find the kit list
GOBUSOOpen the event, read its history
[ COMMON QUESTIONS ]
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. Upload the kit lists, the crew pool and the scanned client sign-off sheets exactly as they are, and you check what it read before anything is saved.
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.
[ GO BUILD SOMETHING ]

Build your first one
this afternoon.

Four questions, a plan you can read and change, then working software.

Build yours, freeStart for free