WattProof

Analysis basis

The entire analysis is based on the self-reported project description provided by the caller. All claims are unverified and must be treated as stated by the author only. No third-party data, financials, customers or historical context are available.

The description states that WattProof is a small Python application built with:

• Flask (for a framework-free responsive interface)
• Pydantic (to define versioned contracts for extraction, evidence, tariff, audit, comparison, and review-request)
• Python Decimal code (for money arithmetic with explicit rounding)
• GPT-5.6 (via OpenAI API) to map unknown native-PDF text into typed evidence
• Codex (used in primary build session)

It runs entirely locally for the bundled public sample without an API key.

Inference The product is described as a proof-of-concept or prototype, not a production-ready SaaS offering. It is not evidenced to be used by customers or deployed beyond the author’s own environment.

The description states that WattProof:

• Uses GPT-5.6 to extract evidence from PDFs
• Does not calculate charges or invent missing data
• Flags errors using deterministic code checks against tariffs
• Drafts review requests citing exact lines and sources
• Operates with a focus on truth, reproducibility, and transparency

Key claims include:

• “Effective-period truth” — newer tariffs are not applied if they didn’t govern the bill
• “Evidence before automation” — users can correct facts before conclusions
• “Deterministic money” — GPT reads evidence; code owns arithmetic
• “Visible uncertainty” — unsupported riders and insufficient data remain explicit
• “Action without overclaiming” — final request asks for review, not resolution

Claim vs. Fact

These are self-stated positioning elements, not verified claims of traction or customer validation.

The description does not state who the intended users are beyond the general context of electricity bill auditing.

Not evidenced No specific customer profile, persona, or ICP is described.

There is no evidence in the description of:

• A pricing model
• Revenue streams
• Monetization strategy
• Customer acquisition costs
• Any commercial arrangement

Not evidenced The business model and pricing are not described.

The project is built with:

• Flask (web framework)
• Python (core logic)
• Pydantic (schema validation)
• GPT-5.6 via OpenAI API
• Codex (used in development)
• JavaScript (for UI, implied)

It includes:

• Versioned contracts for data types
• SHA-256 hashes for source snapshots
• Local execution for sample documents
• Regression testing with golden and synthetic fixtures

Inference The tool is described as a minimal prototype built for demonstration or hackathon use. It is not evidenced to be in production, scalable, or integrated into any larger platform.

The description states:

• Team size: 2
• Built for the OpenAI 2026 hackathon
• No revenue, customers, or adoption data are mentioned
• The sample is bundled and runs locally without API key

Not evidenced There is no evidence of traction, usage, or product maturity beyond the author’s own account.

The description does not mention:

• Competitors
• Market size
• Existing solutions in the electricity bill auditing space
• Product differentiation from other tools

Not evidenced No competitive landscape or positioning relative to existing players is described.

• The project is a self-reported hackathon submission with no evidence of commercial traction.
• GPT-5.6 is used for extraction but not for decision-making or calculation.
• No customer data, revenue, or usage metrics are provided.
• The tool is described as a prototype with local execution and no API integration.
• The team size is small (2 people), which may imply limited scalability or resources.

Inference The lack of any commercial evidence raises questions about viability, market fit, and potential for growth.

1. What is the intended customer segment and how did you identify them?
2. Are there any real-world users or test cases beyond the sample bill provided?
3. How do you plan to monetize this tool if it remains a prototype?
4. Is there any intention to scale beyond the current local execution model?
5. What are your plans for integrating with utility providers or billing systems?