Free consultation — an honest read on what to fix first, whether or not you hire us.

Book yours

Featured case study

iBlast Photobooth

A mobile photobooth business with a strong product, a real portfolio and genuine reviews — all of it scattered across social posts. We designed and built a booking website around a single action: turning a scroll into a complete event inquiry.

Delivered byGen Digital Marketing
BuildStatic HTML, CSS & JavaScript
MarketDipolog City, Philippines

Overview

A booking business that lived entirely inside a social feed.

iBlast Photobooth rents mobile photobooths for weddings, debuts, birthdays, corporate functions and school events across Dipolog City, Dapitan City and nearby areas in the Philippines. The business had built a real reputation the way good local event businesses do — through referrals and guests at one event asking who did the booth at the last one.

What it did not have was an owned home online. We designed, wrote, built and launched a complete website: strategy and page architecture, conversion-focused copy, a custom front end, a guided inquiry system, portfolio and video presentation, an objection-handling FAQ, on-page SEO, and accessibility fundamentals. The site is live and in active use.

The challenge

The work was strong. The online presence wasn't doing it justice.

  • Everything lived on social media. Layouts, event videos, client feedback and pricing were spread across months of Facebook and Instagram posts. A couple planning a wedding had to scroll a feed to answer basic questions — and most won't.
  • There was no owned property online. Nothing to send a lead to, and nothing that could appear when someone nearby searched for a photobooth rental rather than already knowing the name.
  • Pricing questions consumed inquiry time. Every conversation restarted from zero: what's included, how long, how much, do you travel to my venue.
  • The inquiry itself was unstructured. A message reading "hi, how much po?" isn't a lead — it's the start of a five-message exchange just to establish the date and venue.
  • Booking terms surfaced late. The non-refundable deposit, the non-pausing package timer and transportation fees were all discovered mid-negotiation, where they feel like bad news instead of standard practice.

The approach

Three decisions shaped the entire build.

1. Don't fight the channel — feed it

iBlast's customers already book through Facebook Messenger, and it works well for them: fast, personal, and where Filipino event clients are comfortable. Replacing it with a web form would have added friction and cost bookings. So the site doesn't try to own the transaction. It structures the inquiry, then hands off cleanly to whichever channel the visitor prefers, with the details already written out.

2. Answer the money question before it gets asked

Package prices, inclusions, add-ons and the extra-hour rate are published on the page. Hiding pricing behind "message us for a quote" filters out serious buyers and wastes time on people who were never in range. Publishing it does the qualifying automatically.

3. Set expectations early, not late

The deposit terms, the package timer that doesn't pause, the transportation-fee policy, and the fact that an inquiry doesn't hold a date are all stated plainly on the page, before payment is discussed. Uncomfortable terms delivered upfront read as professionalism. The same terms delivered late read as a catch.

The live experience

The strategy, translated into a working website.

Everything above is the reasoning. This is what it actually became — captured from the live site, not from a design file.

The portfolio band inverts to near-black so the printed layouts carry the section on their own. Each card is labelled with the event type first and the celebration second, so a visitor scanning for their own occasion finds it without reading.

Video section: event clips play muted as they scroll into view, each carrying a poster image so nothing loads as an empty rectangle. Mobile menu: every route gets its own full-width row, sized for a thumb, and the panel closes itself on every route change.

What we built

A booking journey, not a contact form.

The centrepiece is a three-step guided flow — Event, Experience, Contact — that walks a visitor through exactly what iBlast needs in order to check availability: event type, date, preferred operation time, venue and city.

At the end, the visitor receives a tidy summary of their own details and three ways to send it. The message opens pre-filled. Their answers are also copied to the clipboard automatically, so if a device opens the app blank they can simply paste — a small detail that quietly rescues inquiries that would otherwise be abandoned.

1 · Event Type, date, time 2 · Experience Package, add-ons 3 · Contact Venue, city, name Structured summary MessengerPrimary channel SMSPre-filled message EmailPre-filled message 1 · Event Type, date, time 2 · Experience Package, add-ons 3 · Contact Venue, city, name Structured summary Messenger Primary channel SMS Pre-filled message Email Pre-filled message
The inquiry system: three guided steps produce one structured summary, which the visitor sends through whichever channel they already use. Their answers are copied to the clipboard at the same time, as a fallback.
01 — Event details
Only what iBlast needs to check a date. The transportation-fee note sits under the city field, so the caveat arrives while the visitor is thinking about location — not later in a negotiation.
02 — Experience
Package prices are repeated inside the selector, so nobody has to scroll back up to remember what they cost. The motif field is labelled as the thing the personalized layout is designed around, which quietly explains why it's being asked.
03 — Ready to send
The payoff. A formatted summary the visitor can read back before anything is sent, with Select all and Copy controls beside it — and the line “Nothing has been sent yet” doing the work that removes hesitation at the exact moment it appears.

Two details that matter more than they look

  • Answers persist. If a visitor leaves the page and returns, their progress is still there. Event planning happens in interrupted sessions.
  • The form is honest about what it does. "Submitting this form does not reserve or confirm your event date" appears at the step and again in the process section. It prevents the single most damaging misunderstanding in date-based bookings.

What we built

Published packages that qualify buyers automatically.

Three packages — 2, 3 and 4 hours — presented with the same seven inclusions and one variable: time. An additional-hour rate is published for events that run long.

Add-ons are listed as available on request and explicitly quoted separately, which protects margin without hiding the option. The high-angle photobooth is presented the same way — visible as a capability, quoted individually.

The structure does the sales work. Every package includes everything, so the only conversation left is duration — a far easier conversation than "what do I get for this price."

What we built

A portfolio that proves range.

At launch, twenty-one layouts and twelve gallery pieces, each labelled with the event type and the actual celebration. That labelling is deliberate: a university student-council officer looking for a school-event booth needs to see a school event; a wedding coordinator needs to see weddings. Generic "our work" galleries make every visitor do that translation themselves.

The screenshot above shows the presentation system. The layouts below are the creative work living inside it.

Video that plays where it counts

Six event clips play automatically as the visitor scrolls, muted by default, with a tap-to-unmute control. Photobooth is an atmosphere product: a still image shows a printed layout, but video shows a room full of people queueing and laughing.

What we built

An FAQ built from real objections, and a visible process.

At launch, eleven questions, each drawn from a genuine friction point in the booking conversation rather than invented for search traffic — what's included, whether an inquiry confirms a booking (it doesn't), the deposit amount and that it is non-refundable, when the balance is due, the deadline for changing event times, whether the package timer pauses (it doesn't), setup arrival window, transportation fees, print customization, digital copies, and outdoor events in bad weather.

Answering "no" clearly on the page is worth more than a soft answer negotiated later. It removes disputes before they exist and makes every "yes" more credible.

Alongside it, an eight-step process runs from inquiry through date verification, private payment instructions, deposit, confirmation, layout approval, final balance and event day. For a business asking strangers to send a non-refundable deposit for a date months away, a visible process is the trust mechanism — it says exactly what happens next and exactly when their money is at stake.

The eight-step process with a running counter and, next to it, the sentence that prevents the most damaging misunderstanding in date-based booking: an inquiry does not hold a date. Stating the non-refundable deposit here — before any money is discussed — is what makes the later request for it feel like procedure rather than a catch.
Eleven answers, and the first one expanded says “No.” Publishing the uncomfortable answers is what makes the comfortable ones believable — a visitor who reads a straight refusal here trusts the inclusions list further up the page.

Client feedback is presented with full names and the source noted, rather than as anonymous praise. Attributed testimonials from a platform anyone can go and check are worth several times an unattributed five-star quote.

Build & performance

Fast by construction, not by plugin.

The site is hand-built static HTML, CSS and JavaScript — no content management system, no page builder, no framework. Every figure below was counted from the site's own source code in August 2026.

Third-party JS libraries0
Video bytes before scroll0
Lazy-loaded images28
ARIA attributes117

What that means in practice

  • No framework, no jQuery, no animation library. Every interaction — the layout carousel, the scroll-triggered video, the multi-step form — is native browser code. Nothing is downloaded to make the page work that the browser couldn't already do.
  • Six event videos totalling roughly 15 MB, and none of it downloads until needed. Every clip carries preload="none" and a poster image, so a visitor who never scrolls to the video section never pays for it. On mobile data in a provincial market, that decision matters more than any score.
  • Images served in WebP throughout — 25 of them — sized for their display context and lazy-loaded below the fold.
  • Accessibility built in, not bolted on: a skip-to-content link, descriptive alt text on every image, 117 ARIA attributes across the interactive components, and a full noscript fallback that lists every video as a direct link so the section stays usable without JavaScript.
  • Motion respects the visitor. prefers-reduced-motion is honoured in both the stylesheet and the JavaScript, so the auto-playing video and scroll effects stand down for anyone who has asked their device to reduce motion.
  • Form progress survives a return visit via sessionStorage — no cookies, no tracking, no account.
  • Mobile-first throughout, with tap-to-call, tap-to-message and clipboard handoff wired for one-handed phone use, because that is the entire audience.

The same page and the same inquiry flow at desktop and phone widths. The summary block reflows to one column, the step indicator drops its labels for numbered dots, and nothing is hidden or truncated — the mobile visitor gets the whole system, not a reduced version of it.

Search and social

A location-specific title and meta description naming the city, the service and an entry price point; full Open Graph and Twitter Card markup with the locale set for the Philippines; structured data; and copy written around how people actually search — "photobooth rental Dipolog City", "photobooth for wedding", "photobooth for debut" — rather than keyword-stuffed. The service area is named explicitly and repeatedly.

Results

Measurement in progress.

The iBlast Photobooth website launched recently. We are currently collecting baseline data — search visibility, traffic, and inquiry volume — and this case study will be updated with verified results once a meaningful measurement period has passed.

We publish outcomes we can evidence, and nothing else. Most agency case studies open with a number nobody can verify. We would rather tell you what we built, show you the live site, and come back with real figures than put an impressive percentage on this page today.

What you can verify right now: every screenshot on this page was captured from the live site, and the site itself is open to anyone.

Open the live site

iblastphotobooth.com — run your own speed test, open it on your phone, and complete the inquiry flow to see exactly what a prospective customer experiences.

Visit iblastphotobooth.com⁠

What we could do for you

If your bookings come through messages, the same system applies.

Photobooth rental, spa treatments, photography, catering, salon services — the mechanics are identical. Someone has to find you, trust you quickly, understand what they're buying, and act on a specific date.

Book a free consultation⁠