Competitor Recent Moves & Trajectories

Competitor Recent Moves & Trajectories

Competitive analysis isn't a one-time snapshot — it's a directional read. Where a competitor is today is less important than the trajectory they're on. A tool that's moving upmarket is actively abandoning its SMB customers. A tool that's staying simple is capping its ceiling. Understanding these vectors helps you see which lane is opening up for Tightly.

What they've shipped recently: Since the 2022 Sage acquisition, the product roadmap has slowed visibly. The major releases have been ERP integration expansions (Sage X3, Sage Intacct), multi-entity support for brands with multiple legal entities, and enterprise-grade audit logging. The Shopify-native improvements that defined the pre-acquisition product have largely stopped.

Trajectory: Moving upmarket toward enterprise and ERP-dependent customers. Sage's existing customer base is mid-to-large enterprise; they want Inventory Planner to serve as the demand planning module for that segment, not to compete on Shopify App Store discovery.

Weakness they're creating: The $1M-$10M Shopify brand is no longer the priority customer. Support is slower, the product moves slower, and pricing is higher. This is a large segment being actively deprioritized — and they're vocal about it on review sites.

What Tightly should do with this: Identify Inventory Planner accounts that are 12-24 months post-acquisition (they'll have lived through at least one renewal cycle) and are starting to feel the service degradation. These are the highest-intent switchers in the market.

What they've shipped recently: Prediko raised in 2023-24 and used the capital to invest in their Shopify-native experience. Recent additions include bundle forecasting (forecasting demand for bundles as a unit, not just components), a refreshed analytics UI with visual DoS charts, and improved onboarding with a guided setup flow. They've also added Shopify Markets support for brands selling in multiple regions.

Trajectory: Stay Shopify-native, stay simple, stay affordable. Prediko is explicitly not trying to be Netstock. Their bet is that there are thousands of Shopify brands in the $500K-$3M range who need 80% of the functionality at 20% of the complexity, and they can own that segment.

Weakness they're creating: The ceiling is real and getting lower as brands grow. Bundle forecasting helps, but multi-location remains limited. More importantly, their forecasting engine is not getting meaningfully more sophisticated — it's a good model applied simply, not a great model. Brands that grow into complexity will outgrow Prediko before they outgrow Tightly.

What Tightly should do with this: Don't compete with Prediko on simplicity — you'll lose, and it's not your segment. Instead, define the upgrade criteria clearly: when a brand has more than 3 warehouses, more than 300 active SKUs, or a seasonal coefficient above 2x, they need Tightly. Make the upgrade story explicit in marketing and sales.

What they've shipped recently: Netstock has added S&OP-style planning layers — scenario modeling, demand consensus workflows, executive dashboard views. They've deepened ERP integrations (SAP, Oracle NetSuite) and are increasingly marketing to VP Supply Chain and COO buyers rather than ops managers.

Trajectory: Moving toward enterprise supply chain planning — less pure replenishment, more planning orchestration. They want to be in the same conversation as Kinaxis and o9 Solutions, just for mid-market.

Weakness they're creating: They're leaving the "I need better Shopify replenishment" customer behind. The brands who used Netstock for Shopify-native demand planning and liked it are now finding the product increasingly complex, expensive, and oriented toward problems they don't have.

What Tightly should do with this: The Netstock customers who are $3M-$15M Shopify-first brands are a natural fit for Tightly. They want sophistication without enterprise complexity. Tightly's pitch against Netstock is: "You're paying for 60% of a tool you don't need. We're built for your size."

What they've shipped recently: Both tools have leaned into AI-labelled features — what are essentially heuristics and analytics wrapped in an "AI-powered" marketing layer. More significantly, they're consolidating into full OMS + inventory suites: order management, warehousing, inventory, and light demand planning in one platform. They've added Shopify Plus integrations and are marketing to brands doing $20M+.

Trajectory: Becoming the operational backbone for high-complexity, high-volume DTC brands. Their play is consolidation — replace 4-5 point solutions with one platform.

Weakness they're creating: The consolidation play adds complexity, not removes it. Brands at $3M-$15M don't want to replace all their tools; they want their inventory planning to work better. Cin7 and Brightpearl require implementation projects, dedicated admins, and ongoing consultants to maintain.

What Tightly should do with this: Explicitly position as a point solution that integrates with what brands already use (Shopify, ShipBob, their 3PL, Gorgias, Klaviyo). "We make your inventory smarter without replacing your stack" is a direct counter to the Cin7/Brightpearl consolidation narrative.

Step back and look at all four trajectories together:

• Inventory Planner → moving upmarket (enterprise ERP)
• Netstock → moving upmarket (enterprise supply chain planning)
• Cin7/Brightpearl → moving upmarket (full OMS consolidation)
• Prediko → staying downmarket (simple, cheap, Shopify-native SMB)

The $3M-$30M DTC brand — sophisticated enough to need real forecasting, too small to need ERP integration, Shopify-native, growing — is being left behind by everyone moving upmarket and underserved by the simplicity-first downmarket tools.

This is Tightly's lane. Not because no one has entered it, but because everyone who could compete there is actively choosing to leave.

The PM implication: every major roadmap decision at Tightly should be evaluated against one question — does this feature serve the $3M-$30M Shopify brand better than anyone else can, or does it pull us toward complexity we don't need or simplicity we've outgrown?