ABOUT TOA11Y

We build the technology layer motorcycle dealerships actually need.

Most dealership websites publish inventory and wait. We build systems that help riders decide, put interactive configurators on the showroom floor, find the revenue leaking out of the service lane, and remember what every shopper is trying to accomplish. One team, one platform, four products.

  • WCAG 2.2 AAbuilt to the standard, not claimed after the fact
  • W3Cvalid markup, zero errors
  • Sub-secondtarget LCP on mobile, server-rendered
The TOA11Y team testing a dealership website with a screen reader
Why we exist

The industry got better at listing bikes. It never got better at helping riders choose them.

Motorcycle dealership websites begin with inventory. Brands, models, specifications, photos, prices, then a contact form. That assumes the buyer already knows which type of motorcycle is right. Many don't. They know their riding reality: the commute, the terrain, the passenger, the experience level, the budget. They don't know which category, engine size, or configuration fits it.

So riders educate themselves on make, model, and trim details they will never need again, on dealership sites or third-party marketplaces, then walk in with a vague question like "how much is a 600cc sportbike?" The dealer pays for the traffic and receives a guess.

Our position

Riders should not need to know the motorcycle model before they can get intelligent help choosing it. A lead should not be a name, an email, and a phone number. A lead should be an understandable riding decision a salesperson can act on.

The ride comes before the motorcycle. A recommendation without reasoning is just advertising.

The TOA11Y operating principle

That conviction turned into a platform. It started as a dealership website with an interactive motorcycle configurator, built on Django and Python with a proper database architecture and Django's security model. It is now four connected products for dealers who want their technology to sell, not just display.

What we build

Four products. One platform.

Everything runs on the same foundation: a Django backend, PostgreSQL, Celery and Redis for scheduled work, REST APIs for devices and integrations, and server-rendered templates tuned for speed and accessibility. Dealers can adopt one piece or all four.

01 — Rider-first websites

The motorcycle decision layer

Two ways in. Riders who know what they want go straight to inventory. Riders who know what they need it to do describe their situation in plain language, and the platform translates it into requirements, eliminates what doesn't fit, and recommends motorcycle paths with reasoning attached: why it fits, what it costs, where it gets weaker, and when it's the wrong choice.

Every recommendation includes reasons not to choose it. Sometimes the honest answer is that none of the available bikes is suitable, and the platform says so. The dealer receives a structured rider brief: use case, requirements, budget, objections, shortlist, and what was rejected and why.

02 — In-store experience

Build A Bike kiosks and Raspberry Pi digital signage

An interactive touchscreen configurator for the showroom floor. Customers select a model, explore colors, trim, accessories, exhaust, seats, luggage, and apparel, and see a live build with pricing and a QR code to save or share it. The same experience runs on the dealership website.

Each screen is driven by a low-cost Raspberry Pi player managed from a central Django CMS. Dealers and their agencies upload campaigns, schedule playlists, control multi-zone layouts, monitor device health, and push updates remotely, across fifteen displays or fifteen states. Content caches locally, so screens keep playing when the internet drops. It gets shoppers off their phones and into an interactive purchase journey.

03 — Service lane intelligence

The service-lane opportunity engine

Every motorcycle owner eventually faces a decision moment in the service lane, and dealerships lose three revenue streams when nobody catches it: the repair, the trade, and the next bike sale. Our engine joins repair history, current estimates, motorcycle value, equity, and live inventory to tell the service team what to do before the customer walks out.

It is a transparent scorecard, not a black box, and it measures everything in dealer dollars: gross opportunity found and gross opportunity recovered. It also runs a revenue-recovery audit first: we review 90 to 120 days of your repair orders and show you, by VIN and dollar figure, what leaked. If we can't identify at least $3,000 to $5,000 of recoverable exposure, you keep the report and pay nothing.

04 — Shopper memory

Identity, memory, and intent infrastructure

A motorcycle purchase takes days or weeks, but most dealership websites treat a shopper who visits Monday, Tuesday, and Friday as three different people. Our platform remembers the useful parts of the journey before the buyer identifies themselves: what they viewed, saved, rejected, compared, and what their riding context is.

Then identification has a purpose. The shopper isn't asked for an email to be marketed to. They're offered a reason to be remembered, so they don't have to start over. The dealer gets riding demand intelligence instead of raw pageviews.

How we work

Engineered like a platform, not assembled from plugins.

Every TOA11Y build is custom code on a documented architecture: Django, Python, PostgreSQL, Celery, Redis, and REST APIs. No page builders, no proprietary lock-in, no dependency stack we can't explain. We document the development process, architecture, and functionality for every client team that asks, and we do it before they ask.

Accessibility and performance are engineering requirements, not add-ons. Our interfaces are built to WCAG 2.2 AA with semantic HTML, visible keyboard focus, sufficient contrast, large touch targets, and screen-reader labels on every interactive element. Our markup validates against the W3C with zero errors. Our pages are server-rendered and optimized for sub-half-second LCP on mobile, with WebP and AVIF imagery, properly sized assets, and minimal JavaScript.

We work in stages with proof at each one. For service-lane clients, that means the audit comes before any software. For kiosk deployments, it means a pilot before a fleet. For websites, it means a documented demo of the exact components a dealer needs before anyone signs anything.

WHAT WE BELIEVE

Convictions that run this company

The ride comes before the motorcycle

Start with what the bike has to do, not with what's in stock. More inventory does not create more understanding.

Every recommendation includes a reason not to

A recommendation without reasoning is advertising. We show the tradeoffs, including when a bike is wrong for the job and when nothing available fits.

Value before contact information

Riders should get useful help before being asked for an email. A well-informed rider is worth more than an unqualified lead.

Honest answers build dealer business

We help dealers make more money by helping customers make better decisions. When the right answer is 'repair it, don't chase the trade,' we say so.

Transparency is engineering, not marketing

Transparent scorecards, visible reasoning, documented architecture. No black boxes, no overlay widgets, no compliance claims we can't back with the code itself.

Technology should reduce confusion

Not add another layer of jargon. If a feature stops making sense with the word 'AI' removed, it doesn't ship.

COMMITMENTS

What we won't do, even if you ask

These aren't preferences. They're the reason the platform is built the way it is.

  • Build a dealer-controlled advertising surface and call it a neutral recommendation engine
  • Hide our reasoning behind a mysterious score or an unexplained algorithm
  • Ask a rider for their email before we've earned it with something useful
  • Pretend a customer status portal or an accessibility widget is the innovation
  • Build on page builders, template kits, or platforms we can't document end to end
  • Claim 'ADA compliance' or 'WCAG certification' as a guarantee, or promise anything prevents a lawsuit
The TOA11Y gecko mascot wearing round glasses
THE MASCOT

Why there's a gecko on this website

Geckos climb walls other animals can't. They see in the dark. They've done it for fifty million years without a redesign. It's a fair metaphor for the work: a small, adaptable system that gets into places bigger platforms can't reach and doesn't need much infrastructure to do its job.

The gecko appears in illustrations, the newsletter, and blog headers. It does not appear in the logo. That was deliberate. The work is the brand, not the mascot.

THE GECKO BULLETIN

A regular look at how riders actually buy, what dealership technology gets wrong, and how we'd fix it

READY TO SEE THE NUMBERS?

Start with your own data.
Keep the report either way.

Export 90 to 120 days of repair orders. We return a revenue-recovery audit with dollar figures and VINs: declined work nobody followed up, repair-versus-replace conversations that should have happened, and money still on the table. If we can't identify at least $3,000 to $5,000 of recoverable exposure, you pay nothing.

Get your revenue-recovery audit
No software to install. No contract. No changes to how your shop runs.
Revenue-recovery audit report listing declined repairs and missed opportunities by VIN and dollar amount