# Custom Add-Ins

When an off-the-shelf Marketplace add-in doesn't quite fit, High Point GPS's developers build one that does.

Source: https://www.highpointgps.com/solutions/custom-add-ins
Last updated: 2026-08-01

The Geotab Marketplace has hundreds of add-ins for cameras, sensors, and workflow tools, but not every fleet's process fits a pre-built option. High Point GPS's in-house developers build and customize Add-Ins for MyGeotab, including tailoring the look, feel, and logic of tools like GeoDocs, to match how your dispatchers, drivers, and safety team actually work.

## Highlights

- Custom Add-In development on top of the Geotab platform
- Tailored look, feel, and workflow logic, not a generic template
- Built by High Point GPS's own development team, not a third-party subcontractor
- Fits alongside Marketplace add-ins you already use

## What Makes an Add-In 'Custom' Instead of Off-the-Shelf

A Marketplace Add-In is pre-built and shared across many fleets by design, which is efficient but means it's built for the average case, not your specific workflow. A custom Add-In is built or modified specifically for one fleet's process: different fields, different logic, a different look and feel, while still running inside MyGeotab the same way a Marketplace listing does. Geotab's open SDK is what makes that possible in the first place; a closed platform wouldn't let a reseller build this kind of tool at all.

## How GeoDocs Came to Exist

GeoDocs is a real example of this process, not a hypothetical. Document management in the cab, getting the right paperwork in front of a driver at the right moment, wasn't a problem the Marketplace had a great pre-built answer for at the time, so High Point GPS built one. That's usually the actual trigger for a custom Add-In: a specific, recurring workflow pain that off-the-shelf tools keep almost, but not quite, solving.

## What the Development Process Actually Looks Like

Building a custom Add-In starts with understanding the actual workflow it needs to fit, not a generic feature request. From there, timeline depends heavily on scope: a themed or modified version of an existing tool like GeoDocs moves faster than an entirely new workflow built from scratch. Once it's live, it runs inside MyGeotab like any built-in feature, and High Point GPS provides ongoing support and updates rather than treating it as a one-time build.

## FAQ

### What's the difference between a Marketplace add-in and a custom Add-In?

Marketplace add-ins are pre-built and shared across many fleets. A custom Add-In is built or modified specifically for your workflow, with different fields, logic, and look and feel, while still running inside MyGeotab.

### How long does a custom Add-In take to build?

It depends on scope. A themed version of an existing tool like GeoDocs is faster than a new workflow built from scratch. High Point GPS scopes timeline and cost after understanding what you need it to do.

### Will a custom Add-In show up inside MyGeotab like a built-in feature?

Yes. A custom Add-In runs inside MyGeotab the same way a Marketplace Add-In does, so your team isn't switching to a separate tool or a second login to use it.

### Does High Point GPS maintain a custom Add-In after it's built?

Yes. Ongoing support and updates are part of working with our development team, rather than a one-time build with no support afterward.