From Estimate to Reality: How the 'Actuals' Button Locks In Your True Profit

# From Estimate to Reality: How the 'Actuals' Button Locks In Your True Profit

The price you sent the client was your best guess. The mission you just flew is what actually happened. Logging the actual numbers, aka 'actuals' after the flight — the real hours on site, the real drive, the real edit time, the real post-processing rate, the real mileage — is what turns a calculator into a business ledger. And in Rotor Rate, every one of those numbers flows straight back into your effective $/hr, your income, and your taxable profit. No spreadsheet gymnastics, no second guess.

What I'm going to cover:

• A clear understanding of why an unlogged mission is a mission you can't price the next one against
• The exact fields the Actuals button captures and what each one moves downstream
• A 3-step post-flight discipline that takes under a minute per mission
• A worked example showing how actuals reshape your effective $/hr, fuel cost, and tax estimate

Why estimates are never enough

Every quote starts as a forecast: 1.5 hours on site, a 30-minute drive each way, two hours of editing at your standard rate. Reality get's you close, but almost never matches the slide:

• The roof inspection that "looked simple" turned into an additional 30-minutes because the homeowner wanted a second pass on the chimney.
• The 30-minute drive was 50 minutes because a wreck closed the interstate.
• Editing ran long once you noticed the sun glare and re-graded the orbit shots — and the Light Detection and Ranging (LiDAR) cleanup on the next job ran at a higher $/hr than your photo-edit baseline.

If you never write those numbers down, your $/hr stays a fantasy and tax season becomes a guess. The Actuals button is how you replace fantasy with the receipt.

Where the Actuals button lives:

On any completed mission in the Workspace tab, the row card surfaces an Edit actuals action. Open it and you'll see every field that originally fed your price, side-by-side with an "actual" column:

• Hours on site
• Drive hours (one-way)
• Miles (with a toggle to enter either one-way or round-trip distance; a colored pill confirms your choice and shows the equivalent distance underneath)
• Editing / post-processing hours
• Editing / post-processing rate ($/hr) — separate from your on-site rate, so scan-to-Building Information Modeling (BIM) or LiDAR cleanup at $275/hr doesn't get blended into a $150/hr photo edit
• Platform / deliverable sub-type (e.g. a network data upload (FlyGuys, etc.,), photogrammetry mesh, digital twin, LiDAR reality capture)
• Out-of-pocket expenses (you can also add these directly from the mission row)
• Final invoice amount (if it changed)

Fill in only what changed — leave the rest blank to keep the original estimate. Save, and Rotor Rate immediately recalculates everything downstream.

What the recalc actually does

This is where Rotor Rate earns its keep. The instant you save actuals, the math re-runs against your locked-in rate snapshot from the day you completed the mission — not today's settings. That matters: a rate change you make six weeks later doesn't retroactively rewrite history.

Here's what flips:

Effective $/hr

Your price said $185/hr based on 1.5 site hours + 1 hour total drive. You actually worked 2.25 + 1.4 = 3.65 hours. On the same invoice, your true effective rate just dropped from $185/hr to ~$123/hr. The verdict chip on the row card updates — sometimes a "Healthy" mission quietly slides into "Thin margin" once the real clock is in.

Gross income, net profit

Fuel cost recalculates against the actual round-trip miles × your local gas price. Out-of-pocket expenses and editing time roll into a fresh expense subtotal — and because post-processing hours and rate are both editable, a 10-hour scan-to-BIM handoff at $275/hr lands in your P&L as $2,750 of edit revenue, not a blended guess. The profit number on the mission card and in your monthly rollup reflects what really happened, not what you hoped for.

Mileage log

The auto-mileage log uses actual miles when present, falling back to estimated otherwise. That's the number that feeds the Internal Revenue Service (IRS) business standard mileage deduction at year-end ($0.725/mi) — getting it right is worth real dollars at tax time. If you enter round-trip miles, Rotor Rate automatically halves the number internally for the log to keep IRS compliance accurate.

Quarterly tax estimate

The `/workspace` quarterly tax widget aggregates net profit across all completed missions in the current quarter. Every actuals edit moves the estimate. Pleasant surprise: the widget often shows you owe less than the original quotes implied, because most pilots over-estimate drive and under-estimate editing.

Estimate-vs-actual variance

Rotor Rate quietly tracks the change between every estimate and actual you log. After a dozen missions you'll see a pattern — maybe you consistently under-priced editing by 25%, or your LiDAR cleanup always runs an hour over. That signal feeds the pricing suggester so the next quote bakes in your real-world bias instead of repeating the same mistake.

Why the post-processing fields matter more than ever

Rotor Rate now prices specialty deliverables on their own rate bands — photogrammetry meshes, LiDAR reality capture, scan-to-BIM/Revit handoff, Matterport digital twins, and cultural-heritage as-builts each carry editing rates well above a standard photo edit ($150–$325/hr depending on sub-type). Two implications:

1. Always log the post-processing rate, not just the hours. A $275/hr Revit hour and a $150/hr photo-edit hour are not the same dollar; recording them separately keeps your effective $/hr honest and your tax-time revenue mix accurate.
2. Pick the right deliverable sub-type when you save actuals. That tag is how Rotor Rate groups your history so the suggester can tell "your LiDAR jobs run 20% over edit estimate" apart from "your real-estate edits are dead on."

If you're on a paid plan and fly recurring data-upload work for networks like RaaD or FlyGuys, Rotor Rate also surfaces an auto-fine-tuning hint on the post-processing row: a rolling 30-job average of your actual upload hours for that specific network + deliverable sub-type. Tap it to prefill the Hours field on the next quote. The hint only exists because of the actuals you've been logging — no actuals, no hint.

A worked example

Before actuals: $450 ÷ (1.5 + 1.0 + 2.0) = $100/hr blended, ~$72 fuel, ~$320 net.

After actuals: $450 ÷ (2.25 + 1.4 + 3.5) = $63/hr blended, ~$96 fuel, ~$272 net, +12 mileage deduction miles logged.

Now swap the deliverable for a LiDAR reality-capture job: 5 hours of post-processing at an actual $275/hr instead of $150/hr is a $625 swing in recognized edit revenue on a single mission — the kind of number that only shows up correctly if you log the rate alongside the hours.

The 3-step discipline that makes it work

The Actuals button only pays off if you actually use it. The habit that works:

1. Land, pack, log. Before leaving the site, open the mission and update on-site hours (this will be much easier when the mobile app is released - coming soon!).
2. Log the drive when you're back at the desk. Drive time and miles, while it's fresh. Pick the one-way or round-trip toggle that matches how you tracked it.
3. Update editing when you deliver. Don't wait until invoice day to backfill three weeks of edits — and set the post-processing rate to whatever the deliverable actually warranted, not your default.

Treat it like a flight log. Five seconds per field, every time, and your $/hr stops being a story you tell yourself and starts being a number you can defend.

Pitfalls to avoid

• Backfilling a month of missions at once. Memory fades; you'll round to the original estimate and the feedback loop dies.
• Leaving the post-processing rate at default. A LiDAR hour logged at a photo rate distorts both this mission and the next quote.
• Skipping the invoice field when scope crept. If the invoice changed, log it — otherwise the verdict and tax estimate are wrong.
• Treating "Thin margin" verdicts as a one-off. Three thin-margin verdicts in a row on the same deliverable type is a pricing problem, not bad luck.

Why this matters for the next quote

Every actual you log makes the next price sharper. Rotor Rate's pricing suggester reads your estimate-vs-actual history — segmented by deliverable sub-type — and nudges defaults. If your real LiDAR editing time runs 30% over estimate, your next LiDAR quote reflects it before you even hit Save. The Actuals button isn't bookkeeping. It's the feedback loop that turns each completed mission into a smarter price for the next one.

Resources & further reading

• IRS Standard Mileage Rates — the deduction your logged miles feed
• IRS Small Business and Self-Employed Tax Center — Schedule C, quarterly estimates, recordkeeping
• FAA Safety Team WINGS Program — free safety credits including the monthly Pro Tips for UAS webinar
• Drone Service Provider Alliance (DSPA) — industry advocacy and operator best practices
• Rotor Rate guides: Why 'Live' Spreadsheets Lie · Drone Post-Processing Pricing Per Industry · Mission Management & Business Management

The free services pricing calculator gets you the up-front quote. The Actuals button — and the locked-in rate snapshot, variance tracking, and auto-fine-tuning hints that ride on top of it — are what a paid Rotor Rate plan unlocks. That feedback loop is the whole reason a quote tomorrow is sharper than the one you sent today.

<!-- auto-freshened: 1.5, 1.8, 1.10 on 2026-08-07 -->