Proration Rules That Don't Generate Support Tickets
Mid-cycle upgrades, downgrades, seat changes and refunds each need a stated rule. Where the rule is implicit, the invoice becomes a conversation.
Premium ContentRecent posts
The US Mortgage Closing Timeline, Step by Step
From application to recording, with the points where a closing usually slips — and which of the deadlines are set by regulation rather than by the lender.
Write Off Dead Stock on a Schedule
Obsolete inventory doesn't get written off because the write-off hits this year's numbers while the hope of selling it costs nothing visible. That asymmetry is the whole problem.
Pipeline Stages That Mean Something
If a stage is defined by how the rep feels about the deal, your forecast is a mood. Define stages by what the buyer has done and the numbers start working.
Requisition or Purchase Order? Getting the Split Right
The requisition is an internal request for permission. The purchase order is an external commitment to pay. Collapsing the two is how unapproved spend happens.
TRID Disclosure Deadlines: What the Clock Actually Requires
Two forms, several deadlines, and two different definitions of 'business day' depending on which deadline you're counting. Here is how the timing fits together.
Map the Process Before You Automate It
Automating the process on the diagram is easy. The process people actually follow has four undocumented branches, and that's the one your bot will meet.
Measuring Forecast Accuracy Without Fooling Yourself
Aggregate accuracy always looks better than item-level accuracy, and errors that cancel out report as precision. Pick the measure that can't flatter you.
Matter Budgets Clients Actually Accept
Clients rarely object to the total. They object to being surprised by it. A budget with phases and a variation trigger converts the argument into a decision.
Dunning Emails That Collect Without Losing the Client
Most overdue invoices aren't refusals to pay. They're an expired card, a missing PO number, or an invoice sent to someone who left — and the tone of the first reminder decides how the rest goes.
Lead Routing: Speed Beats Cleverness
An elaborate scoring model that takes an hour to assign a lead loses to a crude round-robin that assigns it in ninety seconds.
Reviewing an NDA in Ten Minutes
Most NDAs are routine and most reviews of them are slow. Six clauses carry nearly all the risk — read those first and the rest is a skim.
Closing the Gap Between Time Tracking and the Invoice
Revenue leaks in the space between the work being done and the line item being billed. The leak is measurable, and most of it comes from delay.
Run the Migration Three Times Before You Trust It
A migration that has been rehearsed once has been tested under conditions that will never recur. The third run is where the real defects surface.
Recovering Failed Payments Without Annoying Customers
A large share of involuntary churn is an expired card, not a decision to leave. Retry logic that reads the decline reason recovers most of it quietly.
Shortening the Month-End Close Without Cutting Corners
A ten-day close is rarely caused by hard accounting. It's caused by waiting — for a bank feed, a stock count, an approval nobody chased.
When a Semantic Layer Starts Paying for Itself
For one team and three dashboards it's overhead. The crossover comes earlier than most people think, and the signal is duplicated business logic.
Tail Spend: The 80% of Suppliers Nobody Manages
A small number of suppliers get contracts, reviews and negotiated rates. The long tail gets none of that, and it's where the compliance risk quietly lives.
Reading a Title Commitment: The Schedules in Order
The commitment tells you what the insurer will cover, what it wants done first, and what it refuses to cover at all. Most closing surprises are sitting in one schedule.
Moving a CPA Practice From Compliance to Advisory
Everyone agrees advisory is the future and most firms stall in the same place: the compliance work fills the calendar, so advisory never gets scheduled.
ERP Training That Survives Go-Live Week
Classroom training three weeks before go-live has largely evaporated by the time it's needed. What holds is practice on real tasks with real data.
Test Your Data Like You Test Your Code
A silent data bug is worse than a failed job. The pipeline ran, the dashboard is green, and the numbers have been wrong since Tuesday.
A Client Intake Process That Screens, Not Just Collects
Intake is usually treated as data collection before the real work. Treated as a screen instead, it is the cheapest point at which a firm can decline the wrong matter.
Building a Single-Source Risk Register
Most organisations can't name their sole-source dependencies until one of them fails. The register takes a week to build and it is the cheapest resilience you will buy.
Warehouse Slotting: Put the Fast Movers Where the Feet Are
Travel is most of the time in a manual pick operation. Slotting is the cheapest lever on it — no new equipment, no new system, just moving stock to better locations.
Running Conflict Checks in a Small Firm
Large firms have systems for this. A four-lawyer practice can get most of the protection with a disciplined list, consistent naming, and one rule about when to search.
Designing the Human Step Into an Automated Process
A human placed in an automated flow to 'check the output' will approve almost everything. Give them a decision, the context to make it, and a way to disagree.
Build a Clause Library Before You Need It
Without one, every contract is drafted from the last similar contract — which was itself drafted from the one before, carrying forward a concession nobody remembers making.
Wire Fraud at Closing and How Firms Stop It
Real estate closings move large sums on a known date to a party the buyer has never met. Attackers know all three facts, and the defence is procedural rather than technical.
Writing a Document Retention Policy You Can Follow
A policy that says 'keep everything for seven years' is easy to write and impossible to defend. The workable version names categories, periods, and a deletion mechanism.
One Metric, One Definition, One Owner
When two dashboards disagree about revenue, the problem isn't the tooling. It's that nobody was ever made responsible for deciding what revenue means.
Document Automation in a Practice That Bills by the Hour
The objection is that automation destroys billable hours. The firms that adopt it find the constraint was never hours available — it was partner attention.
Why Nobody Opens Your Dashboard
It loads, the numbers are right, and usage is twelve views a month. The usual cause is that it answers a question nobody has to act on.
Workpapers a Reviewer Can Follow
The test of a workpaper isn't whether the preparer understood it. It's whether someone who has never seen the file can reach the same conclusion without asking a question.
Automate the Approval, Not the Judgement
Most approval steps are a person checking that four fields are within policy. Automate those and you free the approver for the cases that genuinely need a human.
What a Data Processing Agreement Has to Cover
A DPA isn't a formality attached to the main contract. It allocates responsibility for a category of failure that is increasingly expensive to get wrong.
RPA or a Real Integration? A Decision Guide
Screen automation is fast to build and fragile by construction. There are cases where that trade is right — and a clear test for when it isn't.
Capacity Planning Around Busy Season
Busy season isn't a surprise. It arrives on the same dates every year, and most firms still plan for it in January by asking people to work harder.
ABC Analysis: Sorting Inventory by What Actually Matters
Ranking stock by annual value tells you where to spend management attention. Ranking it by value alone tells you to ignore the cheap part that stops the line.
Replace the Annual Stocktake With Cycle Counting
Shutting the warehouse for a weekend once a year gives you one accurate day and eleven months of drift. Counting a little every day gives you a number you can trust in March.
Safety Stock: The Formula and When It Lies to You
The standard formula is sound and its assumptions are usually false. Knowing which assumption your business breaks tells you which direction the number is wrong in.
Lead Time Variability Costs More Than Long Lead Times
A supplier who reliably takes six weeks is easier to plan around than one who averages three but ranges from one to eight. Consistency is worth paying for.
The Three-Way Match, Explained Without Jargon
Purchase order, goods receipt, invoice. If all three agree you pay; if they don't, something specific is wrong — and which pair disagrees tells you what.
A Supplier Onboarding Checklist That Prevents Fraud
Most payment fraud doesn't break into a system. It asks politely, by email, for bank details to be changed — and the control that stops it is boring and cheap.
The Five Phases of an ERP Implementation Nobody Budgets For
The software licence and the integrator's statement of work are the visible costs. These five phases are where the schedule actually goes.
The ERP Customisation Trap
Each customisation is defensible on its own. Together they become the reason you cannot take an upgrade — and the reason the next migration costs more than the first.
CRM Data Hygiene That Actually Sticks
Every team runs one big clean-up, feels good for a month, then drifts back. The fix isn't a bigger clean-up — it's making the bad record impossible to create.
Why Your Sales Team Ignores the CRM
Adoption problems are almost never training problems. If the CRM takes more out of a rep's day than it puts back, they will route around it — and they will be right to.
