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

Percy Kuhnneutral

Currently, we build all our sports-related UI components in-house, leveraging Tailwind CSS and shadcn/ui. SportyBlocks offers a pre-built solution, which could save development time, especially for components like scoreboards or player cards. However, the main concern would be how seamlessly these components integrate with our existing architecture. The prompt mentions a one-time purchase, which is appealing, but I'd need to understand if the components are easily customizable or if they lock us into a specific design language. The product manager's reliance on spreadsheets for league rules is a persistent issue, and if these components help bridge that gap, it would be a significant benefit. I'd be willing to pay around $40 per month for a subscription that provides access to a robust, well-maintained library that genuinely speeds up development without introducing significant integration headaches.

Simulated interest: 60/100

Lynne Wyman-Borerneutral

Right now, we're relying heavily on a shared spreadsheet and hand-rolling most UI elements, which is a nightmare. SportyBlocks looks interesting because it offers pre-built sports components for Tailwind. It would be better if it had more flexible options for ticket sales and membership sign-ups, as our current process is quite manual. I'd need to see if the components are easily customizable to fit our specific club's branding and data structures. The biggest thing keeping me on our current method is the cost; while free components are a starting point, they often require significant tweaking. For something like this, I'd be willing to pay around $20 per month.

Simulated interest: 50/100

Yunus Abramovicneutral

Currently, we use a mix of our own small Tailwind component set, Flowbite snippets, and sometimes even raw client spreadsheets for schedules and pricing. SportyBlocks looks interesting because it offers a lot of sports-specific components out-of-the-box, which could save us time compared to building them from scratch or piecing them together. However, our current setup is heavily customized to our specific needs, and I'm not sure how easily SportyBlocks would integrate or if it offers the flexibility we require without significant rework. The one-time purchase model is appealing, but the pricing isn't immediately clear on the page; I'd need to see the actual cost. I would consider paying around $100 per month if it significantly streamlined our workflow and offered genuine value beyond what we can assemble ourselves.

Simulated interest: 60/100

Connie Fayneutral

Currently, I reuse free code snippets and build most components from scratch or adapt them from spreadsheets. SportyBlocks looks interesting because it offers pre-built sports-specific components, which could save me a lot of time, especially for things like player cards and fixtures. The main advantage would be the speed and consistency it could bring. The biggest drawback would be if the components aren't flexible enough for my clients' specific needs or if they don't integrate smoothly with my existing Vue and Tailwind setup. I'd also need to see how easy it is to customize them. If it works well and saves me significant time, I might consider paying around $20 per month.

Simulated interest: 40/100

Geneviève Perrotneutral

Currently, we manage our court booking system using a combination of spreadsheets for data management and DaisyUI-style building blocks for the user-facing elements of our website. SportyBlocks could be better if it offers more flexibility or integrations than what we currently have, especially for managing availability and bookings dynamically. However, if it's just static UI components and doesn't streamline our operational workflow or the onboarding of new partners, it might not be an improvement. The fact that it's a one-time purchase without a subscription is appealing given our budget constraints. I'd be willing to pay around $50 per month for a tool that significantly simplifies our operations and enhances our customer portal without requiring extensive development resources.

Simulated interest: 70/100

Bjarne Patzwahlneutral

We currently manage registration rules, badge text, and fixture data within spreadsheets. This approach is rudimentary, I admit, but it functions for our current scale. SportyBlocks offers pre-built components, which could accelerate our UI development, particularly for elements like standings or player cards. However, the core issue for us is data management, not UI presentation. While these components are built with Tailwind CSS, which we use, I need to understand if they can be easily integrated with our existing, albeit spreadsheet-based, data flow. The fact that it's a one-time purchase is appealing, as I dislike recurring subscriptions. My primary concern would be how much customization is needed to adapt these components to our unique league rules and data structures. If significant refactoring is required to connect to our data, the time savings diminish. Without a clear understanding of integration effort and flexibility, I would not pay more than $50 per month for this.

Simulated interest: 40/100

Omana Duttaneutral

Right now, I mostly use a mix of manually coded components and some shared Sheets, though it's getting messy as our startup grows. Specifically, we’ve got a private Tailwind repo with reusable chart and card components, but it’s far from comprehensive. A solution like SportyBlocks could save us a ton of time if it integrates well with what we already have. The big question is whether it’ll cause more refactoring headaches. I’d need to ensure the components are modular enough to slot into our existing system without forcing a complete overhaul. The Tailwind CSS compatibility is a huge plus—the less I have to fight with stylesheets the better. Also, the one-time purchase model is appealing, as it avoids recurring fees that might strain our budget. We’re ideally looking for something under $50 USD per month, but since this seems like a one-time buy, I’d maybe stretch to around $150–$200 USD if the components are robust and actually save time. Right now, though, I’m not sure if the components will be comprehensive enough to replace what we build in-house. I’d definitely need a trial or a more detailed breakdown of the components before committing.

Simulated interest: 40/100

Sachin Agarwalneutral

Right now, I'm using spreadsheets and doing a lot of manual entry for our SKU updates. I've also looked at a few free UI kits, but they didn't integrate well, so I've leaned more towards shadcn/ui for internal pages. SportyBlocks looks interesting because it's tailored for sports sites, which is exactly what we are. Having pre-built components for scoreboards and player cards could save me a lot of time, especially when we're preparing for match-day promotions. The biggest draw would be if these components are truly copy-paste ready and don't require heavy customization. If it saves me at least 10 hours a month on development or simplifies our current manual processes, I might consider it. I'd be willing to pay up to $20 per month for a subscription if it proves valuable.

Simulated interest: 60/100

Bodi Kuypersneutral

Right now, I’m handling the frontend with custom-coded components in Tailwind CSS. I’ve been copying snippets from communities like CodePen and tweaking them for my app. If SportyBlocks had components that fit my current setup without needing a subscription, I’d take a closer look. The one-time purchase sounds appealing, but I’m not convinced I’d use enough of these 87 components to justify it. Plus, $0.01 per month is unclear. I’d need to see both the actual price and ensure the components are truly low-maintenance. Since I’m bootstrapping, I’d only pay if I could see an immediate return on the time saved.

Simulated interest: 40/100

Marco Antonio Cepeda Coronaneutral

Currently, we are using a free, open-source component library for most of our product interfaces. This was a strategic decision to improve efficiency and consistency across our live score pages, fantasy tools, and promo microsites. The primary advantage of SportyBlocks would be the specialized nature of these sports-specific components, potentially saving us development time on features like scoreboards and player cards, which we often build from scratch or adapt. However, the fact that SportyBlocks appears to be a one-time purchase rather than a subscription is appealing. If it were a subscription, my primary concern would be the recurring cost, especially since we've standardized on free resources. Given my current approach and budget constraints, I'm not sure I would pay for this. If there were a compelling reason, perhaps a very specific set of unique components not easily replicable, I might consider up to $50 per month.

Simulated interest: 30/100