We sit with the people doing the work, map how your business actually runs, then build the system that takes the worst of it off them. Booking systems, purpose-built CRMs, reporting that pulls the numbers into one place, and automation for the jobs nobody should still be doing by hand.

Start a project →

Run by Tommy McCallen · 6+ years in the motor trade, every system on this site built hands-on.

/ Work · Selected projects

A selection of the systems we've built, and the problem each one was made to solve.

Events Motor Trade Ecommerce B2B Every system here is running in production

01 / Case study

Race entries, payments & race-day management

Entries, payment and race-day sign-in on one system, in place of four booking platforms and a stack of spreadsheets.

Events · Booking & payments 02 / Case study

Custom automotive dealership CRM

Every enquiry lands in one place the whole team can see.

Motor Trade · CRM 03 / Case study

Stock system to storefront, automatically

New stock reaches the website without anyone retyping it.

Ecommerce · Automation 04 / Case study

Custom lead scraping software

Prospects gathered, enriched and screened against the contact rules before anyone opens a spreadsheet.

B2B · Automation

01 / Case study · Motorcycle festival, Ireland

Race entries, payments & race-day management

Events · Booking & payments

A large motorcycle festival in Ireland was taking rider and spectator entries across several booking platforms, then rebuilding it all by hand: allocating numbers, chasing forms, seeding entries and reconciling payments in spreadsheets. We replaced the lot with one bespoke system. A customer-facing form collects each entry, applies the festival's rules, and takes the right payment at the point of booking. Everything lands in one database, which builds the race entry pages officials use on the day to sign riders in and run each race.

  • One entry form applies the festival's rules and takes payment at the point of booking
  • Rider numbers allocated and entries seeded without a spreadsheet
  • Officials sign riders in and run each race off the same database on the day
Fig.01 · Entries, race numbers

02 / Case study · Motorcycle dealership

Custom automotive dealership CRM

Motor Trade · CRM

A motorcycle dealership was losing enquiries in individual inboxes: when a salesperson was off or busy, their leads just sat there. We built a CRM shaped to how a bike dealership actually sells, rather than generic automotive software bent to fit. Every enquiry lands in one place the whole team can see, so calls get returned and nothing slips.

  • One shared pipeline, so any salesperson can pick up a lead cold
  • Built around how a bike dealership sells, not generic automotive software
  • Live on the Lisburn sales floor
Fig.02 · One shared pipeline

03 / Case study · Ecommerce store

Stock system to storefront, automatically

Ecommerce · Automation

An online store was listing products by hand: copying details out of their stock management system, tidying them up, and re-entering them on the website one at a time. We built an internal tool that pulls each product straight from the stock system, enriches it with clean titles, descriptions, categories and images, and lists it on the site. New stock shows up online without anyone retyping a thing.

  • Products pulled straight from the stock system, no copy and paste
  • Titles, descriptions, categories and images built on the way through
  • The stock system stays the single source of truth for product data
Fig.03 · Stock → enrich → storefront

04 / Case study · B2B agency

Custom lead scraping software

B2B · Automation

A B2B agency needed a steady flow of qualified leads without a team burning days on copy-and-paste. We built scraping software that walks the right sources, compiles contacts, and enriches them with the details that make outreach land. In a single run it pulls hundreds of qualified prospects into one clean dataset. A compliance filter runs before the export, so anyone outside the rules on who you're allowed to contact never reaches the list in the first place.

  • Walks the right sources and compiles contacts in one run
  • Enriched with the details that make outreach land
  • A compliance filter runs before the export, so out-of-scope contacts never reach the list
Fig.04 · Contacts, one dataset

Four we can show publicly. Not everything we build ends up on a public page.

Tell us the job,
we'll build the system

→ Book a 20-minute call

/ Approach · How MOND works

It starts with your problem, not a product. We learn how your business actually works, design a system around it, build it in stages you can see, and hand it over yours to keep.

How a project runs · Method

Step 01

Discovery

We sit down with the people doing the job to understand how the business runs now: processes, who touches what, where the data sits, and which bits get retyped, chased or lost.

Step 02

The map

One page back. What could come off your plate, what each item is worth on your own figures, and what it would cost to build. Yours to keep whether you go ahead or not.

Step 03

Scope and fixed quote

Only if you want the item at the top. It becomes a written spec in plain English: what the system does, what it doesn't, what it costs. Nothing gets built that isn't in it, and the price doesn't move after you sign off.

Step 04

Build in stages

You see working software early and react to something real, instead of signing off on promises and waiting months for a reveal.

Step 05

Test, train, hand over

We test it with the people who'll use it, train them on it, and put it live. The code, the data and the accounts are yours outright, and we stay available afterwards.

/ Where it starts

The systems map

Twenty minutes on the phone to understand how the business actually runs, day to day. Then a page back, in your words, listing what software could take off your plate and what each one is worth in time or money, using the figures you gave us on the call.

  • Where the time goes now, in your words rather than ours
  • What could come off your plate, item by item
  • What each one is worth, on the numbers you gave us
  • A fixed price for the one at the top, if you want it

It costs nothing, and there's no obligation to do anything with it.

If nothing on it is worth doing, we'll say that instead.

Book a 20-minute call →
Fig.A · One page, costed

Questions we get · FAQ

Good. Our clients sell bikes, run events and run online stores. If you can describe the problem in a sentence, that's all the technical input we need from you.

A fixed quote once we have seen how the work actually runs, before any code is written. A single-purpose booking page sits at the low end; a full CRM sits at the top. The price you sign off is the price you pay.

Keep it. Our systems embed into the site you have or run on their own link. A booking page we built for a dealer open day dropped into their existing site without touching it.

Where it does a real job: reading incoming enquiries and routing them to the right person, drafting replies for your approval, answering the questions that get asked fifty times a week, cleaning and enriching data. What we won't do is drop a generic chatbot on your homepage and call that progress.

Usually the numbers exist, just in four systems that disagree with each other. We pull sales, stock, service and finance into one place and build the reporting on top, so you can see which products, brands and offers actually make money. That side comes from a finance background, not just a technical one.

Usually not. Most jobs are about getting the systems you already pay for to talk to each other and stop being retyped between. Where something genuinely does need replacing, the proposal says so and says why.

You do. Code, data, hosting accounts, the lot. If we disappeared tomorrow, your system keeps running and any developer could pick it up.

Depends on the system, and the proposal will say. A single booking page goes from brief to live in days. A full CRM is measured in weeks, not the quarters an agency will quote you.

/ Contact · MOND Systems

Tell us about the thing your team keeps losing, retyping, or chasing. We'll reply with whether software can take it off your hands, and roughly what that would involve. No pitch deck, no obligation.

Project enquiry · fields marked * required

04What can we help with?
Or email tommy@mondsystems.com

Sending…