Shadow Comp

The description states Shadow Comp:

• Turns a business brief into an editable, evidence-based business decision report
• Helps compare choices such as pricing, usage limits, and hiring plans
• Shows possible impact on revenue, costs, churn, support workload, infrastructure pressure, and runway
• Generates downloadable PDF reports and model-data CSVs
• Uses TypeScript, a web dashboard, and a deterministic simulation engine
• Incorporates AI (Codex, GPT) for organizing briefs, identifying missing assumptions, research context, and explaining results
• Separates AI content from verified results through a calculation engine

Not evidenced: The actual functionality of the tool beyond its self-description, whether it's a working prototype or a proof-of-concept, or if any of these features are implemented.

The description states:

• Shadow Comp was inspired by "letting teams rehearse their company’s future before making real-world decisions"
• It helps users compare business choices and see operational impacts
• The tool is positioned as more than generic AI advice, offering clear view of what is assumed, researched, or calculated
• It aims to be a "business decision platform" with smarter simulations, richer models, and better forecasting

Inferred: The positioning suggests it targets founders, startups, and decision-makers who need structured planning tools. However, no evidence shows how this differs from existing business planning frameworks or AI tools.

The description states:

• Targets founders, startups, and decision-makers
• Helps with major pricing, hiring, and growth decisions
• Aims to support "more business types" in the future

Not evidenced: No specific customer segments, personas, or use cases beyond general references to founders and startups. No evidence of target market research or user interviews.

The description states:

• The tool generates editable reports with PDF and CSV exports
• It is described as a business decision platform for planning and forecasting
• No pricing information or monetization strategy is mentioned

Inferred: If this becomes a commercial product, it would likely be SaaS-based, but there's no evidence of any pricing model, subscription tiers, or monetization approach.

The description states:

• Built with TypeScript, web dashboard, and deterministic simulation engine
• Uses Codex, GPT, CSS, HTML, Node.js, OpenAI, PDF.js, Railway, REST API, Supabase, Vitest
• Features include editable report inputs, industry KPI models, scenario comparisons, sourced research, report-confidence checks, PDF generation with PDFKit, and automated tests
• Challenges included PDF generation, incorrect values from mixed data sources, and unreliable features during development

Inferred: The technical stack suggests a web-based SaaS product with AI integration. However, no evidence of production deployment or scalability.

The description states:

• This is a hackathon submission (OpenAI 2026)
• Built by one person (Muhsin Abdul Kader)
• No revenue, customers, or adoption data are provided
• The team size is listed as 1

Not evidenced: No evidence of traction, user feedback, or product-market fit. The project appears to be a prototype or proof-of-concept.

The description states:

• It aims to help with business decisions and forecasts
• It separates AI content from verified calculations
• It is positioned as more than generic AI advice

Not evidenced: No mention of competitors, market analysis, or competitive differentiation. The author does not reference existing tools in this space.

• The project is a hackathon submission with no commercial traction
• Only one team member (Muhsin Abdul Kader) is listed
• No evidence of revenue, customers, or product-market fit
• The tool is described as a prototype or proof-of-concept, not a production-ready solution
• AI integration is described but not demonstrated in functionality
• No clear business model or monetization strategy

Inferred: The lack of any commercial activity or user testing raises questions about viability and scalability.

1. What specific business decisions have you used this tool to make?
2. Have you tested the tool with actual users or potential customers?
3. How do you plan to monetize this product if it becomes a commercial offering?
4. What is your roadmap for scaling beyond the current prototype?
5. How do you ensure accuracy of AI-generated content vs. deterministic calculations?
6. What are the key assumptions in your simulation engine, and how are they validated?