PracticePro 365

Steven Templeton built this after running Templeton & Company, a Top 300 accounting firm, and the lineage shows in what the product prioritises. It is a firm management layer sitting on Microsoft Dynamics 365 and the Power Platform, so client records, engagements, time entry, WIP release, collections, budgeting and forecasting all live in the same tenant as Teams, Outlook, SharePoint and Power BI. Staff enter time from mobile or desktop, tax and CAS work routes through due-date triggers, engagement letters generate from the client record, and partners read utilisation and realisation off dashboards rather than exports. The company's Microsoft roots go back to 2003, when it was picked as a partner for the original Microsoft CRM launch, and the platform has been developed for over a decade since.

The fit is narrow and worth stating plainly. The pricing page says the product is "Built for 50+ Users. Scaled for 1,000+", and the named customers are BDO USA, Crowe USA, Weaver and Rehmann. That is a different buyer from the five-person tax practice this directory usually serves. The firms it suits are at the top of our range or past it: 40 staff and up, multiple offices or post-merger entities, already committed to Microsoft 365, and looking to replace a stack of disconnected systems with one that finance and IT already know how to administer.

Several gaps matter for a US tax firm. No rates are published at all, so every evaluation begins with a sales call and a quote based on firm size. There is no published integration with Drake, UltraTax, Lacerte, ProSeries or CCH Axcess, and none with QuickBooks Online or Xero, so return status and ledger data are tracked in whatever the firm already uses. The product pages describe engagement letter generation but stop short of confirming a client portal or e-signature, which in 2026 most competitors lead with. Security documentation extends to a SOC 2 Type 1 claim on the site, one level below the Type II report that TaxDome and Qount publish. And the deeper commitment is architectural: this is a Dynamics deployment, so a firm without Microsoft 365 is buying an ecosystem, not an app.

Against Karbon, PracticePro 365 trades the polished work-and-email experience for depth in budgeting, forecasting and partner reporting. Against BQE Core, it covers similar time and billing ground but assumes the Microsoft stack rather than standing alone. Aiwyn overlaps on the revenue and collections side for larger firms and is the more likely head-to-head at that size.

The inherited tier was dated, and the evidence does not support it. The site carries a 2026 copyright, the product pages describe current work including AI automation and Business Central integration, the support portal is live, and the customer list includes firms that renew software only when it works. What is true is that the buyer profile sits above this directory's core reader, and that the published detail thins out exactly where a small firm would look first, at price, portal and tax software integration. Strong-option, on the specific fit of a Microsoft-committed firm large enough to justify the implementation.