Product Specification Document: Deckly

1. Executive Summary

Deckly is a high-performance, secure "Document Workspace for Founders" designed to replace static PDF sharing with interactive, trackable slide experiences. It provides real-time analytics, investor engagement signals, and organized data rooms to streamline the fundraising process and eliminate the "Doc Tax" for early-stage teams.

2. Product Vision & Goals

Vision: To be the default document workspace for founders, offering transparency and control over their most sensitive pitch materials.
Strategic Goals:
- High Fidelity: Ensure pitch decks look perfect on any device with slide-based viewing.
- Privacy-First: Provide granular access control (expiration, passwords, email gates).
- Actionable Insights: Deliver behavioral analytics that identify "Investor Interest Signals."
- Founder-Friendly: Simple, minimal, and premium UI with smooth transitions.

3. Target Audience

Startup Founders: Raising Pre-seed to Series A rounds.
Investors (VCs & Angels): Managing, tracking, and reviewing multiple incoming decks.
Real Estate Developers: Sharing secure project brochures and legal documents.
Sales & Business Development: Tracking proposal engagement and client interest.

4. Technology Stack

Frontend: React 18/19 + Vite (Heavy-Client SPA architecture).
Backend-as-a-Service: Supabase (PostgreSQL, Authentication, Real-time, Storage).
PDF Processing: pdfjs-dist for browser-side rendering of PDFs into high-resolution WebP slides (reduces server load and costs).
Styling: Vanilla CSS with a customized "Obsidian" Glassmorphic Design System.
State Management: TanStack Query for async caching and optimistic UI updates.
Analytics: Custom heartbeat-based tracking (45s intervals) + PostHog integration.

5. Functional Requirements

5.1. Deck Operations

PDF-to-Image Pipeline: Automatically convert PDFs to WebP images (1.5x scale) for web performance.
Silent Updates: Replace pitch decks while keeping the same shareable link — no versioning confusion for recipients.
Multi-Format Support: Support for PDF, PPTX, XLS, and more via client-side processing.

5.2. Custom Viewer Experience

Slide-based Navigation: Fluid transitions between slides with native-app feel.
Mobile Optimized: Responsive viewer with drawer-based navigation on small screens.

5.3. Data Rooms (Bundles)

Document Grouping: Bundle multiple decks into a single shareable "Data Room."
Custom Branding: Room-specific icons, names, and descriptions.
Access Gates: Unified email or password walls for the entire room.

5.4. Visitor Analytics (The "Insight" Engine)

Time-per-Slide: Track exactly how many seconds a viewer spends on each slide.
Drop-off Signal: Identify where most investors lose interest in the deck.
Investor Interest Signals:
- Revisited: Viewed on ≥ 2 distinct days.
- Deep Read: Spent ≥ 20s on ≥ 2 key slides.
- Returned Quickly: Second visit within 3 days.
- Extended Viewing: Total session duration > 60s.

5.5. Investor Interface

Inbox/Library: Save and organize incoming decks with tags.
Private Notes: Add investor-only notes that persist across views.
AI Integration: (Planned) Automated one-click pitch summaries for quick review.

5.6. Subscription Tiers & Limits

The application implements a tiered access model enforced at both the UI and data layer:

Tier	Max Data Rooms	Analytics Retention
FREE	1 Room	7 Days
PRO	5 Rooms	90 Days
PRO+	Unlimited	1 Year

6. Data Schema & Core Models

The system relies on a relational PostgreSQL schema with Row-Level Security:

decks: Stores document metadata, file URLs, and processed slide arrays.
data_rooms: Manages bundles of documents with unified access gates.
deck_page_views: The core analytics engine storing visitor_id, time_spent, and viewer_email.
investor_notes: Private, user-specific annotations linked to decks/slides.

7. Non-Functional Requirements

7.1. Security & Privacy

Row Level Security (RLS): Data isolation ensured at the database level using Supabase policies.
No Force-Email: Optional anonymous viewing to reduce friction for top-tier VCs.
Link Expiration: Automatic disabling of links after a set date/time.

7.2. Performance

Client-Side Compute: Offloading asset processing to the browser to ensure zero latency in the dashboard.
Optimistic UI: Instant feedback on saving notes or updating settings before server confirmation.

7.3. Design Standards

Premium Vibe: Focus on "Obsidian Depth" (#10120f) and subtle grid textures.
Typography: Standardized on sentence-case Outfit font for a human, professional feel.

8. Product Roadmap

Phase 1: Core Foundation (89% Complete)

[x] Social Auth & Basic Security.
[x] Insight Engine (Drop-off detection, updates).
[x] Investor Interest Signals.

Phase 2: SaaS & Scaling (40% Complete)

[ ] Stripe Subscription Integration.
[x] Tier-based usage limits (Free/Pro/Pro+).
[x] Support for non-PDF documents (Office suite, Video).

Phase 3: Investor Ecosystem (Developing)

[x] Private Note-taking and Library.
[ ] Ask Questions: Inline slide commenting for VCs.
[ ] Setup Meetings: Integrated scheduling (Calendly).

9. Success Metrics

Activation: Number of decks uploaded per user in the first 7 days.
Engagement: Total number of "Investor Signals" triggered (signaling value to founders).
Retention: Percentage of users who update a deck using the "Silent Update" feature.

Product Specification Document: Deckly ​

1. Executive Summary ​

2. Product Vision & Goals ​

3. Target Audience ​

4. Technology Stack ​

5. Functional Requirements ​

5.1. Deck Operations ​

5.2. Custom Viewer Experience ​

5.3. Data Rooms (Bundles) ​

5.4. Visitor Analytics (The "Insight" Engine) ​

5.5. Investor Interface ​

5.6. Subscription Tiers & Limits ​

6. Data Schema & Core Models ​

7. Non-Functional Requirements ​

7.1. Security & Privacy ​

7.2. Performance ​

7.3. Design Standards ​

8. Product Roadmap ​

Phase 1: Core Foundation (89% Complete) ​

Phase 2: SaaS & Scaling (40% Complete) ​

Phase 3: Investor Ecosystem (Developing) ​

9. Success Metrics ​