We run the floor of your event.

Ohh-Snaps builds and runs the layer that moves people through a real place — a venue, an expo floor, a multi-stage site, a museum, a district. Guests scan a code on their own phone and the page written for that spot opens in their browser.

Built for venues, museums, CVBs, conventions, seminars, corporate teams and planners. It is bought on its own and it does not need anything you already run to be taken out. Weddings and private events are still bookable.

Scan opens the stop in the browser

9:41Camera

go.ohh-snaps.com

East Hall · Stage 3
Stage 3 — what is here

The page written for this spot — text, photos, audio and video — opened by the code on the stage flat. We change it and the next scan shows the new version.

TextPhotosAudio & video
Where we work

The part of an event that happens on foot.

Ohh-Snaps works on the floor itself. Codes go on placards, plinths, stage flats, doors and windows; a guest scans the one in front of them and gets the page written for that spot. The whole thing is built around moving people around a building.

Anchored to a placeCodes live on placards, plinths, stage flats, doors and windows. What a guest sees is tied to where they are actually standing.
Movement is the pointA tour and a hunt are both built around a route through a physical site: the stops are places, and the order is a decision made when it is built.
Nothing to installA code opens a web page in the browser already on the phone. No app download, and no account — unless a prize hunt needs a verified email to sign in.
Enter anywhereEach stop has its own code, so a guest can start at the one in front of them. A hunt can also be set to a strict order when the route has to be followed.

What Ohh-Snaps does not do.

No registration, no ticketing, no badge printing, no agenda, no attendee directory, no matchmaking, no sponsor portal. It is bought on its own, for the floor, and it does not need anything else taken out to work.

It does not need anything else put in, either. A tour or a hunt runs on its own.

What we run

The structure we build around a site, and the two formats in the product.

A guided tour and a scavenger hunt are the two things the software runs. A program is the structure we assemble out of them for a site — we build it and we maintain it by hand; it is not a button in the product.

Delivered by us · Program

The guest gets what is happening where they are

Not a feature. A program is how we arrange a site’s tours and hunts into one structure and run it. The software has no umbrella object, so the assembly is our work.

This is the shape for a site with several things happening at once — a convention hall, a festival, a campus, a seminar day with parallel tracks. We decide what gets its own code, what sits behind each one, and how a guest gets from one to the next.

  • One code and its own content per stage, hall or building
  • A site-wide view listing what is where
  • Guests can end up holding more than one link — today that assembly is manual on our side
  • Built, published and maintained by us; nobody on your side logs in
Request a quote for a program
In the product · Guided tour

We decide the order

Guided. A sequence of stops — stop one, then stop two — that leads the guest through the place in a set order.

This is the format for a story with a shape: a historic district, a museum route, a campus orientation, a factory or facility walk-through, a donor tour. Each stop is a code on a placard, a plaque or a window.

  • Stops carry text, photographs, audio narration and video
  • Each stop has its own code and its own page
  • Guests move at their own pace and can leave and come back
  • It stays published until we unpublish it — that switch is ours, not yours
  • Content stays correctable: a closed exhibit is a text change, not a reprint
Request a quote for a tour
In the product · Scavenger hunt

The guest is racing

Competitive or casual. A set of clues to find, recorded as they are found, with a finish time.

This is the format for when the goal is coverage — getting attendees to the corners of the floor, past the exhibitors at the back, into the rooms off the corridor. Play can be competitive, scored and ranked, or casual, with no leaderboard and no ranking.

  • Players join from their own phone, one player per phone
  • A live leaderboard view for a lobby screen or a projector
  • Competitive play ranks by clues found, then by finish time
  • A clue already found is rejected on a re-scan, and scans stop when the session’s access window closes
  • We start, pause, resume and end the session while it runs
  • A companion trivia format where a hunt does not fit the room
  • Prize play with a verified email sign-in, with the scoring, tie-break and anti-cheat rules specified
Request a quote for a hunt

Not sure which one? The question that usually settles it: should your guests be walked through something in a set order, or go hunting for it? If the site has several things running at once, the answer is usually both, arranged into a program.

A recent event

One program per stage. One more across all of them.

At a recent multi-stage event, a client used Ohh-Snaps as the program itself rather than as an add-on to one. Every stage got its own program — the lineup for that stage, what was happening there now, what was coming next — reachable from a code on the stage itself.

Then one more sat over all of them, listing every stage and what was on at each. Walking to another stage and scanning the code there brought up that stage on its own again.

It was the client’s idea, not ours. We assembled it by hand out of the pieces the product runs — there is no umbrella feature behind it — and it is the pattern we now propose first for a site with more than one thing happening at once.

The shape of it

  • One code per stage, at the stage
  • That stage’s own lineup behind each code
  • One more spanning every stage
  • Guests moved between them by walking
  • No app, no sign-in, no kiosk
  • Assembled and maintained by hand, by us
How we deliver

We build it, and we are the ones operating it while it runs.

Done-for-you is how we work, and this is exactly what it covers, so you can hold us to it. It is not offered here as something rare.

1

We map the site

The route, the stop and clue locations, where signage can physically go, and where phone signal reaches.

2

We write and build it

Stop copy, clue text, audio and video, the programs and the codes themselves. You review it and mark changes. Nothing goes live until you have signed off on the content.

3

We test the codes

Every code is scanned on a real phone before an attendee sees it, and the page it opens is checked rather than assumed.

4

We run it while it is live

We start the session, watch it while it is live and handle what comes up. For hunts that includes running the board and calling the finish.

What that changes for your team.

The technology is only worth talking about because of what it takes off the people running the day.

  • Nobody on your side operates software

    No admin training, no seat to assign, nobody from your team logging in. We hold the controls.

  • No hardware to buy, charge or store

    Attendees use their own phones, and a stop is a printed code. There is nothing on our side of the arrangement for you to rent, charge, store or account for.

  • Nothing to install

    A code opens a web page in the browser the guest already has. There is no app-store step between the code and the content.

  • You choose where the stops go

    The back of the hall, the upper level, the room off the corridor. Where the codes go is a placement decision you and we make together, not something the software works out.

  • The content stays correctable

    A moved session, a closed exhibit, a re-routed path — we change the content and the next scan shows the new version. The code on the wall does not have to be reprinted.

  • You get back the numbers that exist

    A tour records a view count per stop. A hunt records who joined, which clues each player found and their finish times. That is what the product measures today, and it is what you would get for a post-event report.

Also from Ohh-Snaps

Weddings and private events.

The guest photo experience is still here, still supported and still bookable. A code on the table, a private gallery that fills as guests upload to it, and the files afterwards.

Same platform — it is simply no longer the front door. If you are planning a wedding, a milestone birthday or a private party, start here.

Enquire about a private event

  • Private event gallery
  • Guest photo and video uploads
  • Unique QR code per event
  • Snap Station photo booth
  • Themed photo overlays
  • Digital guest book
  • Voice message recording
  • No app for guests

Common questions.

We already have an event platform. Does this replace it?

No. Ohh-Snaps does not do registration, ticketing, the agenda, the attendee list or sponsor tooling, and it is not sold as a replacement for anything. It is the layer that works on the floor — it moves people through the site and gives them something to do between sessions.

Do our attendees have to download anything?

No. Every guest-facing surface is a web page. Scanning a code opens it in whatever browser the phone already has, which is why there is no install step and nothing for your IT or security team to approve on the attendee side.

What is the difference between a program and a tour?

A tour is a format in the product: a set sequence of stops, each with its own code. A program is not a feature — it is the structure we build for you out of tours and hunts when a site has several things running at once. We assemble it and we maintain it; you will not find a program object if you log in.

Who writes the content — us or you?

We do, working from your material and your subject-matter people. You review and sign off before anything goes live. If you would rather supply finished copy and have us build around it, that works too.

Can we run more than one of these at once?

Yes. Several tours and hunts can run at the same time, across one site or more than one, each with its own content and its own codes. The scope for a given engagement is set in the quote rather than by a package.

What happens if a code stops working mid-event?

Tell us. The codes and the content are ours, so the fix is on our side and there is nothing for your team to file into a system they do not own. We have not set a published response time, so this page does not quote one.

Do you need power, wifi or hardware at each stop?

Not at the stops. A stop is a printed code, so it needs nothing but a surface to live on. Attendees do need enough mobile signal or venue wifi to load a page.

Do you still do weddings?

Yes, and we did not stop. The guest gallery, Snap Station, phone booth and guest book all still run, and private events are still bookable through the form on this page. The floor work simply leads now, because that is where the business is going.

Request a quote

Tell us about the floor and the day.

Every engagement is quoted. What the place is, how many people come and how much of it we are building all move the number, so there is no list price to publish and we are not going to invent one. Tell us the shape of it and we will come back with what we would build and what it costs.

Would rather write to us directly? info@ohh-snaps.com. Sending this form does not create a booking or a contract.