HRF+ - Construction Schedule & Cost Control

Note: This analysis is based entirely on the self-reported project description provided by the caller. No external verification or historical data is available. All claims are treated as stated by the author and not proven facts.

• The description states that HRF+ is a multi-organization workspace for planning and monitoring material and financial progress of construction investments.
• It supports two main views: investment hierarchy (project → investment → group → work item) and contractor-based organization (contractor → investment → work item).
• Users can create, edit, reorder, move, archive, and restore elements within a hierarchical structure.
• Financial tracking includes planned, committed, contracted, invoiced, and paid stages with support for both manual and automatic aggregation modes.
• The system supports document storage, OCR parsing of PDFs/images, Excel import/export, AI-assisted extraction, and real-time collaboration features.
• It uses Supabase Realtime for synchronization and PostgreSQL Row Level Security (RLS) for access control.

Claim: The product is described as a web application that improves over Excel-based workflows in construction planning and cost control.

Evidence: Self-reported by the author; no independent validation or demonstration of functionality beyond the narrative.

• The tagline “Interactive construction planning and cost control—without spreadsheet chaos” positions HRF+ as a replacement for Excel.
• The author frames the project as solving a real-world problem faced by their husband, who works with complex construction investments involving large spreadsheets.
• The evolution from an idea to a deployed application is described as being enabled by AI coding tools like Codex and GPT-5.6.
• The product is positioned not just as a tool but as one that adapts to different working styles—offering both manual control and automation via AI.

Claim: HRF+ aims to replace Excel-based systems with a more structured, collaborative, and intelligent platform.

Evidence: Self-reported; the author describes the motivation and development process but does not provide evidence of prior market positioning or competitive analysis.

• The primary users are described as those working in complex construction investments where material and financial schedules live in large Excel files.
• These include managers needing to track project progress, contractors responsible for specific scopes, and teams managing contracts, invoices, and payments.
• The system supports multiple organizations with data isolation, suggesting enterprise-level use cases.
• Users may be involved in planning at annual, quarterly, or monthly levels.

Claim: HRF+ targets professionals working on complex construction projects requiring structured financial and material tracking.

Evidence: Based on the author’s husband's experience; no explicit customer segmentation or persona data provided.

• No pricing model or business model is described in the submission.
• The application appears to be built for internal use within organizations, with support for role-based access control (administrators, editors, read-only users).
• There is no mention of monetization strategies, licensing, subscriptions, or SaaS offerings.

Claim: No evidence of a defined business model or pricing strategy.

Evidence: Not evidenced; the description focuses on functionality rather than commercial aspects.

• Built using Next.js, React, TypeScript, PostgreSQL, Supabase, Playwright, Vitest, GitHub, and OpenAI APIs.
• Uses GPT-5.6 for AI assistance, including document parsing, summarization, and data extraction.
• Implements a two-stage Excel import system: one using GPT-5.6 to analyze structure, followed by deterministic XLSX parsing.
• Supports real-time collaboration via Supabase Realtime, versioning, conflict resolution, and undo/redo functionality.
• Uses PostgreSQL Row Level Security (RLS) for data isolation between organizations.
• Includes CI/CD practices with schema verification and migration testing.

Claim: HRF+ is a modern web application leveraging AI and cloud infrastructure.

Evidence: Self-reported; the author lists technologies used but provides no evidence of production deployment or scalability metrics.

• The project was submitted to the OpenAI 2026 hackathon.
• It is described as a single-person effort, with the author stating they had no coding experience initially.
• No information about actual users, customer feedback, or adoption is provided.
• There is no mention of revenue, ARR, headcount, or product-market fit indicators.

Claim: No traction or maturity signals are evident.

Evidence: Not evidenced; the description emphasizes development and features over usage or impact.

• The author notes that existing software tools either were too generic or assumed different financial models.
• They imply that current solutions do not reflect how their husband works in practice.
• No specific competitors are named, nor is there any competitive analysis or differentiation strategy described.

Claim: HRF+ addresses a gap in the market for construction planning tools.

Evidence: Based on author’s perception of existing tools; no external benchmarking or competitive landscape data provided.

• The entire project was built by one person with no prior coding experience, raising questions about long-term maintainability and scalability.
• Heavy reliance on AI tools (Codex, GPT-5.6) introduces dependency risks and potential instability if those services change or become unavailable.
• No evidence of production deployment, user testing, or feedback loops.
• The lack of pricing, monetization, or go-to-market strategy suggests the project is still in early conceptual stages.

Claim: High risk due to single-person development, AI dependency, and lack of commercial traction.

Inference: Based on limited evidence of product maturity and business planning.

1. What specific construction workflows or pain points does HRF+ aim to solve in practice?
2. Has the solution been tested with actual users from the construction industry?
3. Are there any plans for monetization, pricing models, or customer acquisition strategies?
4. How is data security and compliance handled, especially given the use of AI tools like GPT-5.6?
5. What are the technical limitations or scalability concerns of the current architecture?
6. Is there a plan to expand beyond Polish/English language support?

Note: These questions are based on the lack of clarity in the self-reported description and aim to probe deeper into unaddressed areas.