Skip to main content
Noah DolinkoAll projects

Project outline · In development

Pulse Tracker

A research tool for following selected topics and getting useful summaries without trying to consume every source.

Visit Pulse Tracker ↗
Initial audience
Builders and founders tracking fast-moving topics
My role
Product concept, direction, and implementation
Stage
In development
Pulse Tracker development interface with topic filters, source selectors, and an empty intelligence view
Development interface before data ingestion is complete.Open full-size screenshot
Proposed research flow
  1. Choose topicsFocus on the areas worth following.
  2. Gather sourcesBring relevant updates into one workflow.
  3. Review a digestRead the main points and trace them back to sources.

The problem I want to solve

Keeping up with AI, startups, small business, markets, and other fast-moving areas can mean spending hours reading, watching, and scrolling. I wanted a way to focus on a set of topics, gather relevant material, and make the important parts easier to review.

Pulse Tracker is an exploration of that idea, including how concise research summaries might support a person's own work and agent workflows.

Who it may help

The initial direction is for builders and founders who need to track changes in areas such as AI, startups, and small business. Market monitoring is another possible use case, but the product is not positioned as financial advice or a trading signal service.

Current direction

The interface includes topic filters, source selectors, and an archive-search view. Data ingestion is not finished, so the product does not yet deliver a dependable stream of populated insights or recurring summaries. The next meaningful milestone is getting relevant source material into that interface and making the resulting summaries easy to check against their sources.

What I am building with

The current project notes include JavaScript, Neon, and social APIs. The technical architecture and integrations are still evolving, so this list should not be treated as a final production stack.

The question this build needs to answer

Can a focused digest help someone spot relevant changes while still making it easy to check the original source? The interface establishes the direction; ingestion and useful, source-checkable summaries still need to be completed and tested.