monospace.studio
← Back to Product Labs

Active product · 2026

NVSBL suite

A suite for discovering product opportunities through autonomous agents, then turning the signal into an API, subscription, and delivery product.

NVSBL is the most complete product thread in the current set: an invisible agent engine finds product opportunities, a public/API surface presents approved signal, and an authenticated app layer turns that signal into subscriptions, API keys, usage, and delivery workflows.

What problem does this solve?

Product opportunities are everywhere, but teams usually find them manually, inconsistently, and too late. NVSBL asks whether autonomous agents can keep scanning for unmet needs and turn the best signal into reviewable product opportunities.

Visual evidence

NVSBL public home page — request access, invisible-platform framing, agent-led product discovery.
Public surface: invisible-platform framing and request-access CTA.
NVSBL suite overview — the three repos (engine, web, app) and what each layer owns.
Suite overview: engine, public website + API, and authenticated app.
NVSBL authenticated dashboard — API keys, usage, subscriptions, Linear delivery, pipelines.
Authenticated app: API keys, usage, billing, and Linear delivery.
NVSBL raw signal pipeline — the agent runtime that scans, scores, and labels opportunities.
Signal pipeline: HN Scout scanning, scoring, and labelling.
NVSBL discovery framing through the Double Diamond — divergence and convergence on opportunities.
Discovery framing through the Double Diamond.
NVSBL product cut — the slice chosen as the buyer-facing path from signal to delivery.
Product cut: the buyer path from signal to delivery.
NVSBL onboarding setup screen for new customers.
Customer onboarding setup.

What it can do

  • Run HN Scout on a schedule to scan Hacker News for complaints, workarounds, and unmet needs.
  • Publish validated opportunities as labelled GitHub Issues before they are packaged for customers.
  • Serve approved opportunities through authenticated API endpoints with API-key validation.
  • Persist API keys, usage logs, subscriptions, customers, and billing events in Supabase.
  • Create Stripe checkout sessions and sync subscription state through signed webhook events.
  • Prepare Linear delivery so customer-qualified opportunities can become issues in the buyer's workspace.
  • Keep the public website, authenticated dashboard, and invisible signal engine as separate surfaces with different evidence boundaries.

Activity signals

  • The private/local `nvsbl` engine repo defines a UI-less platform where agents discover opportunities and surface results through existing channels.
  • Agent 01, HN Scout, is documented as live: weekly Hacker News scanning, LLM analysis, 284 posts scanned, and 30 labelled opportunity issues surfaced in the first successful runs.
  • `nvsbl-web` carries the public surface, including live opportunity feed, request-access CTA, authenticated opportunity API, Stripe checkout, webhook ingestion, and Supabase subscription persistence.
  • `nvsbl-app` carries the fuller authenticated product layer: dashboard, API keys, usage, settings, pricing, billing, Linear integration, pipelines, sources, roadmap, status, and docs-drawer planning.
  • The monetisation roadmap moved from concept into schema and implementation work: API keys, usage logs, subscription tables, Stripe billing primitives, and Linear delivery migrations now exist across the suite.

Suite shape

Private/local engine

nvsbl

Private signal engine and agent runtime

Local active repo

nvsbl-web

Public website, approved opportunity feed, API surface, and first billing layer

Private/local app

nvsbl-app

Authenticated dashboard for API keys, usage, billing, Linear, pipelines, and settings

Why it matters

  • Shows a real product suite rather than a single repo experiment.
  • Connects agentic research, product discovery, public packaging, billing, customer entitlements, Linear delivery, and authenticated app UX.
  • Makes the invisible-platform thesis tangible: useful work happens behind the scenes and surfaces where people already work.
  • Provides a strong hero for Product Labs because it combines product strategy, AI agents, systems design, and implementation.
  • Demonstrates commercial product thinking without pretending the public/private boundary is fully launch-ready.

Recent commits

DateHashChange
2026-05-126a655e2nvsbl: add api_keys, usage_logs, and subscriptions tables for API monetization
2026-05-12dde4a45nvsbl-web: remove offset from API routes, update signin, and add social auth spec
2026-05-12584f3b9nvsbl-app: add product layer for API, billing, and Linear integration
2026-05-12b0907b9nvsbl-app: clarify key injection flow in the docs-drawer plan

Next move

Tighten one buyer path end-to-end: from a signal HN Scout surfaces, to an approved opportunity on the public API, to a subscriber consuming it through an API key, to a Linear issue landing in their workspace. Everything else is supporting evidence around that single loop.