Skip to content
Vinod KumarFull stack · AI engineer
  • Home
  • Projects
  • About
  • Contact
  • Résumé
Résumé
Vinod Kumar

Full Stack Developer | AI Application Engineer

vinodvinni308@gmail.com

Navigate

  • Home
  • Projects
  • About
  • Contact
  • Résumé (PDF)

Elsewhere

  • GitHub (opens in a new tab)
  • LinkedIn (opens in a new tab)

© 2026 Vinod Kumar · Noida, India

  1. Projects
  2. Haylow.ai

Case study · AI Search Visibility Platform

Haylow.ai

Haylow.ai is an AI search visibility platform. It measures how brands appear in AI-generated answers: mentions, sentiment, citations and competitor visibility.

  • React.js
  • Node.js
  • Express.js
  • PostgreSQL
  • AI APIs
Visit haylow.ai (opens in a new tab)
Brand visibilityRun #18 · compared to last run
Visibility score68Sentiment: positive
Model A
Model B
Model C
Model D
Top cited sources
Illustrative mock-up, not product data
  1. Problem & context
  2. My role
  3. Implementation
  4. Workflow
  5. Decisions
  6. Technologies

01

Problem & context

People increasingly ask AI assistants for recommendations. Brands need to know whether they are mentioned, how they are described and which sources the answers cite.

02

My role and contribution

My work

  • Built the integrations with 4 AI providers.
  • Built the backend workflows for response processing and persistent data management that feed visibility analytics and competitor reporting.

Scope

Haylow.ai was built by a team. The parts of the product beyond the provider integrations and these backend workflows were not my work.

03

Technical implementation

  • Provider integrations

    Integrations with 4 AI providers, run from the Node.js/Express.js backend.

  • Response processing

    Backend workflows that process provider responses into structured data.

  • Persistence

    PostgreSQL storage that analytics and competitor reporting read from.

04

Workflow

From query to visibility report
  1. Brand queriesinput
  2. 4 AI providersintegrations
  3. Response processingbackend
  4. PostgreSQLpersisted
  5. Visibility analyticsreporting

Simplified illustration of the flow, not the production schema or architecture.

05

Engineering decisions

  • Providers stay behind the backend

    Provider calls run server-side, so API keys, prompts and failure handling never reach the browser.

  • One pipeline for every provider

    Each provider integration feeds the same processing and storage workflow, so results can be compared across providers and over time.

06

Technologies used

  • React.js
  • Node.js
  • Express.js
  • PostgreSQL
  • AI APIs

The interface shown above is an original mock-up with placeholder data, not a product screenshot.

PreviousMoneyGenceFinancial Management SaaSNextOnGrid.workTeam Operations SaaS
All projectsDiscuss a project