A Client Portal for Drone Clients: Quotes, Invoices, and Files in One Place

Most drone shops still hand clients three different doors: a PDF quote in email, an invoice in another thread, and a Dropbox or WeTransfer link for the ortho. The client loses the first two. You dig for the third on a Friday when they ask where the files went. A drone client portal is the quiet fix—one place the client signs in and finds the job paperwork and the deliverables without pinging you for “the latest version.”

This Pilot Ledger Software post is teach-first for nationwide U.S. commercial ops. Soft CTA only to Pilot Ledger pricing. No invented portal features. No SkyView waitlist pitch dressed up as a shipping portal. No Flight Hub 2.

What a client portal is (and is not)

On Pilot Ledger, clients use a separate front door from pilots: Client Login at /client-login. The page copy is blunt—quotes, invoices, payments, and deliverables from their pilot—plus a payment-protection note. That is the portal story.

It is not the same thing as a Stripe pay link. Quote-to-invoice and the /pay/{token} path already have their own write-up: drone invoicing software, quote to Stripe. Use that article when the question is “how do I get paid from an approved quote.” This post is about where the client returns to see quotes, invoices, and files without hunting email.

Do not invent milestone wizards, escrow-as-portal, fake dashboards, or waitlist claims as if they were live portal screens. Stick to what the live site already markets.

Why clients need one login

Commercial buyers are not your inbox. A GC PM forwards the quote to accounting. Accounting never saw the ortho link. The owner’s rep asks for “the map from last month” and you paste a third Drive folder. Every hop is a chance to lose version control and look disorganized.

A portal compresses that:

• Quotes the pilot already sent live where the client can reopen them
• Invoices sit next to the work they belong to
• Deliverables and maps share the same signed-in space as billing
• Registration uses the email the pilot already has on file—so quotes and invoices find the right person

That last point matters. The client-login page tells people to register with the email their pilot has on file. Wrong email, orphaned paperwork. Right email, the portal can surface what you already issued.

What ships on the live portal path

From the live /client-login page and homepage marketing (pulled 5 Oct 2026):

1. Separate client login — /client-login is not pilot login. Clients and pilots do not share the same auth door.
2. Quotes, invoices, online payment, deliverables — the portal copy lists those four in one sentence. That is the product promise on the page.
3. Email-matched registration — clients register with the email the pilot has on file so quotes and invoices attach to them.
4. Branded quotes with e-sign from an email link — homepage markets branded quotes with service scopes, deliverables, pricing detail, e-signatures, and PDF generation. Clients can approve without a scavenger hunt.
5. Quote-to-invoice — accepted work converts into invoices in the same business stack (payment mechanics: see the quote-to-Stripe post).
6. Client file delivery on jobs — job sheets include client file delivery so the package is not stranded in a personal Drive.
7. Maps and point clouds on private projects — homepage Client Portal / delivery copy: publish maps and point clouds to private PilotLedger projects, share client access, and keep delivery next to billing. Clients sign in to view maps, deliverables, quotes, and invoices in one branded space.

That list is enough for an honest portal post. Stop there.

Field pattern: how a mapping shop actually uses it

You bid a 60-acre ortho for a civil firm. You send a branded quote from the stack. They e-sign from the email link. You convert the accepted quote to an invoice when the flight is booked or when the deliverable lands—whichever your shop’s policy is. When the ortho and the point cloud are ready, you put them on the private project and share client access. The PM logs into /client-login with the same email you used on the quote. They pull the invoice status and the files without asking you to “resend everything.”

If they still owe money, point them at the invoice / pay path documented in quote-to-Stripe—do not rebrand pay links as “the portal.” The portal is the place they find the work; the pay link is how Stripe collects.

What breaks when you skip a portal

• Version chaos — three “final” orthos in three threads
• Accounting lag — AP never saw the quote terms that match the invoice
• Support load — you become the human search engine for every past job
• Trust erosion — clients assume you are disorganized even when the flying was clean

A portal does not replace good scope writing. It stops good scope from disappearing into email archaeology.

Checklist before you tell clients “use the portal”

1. Client email on the job matches the email they will register with
2. Quote was issued from the stack (not only a one-off PDF outside the record)
3. Invoice conversion path is clear for your shop (deposit vs on-delivery)
4. Deliverables are on the private project you intend to share—not only on your laptop
5. Soft CTA for your own shop: point buyers at pricing if they are evaluating the stack; do not oversell features that are not on /client-login

What this post is not claiming

• Not that payment links are the portal (see quote-to-Stripe)
• Not milestone wizards, escrow dashboards, or invented portal screens
• Not SkyView waitlist features as shipping portal UI
• Not Flight Hub 2
• Not a marketplace hire pitch

Bottom line

A drone client portal earns its keep when quotes, invoices, and files share one client login. Pilot Ledger’s live path is /client-login, email-matched registration, and homepage delivery of maps/point clouds on private projects beside billing. Keep pay-link mechanics in the invoicing article. Keep the portal story honest. Soft next step for shops evaluating the stack: pilotledger.com/#pricing.