What would stop you from trying Glass Arc (https://www.glassarc.dev/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

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 $30 · simulated willingness to pay
Response sentiment
What this panel suggests
The responses are neutral and cautious rather than enthusiastic or dismissive. The biggest blocker to trying Glass Arc this month is not the core idea of an autonomous architect inside VS Code; it is uncertainty about how the pricing actually works and whether the tool fits existing engineering workflows. Several respondents said they already handle planning in Figma and Notion, use VS Code with GitHub Copilot Business for boilerplate, and rely on strict RFC processes for larger implementation or architecture changes. Against that backdrop, a tool that drafts files and runs terminal commands raises control concerns: people want to avoid something that could override intended design or add automation before they can fully review the implications. Pricing clarity is the strongest objection. The page’s Energy Credits framing was seen as hard to translate into monthly spend, and one response flagged the mix of subscription-like language and pay-as-you-go language as confusing. The aggregate willingness to pay spans from $0 to $50 with a median of $30, but the $0 responses appear tied to missing cost visibility rather than rejection of monetization itself.
Pricing & positioning
Test a transparent credits-to-task calculator and a simple starter price cap before asking for a paid trial. The main follow-up hypothesis is that clarity, not feature depth, will determine trial willingness.
The stated objection is not that the product is unpriced; it's that respondents cannot map Energy Credits to real work. Publishing example burns for common tasks, a monthly spend cap, and a plain-English explanation of how the credits model relates to any subscription language would reduce friction.
Recurring themes
“My current process involves extensive sketching in Figma and detailed notes in Notion before I even start coding”Read David Waelchi’s response →
“The 'True Pay-As-You-Go' model with Energy Credits is interesting, but without knowing the typical credit consumption for tasks relevant to my squad's work, it's hard to estimate cost”Read Abdul Zimmermann’s response →
“I'm concerned about how it integrates with my existing architectural planning and whether it might override my intended design”Read David Waelchi’s response →
“Regarding cost, the product mentions "True Pay-As-You-Go" and "Top up your Energy Credits securely via Gumroad," but it also mentions a "$20/month AI bill" which is confusing”Read Sean Zemlak’s response →
Objections to investigate
- Unclear Credit Consumption Rates
- Integration with Established Architectural Workflows
- Fear of Unintended Complexity or Automation Risks
- Confusing Pricing Terminology (Subscription vs. Credits)
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.
David WaelchineutralThe main thing that would stop me from trying Glass Arc is the potential for it to introduce more complexity or unexpected behavior into my workflow, especially when I'm trying to maintain predictable project timelines. My current process involves extensive sketching in Figma and detailed notes in Notion before I even start coding, which gives me a high level of control. While I appreciate the idea of an autonomous architect, I'm concerned about how it integrates with my existing architectural planning and whether it might override my intended design. The pay-as-you-go 'Energy Credits' model is intriguing, but I'd need to understand the credit burn rate to estimate costs reliably. For now, I'd be willing to try it out if the initial credits are generous enough to explore its capabilities thoroughly without immediate financial commitment.
Simulated interest: 60/100
Irma LindgrenneutralThis Glass Arc product sounds interesting, promising to act as an 'architect' rather than just autocompleting code. However, my current process is quite robust. We use VS Code with GitHub Copilot Business for boilerplate, and crucially, we have a strict RFC process for any significant implementation or architectural change. Architectural decisions are documented in Miro and Confluence. My primary concern would be how Glass Arc integrates with or disrupts these established workflows, especially regarding security and the manual review of critical code. The concept of 'energy credits' and a 'pay-as-you-go' model is intriguing as it sidesteps the tax on idle time, which I appreciate. If it truly performs as advertised, I might consider a nominal fee, perhaps around $50 per month, to trial its effectiveness on a non-critical component.
Simulated interest: 60/100
Abdul ZimmermannneutralMy current process involves meticulous documentation in Confluence and detailed diagrams in draw.io before implementation, which is working well for my team. What would stop me from trying Glass Arc is the lack of clarity on how it integrates with existing workflows and the potential for it to introduce unforeseen complexities or overhead. I need to understand how it handles trade-offs, as that's a critical part of my decision-making process today. The 'True Pay-As-You-Go' model with Energy Credits is interesting, but without knowing the typical credit consumption for tasks relevant to my squad's work, it's hard to estimate cost. If it proved to be a significant time-saver without introducing new problems, I might consider paying up to $30 per month, but that's contingent on understanding its usage and impact.
Simulated interest: 40/100
Sameer DeshpandeneutralThis month is incredibly busy with multiple client projects running in parallel. My current process involves meticulous planning with flowcharts and Excel before assigning tasks, and I'm focused on documenting our existing integration patterns to build a knowledge base. While Glass Arc's autonomous capabilities sound intriguing, especially the runtime auto-heal, I'd need to see how it integrates with our established workflows and if it truly reduces the manual scaffolding and integration work I currently oversee. The "pay-as-you-go" energy credit model is more appealing than a fixed monthly subscription, but I'd want to understand the cost implications for a small agency like ours before committing. I'd be willing to pay up to $30 per month for a tool that demonstrably saves my team time and improves quality.
Simulated interest: 60/100
Christine CarterneutralMy current process for handling tasks like drafting files, running terminals, and fixing crashes involves me meticulously managing spreadsheets for scope and API choices, and a plain-text checklist for daily tasks. This is all done manually, as I prefer to avoid paid dev-planning tools. The autonomous nature of Glass Arc, especially its ability to "draft files" and "heal runtime crashes," is intriguing, but I'd need to see how it integrates with my existing workflow and if it truly reduces my workload without introducing new complexities. The "pay-as-you-go" model with "Energy Credits" is appealing because I'm highly budget-conscious. I'd need to understand the cost of those credits and how quickly they're consumed for my specific use cases before committing. For now, I'm not willing to pay a monthly subscription. I'd be willing to pay $0 per month.
Simulated interest: 40/100
Francisque DumasneutralThe idea of an AI architect is intriguing, but my current workflow is quite established. I meticulously document architectural decisions in Notion, and while VS Code is my primary environment, I'm wary of introducing a tool that might automate too much before I've had a chance to thoroughly analyze and understand the implications for my clients. My process involves a structured approach, mapping out solutions and weighing pros and cons, and I'm not sure an autonomous agent can fully replicate that rigor yet. Currently, I handle architectural tasks manually, supported by my documentation tools. I'm willing to pay up to $50 per month, as a subscription, for something that proves its value without compromising my analytical process.
Simulated interest: 40/100
Bhagavaan PillaineutralHonestly, the biggest thing stopping me is the "energy credits" model. My current process involves a lot of planning on whiteboards and in Google Docs, and I'm used to free tools. While I'm intrigued by the idea of an autonomous architect in VS Code, especially the runtime auto-heal feature, I need to understand how quickly these credits deplete. The page mentions "True Pay-As-You-Go" and cancelling a $20/month bill, but it's unclear how many credits are consumed for typical architectural tasks or builds. I'd need to see that to commit. For now, I'd pay $0 per month until I understand the credit usage better.
Simulated interest: 30/100
Sean ZemlakneutralThis month, what would stop me from trying Glass Arc is really understanding its practical application for our platform team. While the concept of an "autonomous AI architect" sounds intriguing, my current focus is on refining existing systems and ensuring long-term stability, not necessarily introducing a new, potentially disruptive tool without clear evidence of its benefit. We manage our implementation order through Jira and spreadsheets, and coordinating a new tool would require careful planning and evaluation. We currently rely on detailed documentation and code reviews to manage our processes. Regarding cost, the product mentions "True Pay-As-You-Go" and "Top up your Energy Credits securely via Gumroad," but it also mentions a "$20/month AI bill" which is confusing. Without clearer pricing terms, I can't determine a maximum acceptable price.
Simulated interest: 30/100
Inaya de CorteneutralThe primary hesitation for me would be the ROI for the team. We're currently exploring AI tools, with some team members using paid Cursor seats alongside VS Code, so I'd need to see a clear, quantifiable productivity boost to justify adopting another tool. The pay-as-you-go "Energy Credits" model is intriguing as it bypasses subscription fatigue, but I'd need to understand the credit consumption rate to estimate costs. I'd be willing to pay up to $50 per month in USD for such a tool if it demonstrably improved our team's output.
Simulated interest: 60/100
Willie MedhurstneutralThis Glass Arc sounds interesting, especially the 'runtime auto-heal' feature – that could save a lot of debugging time. However, my current workflow relies heavily on Trello and Excel for architecture and project tracking, and I haven't seen how this tool would integrate with that. It mentions 'multiplayer magic links' for team collaboration, but it's just me and Sarah, so that's not a primary concern right now. The pricing model seems to be pay-as-you-go with 'Energy Credits', which is a bit vague. I'd need to understand the cost implications of these credits before committing. I'm happy to try it out with the free credits, but I wouldn't pay more than $20 per month for something like this, assuming the credits don't run out too quickly.
Simulated interest: 40/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.