Track a typical purchase file honestly, from first consultation to funding, and the total commonly lands around 8 to 12 hours. The split matters more than the total: the licensed, relationship-driven work — consultations, structuring, product and lender selection, the pivotal calls — is usually only 3 to 4 of those hours. The remaining 4 to 6 hours is process work: collecting and chasing documents, packaging the submission, tracking conditions, following up with the lender, coordinating with a lawyer or appraiser. The rest is the switching cost of jumping between a client call and a document checklist all day.
Roughly two-thirds of a file, in other words, is work that doesn't require a licence — it requires precision and follow-through. That single ratio is the foundation for almost everything else in this course.
Multiply it out. At 10 files a month and 10 hours a file, the files alone consume 100 hours — roughly 25 hours a week — before any time spent prospecting, following up on leads, managing referral relationships, continuing education, or running the rest of the practice. Many solo brokers land at a functional ceiling somewhere around 12 to 15 files a month, and brokers who claim meaningfully more are often borrowing the extra hours from marketing, family, or sleep — a loan the business eventually calls in.
What fails first is rarely volume itself; it's quality, quietly. Response times stretch, status updates thin out, a condition gets chased a day late, and next quarter's pipeline empties because prospecting was the flexible line in the week that gave way first. The ceiling doesn't announce itself with a dramatic failure — it shows up as a slow leak in numbers three months out.
Almost every broker who estimates their own hours-per-file underestimates it, because the process lane hides in fragments too small to remember individually but too frequent to be free: a three-minute status text here, a quick check-in call there, a five-minute context switch back into a document review. Add those fragments up over a real file and the total is reliably higher than a broker's gut estimate.
The fix isn't complicated: track one full file, honestly, from first contact to funding, logging every piece of work as it happens rather than reconstructing it from memory afterward. A simple timer app or even a running note is enough. Do this for two or three files across a normal month, not your easiest one, and you'll have a real number instead of an assumption to build the rest of this course's decisions on.
Working longer hours buys perhaps 10 to 20% more capacity for a quarter, and then hands the cost back as burnout, errors, and stalled marketing — the exact things a broker at capacity can least afford to lose. Working faster through better templates and tighter routines is genuinely worth doing, covered in the next two modules, but it yields single-digit gains on its own; you cannot template your way out of two-thirds of every file being process work. Cherry-picking larger files raises revenue per hour without raising the number of files you can actually run — a legitimate strategy, but a different lever, and one that eventually meets the same wall.
The honest conclusion, before any decision about delegating or hiring gets made: once you're near the ceiling, optimising inside the current structure — the same person doing the same mix of work, just trying to do it faster — is rounding error. The structure itself, specifically who does the process work, is the variable that actually matters, and that's exactly what the next several modules work through.
A broker estimates spending about 5 hours per file, but a careful two-week time-tracking exercise shows the real number is closer to 9 hours. What does this course say is the most likely explanation?
Underestimating hours-per-file is the norm, not a sign of personal slowness — the gap almost always comes from fragmented process work that never gets consciously logged, not from any single dramatic time sink. The tempting answer blames the tools or the person, but the real point is structural: fragments of process work are invisible until they're deliberately tracked, which is exactly why guessing is unreliable and measuring matters.
