A Hypothetical Tightly Roadmap

A Hypothetical Tightly Roadmap

A roadmap is a communication tool as much as a planning tool. The best roadmaps don't list features — they explain the bets the team is making and why. This lesson walks through a hypothetical 12-month Tightly roadmap organized into four strategic themes, with the customer segment logic and retention metric behind each one.

This isn't the actual Tightly roadmap (you'll discover that in your first weeks). It's a structured example of how to think about sequencing, rationale, and internal alignment — so you can evaluate the real roadmap against this kind of thinking.

The bet: PO acceptance rate is the most important early retention metric. If buyers don't accept the recommendations, they're not getting value from the product. The fastest path to improving acceptance rate is not improving the model — it's showing buyers why the model made its recommendation.

What gets built:
- *Recommendation explanation cards*: Every PO recommendation surfaces the top 3 contributing factors (e.g., "Seasonality +40%, 14-day supplier lead time, DoS drops to 6 in 11 days"). Written in plain language, not model parameters.
- *Confidence intervals on forecasts*: Show a range, not a point estimate. "We expect 180-240 units sold in the next 30 days" is more honest and more useful than "208 units." Buyers who see uncertainty make better override decisions.
- *Override tracking and learning loop*: Log every time a buyer adjusts a Tightly recommendation, and track whether their override or the original suggestion turned out to be more accurate. This data feeds model retraining and gives buyers a scorecard that builds trust in the system over time.

Why this comes first: Trust is the prerequisite for everything else. A buyer who doesn't understand the recommendation will override it (lowering acceptance rate), ignore it (making the product unused), or churn. Transparency features don't require new model investment — they expose what the model already knows. The ratio of customer value to engineering effort is the highest of any theme on this roadmap.

Customer segment it serves: All segments, but most directly the ops manager persona who approves POs and needs to understand the recommendation before signing off.

The bet: The biggest source of bad PO recommendations isn't the demand forecast — it's incorrect supplier data. If the tool thinks a supplier delivers in 14 days and they're actually delivering in 22 days, every replenishment suggestion will be late. Fixing the input quality problem fixes the output quality problem.

What gets built:
- *Lead time actuals tracking*: Log the actual delivery date against the expected delivery date for every PO processed through Tightly. Build a rolling average of actual lead time per supplier.
- *Lead time drift alerts*: Surface a notification when a supplier's actual lead time has increased more than 20% from their configured baseline. "This supplier's average delivery time has increased from 14 to 22 days over the last 3 months."
- *Automatic lead time adjustment in replenishment model*: After sufficient data (e.g., 5+ completed POs per supplier), automatically adjust the lead time used in replenishment calculations to match observed actuals — with user confirmation before applying.
- *Supplier scorecards*: A simple view per supplier showing on-time delivery rate, average lead time variance, and MOQ compliance history. Makes supplier performance conversations with reps data-driven.

Why this comes second: Trust & Transparency (Theme 1) establishes why the model recommended something. Supplier Intelligence fixes the cases where the recommendation is wrong because the inputs are wrong. Together they address the two biggest drivers of low PO acceptance rate.

Customer segment it serves: Primarily the ops manager with multiple active suppliers. Brands with 3+ suppliers and variable lead times get the most value. This feature is part of the pitch to larger, more complex brands — it's a differentiation point against Prediko, which has no supplier intelligence capabilities.

The bet: The decision to approve a $180K purchase order is not made by the ops manager — it's made by the founder. Founders think in cash, not units. A feature set that translates inventory decisions into cash impact language opens a new retention lever: CEO-level buy-in.

What gets built:
- *Cash impact calculator on every PO*: "Approving this PO ties up approximately $22,000 in working capital for ~38 days, based on your current DoS for this SKU." Shown alongside the PO recommendation, not buried in a report.
- *Inventory value at risk dashboard*: A single-screen view of total working capital tied up in inventory, segmented by DoS cohort — what's healthy (30-60 days), what's overstocked (90+ days), and what's at stockout risk (<14 days).
- *Optional: Bank balance integration*: Pull cash balance from Shopify Payments, Mercury, or another connected account to show "you have $X available; these approved POs will require $Y over the next 30 days." This is a significant integration build — may be Phase 2 of the theme.

Why this comes third: The first two themes build trust with the ops manager persona. The Cash Flow Layer brings the founder into the product experience. Founder engagement is the strongest predictor of renewal — if the CEO sees Tightly as a cash management tool, not just an inventory tool, the renewal conversation is about business outcomes, not feature comparisons.

Customer segment it serves: Primarily the founder/CEO persona at $1M-$10M brands. Also relevant to CFOs at brands that have hired finance staff. This feature opens a natural expansion motion — from inventory planning to working capital intelligence.

The bet: As Tightly customers grow from $3M to $15M, they add team members. A single-user tool becomes a bottleneck. Building multi-user workflows retains customers who would otherwise outgrow the product and switch to something with role-based access.

What gets built:
- *Multi-user workflows*: Role-based access (Viewer, Buyer, Admin). Buyers can create and submit POs; Admins approve them. Viewer role for executives who need visibility without edit access.
- *Buyer notes on POs*: A comment field on PO recommendations where team members can leave context — "held this PO because supplier confirmed they're out of material until March 15." This reduces the workaround of emailing context outside the tool.
- *Approval workflows for larger brands*: POs above a configurable dollar threshold require a second approval. Simple, not enterprise-complex.
- *S&OP meeting export*: A one-click export of the current inventory health summary (DoS by category, upcoming POs, flagged SKUs) formatted for a weekly ops meeting. Not a full S&OP module — just the data most ops teams screenshot and paste into a slide.

Why this comes fourth: Collaborative features require a user base that's large enough to have multi-person ops teams — and those customers need the core trust and intelligence features to already be working before collaboration layers help. Shipping collaboration first, before explainability and supplier intelligence, builds a better experience for larger teams onto a foundation that smaller teams don't yet need.

Customer segment it serves: Primarily brands at the upper end of Tightly's ICP — $10M-$30M with 2-5 people involved in procurement decisions. This is the feature set that makes retention sticky as customers grow, and that makes Tightly competitive against Netstock for teams that need some S&OP capability without full enterprise complexity.

Every theme in a well-structured roadmap should be explainable in one paragraph that connects: (1) the customer segment and persona, (2) the retention metric it moves, and (3) why it's sequenced here rather than earlier or later.

A template:

> [Theme Name] serves [persona] at [customer segment] by [what it does]. The primary retention metric it moves is [metric] because [causal logic]. We're building this in [Q] rather than earlier because [dependency or sequencing logic] and rather than later because [urgency or opportunity cost].

Using this template in quarterly planning docs forces clear thinking and makes roadmap trade-offs explicit — which is what prevents the roadmap from becoming a feature list with no strategic coherence.