What do you use today instead of Storecraft (https://storecraft.app/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Storecraft 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

Storecraft - Next Gen Commerce-As-CodeMongo DBSQLitePostgresMySQLTurso SQLiteNeon PostgresCloudflare D1Planetscale mysqlS3Google StorageNodeDenoBunAWS LambdaGoogle CloudCloudflare Workers

https://storecraft.app/ (opens in a new tab)
Saved screenshot of Storecraft - Next Gen Commerce-As-CodeMongo DBSQLitePostgresMySQLTurso SQLiteNeon PostgresCloudflare D1Planetscale mysqlS3Google StorageNodeDenoBunAWS LambdaGoogle CloudCloudflare Workers
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

37/100

AI synthesis, not measured demand

Suggested price range

$50–150

Median $50 · simulated willingness to pay

Response sentiment

Positive 0%Neutral 100%Negative 0%
The takeaway

What this panel suggests

Respondents mostly said they currently rely on spreadsheets, Airtable, manual workflows, or custom scripts instead of Storecraft, with a few also comparing it to other commerce platforms such as Medusa or Saleor. The main reason they would switch is flexibility: a code-first commerce backend could replace fragmented tooling and make custom logic easier. The main reason they would not switch is that Storecraft still feels developer-heavy and potentially more complex than their current setup. That concern shows up even though the page emphasizes quick creation, broad platform support, an official dashboard, and AI features; the gap is that buyers still perceive a steep learning curve and uncertainty about how much customization is possible without complexity. Migration effort is another major blocker, especially around moving existing data/workflows and handling subscription or recurring billing cleanly. Storecraft would be better if it clearly reduced setup work, made migration easy, and was understandable for teams with limited developer time. It would be worse if it adds a new system that only a JavaScript-savvy team can manage. Observed max willingness to pay is modest, centered around $50/month, with an upper observed point at $150/month.

A hypothesis to test

Pricing & positioning

Position Storecraft as a low-friction upgrade from spreadsheets/manual workflows, and reduce perceived setup complexity before leaning on premium pricing.

Observed willingness to pay is modest in this batch, with an exploratory center around $50/month and an upper observed point of $150/month. A simple starter tier near $50/month looks like the most plausible entry point, with higher tiers only after the team proves migration help, onboarding, and advanced extensibility.

Recurring themes

Current work is manual or spreadsheet-based
“Right now, I'm managing product data for my clients using spreadsheets or Airtable”Read Corey Swaniawski’s response →
Storecraft feels developer-heavy or too technical
“We have a part-time developer, but the 'code' aspect feels quite advanced for us”Read Macaria Nobili’s response →
Migration, integration, and billing setup feel risky
“I'd need to see how it handles the specifics of subscription logic and recurring billing without adding complexity”Read Doug Ebert-Ruecker’s response →
Price and simplicity are still unclear

Objections to investigate

  • Steep learning curve and technical barrier
  • Unclear migration effort and setup time
  • Lack of pricing transparency

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.

Corey Swaniawskineutral

Right now, I'm managing product data for my clients using spreadsheets or Airtable, depending on their setup. It works, but it's definitely a manual process and can be a bottleneck for clients without ops teams. Storecraft's promise of a 'Commerce As Code' backend is interesting, especially the flexibility in databases and cloud deployment. The AI features could streamline things, but I'd need to see how well it integrates with existing workflows and if it genuinely reduces the data management overhead I currently handle. The biggest unknown is the learning curve and how much customization is truly possible without becoming overly complex. I'd be willing to pay around $50 per month, but that's contingent on a much clearer understanding of its capabilities and ease of integration.

Simulated interest: 30/100

Doug Ebert-Rueckerneutral

Right now, we're on a Medusa-based stack, managing everything from the API to recurring orders. The idea of a 'Commerce As Code' platform like Storecraft is interesting, especially the flexibility and potential to reduce maintenance overhead, which is a constant struggle. The biggest draw would be reclaiming time from firefighting to focus on strategic growth. However, I'd need to see how it handles the specifics of subscription logic and recurring billing without adding complexity or stability issues. I'm also trying to move towards serverless where it makes sense, so the 'run anywhere' aspect is appealing, but the initial setup and migration effort is a significant barrier. What's the pricing model? Is it a per-month subscription for the platform itself, or based on usage?

Simulated interest: 50/100

Jolina Mögenburgneutral

Right now, we manage SKU mapping with shared spreadsheets, which is quite inefficient, and handle maintenance tickets manually. Storecraft's 'Commerce As Code' approach sounds intriguing, especially the flexibility in databases and cloud deployment. It could potentially streamline our bespoke JavaScript development significantly. However, I'd need to understand the actual effort involved in migrating our current data and workflows, and whether it genuinely simplifies the recurring maintenance rather than just shifting it. The AI integration is also interesting, but its practical application for our clients needs to be clear. I wouldn't pay for a solution that introduces more complexity than it solves.

Simulated interest: 30/100

Shubhaprada Johar-Khannaneutral

Today, I manage my entire online store using WooCommerce for the website, Google Sheets for inventory and sales tracking, and WhatsApp for customer communication and coordinating with my contract packers and couriers. It's a very manual process, but it works for my one-person operation. Storecraft sounds interesting with its 'Commerce As Code' approach and AI capabilities, especially the idea of letting customers speak with AI for their cart. However, it seems quite technical, requiring significant developer effort, which isn't my current strength. My self-taught web skills are primarily focused on WooCommerce, not backend development with JavaScript platforms like Deno. The flexibility it offers in databases and cloud hosting is appealing, but I'm not sure if I have the resources or expertise to leverage it effectively right now. What would keep me on my current setup is the simplicity and familiarity. Storecraft seems to offer a lot of power, but potentially too much complexity for my current needs. I wouldn't pay for it.

Simulated interest: 20/100

Claude Kubneutral

Today, we're managing our supplier feeds manually, which is, frankly, a constant source of friction. I'm the one wrestling with the data coming in from two warehouses. Storecraft's promise of a 'Commerce As Code' backend with flexibility in databases and cloud deployment sounds intriguing, especially the extensibility. However, I'd need to see how it handles real-time, complex supplier integrations and if it can replace the fine-grained control I currently have over our Vendure backend and custom Next.js storefront. The manual process is painful, but it's predictable. A sudden shift to a new system needs to demonstrate a clear, quantifiable improvement in reliability and a significant reduction in my operational overhead. I wouldn't pay more than $50 per month.

Simulated interest: 40/100

Pétronille Barreneutral

Today, I manage our Saleor deployment and custom admin scripts manually for our small skincare brand. The idea of a "Commerce As Code" backend like Storecraft is intriguing, especially the flexibility in choosing databases and cloud platforms. However, the "AI first" and "Next Generation" marketing feels a bit abstract for my practical needs. I need to understand how it integrates with existing systems and if it simplifies tasks like complex tax configurations. The price isn't clear; I'd need to see detailed pricing and perhaps a free tier or trial before considering it. Without that clarity, I cannot estimate a monthly cost.

Simulated interest: 30/100

Edmund Janusneutral

Currently, we're using a combination of JavaScript frameworks, custom scripts, and sometimes even shared spreadsheets to manage order workflows and headless stores. Storecraft's appeal lies in its 'Commerce As Code' approach, which sounds like it could streamline setup and offer more flexibility than our current ad-hoc methods. The ability to choose databases and cloud platforms is interesting. However, the biggest question for me is how quickly we could actually implement it for clients, given their tight budgets and aggressive launch schedules. We need solutions that are fast to deploy and easy to integrate. If it requires a steep learning curve or complex initial setup, it might not be worth it. I'm not sure about the pricing structure; it says 'per month subscription' but doesn't give amounts. I'd need to see more details. For now, I wouldn't pay for it without understanding the full scope and integration effort.

Simulated interest: 30/100

Homer Wuckertneutral

Right now, we're mainly using spreadsheets and a few internal scripts that I've put together to manage our product catalog and order operations. It's getting to be a real bottleneck, honestly. This Storecraft offering sounds interesting with its 'Commerce As Code' approach, especially if it can automate some of the data handling and updates. The main thing would be if it significantly reduces the manual effort and errors we currently deal with. We'd also need to see how it integrates with our existing systems. If it streamlines things without adding a lot of complexity or requiring our developer to spend all their time on it, that would be a win. I'd be willing to consider up to $150 per month for something that genuinely improves our efficiency and reduces errors, but that depends heavily on the features and ease of use.

Simulated interest: 60/100

Ed Andersonneutral

Right now, I'm managing payments and downloads with a custom JavaScript backend, and inventory is in Notion. It's a bit of a Frankenstein's monster, but it works for me. Storecraft looks interesting, especially the idea of a 'Commerce As Code' approach and the flexibility in databases and cloud deployment. That could definitely streamline things and potentially solve some of the intermittent glitches I face. However, I'm hesitant about adding another layer of complexity if it's not a clear win. The biggest draw to my current setup is that it's essentially free, aside from hosting costs. I'm a solo operator, so every euro counts. I'd need to see a significant improvement in reliability or a substantial time saving to justify paying for something like this.

Simulated interest: 40/100

Macaria Nobilineutral

Currently, we manage everything in Google Sheets – product data, orders, launch calendars, you name it. It's manual, but it works for our small team. Your platform, Storecraft, sounds interesting with its 'Commerce As Code' approach. It could potentially streamline things, especially if it integrates well with our current setup or offers more robust inventory management than spreadsheets. However, I'm a bit concerned about the technical expertise required. We have a part-time developer, but the 'code' aspect feels quite advanced for us. What I would need to see is how easily it could be managed without a dedicated developer on staff. It's about finding the balance between efficiency and complexity. Price isn't my primary concern if it solves a real problem, but given our budget, we'd have to be very careful.

Simulated interest: 40/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.