HubSpot will store a client. Jobber will store a job. Neither will store the Part 107 date that keeps me legal, the battery pair I flew yesterday, the GSD I promised, or the per-acre rate on that tract. That's the gap.
I've been flying commercially for eight years out of Springdale, Arkansas, for Drones Inbound. I run a Part 107 shop. The work is mapping, inspection, and the follow-on jobs that come from the same GC. A drone pilot CRM has to keep the ops record, not just a sales pipeline.
I'm not here to dunk on HubSpot or Jobber. They're good generic CRMs. HubSpot is excellent if you sell software. Jobber is excellent if you run HVAC or lawn care. We need fields those products were never built to hold.
A pipeline is not the record
A generic CRM is built around a deal. Contact, company, stage, next task, close date. That's a pipeline. I use a pipeline. Every shop should.
The problem is what sits behind the contact. On a mapping job I need the client, yes. I also need the certificate that lets me fly, the aircraft and batteries that fly it, the GSD on the quote, and the per-acre rate that made the number. If those live in a spreadsheet next to HubSpot, I don't have a record. I have two systems and a prayer.
Jobber is closer because it's field service. Jobs, quotes, a schedule, a client file. That's the right shape for a plumber. It's still the wrong object model for a remote pilot. Custom fields aren't the same as a record the shop is designed around.
I ran that split for years. Contacts in one tool. Fleet in a sheet. Quotes in a template. It looked organized until a GC asked for the same spec as last fall and I had to reconstruct the job from email.
What HubSpot actually does well
HubSpot is a strong sales CRM. Contacts and companies. Deal stages. Email sequences. If I were selling seats, I'd use it without blinking.
I'm not selling seats. I'm selling a 2 cm ortho on 80 acres with a legal pilot and a matched battery pair. HubSpot doesn't know what those nouns mean. I can make a custom property called GSD and another called Part 107 expires. That's extra work, not a CRM.
HubSpot can date-stamp a contact. It won't treat my remote pilot certificate as a legal item, group batteries into pairs, or put a per-acre rate and a GSD on a branded quote. Those aren't HubSpot bugs. They're out of scope.
What Jobber actually does well
Jobber is built for home service. A client calls. You quote. You schedule. You invoice. For a plumber, that's the whole loop, and Jobber does it well.
A Part 107 shop has extra objects Jobber doesn't treat as first-class. The FAA certificate isn't a license sticker on a van. It expires, and if it expires I can't fly. Batteries aren't a box of fittings. They're matched pairs with cycle counts and health. A mapping quote isn't "clean the gutters, $189." It's acres times a rate, with a GSD on the page so the surveyor knows what they bought.
You can stretch Jobber. You can type acres into a quantity field and paste a GSD into a note. You'll still be typing drone facts into generic job objects because the product is a service call, not a flight.
Four fields a Part 107 shop has to keep
This is the side-by-side. Fields that have to live on the record.
GSD. Ground sample distance is the spec on the map. If it's only in a text thread, the next quote for that GC will guess. A generic CRM has a notes box. A drone pilot CRM keeps GSD on the quote with the service, where the client can see it.
Part 107 expiry. The certificate is the shop. HubSpot and Jobber will store a date if you invent a field. They won't watch it as a legal item. Pilot Ledger tracks Part 107 expiration and sends alerts. I want that date in the shop, not on a sticky note I forgot to clone when I hired a second pilot.
Battery pairs. I don't fly random packs. I fly matched pairs. Cycle count, health, mismatch warnings. Generic CRMs don't have a battery object. Fleet in a drone pilot CRM does. Group batteries into pairs, track health and cycles, get a mismatch warning, and let flight cycles record against the group so I know when to rotate or retire.
Per-acre rates. Mapping isn't a lump line called "drone service." Acres times a rate is the math. HubSpot deals are amounts. Jobber line items are quantities and prices you type. Neither starts with acreage as a first-class input on the quote, next to a GSD. I'm not going to rewrite how to price by the acre here. I'm saying the field has to exist. If you want the click path, the quote builder how-to covers creating a new quote, setting acreage, and the per-acre rate.
Those four are why I stopped treating a generic CRM as the system of record. The pipeline was fine. The shop wasn't in it.
What I keep in Pilot Ledger instead
Pilot Ledger is a client CRM and pipeline built for drone pilots, not generic sales teams. Full client database. Sales pipeline. Lead tracking. Follow-up scheduling. Lifetime value. Activity timelines. The rest of the record sits next to that client.
Fleet is in the same shop. Aircraft, batteries, maintenance, expiration alerts. Part 107 alerts live there. Battery pair tracking lives there. Quotes are in the same shop. Branded scopes, deliverables, per-acre pricing, GSD specs, e-sign, PDF. The client on the CRM card is the client on the quote. That's the point of a drone pilot CRM. One record, not a pipeline glued to a Word doc.
When the quote is accepted, the money path is a separate post. Quote to a Stripe pay link is enough on invoicing for this page.
When a generic CRM is enough
If you fly a handful of real estate stills and every job is a flat fee, HubSpot or Jobber can hold the client list. You won't miss GSD.
If you quote mapping by the acre, promise a GSD, fly matched packs, and keep a legal certificate, a generic CRM is a nice contact book. It isn't the record. Custom fields will feel like progress for a month. Then you'll hunt for the expiry, the pair, and last year's rate in three different places.
I don't need HubSpot to fail. I need the ops objects to be native. I don't need Jobber to fail. I need the job to know what a battery pair and a GSD are.
The record I actually need
A Part 107 shop needs the client and the pipeline. It also needs the certificate date, the battery pair, the GSD, and the per-acre rate in the same system that holds the deal. HubSpot and Jobber are good at the first half. They weren't built for the second.
That's what a drone pilot CRM is for. Not a prettier kanban. A record the shop can fly from.
Start on Pilot Ledger. The CRM, pipeline, fleet, and quotes are on the homepage. If you're building the first quote, use the how-to on the quote builder.