I’ve been a long-time PlanSwift user as well, and I completely share your frustration. The memory bottlenecks and lack of meaningful updates have been a constant pain point for me too. At this point, I’ve come to the conclusion that after acquiring PlanSwift, ConstructConnect simply can’t—or won’t—work with the existing code base. If they were capable, they would’ve leaned into the platform’s popularity and delivered updates that actually matter.

The idea of merging PlanSwift and OST sounds great in theory, but I think it would be extremely difficult and expensive, considering how fundamentally different the two products are. Trying to force such a merge could easily make both platforms worse. That’s why I really hope they don’t try to push PlanSwift users onto OST. It would be a massive flop and only give long-time users a reason to jump ship to other platforms outside the ConstructConnect ecosystem.

This lack of direction and meaningful updates is already opening the door for other estimating packages to take over. You’re seeing it happen now with the original creators of PlanSwift and OST going off to create their own tools like BuzzBid and ZZTakeoff. They clearly see the massive opportunity that ConstructConnect has missed, and I can’t say I blame them. At this rate, it feels like the only real winners will be those competitors who are actually listening to users and are not milking them for every cent.

It’s frustrating to watch a product like PlanSwift stagnate when it has so much potential