User Personas at Tightly

User Personas at Tightly

Tightly is a B2B SaaS product with a multilayer user structure. The person who signs the contract is rarely the person who uses the product daily. Understanding this separation is critical for prioritization, onboarding design, and churn prevention.

The Economic Buyer: Founder / CEO

Profile: Owns a Shopify brand doing $1M-$20M in revenue. Often the original operator who grew the brand from zero. Increasingly time-constrained as the team grows.

Job-to-be-Done: Protect cash and margins without micromanaging. They want to trust that inventory won't blow up while they focus on growth, marketing, and fundraising.

Success looks like: No more midnight stockout alerts. Monthly inventory costs trending down. A report they can share with their CFO or investor.

Why they churn: They don't see ROI fast enough. The product feels like it requires too much manual setup. Or a cheaper tool (Prediko) comes along that covers the 80% they actually use.

PM implication: The founder needs a fast time-to-value. Onboarding must be self-serve or near-self-serve. ROI calculators and benchmark comparisons ("Brands like yours typically reduce overstock by 18%") drive retention at this persona.

The Power User: Operations Manager / Head of Supply Chain

Profile: Hired by the founder once the brand hits ~$3M-$5M ARR. Lives in spreadsheets. Probably has an existing process (however manual) that Tightly needs to improve, not replace wholesale.

Job-to-be-Done: Hit fill rate targets, minimize freight premiums from emergency orders, and justify headcount by showing operational leverage from tooling.

Success looks like: Fewer weekly fire drills. Clear visibility into which SKUs need attention this week. Purchase orders that go out on time without heroics.

Why they churn: Product doesn't match their workflow. They had a mental model of how replenishment should work; if Tightly's model conflicts without explanation, they lose trust. Or the UI is too rigid — they need to override things and the product fights them.

PM implication: This persona needs configurability, explainability, and bulk actions. They want to understand WHY Tightly is recommending a PO, not just accept it blindly. Audit trails, editable parameters, and batch approve/reject workflows matter enormously here.

The Daily User: Buyer / Inventory Analyst

Profile: Often a more junior team member — sometimes the founder wearing a different hat at smaller brands. Executes POs, updates supplier lead times, manages catalog data.

Job-to-be-Done: Get through their daily task list without making a mistake that costs the brand money or customer trust.

Success looks like: A clear daily to-do view. Easy PO creation and supplier communication. Alerts that are actionable, not noisy.

Why they churn: Tool is too slow. Too many clicks to do common tasks. They go back to Excel because it's faster for the specific workflow they repeat 50 times a week.

PM implication: This persona is where UX polish wins. Speed, keyboard shortcuts, sensible defaults, and bulk operations matter. They're also the best source for task-level friction discovery — if you can get 30 minutes with them, you'll find the next 5 quick wins.

Enterprise Buyers: COO / VP Operations

Profile: At brands $20M+, there's often a COO or VP of Operations who evaluates tools from a systems perspective. They care about integrations (does it talk to our ERP?), security, SLA, and fit in a broader supply chain stack.

Job-to-be-Done: Build a scalable ops infrastructure that doesn't break as the brand grows from $20M to $100M.

Why they churn: Product can't handle their complexity. Multi-DC, multi-channel, complex supplier relationships. Or the Tightly team can't give them the white-glove support they expect at their contract size.

PM implication: This persona drives the enterprise roadmap — multi-location planning, ERP integrations, role-based permissions, audit logging. Features that Prediko (the lower-market competitor) doesn't have and can't easily build.