Should I Buy This?

Company: Should I Buy This?

Tagline: Stop doom-scrolling your cart. Describe the item, answer 3 quick questions, and get an honest AI verdict Buy, Wait, or Skip before you regret the purchase.

Self-reported basis: The entire analysis is based on a single project description submitted by the author to the OpenAI 2026 hackathon on Devpost. No external verification, revenue, customer data, or traction evidence is available.

What it appears to be: A decision-support tool for consumer purchases, using AI to evaluate whether a user should buy an item based on personal financial context and desire intensity.

What changed: The project was submitted as part of a hackathon. No indication of prior development or product launch exists in the description.

Single most important open question: Is there any evidence that users actually engage with this tool, or that it has been tested beyond the author’s own use?

The description states that Should I Buy This is a quick decision assistant for purchases. Users input an item (name, price, and optionally a link or photo), then answer three questions:

• How much they make (monthly income)
• How badly they want it (intensity scale of 1–10)
• When they last bought something similar

The system computes a score using a formula and provides a verdict: Buy It, Wait a Week, or Skip It. The explanation for the verdict is generated by GPT 5.6.

Inference: The tool appears to be a lightweight, AI-powered personal finance decision aid, designed to intervene at the point of purchase.

Not evidenced: No information about how the scoring weights are applied in practice, or whether they are dynamic or static.

The author claims that most budgeting apps only tell users what they already spent — not what they’re about to spend. The product is positioned as a tool that intervenes at the moment of decision, before a purchase is made.

Claim: It gives an “honest, personalized answer” instead of generic advice like “wait 24 hours.”

Inference: The positioning is centered on personalization and timing — intervening in real-time to prevent impulse purchases.

Not evidenced: No evidence that the tool has evolved from a prototype or been tested with users beyond the author’s own experience. No mention of how it differentiates from existing budgeting tools or AI assistants.

The description states that the product is for people who have “that moment of staring at an ‘Add to Cart’ button, torn between wanting something and knowing we probably don’t need it.”

Inference: The target customer is a consumer with some disposable income who struggles with impulse buying.

Not evidenced: No segmentation or persona details beyond this general description. No evidence of user research or market validation.

The description does not mention any pricing, monetization strategy, or business model.

Inference: The tool appears to be a prototype or proof-of-concept, with no indication of how it would be monetized.

Not evidenced: No evidence of revenue streams, subscriptions, ads, or paid features.

The product was built using:

• Codex
• GPT 5.6
• React
• Node.js
• HTML/CSS/JavaScript
• OpenAI API

The system uses a weighted formula to score purchases and then feeds that into GPT for natural language explanation.

Inference: The tool is built with AI-assisted development tools, suggesting a rapid prototyping approach.

Not evidenced: No evidence of scalability, infrastructure, or deployment details. No mention of data privacy or user onboarding.

The project was submitted to the OpenAI 2026 hackathon. The author states that it is a prototype built in a short time by one person.

Inference: This is a very early-stage product, likely not yet launched to users or monetized.

Not evidenced: No evidence of user engagement, adoption, or usage metrics. No mention of any prior versions or iterations.

The description does not reference any competitors.

Inference: The tool appears to be positioned as a novel solution for impulse purchase decisions, but no competitive analysis is provided.

Not evidenced: No information about existing tools that help with budgeting, impulse control, or decision-making around purchases.

• No traction evidence: The project is described as a hackathon submission with no prior usage or adoption.
• Unproven model: The scoring formula and GPT reasoning are not validated beyond the author’s own testing.
• Single-person team: The entire product was built by one person, raising questions about scalability or long-term maintenance.
• No monetization strategy: No indication of how the tool would be monetized or whether it is intended for commercial use.

Not evidenced: No evidence of user feedback, market demand, or product-market fit beyond the author’s own experience.

1. What was the process of testing the scoring formula with real users?
2. How does the tool handle edge cases (e.g., very high or low income, unusual purchases)?
3. Is there any plan to collect user data or build a history of decisions?
4. What are the plans for scaling beyond a single developer?
5. Has the tool been tested in real-world scenarios outside of the hackathon?