FlowPilot

The description states that FlowPilot is an event-driven personal automation app. It connects to services such as email, calendar, files, GitHub, weather, and notifications.

It allows users to create "standing orders" — workflows triggered by specific events (e.g., receiving a flight confirmation). These workflows can include actions like creating an itinerary, updating the calendar, saving tickets, checking weather, and notifying family — with approval steps where needed.

The system converts incoming data (emails, files, webhooks) into structured events, matches them to saved standing orders, prepares an action plan, checks permissions and risk levels, and executes approved tasks through connected services.

Evidence The author describes the functionality in detail, including how it handles event detection, workflow execution, and user control. It is not evidenced whether any of this has been tested or used beyond the prototype stage.

The author positions FlowPilot as a tool that goes beyond simple question-answering to automate tasks that begin with real events — such as flight confirmations, client messages, or subscription renewals.

It is described as:

• An automation app that keeps users in control.
• A system for handling the next steps automatically after an event.
• Focused on reliability and safety, especially when dealing with external data sources.

The claim evolution shows a shift from “I want to build something more than answering questions” to a concrete prototype that handles multi-step workflows triggered by events.

Evidence The positioning is self-reported. No third-party validation or market positioning data is provided.

The author states that FlowPilot is intended for:

• Freelancers, students, families, and small businesses
• Users who want to reduce manual work through automation
• Non-technical users (the author plans to improve the standing-order builder so it’s easier to use)

Evidence The target customer is inferred from the author's stated goals and future roadmap. No actual customer data or segmentation is provided.

The description does not contain any information about pricing, monetization, or business model.

Evidence Not evidenced.

The system was built using:

• Frontend: Next.js, TypeScript
• Backend: FastAPI, PostgreSQL
• Services connected: GitHub API, Gmail API, Google Calendar API, Google Drive API, Telegram Bot API, OpenAI API, Open-Meteo API, OAuth 2.0, Webhooks
• Deployment: Vercel, Google Cloud Run
• Other tech: PWA, Supabase, Tailwind CSS, shadcn/ui

The author notes challenges in making the system reliable and safe, including:

• Event validation
• Duplicate protection
• Permission checks
• Retries
• Approval steps
• Error handling

Evidence The technical stack is self-reported. No evidence of production deployment or scalability.

The project was submitted to a hackathon (OpenAI 2026), and the author describes building a working prototype with:

• A Travel Autopilot feature
• Clear action timelines
• Multi-step workflows

There is no evidence of any users, customers, or revenue.

Evidence Not evidenced. The project is described as a single-person hackathon submission.

The description does not mention competitors or market positioning.

Evidence Not evidenced.

• Single-person build: Only one team member (Sujit Sarkar) is listed.
• No traction or users: No evidence of real-world usage, customers, or revenue.
• Unverified claims: All descriptions are self-reported and unverified.
• Prototype stage: The system is described as a working prototype, not a production-ready product.
• Limited scope: The author notes that small, focused workflows are more useful than broad automation.

Evidence These are inferred from the lack of any external validation or usage data.

1. What is the actual user base or adoption rate for FlowPilot?
2. How many users have created and executed standing orders?
3. Has the system been tested in real-world scenarios beyond the prototype?
4. Are there any plans to monetize or scale the product?
5. What are the key challenges in moving from prototype to production?
6. How does FlowPilot handle edge cases or failures in external service integrations?