Skip to content

Parking

New income from drivers who were already parking

Recurring permits and a self-serve advertising business, added to a parking booking product without getting in the way of drivers who just want a space.

  • Hourly to monthly, one flow
  • Self-serve advertiser portal
  • Multi-tenant, every location
Book a 30-min call

At a glance

Client
Park Pay
Industry
Parking
Engagement
Dedicated product engineering team, ongoing
Services
SaaS Development, Software Development, Web Development

Park Pay makes the software parking operators use to sell space — finding a spot, paying for it and managing the locations behind it.

The situation

What the business was running before

Each parking session made a little money and then ended. A driver parked, paid, drove off, and might never come back through the product — so every visit had to be won again, and the margin on each one was small.

Park Pay already had something most advertisers want: a steady audience of local drivers making a decision at a known moment. It wanted two things from the same product — regular parkers on recurring plans, and businesses paying to reach the people using it — without making the simple job of booking a space any harder.

The constraints

What was in the way

These are the conditions the design had to survive. They are on the page because a study with no obstacles in it tells you nothing about how the team behaves when something goes wrong.

  1. Two kinds of parker, one checkout

    Someone paying for an afternoon and someone holding a monthly permit want different things from the same screen. Splitting them into separate products would have doubled the work and confused both.

  2. An advertising business with no advertisers yet

    There was no ad sales team, no inventory and no tools for a business to buy space. Whatever was built had to let advertisers sign up and run campaigns on their own.

  3. Availability that is right at the moment of booking

    Many drivers book the same locations at the same times. A space shown as free has to still be free when payment goes through, across every site at once.

  4. Revenue that can't slow the driver down

    Permits and ads only pay if people keep coming back. Any friction added to the booking path would cost the repeat use the new revenue depended on.

What we built

The system that replaced it

  • One flow for every length of stay

    Pay by the hour, by the day or by the month, all chosen from the same booking path, with rates that can move with demand.

  • Permits drivers manage themselves

    Recurring billing, automatic renewal, and upgrades, downgrades or cancellations handled by the driver — not by a support ticket.

  • An operator console

    Rates, space limits and earnings for each location, managed from one admin interface.

  • Self-serve advertiser onboarding

    A business signs up, sets up a campaign, chooses who to reach and follows how it performs, with no one at the operator involved.

  • Ads placed where they make sense

    Placements appear inside the parking journey, matched to the moment, so an offer reaches a driver when it is relevant to them.

How we worked

The order we did it in

  1. Three users, mapped before anything was drawn

    We traced what a pay-as-you-go driver, a permit holder and an advertiser each need from the product, and where those needs collide. Advertising had to fit the driver's path, not interrupt it.

  2. Booking first, new revenue after

    The parking core was made solid before anything was added to it. Permits and advertising were sequenced to arrive once booking was dependable, so a new feature never put the existing business at risk.

  3. Multi-tenant from the first release

    Every operator and location runs on one shared platform, so adding a site is configuration rather than another deployment, and capacity grows by adding servers rather than rewriting code.

  4. Advertising as its own module

    The ad side was built as a separate module with its own onboarding, campaigns, targeting, placements and reporting. It can change without touching the code that takes payments for parking.

Built with

  • React
  • Next.js
  • Python
  • REST APIs

What changed

What the business can do now

What the business can do since the new system went live.

  • Parking fees and ad revenue from one product

    The operator now earns from the space and from the audience using it. The second stream runs on drivers it already had, not on a new market it had to find.

  • Occasional and regular parkers in one place

    Daily bookings and monthly permits sit in the same product and the same flow, so a driver can move from one to the other without starting again.

  • Advertisers onboard without operator staff

    Businesses sign up and run their own campaigns. The advertising side grows without the operator hiring a team to sell it.

  • New locations without new builds

    Because the platform is multi-tenant and scales out, another site or operator joins the platform already running.

Questions

Questions about this build

Running something that looks like this?

Tell us which systems are disagreeing with each other. That conversation usually tells us within half an hour whether the answer is integration, replacement, or leaving it alone.

Book a 30-min call

Published Nov 5, 2026