<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Weighing this decision and honestly dreading either direction right now.]]></title><description><![CDATA[<p dir="auto">Weighing this decision and honestly dreading either direction right now.<br />
We're about four months into a route optimization build and progress has slowed to a crawl, communication feels one sided, and half our questions go unanswered for days. Considering whether to switch to a different <a href="https://www.remotestate.com/industries/logistics/" rel="nofollow ugc">logistics software development company</a> or just push through since we're already this deep into the build.<br />
Never had to make this call mid project before so genuinely torn on what's the smarter move here.<br />
Things I keep going back and forth on:<br />
How much time a handoff to a new team would realistically cost us at this stage<br />
Whether slow progress now is a sign of bigger problems ahead or just a rough patch<br />
If you've switched vendors partway through something like this, was it worth the disruption?</p>
]]></description><link>https://community.bemeapps.com/topic/40141/weighing-this-decision-and-honestly-dreading-either-direction-right-now.</link><generator>RSS for Node</generator><lastBuildDate>Mon, 21 Sep 2026 13:38:37 GMT</lastBuildDate><atom:link href="https://community.bemeapps.com/topic/40141.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 21 Sep 2026 12:19:35 GMT</pubDate><ttl>60</ttl></channel></rss>