Biswarup Mondal
Bengaluru
Senior Product Designer @ 4flow (opens in a new tab)

Designing AI-native, agentic experiences

Cross-domain multi-agent frameworks, agentic analytics, and explainable human-in-the-loop systems — turning complex, regulated data into products a person can actually decide from. Held together by design systems I build and document, alongside PM and engineering.

Experience
5+ years, 0→1
Domains
AI · Fintech · Logistics
KYC & onboarding
95% faster
Agent memory
Multi-domain context
Aside

A low-key dream of mine: to join — and one day nurture — a team that cares this deeply about craft, quality, and building great tools.

Selected work

Currently · Side project

A foundry for a team's own icons. A designer draws or describes an icon; the foundry sketches it on the 24 grid, turns the sketch into a house-style icon made of named parts, checks it against the house rules, and ships it: to Figma with its layers, and to code as packages and URLs.

Fig · One pallet, from five strokes to an icon. Replayed from a real session on the Canvas, not a mock-up. Recorded at commit 4491759.

a real session, replayed: every stroke, layer name and reply is what the app did with this pallet.

the sketch stays under the icon, like tracing paper. name the layers and the parts keep the names, into Figma.

/icon and /check cost no tokens. code builds the icon; the model only proposes, plans and judges.

  • 1,855 icons
  • 9 house rules
  • release 0.1.1
  • React · Vue · Angular · SVG · sprite
  • MCP server

Build log

  1. Still not true

    Seven logistics icons by hand

    Cross-dock, pallet, driver, milk run, supply network, emissions and shared load still need a designer on the Canvas.

    Next
  2. Phase 5 · Anywhere

    The foundry from any agent

    An MCP server over the same operations (search, make, compose, check, export for Figma, save), so Claude or Cursor can ask for an icon and find it in the library.

    Shipped
  3. Phase 4 · Agents

    Agents that propose, never draw

    A Librarian names the concept or finds the icon that already is it; a sketch is drawn several times and a Judge keeps the one that reads; one message can run sketch, make, check and judge.

    Shipped
  4. Phase 3 · Code

    Into code as packages and URLs

    One build makes the packages (core, React, Vue, Angular), a sprite and a gallery of URLs: 1,855 icons, 3,739 files. Released as 0.1.0, then 0.1.1.

    Shipped
  5. Phase 2 · Figma

    Out to Figma with its layers

    Copy for Figma gives one named group per part. Checked in Figma: the truck arrived as body, cab and wheels.

    Shipped

Playground

Smaller things built to answer a question rather than to ship — a plugin, a demo, a tool, each shown doing the thing it does.

Everything in the playground

still here??

Things I love doing

  • Drawing the thing before arguing about it
  • Naming things until the name does the explaining
  • Reading the logs with the engineers
  • Sitting in on support calls
  • Building the tool instead of filing the ticket
  • Throwing away the first three versions
  • Teaching someone the shortcut I just found