What do you use today instead of Marrow Stack (https://marrowstack.dev/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Marrow Stack 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
MarrowStack — Production TypeScript Blocks for Next.js
https://marrowstack.dev/ (opens in a new tab)
10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations
Simulated interest
AI synthesis, not measured demand
Suggested price range
Median $50 · simulated willingness to pay
Response sentiment
What this panel suggests
Respondents mainly described replacing Marrow Stack with a mix of manual in-house development and stitched-together boilerplates, often around Next.js, Supabase, and Stripe-style setup work. The appeal of Marrow Stack is speed: a copy-paste block library could reduce the time spent assembling authentication, billing, admin, and workspace flows. However, the main hesitation is practical fit. People want to know whether the blocks will integrate cleanly with their existing Supabase-based architecture, or whether they will introduce extra dependencies, abstraction, and debugging complexity. Some also worried about vendor lock-in and whether the “ORM Agnostic” positioning will hold up in real projects, which suggests a clarity gap rather than a rejection of the concept. One respondent also wanted verification of the Solana-related features before trusting them. Overall, the current option is kept when it is already working, customizable, and safer than adopting a new layer. The willingness to pay data suggests modest subscription pricing can work, especially if the product proves it saves real engineering time without constraining implementation choices.
Pricing & positioning
A subscription can make sense, but the value needs to be framed around reducing build time and lowering implementation risk rather than just selling code snippets. A low-friction starter tier and a higher team tier would fit the range of willingness to pay.
The reported max willingness to pay clusters around $50/month, with a lower-end group around $15 and a higher-end ceiling near $150 for stronger production use cases. Pricing should be easy to compare against the cost of maintaining in-house boilerplate and engineering time.
Recurring themes
“It could potentially speed up development significantly”Read Brendan Kuphal’s response →
“I'd need to understand how easily these blocks integrate with my existing Supabase setup”Read Brendan Kuphal’s response →
“whether they abstract away too much, hindering our ability to debug and customize”Read Stephanie Windler’s response →
“stitching together features using a mix of internal patterns and paid boilerplates”Read Brendan Kuphal’s response →
Objections to investigate
- Integration Friction with Existing Stack
- Risk of Vendor Lock-in or Over-Abstraction
- Customization Limitations
- Verification of Claims (e.g., Solana Features)
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.
Brendan KuphalneutralRight now, I'm stitching together features using a mix of internal patterns and paid boilerplates, often integrating Supabase and Stripe directly. Marrow Stack's promise of copy-paste, production-ready Next.js code blocks, especially for auth, billing, and admin views, is appealing. It could potentially speed up development significantly, which is a major plus given my fixed-bid projects. However, I'd need to understand how easily these blocks integrate with my existing Supabase setup and ensure they don't introduce unnecessary complexity or vendor lock-in. The fact that they're described as 'self-contained server actions' sounds promising for integration. I'd be willing to pay up to $75 per month for a service like this.
Simulated interest: 60/100
Stephanie WindlerneutralToday, for authentication, billing, and team management, we're building it all in-house on Next.js and Supabase. It's a significant amount of work, but it gives us full control. Marrow Stack's promise of "copy-paste production-ready Next.js code blocks" sounds appealing, especially with its focus on security and type safety, which aligns with my values. However, I'm concerned about how seamlessly these blocks would integrate into our existing, albeit shared, codebase and whether they abstract away too much, hindering our ability to debug and customize. The "ORM Agnostic" claim is good, as we use Supabase. The main draw would be saving significant development time, but the risk of vendor lock-in or difficulty in customization is a deterrent. I'm not willing to pay anything for this, as we're committed to our current in-house approach.
Simulated interest: 30/100
Anal AroraneutralRight now, I’m piecing together auth, billing, and admin features manually for each client project. I use free Supabase templates and tweak Next.js boilerplate code, which takes hours of repetitive work. Marrow Stack’s pre-built blocks sound appealing because they’d save time—especially the auth and team workspace systems. However, I’d need to verify if their Supabase integration is seamless or if it introduces new dependencies. The ‘ship in hours’ claim is tempting, but I’ve been burned before by tools that promise simplicity but require deep customization. If it truly works out of the box, I’d pay $20/month, but only if I can test drive it without long-term commitment. My biggest hesitation? Switching tools mid-project could introduce bugs, and I can’t afford extra client headaches.
Simulated interest: 60/100
Nadja JanderneutralCurrently, we're piecing together our authentication, billing, and role management systems using internal patterns and, frankly, a lot of spreadsheets. It's a temporary measure, but it's consuming valuable development time. Marrow Stack appears to offer pre-built, typed code blocks for these exact functionalities, which could significantly accelerate our rebuild of the ops portal. The promise of shipping in hours and the focus on security and type-safety are appealing. However, I would need to see how easily these blocks integrate with our existing Supabase setup and if they truly offer the flexibility we need for granular admin controls beyond what's listed. The current ad-hoc approach is costing us time, but a poorly integrated solution would be worse. I'd be willing to pay up to $150 per month, depending on the scope and ongoing support.
Simulated interest: 70/100
Beulah NienowneutralRight now, I'm essentially building out my own authentication and billing systems within my Next.js app using Supabase and Stripe. The idea of having production-ready code blocks, especially for things like team workspaces or advanced auth, is appealing because it could save me a significant amount of time. However, I'd need to see how seamlessly these blocks integrate with my existing Supabase setup, and if they're truly 'ORM agnostic' as claimed, or if they impose specific patterns. My main concern is maintaining flexibility without introducing too much complexity. If the blocks are truly copy-paste and work with my current Supabase structure, I might consider paying around $49 per month.
Simulated interest: 40/100
Ernesto PaucekneutralCurrently, we build all our authentication, team access, and billing logic from scratch using Supabase and Stripe. It's a lot of repetitive 'plumbing' work that eats into our development time. Marrow Stack's promise of copy-paste production-ready blocks, especially for auth and billing, sounds appealing as it could significantly reduce that overhead and speed up delivery. However, I'd need to see how seamlessly it integrates with our existing Supabase setup and understand the flexibility for customization. If it truly simplifies the setup and reduces cognitive load, it could be valuable, but I'm cautious of adding complexity for the sake of speed. I'd be willing to pay up to $40 per month, provided it proves reliable and saves us considerable time.
Simulated interest: 70/100
Oriande LucasneutralRight now, I mostly cobble together auth screens and admin pages for our MVPs with a mix of Supabase quickstarts and code I’ve copied from old projects. It’s kind of a mess, honestly—whenever we need a new feature, I spend hours tweaking and debugging. If Marrow Stack could give me pre-tested, production-ready blocks for stuff like billing and workspaces, that would save me so much time. The thing holding me back? I’d want to see real examples of those Solana features, since we’ve got a client who needs crypto payments soon. As for cost… I’d try it if it were under $50/month, but only if it’s actually faster than my DIY method. I’m impatient, but I’m not reckless with my partner’s budget.
Simulated interest: 60/100
Chandni JainneutralToday, we manage authentication, role-based access, billing, and admin tasks ourselves within our Next.js application. We've been building these systems incrementally. Marrow Stack's advantage would be the speed to integrate pre-built, typed code blocks, especially for features like billing and team workspaces. However, I'd need to evaluate how well these blocks integrate with our existing Supabase setup and how much customization they allow. We're a small team, so adopting a new dependency requires careful consideration. If the integration is seamless and saves us significant development time, I might consider paying up to $150 per month.
Simulated interest: 60/100
Pedro OsinskineutralRight now, I'm mostly piecing things together from tutorials and Stack Overflow for auth, subscriptions, and the admin stuff. It takes time, but it's free. Marrow Stack looks interesting because it's production-ready and typed, which could save hours. The 'ship in hours' claim is tempting. But honestly, I'm always a bit skeptical of paid solutions unless I can't replicate it myself. I'd need to see if these blocks actually fit my specific needs without a ton of customization. If they did, and I could just drop them in, maybe I'd pay $15 per month.
Simulated interest: 30/100
Mark VosneutralCurrently, for my clients, I build out auth, team management, and billing systems from scratch using Supabase, and repository scaffolding is done through custom scripts and internal guidelines. Your Marrow Stack's 'Auth System' and 'Billing & Subscriptions' blocks look interesting, especially since they are Supabase-ready and typed. The main advantage would be the speed of implementation, potentially saving days of work. However, I'd need to evaluate how easily these blocks integrate with existing, potentially complex, codebases. The security defaults are a plus, but I'd still want to review them thoroughly. The biggest deterrent would be a lack of flexibility or if the blocks introduce too much opinionation that conflicts with our established patterns. I would be willing to pay up to $150 per month, but that would depend heavily on the breadth of blocks available and their customization options.
Simulated interest: 60/100
Keep exploring.
Find your next question or see which topics divide AI panels.
What would you ask next?
Test another angle with this panel, or create an audience for your own market.