What would stop you from trying Val (https://val.build/docs) 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 $50 · simulated willingness to pay
Response sentiment
What this panel suggests
The main reasons respondents would not try Val this month are workflow friction and pricing ambiguity. Several said adopting Val would require a significant change from how they currently handle content in Google Docs, Excel, Slack, Confluence, Google Sheets, and Notion, so the key question is whether it fits their existing process without adding overhead. They wanted to know, specifically, how Val would interact with that workflow and how it would handle versioning and approvals before publishing. Another recurring blocker was that pricing was not clear enough on the page for them to decide whether to try it, with one respondent saying, "Since pricing isn't immediately clear on this page, I couldn't put a figure on it." That seems to be a clarity issue, not proof of rejection; the page also says no signup is required, but respondents still wanted a visible subscription structure. When respondents did name a price, $50/month was the central point and $150/month was the upper end.
Pricing & positioning
Make pricing explicit on the page and keep the first paid tier simple; the biggest hesitation is not the concept, but uncertainty about fit and cost.
The reported willingness to pay clustered around $50/month, with some respondents willing to go up to $150/month. Treat this as directional only; it is not validated demand.
Recurring themes
“Integrating Val would mean a significant shift for my team, and I'm not sure how it would mesh with our existing tools”Read Patricia Parker’s response →
“Since pricing isn't immediately clear on this page, I couldn't put a figure on it”Read Patricia Parker’s response →
“We'd also need to understand how it handles versioning and approvals before publishing”Read Patricia Parker’s response →
Objections to investigate
- Workflow Integration Complexity
- Unclear Pricing Structure
- Lack of Team/Approval Features Visibility
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.
Patricia ParkerneutralThis "Content as Code" approach is intriguing, and the local-first aspect sounds appealing for offline work. However, my current workflow relies heavily on Google Docs for drafting and Sheets for the calendar, with Jira and a separate spreadsheet for tracking. Integrating Val would mean a significant shift for my team, and I'm not sure how it would mesh with our existing tools or if my team is ready for that. We'd also need to understand how it handles versioning and approvals before publishing. Since pricing isn't immediately clear on this page, I couldn't put a figure on it.
Simulated interest: 30/100
Lynn KingneutralVal's 'content as code' approach is certainly intriguing, aligning with our use of GitHub markdown. However, the primary obstacle to trying it this month is integrating it with our existing, albeit fragmented, toolchain. Today, I meticulously manage review dates and publishing status in an Excel spreadsheet, cross-referencing it with Confluence and GitHub. I'd need to understand precisely how Val would interact with this workflow, particularly concerning regulatory auditability. Without a clear picture of that integration and a demonstration of its stability, I'm hesitant. Regarding pricing, the lack of specific tiers makes it difficult to estimate. If it were priced similarly to other specialized developer tools, I might consider up to $50 per month, but that's a very rough estimate.
Simulated interest: 30/100
Nila StrohschankneutralThe primary obstacle to trying Val this month is the lack of clear pricing details, especially regarding team collaboration and the nature of the subscription. Currently, I manage content and translation briefs using a combination of Notion, Excel, and Airtable. While Val's 'Content as Code' approach is intriguing, I need to understand how it integrates with a team workflow and the costs associated with that. Without a pricing page that outlines different tiers or team plans, I cannot commit to a monthly expenditure. If it supports a small team and integrates smoothly, I might consider up to $50 per month.
Simulated interest: 40/100
Kailash SainineutralThe biggest hurdle for me right now is integrating a new system with our existing workflow. Our current process involves Google Docs for drafting, Slack for feedback, and then manually pasting into the CMS. While Val's "content as code" approach sounds interesting, especially the local-first aspect, I'd need to understand how it fits into our current pipeline without adding significant overhead for my team of two other marketers and myself. We don't have dedicated developer resources for complex integrations, so ease of implementation is key. The pricing basis also isn't clear – is it per user, per project, or something else? Without clarity on that and how it integrates with our current Google Sheets and Notion planning, it's hard to commit.
Simulated interest: 30/100
Isabelle de WitneutralThe main thing that would stop me is the current lack of a centralized system for managing content and tracking review cycles. Today, I'm manually documenting everything in Figma comments, Notion, and a spreadsheet, which is quite time-consuming. I'd need to understand how Val integrates with our existing workflow, especially how it handles multiple product teams and ensures consistency. The pricing isn't clear from the page, so I'd need more information on that. If it truly streamlines our process and offers a single source of truth, I might consider paying up to $50 per month.
Simulated interest: 40/100
Earl BashirianneutralThis Val product sounds interesting, particularly the 'Content as Code' aspect. However, my biggest hurdle right now is integrating directly with client systems. My team and I spend a lot of time manually copying approved content into various client platforms because each has its own naming conventions and approval path. While Val's local-first approach and Git integration are appealing for our internal workflow, it doesn't seem to address the core problem of getting content *out* and into client-specific environments without that manual step. The pricing page doesn't show specific tiers or costs, so I can't estimate a monthly payment. I'd need to see how it handles client-side integration before considering a purchase.
Simulated interest: 30/100
Aagam Embranthiri-SharmaneutralAs a documentation engineer managing everything from Markdown to versioning, I handle my current workflow manually: Markdown in GitHub, release tracking Sheets and Jira. The idea of Val's Git-centric, TypeScript-based system is intriguing, but I have concerns. My primary workflow is already code-adjacent, but I'm cautious about adopting a new CMS right now because our startup is hyper-focused on API changes, and I need stability more than new features. If I tried Val, I'd worry about migrating existing content, an unwelcome distraction when I'm drowning in documentation updates. I might pay something, but it would have to offer instant-value for my current workflow. As it stands, I'd need to see undeniable proof that Val integrates with our existing GitHub ecosystem without disruption. $150 USD per month might be acceptable, but I'm not optimistic unless there's a clear migration path and minimal learning curve. The $0signup is helpful, but I'd still need to allocate time for the switch.
Simulated interest: 30/100
Dixie GrahamneutralThe main thing that would stop me is understanding how this "content as code" approach integrates with our current workflow, especially with product and support teams. Right now, we're using Google Docs and a knowledge-base platform, and the manual handoffs are the biggest bottleneck I'm trying to solve. I'd need to see if Val can actually streamline that rather than adding another layer. I also don't see pricing listed here, so I can't estimate a monthly cost. If it's an easy integration and solves our publishing issues, I might consider up to $50 per month, but that's a tentative guess without seeing the pricing structure.
Simulated interest: 40/100
Irina CharpentierneutralThis Val tool seems interesting, especially the 'Content as Code' approach, which might appeal to our legal team's desire for structure. However, to try it this month, I would need to understand how it integrates with our current workflow. Today, we use Word for drafting, email for approvals, and Excel for tracking. My primary concern is how to manage the approval process with HR and Legal using Val, as their input and sign-off are critical and currently rely on email chains. Without a clear understanding of this collaborative aspect and how it handles version control across departments, I cannot commit to adopting it. Also, the pricing isn't detailed on the page; I need to see the monthly cost in USD.
Simulated interest: 40/100
Genevieve WunschneutralMy main concern with trying Val this month would be integrating it with our current workflow. We rely heavily on our spreadsheet for tracking seasonal copy and SKU changes, and then manually inputting that into the storefront CMS. I'd need to understand how Val would streamline that process without creating more work for our two-person marketing team. I'm a bit skeptical about the "content as code" approach for our team, as we don't have dedicated developers for content operations. The lack of signup required is appealing, though. I'd be willing to explore this further if the setup is straightforward. If it's easy to adopt, I might consider paying up to $50 per month.
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.