A Proposal from Monstarlab  ·  April 2026

Kiosk
Ordering
Platform

A custom kiosk experience built on your Olo infrastructure.

Phase 1 Proposal iPad Native App Olo Integration Backend Application
Scroll to explore

The case for
custom kiosks

Kiosk orders at quick-service restaurants average 15–20% higher ticket values than counter orders. Customers move at their own pace, browse visuals, and make more add-on selections without social pressure from a line behind them. For Irv's, where burger customizations, fries, shakes, and sauces are natural upsells, that dynamic should be especially strong.

Off-the-shelf kiosk products handle the transaction. They don't deliver the brand experience. We propose a custom kiosk application built on your new Olo infrastructure, deployed on iPads, starting with a single-location pilot before rolling out across multiple Irv's locations.

You'll own the kiosk application and supporting backend outright, with no ongoing licensing fees.

Irv's Kiosk
Birthday Shake Irv's Burgers Just For You Burger Best Burger Tater Tots Onion Rings

A Three-Phase
Approach

Each phase has a clear go/no-go decision point before committing to the next. A pilot surfaces UX unknowns (how your specific clientele interacts with it) and operational unknowns (staff workflow, hardware placement, edge cases at the counter) before you've invested in hardware across multiple locations.

1
First Phase
Pilot
Core ordering, payment, basic loyalty earn, designed for one location
Goal
Validate UX, technology stack, and operational workflow before broader commitment.
2
After Pilot
Full Rollout
Multiple Irv's locations
Goal
Scale what's proven to work. Same codebase, same stack, new hardware across remaining locations.
3
Future
Loyalty + Expansion
Full Paytronix redemption, Prince Street extension
Goal
Build on a stable, tested foundation. Multi-brand support will be designed into Phase 1, keeping Phase 3 scope small.

What we're
building

Phase 1 is intentionally scoped to the core ordering experience. Full loyalty redemption and brand expansion are deferred until the pilot validates assumptions.

Feature Phase 1 Phase 2 Phase 3
Menu browsing with category navigation
Item detail pages with customization
Cart and order review
Upsell prompts (driven by Olo menu)
Olo integration (menu sync + order submission)
Payment processing (Olo Pay or Stripe Terminal)
Basic Paytronix loyalty (phone number for point earning)
Webhook listeners for real-time menu updates
iPad Air 13" deployment — one pilot location
ADA-compliant lower-mount option
Full six-location rollout
Full Paytronix redemption UI
Prince Street Pizza kiosk
On payments: Olo Pay card-present is our preferred option. Whether we launch on Olo Pay or Stripe Terminal depends on Olo Pay's readiness timeline, which we'll confirm in week 1 of the engagement.

What's out of scope

Designed for
speed and clarity

The existing prototype establishes the visual direction. Phase 1 design work translates that into a production-ready system, optimized for one constraint above all others: a first-time customer should complete an order in under a minute.

Ease drives every design decision

Every layout decision is filtered through tap count and time-to-order. Irv's has a loyal older clientele who value simplicity. That means generous touch targets, minimal nesting, and a checkout flow that never asks for information it doesn't need. We'll measure success by how few taps it takes to complete a typical burger-fries-shake order.

Upsell through visual merchandising

The 15–20% ticket lift doesn't come from pop-ups or interstitials that slow checkout. It comes from how items are presented: food photography at the item detail level, smart add-on placement within the customization flow, and suggested pairings that feel like part of the menu rather than interruptions. Design drives this outcome, not just Olo configuration.

Irv's visual language, reusable UI

The visual language is Irv's: color palette, typography, photography treatment, animation style. The UI components underneath are built to be reusable. Extending to Prince Street in Phase 3 means applying a new brand layer to the same components, not redesigning screens. We make this structural decision in Phase 1 so Phase 3 stays small.

Food photography and asset requirements

Strong kiosk performance depends on high-quality menu imagery. We'll provide an asset spec (dimensions, background treatment, file format) and a delivery timeline that syncs with the design schedule. If photography isn't ready, the kiosk launches with a fallback layout, but the upsell effectiveness takes a hit. This is a shared dependency worth getting right early.

On accessibility: Beyond the hardware-level ADA mounting, the kiosk UI will meet WCAG contrast ratios, use a minimum 16px body type, and size all interactive targets for comfortable use without precise tapping. These aren't afterthoughts layered on at QA; they're baked into the visual language from the start.

A Three-Layered
Architecture

The iPad app talks only to our backend, which coordinates all provider communication. No provider receives a direct call from the client.

Presentation
Native iPad App
Native or hybrid native/web — light offline capability (ordering requires active internet). Menu data cached locally with 24hr Olo sync.
Integration
Backend Application
Coordinates all communication between the kiosk and providers — handles order creation, menu ingestion, loyalty lookups, and payment orchestration. No provider is called directly from the client.
Webhook Listeners
Real-time availability updates — changes surface instantly without waiting for the 24hr sync cycle.
Providers
Olo
Order creation, menu ingestion, modifier handling — single source of truth for menu data.
Olo Pay / Stripe Terminal
Card-present payments — tap, chip, swipe. Olo Pay preferred; confirmed in week 1.
Paytronix
Phone number lookup at checkout → account lookup + point earn transaction submission.
Multi-brand readiness: The backend and codebase will be structured so extending to Prince Street is a configuration change, not a rebuild. We'll make this decision in Phase 1, keeping Phase 3 scope manageable.

Built for
the counter

iPad Air 13"
$800 each. 13" format provides enough real estate for menu browsing without overwhelming a counter. 11" ($350) is a viable alternative if cost is a constraint.
Gooseneck Mount
Supports wall, counter, and freestanding configurations.
ADA Compliance
Lower-mounted kiosk (34" from floor to screen center) should be standard. The gooseneck system accommodates this without additional hardware.
On outdoor locations: iPads aren't rated for direct weather exposure. Movable countertop units (taken inside nightly) are the practical solution until a permanent enclosure is found.
Kiosk at the counter
10–12 estimated weeks
to pilot launch
Stage 1
Foundation
  • Technical setup
  • Olo integration
  • UX flows finalized
  • Visual language drafted
  • Design system finalized
  • Order flow prototyped
Stage 2
Core Build
  • Screen designs: menu, detail, cart, checkout
  • Upsell placements
  • Full menu browsing
  • Cart
  • Checkout
  • Payment integration
  • Upsell logic
Stage 3
Loyalty + QA
  • Loyalty flow screens
  • Visual QA
  • Paytronix phone lookup
  • End-to-end QA
  • Hardware testing
Stage 4
Pilot Launch
  • Single-location deployment
  • Staff walkthrough
  • Live order validation
  • On-site customer observation (if feasible)
Post-Launch
Iteration
  • Bug fixes
  • Menu edge cases
  • Feedback collection
  • Phase 2 decision

Our Proposed Team

Colombia
Delivery Lead
50% allocation
Colombia
iOS Engineer
Primary build resource
Colombia
Backend Engineer
Olo + Paytronix integration
US
Director of Engineering
Technical oversight
US
Director, Technical PM
10–50% allocation
Colombia
QA Engineer
0–50% allocation
US
Director of Design
Oversight
Irv's Burger

A Wholly-owned
Custom Solution

No licensing fees, no ongoing transaction percentage, no dependency on Monstarlab after delivery.

Software Ownership
The kiosk application, design system, and integration code are yours. We deliver the repo and walk away — you're in control.
No Licensing Fees
Zero ongoing transaction percentage. Zero recurring platform fee. Hosting is lightweight — modest cost.
No Lock-In
Post-launch costs are hosting (lightweight, modest cost), Apple Device Management (Business Manager or Jamf), and hardware.
Irv's Burgers