**A Difficult Conversation About Quality Control and the Future of iGUIDE**

A Difficult Conversation About Quality Control and the Future of iGUIDE

It genuinely breaks my heart to write this because I am, and have been for a very long time, a huge fan of iGUIDE.

I’ve been working with iGUIDE since the IMS-4 days, more than 10 years ago. Back when we used Trello (I think that’s what it was called!) to place orders and move projects through the production process. LOL.

I’ve had the privilege of watching Planitar and iGUIDE grow, evolve, and become bigger and better over the years. I’ve always been proud to be part of that journey and to have such incredible technology in our hands. I’ve also always appreciated the attention to detail in the work. After all, we are in the measurements and documentation business. Accuracy isn’t just a nice-to-have; it’s the foundation of what we sell.

For roughly nine out of those ten years, I had complete confidence in the finished product. I could receive a project, turn around, and deliver it to my clients without having to second-guess the work or spend time checking every detail.

Unfortunately, something has shifted in 2026.

At the beginning of the year, I started noticing errors in deliverables. Around the same time, I began seeing other operators raising similar concerns here in the forum. Some were more vocal than others, but the common thread was becoming difficult to ignore.

Initially, I approached this with patience and understanding. Every business experiences growing pains, and Planitar is certainly not immune to that. I defended the company when others were critical, remained optimistic, and genuinely hoped these issues were temporary.

But we’re now eight months into what feels like an uphill battle, and my patience is being tested.

Of my last 16 projects, I’ve experienced significant and minor errors in 7 of them. That’s approximately 43% of my projects requiring some level of correction or intervention.

This has become an enormous amount of additional work. I’m spending valuable hours identifying, documenting, communicating, and correcting errors while simultaneously trying to operate my own business and look after the clients who depend on me.

Quite frankly, this is no longer sustainable.

And I want to be clear about the types of errors I’m referring to.

These aren’t simply mislabeled rooms or minor drafting inconsistencies. I’m talking about missing structural support posts, doors appearing where none exist, missing windows, and incorrect window measurements.

These are fundamental details that architects, engineers, and construction professionals rely on when making decisions. When we position ourselves as documentation and measurement experts, the accuracy of these deliverables is critical.

The consequences go well beyond an inconvenience or an extra hour of drafting corrections. Incorrect documentation can undermine client confidence, damage an operator’s reputation, and potentially expose small business owners to significant financial and professional liability.

As independent operators, we rely on Planitar to have robust quality assurance processes and procedures in place. We simply cannot be expected to independently audit every single detail of every deliverable before passing it along to our clients.

So, why am I posting this?

I’m not looking to start a complaint session or create a “bitching fest.” That’s not productive, and it’s certainly not my intention.

I’m looking for an honest, constructive conversation with fellow operators. I cannot imagine I’m the only one experiencing this, and I think it’s important that we start talking openly about what’s happening.

I would genuinely welcome a conversation with anyone at Planitar who is willing to sit down and review my experiences in detail. I’m happy to share specific examples, documentation, and the time and effort involved in addressing these issues.

I’m also interested in connecting with other operators who have noticed a change in quality over the past year. I’d like to understand whether our experiences are isolated or part of a broader issue, and more importantly, whether there are constructive ways we can work together to help Planitar get things back on track.

I haven’t lost my appreciation for the technology, nor have I forgotten the years of great work and innovation that brought us here.

But being a loyal supporter also means being willing to speak up when something isn’t right.

I’m raising this out of respect for the company, the technology, and the community of independent operators who have built their businesses around it.

I’d really appreciate hearing your experiences and perspectives. Let’s have an honest, professional, and productive conversation.

1 Like

Hi Alex,
Thank you for writing this, and for the way you wrote it. Ten years with iGUIDE, going back to IMS-4 and the Trello days, means you’ve seen this product through all our growth stages. When someone with that history tells us something has slipped, we need to listen closely.

You’re right about the stakes. Missing posts, phantom doors, missing windows and wrong window dimensions are not cosmetic. Operators put their names on these deliverables, and their clients make real decisions from them. You shouldn’t have to audit every plan before you can trust it, and 7 errors in 16 projects is not the standard we hold ourselves to.

I’d like to take you up on your offer to sit down and go through your examples in detail. I’ll bring our quality and production leads so we can trace each error back to where it happened in our process and talk through what we’re changing. I’ll message you directly to find a time.

To any other operators who have seen similar issues this year: please message me. Specific project links are the most useful thing you can share, because they let us find patterns instead of guessing.

Thank you for speaking up, and for caring enough about this product and community to do it constructively.

Matt Ignor
VP, Operations
E: mignor@planitar.com

2 Likes

Hi Matt

I appreciate your quick, proactive and genuine response. I look forward to our meeting and to work on a solution to these growing pains.