Case Study
Baltimore Courier Co.
A legal courier and process-serving company running on a custom platform: instant mileage-based quoting, a dispatch scheduler that turns down work it can’t deliver on time, chain-of-custody evidence on every handoff, live tracking, and a native driver app.
The Result
- #1 on Google for “Baltimore legal courier”
- The top two organic results for “Baltimore title courier”
As of September 2026, within weeks of launch, with no ad spend and no purchased links.
Plain disclosure: The Baltimore Courier Company is our own venture, not a third-party client. That is exactly why it sits in the portfolio — it is the build where nothing was cut for budget or scope, and every part of it runs a real business today.
The Challenge
Law firms and title companies hire a courier the moment a filing deadline is at risk. They need a price before they call, and proof afterward that the documents were handed to the right person, sealed, at a time they can point to. Most small couriers offer neither.
The established competition already had the search results and the standing relationships. Winning work meant answering the two questions faster than they did: what does it cost, and can you prove it got there.
One constraint shaped every decision: one driver, one vehicle. A booking form that accepts everything is worthless if the driver physically cannot make the run. This is the kind of work the custom web development side of the business exists for.
What We Built
Instant Quoting and Online Booking
Competitors make a law firm call for a price. Here the customer types two real addresses and gets a real number.
- Google Geocoding and the Routes API calculate true round-trip driving miles, not straight-line estimates
- Base fee with the first 20 round-trip miles included, per-mile beyond that, plus Same-Day, Rush (under 2 hours) and STAT (under 60 minutes) surcharges
- Additional stops, coupon codes and standing-account discounts all priced in before checkout
- Online booking is bounded by a 100-mile service radius from the hub — anything farther is routed to a phone quote instead of quietly failing
- A separate process-serving flow with per-attempt pricing, attempt previews, document pickup and Maryland-only service rules
A Dispatch Scheduler That Refuses Work It Can’t Keep
This was the hard part. One driver, one vehicle, and a missed Rush deadline costs the client relationship. So the system protects its own capacity instead of taking every order that comes in.
- Every booking is simulated against the whole day’s committed queue using live traffic, in the most accurate traffic mode the Routes matrix offers
- Earliest-deadline-first sequencing, with 10 minutes of grace at every stop, a 10-minute safety buffer per deadline, and a 15-minute dispatch lead when the driver isn’t already rolling
- If accepting a Rush job would make an existing delivery late, the customer is told the truth and offered the best time the system can actually hit
- Business hours, per-service cutoffs, scheduled next-morning runs, a Maryland court holiday calendar and owner closure days all feed the same engine — including the difference between a day off and the courts being closed
Payments That Match the Promise
Nobody is charged before their documents arrive.
- Booking places a Stripe hold for the exact quoted price after discounts; the card is charged at delivery, not before
- Wait time is measured from the driver’s arrive and depart taps: 10 free minutes per stop, then a per-minute rate billed separately after delivery and disclosed at checkout and in the Terms
- Every status change is idempotent — a double tap or a retry on a weak signal cannot double-charge or corrupt a trip. Each transition is claimed atomically and reconciled with Stripe before any failure is recorded
- Receipts show the full breakdown: trip price, coupon, standing discount, fuel surcharge, wait time, and what was actually charged
Chain of Custody: Evidence, Not Promises
Legal, title and financial documents carry deadlines and liability. The system captures proof of every handoff and shows it to the customer.
- A serialized seal, barcode-scanned at pickup and again at delivery. A mismatch has to be acknowledged before a signature can be collected, and it stays on the trip record permanently
- Photos of the sealed package at pickup and before handoff, embedded in the emails and on the tracking page
- Typed name plus signature at both ends — who released the package and who received it, because signatures aren’t always legible
- GPS stamps at pickup, en route and delivery, with a quality filter that rejects imprecise or stale fixes. No stamp beats a wrong one
- A stop-by-stop visit log with arrival and departure timestamps, which is also what drives wait-time billing
- Tracking codes generated from cryptographic randomness in an unambiguous alphabet — roughly 850 billion combinations, so nobody guesses their way into someone else’s delivery
Live Tracking and an Honest ETA
The customer watches the delivery the way they would watch a rideshare, and the system tells them when it is running late before they have to ask.
- A tracking page with the courier’s live location on a map, a status timeline, the stop log, seal photos, signatures and the receipt
- Privacy enforced in code: a customer sees the courier’s location only while their own job is being served, never on another client’s run, never on a process-serving case, and never from a fix older than 30 minutes
- “Arriving now” appears automatically within about half a mile; “Courier has arrived” only when the driver taps Arrived, because a courier circling for parking hasn’t arrived
- Automatic delay notices: the queue is re-simulated from the driver’s live position and live traffic, and any customer whose ETA slips 10 minutes or more gets an updated time by email, with the driver shown exactly what the customer was told
- Rush and STAT jobs at risk alert the driver instead, so a premium delivery gets a phone call rather than an automated email
A Fuel Surcharge Tied to a Government Index
National carriers charge a percentage of the bill. This one passes through actual cost.
- Pulls the EIA weekly regular-gasoline price for the Central Atlantic region on a schedule, with a manual override
- Nothing is added at or below a set price per gallon; above it, only the added fuel cost per round-trip mile, based on the vehicle’s real mileage
- Itemized at checkout, in the Terms and on the receipt, and never discounted
Transactional Email That Runs Itself
One branded template and a sequence the owner never has to think about.
- Booking Confirmed, Picked Up (with seal number, seal photo and release signature), On the Way, Updated Arrival Time when genuinely late, and Delivered with seal verification, recipient signature, photo and final billing
- Automated Google review requests sent 90 minutes after delivery and again at 24 hours, pointing the customer straight at the company’s Google Business Profile star rating. Clicking the first cancels the second, so nobody gets nagged twice — the reviews that lift the map pack come in without the owner ever having to ask
- Cancellation notices, certificate-of-insurance requests, standing-account applications, staff invitations, password resets and customer email verification
- SPF, DKIM and DMARC on the sending domain, separate dispatch and info addresses, escaped customer values, Outlook-proof buttons, a dark-mode-safe logo, and suppressed auto-linking so times and addresses don’t turn into blue underlined text
A Native Driver App
The browser could not do what dispatch needed, so the driver side ships as an Android app.
- A Capacitor wrapper around the live dispatch screens, so most updates ship with a normal website deploy instead of an app rebuild
- Background GPS through a foreground service: location keeps reporting no matter what else the driver is doing — screen off, phone in a pocket, navigating in another app, taking a call. It stops only when the phone is off or the app is swiped closed. A browser cannot do this, which is why the driver side is a real app
- Camera barcode scanning for seals at both ends
- A driver-only shell — the public header and footer are replaced by a slim branded bar, with navigation limited to dispatch, admin and tracking
Accounts, Roles and Admin
Built for one driver, ready for a crew.
- Staff logins with roles: the owner sees everything, drivers see the queue and their trip actions, never see what a customer is paying, and cannot cancel trips or reach admin
- Passwords hashed with scrypt, signed and expiring sessions, and drivers invited by email to set their own
- Customer accounts with email verification before any trip history is shown, so nobody opens an account on a law firm’s address and reads their delivery record
- Standing accounts approved by the owner, with the discount applied automatically at checkout
- Admin covering the dispatch queue, customer detail with full trip evidence and billing, coupons, closures, fuel price, staff and accounts
What Earned the Rankings
The same structure behind every local SEO build here, applied to a business with real competition:
- Next.js App Router with server-rendered and statically generated pages on Vercel’s edge network — fast first paint and solid Core Web Vitals
- A page per service and per audience: legal courier, court filings, title and real estate, secure delivery, process serving, plus industry pages for financial institutions and IT and data-center media
- More than ten resource pages aimed at what these firms actually search: court filing hours and window cutoffs, deed recording in Baltimore County, SDAT filings, process-serving rules, chain-of-custody explainers and coverage guides
- A coverage page with a mapped 100-mile radius and named courthouses and jurisdictions
- Per-page titles, descriptions and canonicals, LocalBusiness structured data, a clean sitemap, and a robots policy that keeps tracking, driver, admin and account surfaces out of the index
Stack and Scope
Next.js (App Router), TypeScript, Tailwind CSS, Vercel, Neon Postgres, Stripe with manual capture, Resend, Vercel Blob, Google Maps Platform (Geocoding, Routes, Static Maps), EIA open data, Capacitor for Android, and Google ML Kit for barcode scanning.
Twenty-four database migrations, a custom scheduling engine, a native app, and roughly 60 pages and routes — built solo, in weeks rather than months.
Most booking forms take any order that comes in. This one checks its own schedule against live traffic and says no when it has to. That is the difference between a website and a system your business actually runs on.
Everything above is running on the live site right now.
View Live SiteSee How We Can Help You Capture Business!
8 a.m. – 5 p.m., Mon–Sat
Or call and skip the form
(410) 432-0095