What would stop you from trying Persian License Plate Recognit (https://truthofmatthew.com/projects/persian-license-plate-recognition/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

Page reviewed

Persian License Plate Recognition (PLPR): open-source Iranian plate reader

https://truthofmatthew.com/projects/persian-license-plate-recognition/ (opens in a new tab)
Saved screenshot of Persian License Plate Recognition (PLPR): open-source Iranian plate reader
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

28/100

AI synthesis, not measured demand

Suggested price range

$0–50

Median $20 · simulated willingness to pay

Response sentiment

Positive 0%Neutral 90%Negative 10%
The takeaway

What this panel suggests

The main thing that would stop people from trying PLPR this month is deployment uncertainty, not outright rejection of the idea. Respondents want a clear path from the product’s browser, desktop, API, and edge-agent options to their own cameras and gate hardware. As one person put it, "I'm unclear on how to integrate an edge agent for our camera feed," and another said, "We don't have a dedicated IT department, so setup needs to be straightforward". Reliability is the second blocker: people want proof it can handle glare, night conditions, and other messy real-world inputs, especially if they have already been disappointed by OCR tools. A few also questioned the monetization story because the page says the product is free/open source, yet a subscription is implied; one respondent said, "The pricing basis is unclear regarding a subscription for an open-source product". In practice, some buyers seem to handle this today with manual checks or spreadsheet-based whitelists. Among the five respondents who gave a number, willingness to pay was modest: $0 to $50 per month, with a median of $20.

A hypothesis to test

Pricing & positioning

If charging monthly, position it as managed deployment, support, and integration help rather than charging for the open-source code itself.

The subscription story is not yet clear next to the free/open-source positioning. Among the respondents who named a price, willingness to pay was modest, ranging from $0 to $50 per month with a $20 median.

Recurring themes

Integration and Setup Complexity
“I'm unclear on how to integrate an edge agent for our camera feed”Read Justin Hermann-Dare’s response →
Reliability in Challenging Conditions
“I'd need to see how it handles varying light conditions, like the glare I already deal with”Read Margarita Brekke’s response →
Open Source vs. Paid Support Expectations
“The pricing basis is unclear regarding a subscription for an open-source product”Read Isaac Bradtke’s response →

Objections to investigate

  • Lack of Clear Integration Path
  • Current Manual Process Sufficiency
  • Niche Geographic Limitation

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.

Justin Hermann-Dareneutral

This "Persian License Plate Recognit" sounds interesting, but I'm not sure if it's what we need right now. My main concern is that our camera system's image clarity is inconsistent, especially with Iranian plates, which forces my team to manually log them. I'm trying to improve that with better camera maintenance and lighting adjustments. The website mentions it's open-source and free, which is great, but I'm unclear on how to integrate an edge agent for our camera feed, or if it directly replaces our current process of checking against a Google Sheet and PDF list. Without more clarity on integration and if it handles blurry images well, I can't commit. If it works seamlessly with our existing setup and the edge agent can automate the verification against our lists, I might consider a small monthly fee, maybe around $50 per month.

Simulated interest: 30/100

Isaac Bradtkeneutral

This looks like an interesting piece of software, especially with it being open source. However, my current client, the logistics firm, already has a paid LPR platform in place. My job is to export their Iranian plate data to CSV for their manager to cross-reference with guard logs and contractor lists. I don't see a need to replace their existing system or add another layer of complexity for this specific task. If I were to consider something like this, it would be for a new project or if the existing system proved unreliable, but that's not the case here. I wouldn't pay for this; it's open source, so I can download it and test it myself. The pricing basis is unclear regarding a subscription for an open-source product, so I can't estimate a monthly cost.

Simulated interest: 20/100

Megan van de Walneutral

Right now, I handle Iranian license plates manually by having residents email or submit them through the app, and then cross-referencing them with an Excel whitelist. This process is time-consuming and error-prone, especially when guards have to manually check each plate. Trying Persian License Plate Recognition (PLPR) sounds appealing, but I’d need to ensure it integrates seamlessly with our current setup and doesn’t require extensive IT knowledge to operate. I’m also skeptical because it’s open-source, and we might need professional support for implementation. Additionally, we’d have to maintain the whitelist manually, so unless it offers direct integrations with our existing systems, the benefits might not outweigh the effort. I wouldn't pay anything for this right now given these concerns, but if it proved reliable, I’d consider a small budget of $50 per month for a premium supported version if it existed, assuming it included compliance features we lack today.

Simulated interest: 35/100

Anunay Maliknegative

The main issue for me is that this product specifically reads *Iranian* license plates. My concern is with any foreign plate, not just those from Iran. Today, my guards check a shared sheet and call me if a car isn't on the day's entry list. It’s manual and can be slow. While I appreciate that this is open-source, I'm not sure how easily it could be adapted for all foreign plates, or integrated with our basic CCTV. I would not pay for a solution that only handles Iranian plates.

Simulated interest: 10/100

Margarita Brekkeneutral

This "Persian License Plate Recognit" sounds interesting, but right now, what would stop me from trying it is the manual process I'm already used to. I copy Iranian plates from camera stills into a spreadsheet, then match them with paperwork and driver IDs. It's repetitive, but it works, and I know it. It's open-source, which is great, but I'm not sure how easy it would be to integrate with our current system or if it would require a lot of setup time. I'd need to see how it handles varying light conditions, like the glare I already deal with, and if it's reliable enough for our yard. As for payment, since it's open-source, I don't see myself paying for it. $0 per month.

Simulated interest: 10/100

Carlos Boganneutral

At present, my team and I rely on a free web OCR tool, and when it fails to recognise an Iranian plate, which is quite often, we meticulously log the details in a handwritten exception book kept at the barrier. This new tool you're mentioning, Persian License Plate Recognition, sounds like it might be an improvement, especially if it runs in the browser or as an API. However, as a supervisor, I need to be absolutely sure of its reliability and integration before considering it. Our current method, while manual, is a documented procedure. I would need to see clear evidence of its accuracy and how easily it can be implemented without disrupting our existing operations. Given my salary and the university's budget constraints, I'm not in a position to commit to a monthly fee for software unless it offers a significant, proven benefit. Therefore, I would not pay anything per month at this time.

Simulated interest: 30/100

Daphné Davidneutral

This sounds interesting, as the manual verification of Iranian license plates is indeed a very time-consuming process for my team and me. We spend a significant amount of time cross-referencing booking notes with our arrival list, especially when guests send photos beforehand. The biggest obstacle to trying this immediately is understanding the integration. You mention it can run in a browser, as an API, or as an edge agent – I need to know more about how this connects with our existing system to open our barrier. We don't have a dedicated IT department, so setup needs to be straightforward. Regarding payment, since this is open-source and available on GitHub, I wouldn't pay a monthly subscription. I would consider a one-time fee for professional support or a more polished, integrated version if it proved exceptionally valuable and simple to implement, perhaps around $50.

Simulated interest: 30/100

Javas Nehruneutral

Honestly, the main thing stopping me is that it's for Iranian plates. While I appreciate the open-source nature, my clients here in Ahmedabad use Indian plates, and I've already built custom scripts and trained models to handle those accurately. I rely on my spreadsheet whitelist and Python scripts for handover. If this product supported Indian plates out-of-the-box or was easily adaptable, I'd consider it, but right now, it's not a direct fit for my current projects. The free and open-source aspect is great, though. I wouldn't pay for a subscription for this particular tool given its current focus.

Simulated interest: 20/100

Darlene Boyerneutral

Right now, I handle Iranian plates by manually reviewing short video clips against our tenant records and visitor log. The process is time-consuming, and if the plate is unclear, I make a note to review later. The main thing stopping me from trying Persian License Plate Recognition (PLPR) this month is that I need to ensure it's accurate enough to reduce my workload without creating more errors. I've tried free OCR tools before, and the inaccuracies weren't worth the time saved. I'd need to be confident that PLPR can reliably read obscured or damaged plates. Given my cautious nature, I'd need to test it thoroughly before committing to any tool. As for the cost, I'd be willing to pay up to $20 per month if it significantly reduces the time I spend on plate verification and improves accuracy.

Simulated interest: 60/100

Basilio Carrieroneutral

This 'Persian License Plate Recognit' sounds interesting, especially since we still have guards manually writing down Iranian plates. Today, my team uses a competitor's LPR tool at one site and free software at another. Neither handles Iranian plates well, so we keep paper exception cards for those. The main hesitation is understanding how this integrates with our current systems and if it's truly reliable. It's open source, which is a good start, but I'd need to see it in action with our cameras. I'm not prepared to pay for something like this given our budget constraints. So, for now, it's $0 per month.

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