During a discovery call a few days ago with a construction manager at a commercial pool builder, the conversation turned to Dynamics Project Operations, and we told him something that surprised him: a couple of weeks earlier we'd put together a large Project Operations proposal for a different company, and then recommended they not proceed with it.
That's worth explaining, because it gets at something every SMB buyer evaluating an ERP or project platform should keep in mind. The platform being powerful doesn't mean it's the right fit for how your team works.
What Project Operations is good at
Microsoft Dynamics 365 Project Operations is built for project-oriented, professional-services style businesses: firms that deliver engagements, track time against those engagements in a standardized way, manage the tasks tied to them, and bill from that work. Think of it as project management connected to a finance and billing engine, so the hours and milestones you track flow straight through to invoicing.
For a company whose whole model is design, build, and deliver against projects, that's a natural direction to explore. But natural direction and confirmed fit are two different things.
Why we recommended against our own proposal
The client we told no to had an accounting team that would not budge on certain details of how time gets tracked, where it gets invoiced, and what gets handed off to accounting. Those aren't cosmetic preferences. They're the exact seams where Project Operations either fits beautifully or fights you at every step.
If the platform's model for tracking and invoicing doesn't line up with how accounting insists on working, you don't get a smooth rollout. You get an expensive tool that everyone works around, which is the worst possible outcome for a six-figure investment. So the recommendation was not to proceed: with that constraint in place, the platform would fight the process at every step.
A platform that fights your accounting process becomes an expensive tool everyone works around.
The details that decide fit
Before anyone should sign an SOW for a project platform, these questions need clear answers. They sound small. They aren't.
- Where does time get tracked today, and by whom?
- Where and how does that time turn into an invoice?
- What exactly gets passed to accounting, and in what form?
- What is your current system of record for billing today, and is it staying or going?
- Which milestones drive billing, and how are they triggered?
- Is accounting willing to adapt its process, or are certain steps non-negotiable?
The gap between a great implementation and a painful one usually isn't the software. It's whether the finance workflow the software assumes matches the one your team refuses to change. Find that out before you buy, not after.
How we surface this before you spend
Our approach front-loads these questions on purpose. A discovery call gives us the shape of the business. A detailed questionnaire (one you can circulate to your sales, project, after-sales, and accounting leads so it isn't all on one person) fills in the specifics. Only then do we put together a rough, high-level estimate, and we treat the first review meeting as a simple checkpoint: did we understand the situation, does the approach make sense, are we on the same page on budget, and should we keep talking?
If it's a solid yes, we build a demo around your real workflows and the people who'll use the system every day. If the details reveal a mismatch, better to know at the questionnaire stage than after go-live.
If you're weighing a big platform decision
A new ERP or project platform changes how you deliver work and how you get paid, so fit matters more than features. If you're evaluating Business Central, Project Operations, or anything in that family and want a clear read on whether it fits your accounting reality, we're glad to walk through the details with you before a dollar is committed. Reach out anytime to think it through.