What do you use today instead of StockBack (https://stockback.duckdns.org) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make StockBack better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

Page reviewed

Get paid for stock warehouses lose · StockBack

https://stockback.duckdns.org/ (opens in a new tab)
Saved screenshot of Get paid for stock warehouses lose · StockBack
Screenshot saved with this question. The live page may have changed.Open full image ↗

10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Simulated interest

46/100

AI synthesis, not measured demand

Suggested price range

$0–50

Median $50 · simulated willingness to pay

Response sentiment

Positive 10%Neutral 80%Negative 10%
The takeaway

What this panel suggests

Respondents mostly described a manual status quo: spreadsheets, WMS reports, ERP/audit logs, and hand-built reconciliation to track inventory discrepancies. Compared with that, StockBack sounds attractive when it can automate the day-to-day work of finding short deliveries, lost stock, and returns that never came back, then write the claim for them. The main friction is not the idea itself but fit: several answers show uncertainty about whether StockBack connects cleanly to their existing ERP/WMS stack, especially older or custom systems such as Odoo, Tally, Zoho, or internal warehouse workflows. That is a perception gap, not a verified product limitation; the page claims read-only connections for specific marketplaces and warehouses, but respondents did not see enough clarity that it matches their environment. Another consistent concern is that they still have to submit claims manually, which preserves some operational burden. Pricing sentiment is cautious but not hostile: the sample max willingness to pay centers around $50/month, with some saying $0, suggesting that proof of recovered dollars matters more than feature breadth. Current tools are kept when they are already embedded in the workflow or when integration/ROI uncertainty feels too high.

A hypothesis to test

Pricing & positioning

Keep the free audit and success-fee model as the default, since the strongest motivation is proving recovered value first. If you test any monthly subscription, position it as optional and only after demonstrating fit and recoveries. The clearest hypothesis is that a small, low-commitment monthly tier would need to be paired with very explicit integration support and ROI proof.

Willingness to pay is modest and uneven: some respondents gave 0, while the median max was $50/month. That suggests price sensitivity and a need to anchor pricing to visible recovered value rather than generic SaaS convenience. The current 15% of recovered funds may be easier to understand than a flat fee, but only if users believe the product fits their stack.

Recurring themes

Manual reconciliation pain points
“Right now, we're using a mix of WMS reports and a lot of manual work in Excel to track down inventory discrepancies.”Read Leroy Bauch’s response →
Integration uncertainty
“I'm concerned about how seamlessly it integrates with our existing ERP system, which is a bit of a legacy system.”Read Bernice Lemke’s response →
Value-based pricing preference
“The pricing model, 15% of recovered funds, is interesting, but I'd need to see the actual volume of claims it finds before committing.”Read Leroy Bauch’s response →

Objections to investigate

  • Lack of specific system integration clarity
  • Requirement for manual claim submission
  • Uncertainty regarding ROI without proof
  • Relevance to internal vs. external fulfillment

Use these findings to plan customer interviews or experiments. How to interpret AI research

What the panel said

Click a name to open that persona’s full profile.

Leroy Bauchneutral

Right now, we're using a mix of WMS reports and a lot of manual work in Excel to track down inventory discrepancies. It's time-consuming. The idea of StockBack finding claims automatically is appealing, especially since it handles the claim writing. What I'm not clear on is how it integrates with our specific WMS, and if it can handle our client-specific Service Level Agreements. The pricing model, 15% of recovered funds, is interesting, but I'd need to see the actual volume of claims it finds before committing. Based on what I understand, I wouldn't pay anything per month, but I'd consider a small percentage-based fee if it proves highly effective. I'd estimate a maximum of $0 per month, as the current process is what it is, and I'm not looking to add new subscription costs without a proven, immediate ROI.

Simulated interest: 20/100

Bernice Lemkeneutral

Currently, I rely on a combination of spreadsheets and our warehouse system's audit logs to track stock variances. I spend a significant amount of time manually tracing lost items. StockBack's promise of automatically identifying and flagging claims for missing stock sounds appealing, as it could potentially save me hours of painstaking work. However, I'm concerned about how seamlessly it integrates with our existing ERP system, which is a bit of a legacy system. Also, the claim process still requires me to manually send the claim, which isn't fully automated. My maximum acceptable price would be $50 per month, as I'm quite budget-conscious and need to see a clear return on investment.

Simulated interest: 60/100

Digambara Gunetapositive

Right now, I’m wrestling with Zoho Inventory and shared sheets to track lost SKUs, returns, and dispatch errors. It’s a time sink, especially during peak seasons. StockBack seems like it could save a ton of time by automating the process of finding and claiming reimbursements. The fact that it’s read-only and only charges me when I actually get money back is appealing. The main question I have is how well it integrates with our setup—we use Zoho Inventory, and I’d need to know if StockBack can pull data from there seamlessly. Given the time I spend manually reconciling inventory, it would be worth a shot. My gut says I’d pay up to $50/month for a tool that could reliably recover lost stock. Anything beyond that, and I’d have to weigh the cost against our current margins.

Simulated interest: 70/100

Etienne Deckerneutral

Today, we rely on our ERP system and manual checks to track stock. My main concern is pallet mismatches and negative stock alerts. If StockBack could reliably identify these discrepancies and automatically generate claims, that would be a significant improvement. However, I would need to be sure it integrates well with our current system and doesn't create more work. The idea of paying a percentage of recovered funds is interesting, but I would need to see the actual recovered amounts first. I am hesitant to commit to a monthly fee without that proof. Perhaps $0 per month, given the performance-based model, and I would evaluate its value based on the recovered funds.

Simulated interest: 40/100

Aloyse Barbiernegative

Currently, we rely on Odoo Inventory with barcode scanning and monthly reconciliations to manage our stock. We do not use spreadsheets or manual methods for this specific purpose. StockBack seems to focus on recovering lost stock from external fulfillment partners, which isn't our primary issue. Our challenges are more internal – discrepancies within our own picking and overflow areas. If StockBack could identify and help us reclaim discrepancies from our own internal processes, that would be a significant improvement. However, its current focus appears to be elsewhere. Given its stated functionality, I wouldn't pay for this service. My priority is internal inventory accuracy and management.

Vik Postneutral

Right now, I'm using Excel spreadsheets and printed lists to keep track of our stock. It's a manual process, and I personally handle stock counts and check for damaged or lost items. The idea of StockBack finding lost stock and helping me get reimbursed sounds interesting, especially the 'free audit' part. However, the way it works seems to be for larger fulfillment centers like Amazon or Walmart, which isn't quite what I have. I'm not sure how it would integrate with my small warehouse or if it's even applicable to my situation. If it could truly help me recover money from suppliers or transport issues without adding a lot of complexity, I might consider paying a small monthly fee, perhaps around $50 USD per month, but honestly, I'd need to see it work for a business like mine first.

Simulated interest: 30/100

Sonja Hackettneutral

Right now, I’m using a mix of Google Sheets, yellow legal pads, and the warehouse’s aging scanners to track discrepancies. It’s a mess, but it’s what I know. StockBack sounds promising because it automates something I already do manually—hunting down short deliveries, lost or damaged stock, and unreturned customer returns. But I’d need to see it in action before committing. The 15% fee is fine if it actually saves me time and finds claims I’d miss. My boss would need proof it’s worth it. For now, I’d test it out, but I’m not sure how much we’d pay. Maybe $50 a month if it adds up to more recovered stock. That’s about what I spend on my yoga classes, which I see as an essential time-saver too. Right now, I’d stick with $30 to test it out and see real results in a few months before scaling it fully. But honestly, I’d guess it needs to find at least $200 consistently before justifying that.

Simulated interest: 65/100

Gonsalwy Niemiecneutral

Currently, I rely on my own meticulous spreadsheets and a lot of manual tracing to find discrepancies. The idea of StockBack automatically identifying these missing SKUs and even drafting the claims is appealing, as it addresses a significant pain point for me. However, the product page doesn't clearly state which specific systems it integrates with beyond general marketplaces like Walmart or Amazon, which are not directly relevant to our import operations in Kraków. We don't ship to or from these platforms. If it could integrate with our internal inventory system, that would be a significant advantage. Otherwise, it might just be another tool to manage. Given the 15% fee on recovered funds, I would be willing to pay up to $50 per month for a service that demonstrably saves me time and recovers funds, assuming it integrates with our operations.

Simulated interest: 30/100

Noel Kemmerneutral

Right now, I'm basically juggling spreadsheets and a clunky inventory app to track any lost units. It's a proper pain, takes ages to reconcile everything. What StockBack seems to do is automate that whole process of finding missing stock and getting claims sorted, which sounds brilliant. The main thing that would put me off is if it wasn't accurate or if it meant more manual work, you know? It says Amazon is 'coming soon', which is a bit of a bummer as that's a big chunk of our business. If it worked perfectly and saved me hours of faffing about with spreadsheets, I'd consider paying up to $30 per month, but that's on the high end.

Simulated interest: 50/100

Menaka Menonneutral

Currently, my team and I rely heavily on Tally, manual count sheets, and WhatsApp photos for tracking inventory and discrepancies. While this system catches issues, it's quite labor-intensive. StockBack sounds interesting because it promises to automate finding lost stock and claims, which would significantly reduce my workload and the stress of data disruption. The idea of getting paid for stock that's already lost is appealing. However, I'm unclear if it integrates with our specific Tally system or if it's primarily for direct warehouse-to-marketplace shipments. The pricing model of 15% of recovered funds seems reasonable if it truly recovers money we would otherwise lose. I would be willing to pay up to $50 per month, but that's assuming it works seamlessly with our current processes and proves its value. The lack of clarity on integration with systems like Tally is a concern.

Simulated interest: 50/100

Keep exploring.

Find your next question or see which topics divide AI panels.

Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.