Consul

The description states that Consul is:

• An AI-first marketplace for paid online consultations.
• A platform where clients discover specialists, book slots, and pay via token balance.
• A system enabling live video and real-time voice translation across languages.
• A product with native iOS apps (SwiftUI) for both client and expert roles.
• Integrated with LiveKit for media sessions, Kafka for event streaming, and PostgreSQL/Redis for data.

Inferences:

• The platform includes a real-time assistant that operates within the session boundaries.
• It uses token-based billing during live consultations.
• It supports guest booking without requiring pre-existing accounts.

Not evidenced:

• No information on actual users or customer base.
• No evidence of revenue, pricing models beyond “token balance,” or payment processing details beyond the system architecture.

The author claims Consul aims to:

• Remove language barriers from paid consultations.
• Ensure clarity around expertise, logistics, and trust during calls.
• Provide a seamless experience for booking, speaking in different languages, and settling payments.

Evolution of claims:

• Initially positioned as a marketplace with live translation and token-based billing.
• Extended during Build Week to include an AI assistant with bounded authority and durable history.
• Emphasizes safety and trust through explicit product contracts around identity, payment, and irreversible actions.

Inferences:

• The platform evolved from a basic consultation tool into one that integrates AI assistance in a controlled way.
• The team prioritized reliability and auditability over ease-of-use or demo-style features.

Not evidenced:

• No evidence of market positioning beyond the author’s own description.
• No mention of competitors, pricing tiers, or strategic differentiation.

The description states that Consul targets:

• Clients who want to book consultations with specialists across borders.
• Experts who set their own prices and manage availability.
• Users who value clarity in trust, payment, and communication during live sessions.

Inferences:

• The platform caters to a global audience seeking expert advice or services.
• Both client and expert roles are supported through separate mobile experiences.
• Guest booking allows for low-friction entry into the system.

Not evidenced:

• No data on customer segments, personas, or usage patterns.
• No indication of whether clients or experts are individuals or organizations.
• No evidence of market size or target geography.

The description states that Consul:

• Enables experts to control their pricing.
• Uses a token-based payment system settled during live consultations.
• Reserves and settles payments through the platform as sessions run.

Inferences:

• The business model involves facilitating transactions between clients and experts.
• Payment settlement occurs in real time, likely using blockchain or tokenized ledger systems.
• There is no mention of platform fees or commissions.

Not evidenced:

• No evidence of revenue streams or pricing structures beyond “token-based billing.”
• No indication of how tokens are acquired, used, or converted.
• No information on monetization strategy beyond the platform’s own operations.

The description indicates that Consul uses:

• Next.js, React, and TypeScript for web product.
• SwiftUI for native iOS app.
• Go bounded-context services for marketplace, booking, billing, identity, and session workflows.
• Python/FastAPI LiveKit agents for real-time translation.
• PostgreSQL, Redis, Kafka, Kubernetes, and LiveKit for runtime support.

During Build Week:

• Used Codex with GPT-5.6 to investigate boundaries and implement assistant features.
• Implemented a server-owned Meet flow with durable journaling and short-lived connector actions.
• Ensured failure recovery and visibility in real-time sessions.

Inferences:

• The platform is built on modern, scalable tech stacks.
• AI integration is tightly controlled and auditable.
• Real-time session handling includes robust error management.

Not evidenced:

• No evidence of production deployment or scalability metrics.
• No information about performance benchmarks or uptime guarantees.
• No details on how the assistant interacts with external tools or APIs.

The description states that Consul:

• Was built over three months as a working product.
• Has a native iOS app in active development, not yet published.
• Includes guest booking and token-based settlement.
• Supports both client and expert mobile experiences.
• Features an assistant beta with bounded authority.

Inferences:

• The team has completed a full consultation loop from discovery to settlement.
• The platform is under active development but not yet live to users.
• The product shows early maturity in core functionality.

Not evidenced:

• No evidence of user adoption or retention.
• No data on number of specialists, clients, or sessions.
• No indication of monetization or revenue generation.
• No mention of any beta testing or pilot programs.

The description does not provide:

• Any information about existing competitors.
• No mention of similar platforms or market gaps.
• No evidence of competitive positioning or differentiation strategies.

Not evidenced:

• No reference to other consultation, marketplace, or translation tools.
• No indication of how Consul compares technically or commercially to alternatives.

Key risks identified from the description:

• The platform is described as a working prototype built in three months; no evidence of user traction or commercial viability.
• AI assistant functionality relies on bounded actions and short-lived authority — this may limit its utility unless further refined.
• Native iOS app is not yet published, suggesting incomplete product delivery.
• No mention of legal, compliance, or regulatory considerations for cross-border consultations.

Red flags:

• Lack of revenue or customer data makes it difficult to assess commercial viability.
• The focus on “token-based billing” without clarity on token mechanics raises questions about scalability and trust.
• No evidence of monetization beyond platform operation.

1. What is the current status of the native iOS app? Is there a timeline for App Store release?
2. How does Consul plan to scale its specialist supply and ensure quality control?
3. Can you explain how token-based billing works in practice, including conversion rates or mechanisms?
4. What are the key assumptions about user behavior that underpin this product design?
5. Are there any legal or compliance challenges related to cross-border consultations or AI assistance?
6. How does Consul intend to differentiate itself from existing platforms offering similar services?