WorkLens

• The description states that WorkLens is a work intelligence platform that records employee activity during configured schedules.
• It tracks:
  • Application names and active time
  • Website domains
  • Work categories (development, research, communication, administration, personal browsing)
  • Activity duration
  • Team and organization coverage
  • Optional screenshots controlled by workspace policy
  • Desktop agent and browser extension status
• It does not collect keystrokes, passwords, form entries, page content, microphone audio, or webcam video.
• The system automatically classifies activity into work areas without requiring manual explanation from employees.
• At the end of a period (week/month), it generates reports showing:
  • Time recorded
  • Work area distribution
  • Team coverage
  • Activity timelines
  • Uncategorized activity
  • AI-assisted plain-language summaries

Inference The product appears to be a hybrid desktop/browser tool with backend reporting capabilities, intended for use in remote or hybrid work environments.

• The description states that WorkLens was built to address the problem of invasive monitoring tools, which focus on screenshots and keystrokes.
• It positions itself as a transparent work intelligence platform that helps teams understand work patterns while respecting employee privacy.
• The authors claim it offers:
  • A better way to understand how work happens
  • Employee visibility into what is being collected
  • Control over privacy settings (e.g., enabling/disabling privacy mode)
  • AI-generated summaries instead of raw data
• They emphasize that the system does not treat employees like machines being watched.
• The long-term goal is to become the trusted work intelligence layer for modern teams, helping organizations understand how work happens while preserving dignity and privacy.

Inference This is a positioning shift from traditional time-tracking tools toward a more privacy-conscious, AI-enhanced approach. However, no evidence exists that this has been validated in practice or adopted by users beyond the authors.

• The description states that WorkLens targets remote and hybrid teams.
• It is designed to help organizations understand work patterns without treating employees like machines being watched.
• The product includes features such as:
  • Role-based dashboards
  • Team and organization coverage metrics
  • Privacy controls visible to employees
  • Policy-driven collection rules

Inference The ICP likely includes small-to-medium-sized companies or teams that are transitioning to hybrid work models and want to monitor productivity without compromising employee trust.

• No pricing information, business model details, or monetization strategy are provided in the description.
• The product is described as a SaaS platform, but there is no mention of subscription tiers, per-user costs, or enterprise licensing models.
• There is no indication whether WorkLens intends to sell directly to customers or through partners.

Inference The business model remains undefined. It is unclear how the company plans to generate revenue from this product.

• WorkLens consists of:
  • A web application
  • A backend API
  • A native desktop agent (Electron-based)
  • A browser extension
• The backend uses:
  • REST API
  • Node.js, Express.js, Next.js
  • PostgreSQL with Prisma ORM
  • OpenAI integration (specifically GPT-5.6)
  • Codex for code inspection and debugging
• It supports:
  • Authentication
  • Session persistence
  • Role-based access control
  • Activity ingestion
  • Report generation
  • Privacy policies
  • Audit events
• The desktop agent handles:
  • Local configuration
  • Background activity collection
  • Connection status
  • Retry behavior
  • Communication with backend
• AI is used for generating report narratives, but with a deterministic fallback if the AI provider is unavailable.
• It includes offline and reconnection handling.

Inference The technical stack suggests a full-stack SaaS product built using modern web and cloud technologies. However, no evidence of production deployment or scalability beyond prototype status.

• Not evidenced.
• No mention of:
  • Customers
  • Revenue
  • User engagement
  • Product usage metrics
  • Beta testing or pilot programs
  • Any form of traction or adoption data

Inference There is no evidence that WorkLens has moved beyond the prototype stage or gained any real-world traction.

• The description does not reference competitors.
• It implies a gap in the market for less invasive monitoring tools compared to existing solutions that focus on screenshots, keystrokes, and constant surveillance.
• The authors state their goal is to offer a more transparent alternative, which suggests they perceive current offerings as lacking in privacy or employee trust.

Inference While the product addresses a known pain point (invasive monitoring), there is no evidence of competitive analysis or awareness of existing players in this space.

• The project is described as a hackathon submission, not a commercial product.
• No evidence of:
  • Revenue
  • Customers
  • Product-market fit
  • Scalability
  • Real-world testing
• The use of GPT-5.6 (which may not exist) raises questions about feasibility or accuracy of AI claims.
• The system relies heavily on AI for summarization, but includes a fallback mechanism, suggesting potential reliability issues.
• There is no indication of:
  • Legal compliance
  • Data governance
  • Employee consent processes
  • Integration with HR or payroll systems

Inference This appears to be an early-stage concept or prototype. The lack of traction, revenue, and customer feedback makes it difficult to assess viability as a commercial product.

1. What is the current status of WorkLens? Is it in production, beta, or still a prototype?
2. Have you conducted any user research or interviews with potential customers?
3. How do you plan to monetize this product? Are there any pricing models or revenue streams already defined?
4. What are your plans for scaling and supporting enterprise users?
5. Can you provide examples of how the AI-generated summaries have been validated in practice?
6. Have you considered legal or compliance implications around employee monitoring and data privacy?
7. How do you intend to differentiate from existing tools like RescueTime, Toggl, or Clockify?