PRODUCT CONCEPT DEMO

A unified portal for Dialectica’s expert network

This demo explains how a single expert-facing product could consolidate workflow visibility, compliance gating, scheduling, and payment clarity.

< 5 min
Target response time from opportunity to expert action
90 days
Profile freshness cadence before re-confirmation is required
100%
Compliance gate coverage enforced before scheduling
$450/hr
Sample rate visibility shown to experts upfront

Why this exists

Expert workflows are fragmented across email, documents, and manual coordination

Before

Opportunity outreach happens via email with no structured response tracking. Experts may miss invitations or lack context to respond quickly.

After

Opportunities appear in a unified workspace with full brief, compliance flags, and screening questions — enabling sub-5-minute response.

Before

Profile information decays silently. There is no systematic signal for when expertise data becomes stale or unreliable.

After

Profile freshness is tracked explicitly with recency signals, confidence scores, and re-confirmation prompts within a 90-day window.

Before

Scheduling requires manual back-and-forth over email, often delayed by timezone confusion and missing availability data.

After

Experts define availability rules with timezone and lead-time preferences. Scheduling is gated on compliance completion.

Before

Payment status is opaque to experts, generating support tickets and eroding trust after completed engagements.

After

Payment status is visible in the expert pipeline — pending, approved, and paid states reduce support friction to near zero.

Seven pillars

Seven operational surfaces in a single expert experience

Opportunity Clarity

Structured opportunity briefs with scope, rate, deadline, and compliance flags replace unstructured email outreach.

Profile Freshness

Recency signals, confidence scores, and re-confirmation workflows keep expertise data current and reliable.

Availability Control

Rule-based availability with timezone, lead-time, and blackout preferences replaces per-request scheduling negotiation.

Compliance Visibility

Attestation, conflict-of-interest checks, and MNPI flags are surfaced before scheduling — not discovered after.

Pipeline Transparency

Experts see where each engagement stands — from invitation through completion — without needing to ask.

Payment Clarity

Payment states — pending, approved, paid — are visible to experts, eliminating post-engagement support friction.

Ops Control Layer

Internal teams retain override capability, audit trails, and governance controls. Self-service does not mean uncontrolled.

Expert journey

A clear path from opportunity to payment

Opportunity Screening Compliance Scheduling Consultation Payment

Opportunity → Screening

Expert receives a structured brief with scope, rate, and compliance flags. Screening questions capture fit and availability before proceeding.

Compliance → Scheduling

Attestation, conflict-of-interest checks, and MNPI declarations must be completed before the expert can be scheduled. This gate is enforced, not advisory.

Consultation → Payment

After the consultation is completed, payment transitions through pending, approved, and paid states — all visible to the expert in their pipeline view.

Design decisions

Why the product is structured this way

Compliance before scheduling. Attestation and conflict-of-interest checks are enforced gates, not optional steps. An expert cannot be scheduled until compliance is cleared — this prevents downstream risk and manual remediation.

Profile freshness is explicit. Rather than assuming profile data remains valid indefinitely, the system tracks recency signals with confidence scores and prompts re-confirmation within a 90-day window.

Payment visibility reduces friction. Experts see payment status (pending, approved, paid) to reduce post-engagement support tickets. Transparency builds trust without exposing internal financial operations.

Availability as rules, not dates. Experts define recurring windows with timezone and lead-time preferences rather than picking individual slots. This reduces coordination overhead while keeping a conservative v1 boundary.

Demo scope

What is implemented, mocked, and future-state

Implemented
  • Seeded illustrative data across all surfaces
  • Static HTML + CSS surfaces with no build system
  • Compliance gates enforced before scheduling
  • Profile freshness and recency signals
  • Ops command center with override controls
Mocked
  • WorkOS SSO authentication flow
  • Persona identity verification
  • Payment provider integration
  • Form submissions and data persistence
  • Audit trail event generation
Future
  • Calendar sync (Google, Outlook)
  • Real-time notification system
  • Live data updates and WebSocket events
  • AI-assisted expert matching
  • Multi-language support
i

This is a product concept demo. All data is illustrative and seeded. No real expert information is stored or transmitted. Form submissions and button interactions are non-functional by design.