What we build
- Online booking, scheduling, calendars and payments for service businesses
- Technician calendars
- Stripe payments
- Google Calendar sync
- Booking, dispatch and payments for mobile crews (DispatchEngine)
Mobile and on-site service businesses: tire and auto service, repair, cleaning and installation crews. Before they call us, bookings usually arrive by phone, text and email, someone copies them into a calendar, and payments get chased after the job.
AI built in
An assistant that books jobs while you're under a car.
Most booking systems wait for customers to fill in a form. We build AI into yours: it answers texts, books jobs, plans the day and writes the follow-ups, using your prices, your schedule and your rules.
Pay $95 by card
Books jobs by text and chat
Customers write the way they talk. The assistant checks real availability, quotes your prices, books the job and takes the payment.
Answers after hours
Missed calls and late-night texts get an instant reply that captures the job, so the lead doesn't go to the next shop.
Plans the day for you
Suggests which tech takes which job and in what order, based on location, skills and drive time.
Reads customer photos
A photo of a tire sidewall or a dashboard light becomes the size, the issue and a draft job before anyone calls back.
Follow-ups that write themselves
Reminders, review requests and "time to swap" messages each season, written in your voice and sent at the right time.
Ask your business anything
"How many tire swaps did we do in October, and what did they earn?" Plain-English answers from your own records.
Agents that run the routine
An agent is AI that works through a whole job by itself, step by step, and reports back. Ours run on a schedule inside your system, with your rules.
Every evening at 6
- Confirms tomorrow's jobs by text
- Moves cancellations and fills gaps from the waitlist
- Chases unpaid invoices
- Sends you a two-line summary
Run it from ChatGPT or Claude
We give your system an MCP connection, the standard way AI assistants plug into software. Then you run your business by asking the assistant you already use.
- “Move Mrs. Lee to Thursday morning and let her know.”
- “What's still unpaid from last week?”
- “Block Friday afternoon for Marcus.”
You stay in chargeYou decide what the AI may do on its own and what waits for a person to approve.
Your data stays yoursWe use AI providers whose business terms don't train their models on your data, and send only what each task needs.
Costs you can seeAI usage is metered and capped, so a busy month never turns into a surprise bill.
Built for real businesses
Online booking, technician calendars and Stripe payments. It replaced their Wix site and has run the business every day for over two years.
Read the case study →
For mobile mechanics
DispatchEngine
Booking, dispatch and payments for mobile mechanics and fleet-service shops in Ontario. It grew out of the system we built for Wheel Easy.
See DispatchEngine →How a project runs
- 01
Understand the work
We map how your business runs today: who books, who does the job, who gets paid, and where it breaks.
- 02
Design the screens
You see and click through the screens before any code is written, and change what doesn't fit.
- 03
Build
Web, iOS and Android, with the dashboards and back office behind them.
- 04
Test
We test on real phones and with real staff before anything reaches your customers.
- 05
Launch
Domains, app store listings, payments and accounts set up and handed over to you.
- 06
Look after it
We keep it running and keep improving it. Wheel Easy's system has run every day for over two years.
What clients say
I came to them with just a vision of what I wanted to create, and their help has been a dream scenario for a non-technical founder like myself.
Questions
How long does it take?
A first version usually takes 6 to 12 weeks, depending on what it needs to do.
Who owns the software?
You do, once the project is paid in full: the code, the accounts and any app store listings.
Why not build it myself with AI?
You can get a working demo with AI in a weekend, and for some things that's enough. The hard part comes after: payments, logins, data that must not be lost, app store review, and someone to fix it when it breaks on a Saturday morning. We use AI to build faster, and we take responsibility for it working, for years.
What are AI agents and MCP, in plain terms?
An agent is AI that carries out a multi-step job by itself, like confirming tomorrow's bookings, and reports back. MCP is the standard way AI assistants such as ChatGPT and Claude connect to software; with it, you can run your own system by asking your assistant.
Can you add AI to software we already have?
Often, yes. If your system has an export or an API, we can connect an AI assistant to it. We'll tell you what's possible after a look at it.
Is our data safe with AI?
We use AI providers whose business terms don't use your data to train their models, send only what each task needs, and keep the records in your own system.
Which AI do you use?
We pick the model that fits the job, usually from Anthropic (Claude) or OpenAI, and can switch when a better one comes along.
What happens after launch?
We look after hosting, updates and fixes for a monthly fee, and quote new features separately.
Can customers pay by card when they book?
Yes. Payments run through Stripe, so card details never touch your systems. Wheel Easy's customers pay when they book.
Does it work with Google Calendar?
Yes. Bookings can sync with Google Calendar, so your team sees jobs where they already look.
Do you work with businesses outside Ontario?
Yes. We're based in London and Barrie, Ontario, and we've built for clients in British Columbia.