Foreman

Analysis basis

This report is based entirely on the self-reported project description provided by the author. No external verification, revenue data, customer names, or traction metrics are available. All claims are treated as stated by the author and not independently confirmed.

The description states that Foreman is an AI employee that lives on WhatsApp. It processes natural language requests from business owners and performs operations such as:

• Planning tasks
• Looking up customers
• Generating PDF invoices
• Sending emails
• Scheduling appointments
• Creating payment reminders
• Updating customer history
• Streaming actions to a live dashboard
• Confirming outcomes via WhatsApp

It supports multi-turn conversations, allowing users to reference previous customers without repeating context.

The system uses a two-phase execution model: first, an AI planner creates a structured plan; then, tools execute the plan and only after successful completion does the final WhatsApp response get sent.

Evidence The author's own write-up describes Foreman’s functionality in detail. No independent corroboration or demonstration of actual product behavior is provided.

The author positions Foreman as an “AI foreman” — an AI employee that works over WhatsApp, enabling business owners to send simple instructions like:

"Schedule Rahul for Friday at 3 PM, invoice him after the job."

This implies a shift from traditional CRM or task management tools toward a conversational interface for daily operations.

The project evolved from a hackathon idea into a modular system designed to support future integrations and workflows. The team notes they moved away from serverless architecture due to reliability issues with persistent connections and background tasks.

Inference The positioning suggests Foreman aims to become an automated assistant for small trades, not just a chatbot or tool. However, the claim of being an “AI employee” is unverified without evidence of real-world usage or performance.

The description identifies small service businesses such as HVAC technicians, plumbers, electricians, and similar trades as primary users. These businesses reportedly do not use expensive CRM software; instead, they rely on WhatsApp, spreadsheets, and memory for managing operations.

Evidence The author explicitly names these industries and describes their current practices (WhatsApp + spreadsheets). No data on customer segments or personas beyond this is provided.

There is no mention of pricing, monetization strategy, or business model in the description. The project is presented as a hackathon prototype with no indication of commercial viability or revenue streams.

Not evidenced No information about how Foreman would be sold, whether it's freemium, subscription-based, or one-time purchase.

Foreman was built using:

• AI development tools: Codex + GPT-5.6 (for scaffolding, debugging, testing)
• Runtime AI: Groq Llama 3.3 70B
• Frontend: Next.js 15, Tailwind CSS, shadcn/ui
• Backend: FastAPI, SQLAlchemy, PostgreSQL (Supabase)
• Integrations: WhatsApp Business Cloud API, ReportLab, Resend/Gmail, Supabase Storage

Key technical decisions include:

• Provider-agnostic PlannerLLM interface for switching models
• Two-phase execution model to prevent hallucinations and ensure verified results
• Modular architecture supporting easy addition of new tools

Evidence The write-up includes a detailed tech stack and architectural choices. No evidence of production deployment, scalability, or performance data is included.

The project was submitted as part of the OpenAI 2026 hackathon on Devpost. There is no evidence of:

• Revenue
• Customers
• User adoption
• Product-market fit
• Deployment in real-world settings

Not evidenced No traction data, user feedback, or live usage metrics are reported.

No competitive analysis or market positioning relative to existing solutions (e.g., CRM platforms like HubSpot, Zoho, or niche tools for trades) is included in the description. The author does not reference competitors or explain how Foreman differentiates from them.

Not evidenced No mention of existing alternatives or competitive advantages.

• Unverified claims: The project is described as an AI employee, but there is no evidence of real-world performance or user testing.
• No commercial viability: No pricing model, monetization strategy, or business plan is evident.
• Prototype-only status: Built for a hackathon; no indication of production readiness or long-term roadmap implementation.
• AI hallucination risk: While mitigated through validation, the system still relies heavily on AI interpretation — a known challenge in real-world applications.
• Limited scope: Only one team member worked on it, suggesting limited development capacity.

Inference These points are based on the lack of evidence for traction or commercialization, combined with the prototype nature of the project.

1. What specific business problems does Foreman solve today? How do you know?
2. Have any real customers used Foreman beyond the hackathon?
3. Is there a plan to monetize this product? If so, what is it?
4. How are you handling data privacy and compliance (especially around customer information)?
5. What are the technical limitations of the current system that would prevent scaling?
6. Are there any plans for integrating with accounting or ERP systems beyond what’s mentioned?
7. How do you intend to onboard users and train them to use Foreman effectively?