ReConvene | Meeting Orchestration

Note: This analysis is based entirely on the self-reported, unverified description provided by the authors. No external data, revenue figures, customer names, or third-party validation are available.

The description states that ReConvene is a "privacy-conscious coordination layer above existing calendars" that orchestrates and repairs critical meetings with explicit consent. It operates through:

• Natural language input from an executive assistant.
• Structured output from GPT-5.6 to convert the request into a typed meeting brief (objective, duration, deadline, must-attend people, required roles, etc.).
• A deterministic policy engine that evaluates candidate plans based on constraints like deadlines, role coverage, attendance modes, and consent.
• Human workflows for approval and reconfirmation.
• Simulated integration with Outlook-like systems.

It is described as a Next.js 16 / React 19 / TypeScript application deployed on Vercel, using Supabase for data synchronization and GPT-5.6 for structured interpretation.

Claim: ReConvene is a meeting orchestration tool that uses AI to interpret requests and deterministic logic to manage scheduling decisions.

Evidence: The author's own write-up describes the architecture and workflow in detail, including use of GPT-5.6, Supabase, and Next.js.

The description indicates that ReConvene positions itself as a solution to inefficiencies in high-stakes executive scheduling, particularly around manual coordination and lack of clear consent signals. It claims to reduce repetitive negotiation while preserving human authority and participant consent.

It also emphasizes privacy: calendar availability is not treated as consent; instead, only busy intervals are visible to the system, not event details.

Claim: ReConvene reduces manual coordination in executive meetings and preserves privacy.

Evidence: The inspiration section explicitly states that scheduling requires "a surprising amount of manual coordination" and that "calendar availability is not consent."

The description identifies three synthetic personas to demonstrate the workflow:

1. Emma Brooks – Executive Assistant
2. Olivia Carter – CEO
3. Marcus Reed – Head of Operations

These roles suggest a target customer segment focused on large organizations with complex executive-level scheduling needs.

Claim: The primary users are executive assistants and executives managing high-stakes meetings.

Evidence: The demo personas reflect organizational hierarchy, where assistants coordinate but cannot approve for executives or reconfirm for others.

No information is provided about pricing models, monetization strategies, or business model assumptions.

Claim: Not evidenced.

Explanation: There is no mention of how the product would be sold, who pays, or what revenue streams are envisioned.

The system is built using:

• Frontend: Next.js 16, React 19, TypeScript
• Backend: Node.js, Supabase (PostgreSQL), Vercel
• AI: GPT-5.6 with Structured Outputs
• Security: Row Level Security, tenant isolation, participant-owned consent

The architecture separates:

• Natural language interpretation (GPT-5.6)
• Deterministic decision logic (policy engine)
• Human authorization steps

It includes simulated integrations with Outlook and plans for future Microsoft Graph support.

Claim: The system uses a hybrid approach combining generative AI and deterministic logic.

Evidence: The write-up explicitly states that GPT-5.6 interprets language, while deterministic code handles scoring, deadlines, and eligibility.

There is no evidence of revenue, customers, or adoption beyond the hackathon demo.

Claim: Not evidenced.

Explanation: The project is described as a hackathon submission with no indication of real-world usage or pilot deployments.

The description does not reference competitors directly. However, it implies a niche in executive scheduling and coordination tools that prioritize privacy and consent over traditional calendar-based solutions.

Claim: Not evidenced.

Explanation: No mention of existing products or competitive landscape is present in the provided text.

1. No commercial traction or validation – The product exists only as a hackathon demo.
2. Unproven scalability – The architecture is described for a small-scale demo, not production use.
3. Dependency on AI and external APIs – Reliance on GPT-5.6 and Microsoft Graph integration introduces risk if those services change or become unavailable.
4. Limited team size – Only two founders are listed, which may limit execution capacity.

Inference: Without real-world testing or customer feedback, the viability of this product remains unproven.

Explanation: The description does not include any evidence of user testing, market validation, or performance metrics.

1. What specific pain points in executive scheduling led to the creation of ReConvene?
2. How do you plan to validate demand for this product outside of a hackathon setting?
3. Are there any early adopters or pilot customers interested in testing the solution?
4. What are the key assumptions about user behavior and organizational workflows that underpin your design choices?
5. How will you ensure secure handling of sensitive calendar data, especially with third-party integrations?
6. What is your roadmap for transitioning from a demo to a production-ready product?