Four areas of focus.

Where I focus

Product design is the core. Each area below strengthens the others, from first framing to final handoff.

01 — Product & UX/UI Design

Make complex things feel clear.

Information architecture, user flows and interaction design for dense, multi-role B2B products. Turns complicated workflows into screens people can actually use.

Product designInformation architectureInteraction design

02 — AI-native Experience

Design for what AI changes.

Interfaces where people review, direct and correct AI output, with the right balance of trust and control. Moves my practice from designing with AI to designing for it.

AI UXHuman in the loopReview states

03 — Systems & Craft

Consistency that scales.

Design systems, high-fidelity UI and clean handoff, so products stay coherent as they grow. Keeps the details sharp across every screen and release.

Design systemsHigh-fidelity UIHandoff

04 — Research & Strategy

Frame it before you build it.

Problem framing, discovery and validation that define what is worth building first. Gives every design decision something solid to stand on.

UX researchProduct strategyValidation

One designer. Four focus areas. Connected thinking.

About

Nothing meaningful
begins fully formed.

I started in code and followed the harder problems: insurance workflows, systems at scale, and now AI. Three years of designing rule-heavy, multi-role products across web and mobile.

UI/UX Designer

Injala Private Limited B2B SaaS

Jul 2023 – Jul 2026

Led end-to-end product design across complex insurance, SaaS and AI products, from discovery and workflow analysis through information architecture, interaction design, prototyping, high-fidelity UI and production.

B.Tech, Computer Science & Engineering

Amity University, Ranchi

2018 – 2022

I began by learning how software is built, before I started designing it.

Design & prototyping

Figma
FigJam
Figma Make
Framer
Spline
Lottie

Research & testing

Maze
Hotjar
UserTesting

Delivery

Jira
Notion
GitHub

Selected work

Ideas, made tangible.

Four different challenges. One consistent way of thinking.

01 04

Kinetic

B2B SaaS
Product design
Insurance

A policy management system designed to help brokers, carriers, and insurers coordinate project enrollment and complex approval workflows.

Context: Brokers, carriers and insurers needed one system to move projects, policies, documents and approvals forward.
Contribution: Product design across core workflows and modules: information architecture, user flows, interaction design and high-fidelity screens, with product and engineering.

View case study

Kinetic WTW Compass dashboard with AI bulk upload result

Kinetic project listing and AI-generated project records

02 04

Learning Management System

EdTech
Product design
Learning systems

A connected university platform bringing program and department administration, faculty scheduling, and community support into one learning management experience.

Context: Administrators, university teams, faculty and students each needed a clear path through one connected learning platform.
Contribution: The ecosystem structure and role-specific workspaces for Super Admin, University and Faculty, plus AI-enabled learning capabilities.

View case study

Learning Management System community and support interface

Learning Management System faculty timetable and meeting management interface

03 04

AI for Insurance

AI workflows
Insurance
Product design

AI-assisted insurance workflows for reviewing coverage, comparing policy documents, and surfacing critical information with greater clarity.

Context: Insurance decisions start with documents. The challenge was making them usable without taking human judgment out.
Contribution: Product framing, information architecture, workflow definition, AI-assisted review states and interface design for the concept.

View case study

AI for Insurance personal risk advisor dashboard

AI for Insurance policy versus policy comparison results

04 04

Asuretify

Web design
UX strategy
Digital experience

A focused website experience that makes the offering easier to understand and gives visitors a direct path to take the next step.

Context: The broker-facing experience needed a clearer link between what the product offers, how information is organised and what to do next.
Contribution: Reviewed the existing experience, identified UX friction, restructured the information architecture and redesigned the web and onboarding journey.

View case study

Asuretify homepage and product experience

Asuretify integrations, metrics, and trusted clients

01 / 04

How I work

How ideas evolve.

Six stages take a product from the first question to something that keeps improving, each one building on the last.

Discover & Frame · 01 / 06

Start with the real problem.

Understand the people, the context and what is actually going wrong before opening a design file.

Stakeholder and user conversations
Competitor and market scan
Problem framing
Success criteria
MVP scoping

Example tools Notion · Maze · Hotjar · UserTesting

Structure & Flow · 02 / 06

Make the system legible.

Map roles, journeys and information so the product makes sense before it looks good.

Information architecture
User flows and journeys
Role and permission mapping
Content hierarchy
Low-fidelity wireframes

Example tools Figma · FigJam

Design & Prototype · 03 / 06

Turn structure into something tangible.

Shape interfaces and interactions, and test ideas with prototypes people can click.

Interaction design
High-fidelity UI
Interactive prototypes
AI states and edge cases
Design systems

Example tools Figma · Figma Make · Framer · Spline · Lottie

Test & Refine · 04 / 06

Check it against real behaviour.

Put the design in front of people and tighten whatever does not hold up.

Usability testing
Heuristic review
A/B comparisons
Feedback synthesis
Iteration

Example tools Maze · Hotjar · UserTesting

Hand off & Ship · 05 / 06

Close the gap between design and build.

Work with product and engineering so what ships matches what was intended.

Specs and documentation
Component libraries
Developer collaboration
Design QA
Release support

Example tools Figma · Jira · GitHub

Measure & Evolve · 06 / 06

Launch is not the finish line.

Learn from real usage and keep improving what comes next.

Usage analytics
Behaviour analysis
Retention insights
Experimentation
Product iteration

Example tools Hotjar · Maze · UserTesting · Jira

Frame the problem. Shape the system. Design the experience. Test it. Ship it. Keep evolving.

Frequently Asked Questions

Everything you might want to know before getting in touch.

I’m a product designer focused on B2B SaaS and AI-native products. My work spans insurtech platforms, EdTech systems and AI-assisted workflows, covering research, information architecture, interaction design and design systems.

Yes. I’m open to product design roles on AI-native and B2B products, and to selected projects with early-stage teams. If you’re not sure which fits, send a note and we can work it out.

I use AI tools to move faster through research synthesis, exploration and prototyping. I also design for AI: shaping how people review, direct and correct what these systems produce, with human judgment kept in the loop.

Email me, or message me on WhatsApp or LinkedIn, with a short note on what you’re building or what’s stuck. You don’t need a detailed brief.

Closely and early. I join discovery, define flows with product, and stay involved through handoff and design QA so that what ships matches what was designed.

The case studies above cover context, process and outcomes for each project. More long-form work is on Behance, linked in the footer.

Didn’t find your question? Get in touch and I’ll take it from there.

← Back to selected work

Product design · B2B SaaS · Insurtech

Kinetic
Policy management.

Insurance work, untangled. One system for brokers, carriers, and insurers.

Enterprise workflowsPolicy managementHuman + AI

Have a problem like this? Let’s talk

Kinetic dashboard showing project management and AI-assisted bulk upload

Kinetic · Product interface01 / Platform evolution

283 → 4,500+Project enrollments reported across 18 months

3Core stakeholder groups: brokers, carriers, insurers

End-to-endProject, policy, document and approval workflows

Chapter 01Context

01 / CONTEXT

One product. Different responsibilities. Shared outcomes.

Kinetic supported insurance project and policy operations across multiple organizations.

Brokers needed to coordinate project information and move submissions forward. Carriers needed consistent information and clear decision points. Insurers needed visibility, governance, and confidence that the right steps had been completed.

02 / CHALLENGE

Complexity was distributed across the workflow.

The product had to bring structure to operational complexity without flattening the real differences between roles, approval stages, and insurance requirements.

01 / CONTEXT

Fragmented information

Project details, policy information, documents, and communication needed to be easier to find in the context of the work.

02 / COORDINATION

Multi-party decisions

Broker, carrier, and insurer responsibilities overlapped, but each role needed clear ownership and next steps.

03 / SCALE

More projects, more states

As enrollment grew, list views, status indicators, bulk actions, and reusable patterns had to remain legible at scale.

Chapter 02Craft

03 / EVOLUTION

Designing for the insurance lifecycle, not isolated screens.

The work evolved around the decision sequence that users actually moved through.

Stage 01

Before Quoting

Collect and structure project details, understand the submission, and prepare the information needed to evaluate risk and move toward a quote.

Stage 02

Before Binding

Review quote details and outstanding requirements, coordinate approvals, and make the transition from quote to bind explicit.

Stage 03

After Binding

Keep policy information, documents, and follow-up activity connected after binding so the record remains useful beyond the decision point.

Kinetic project listing interface showing records and AI-generated project data

Project listing · Record visibilityIllustrative product screen

04 / SYSTEMS

Make the next action easier to see.

The product experience was built from connected capabilities: project tracking, detailed policy records, supporting documents, communication, and approvals.

01 · Project operations

From record keeping to project visibility.

Project lists and record details helped users orient themselves in a growing portfolio of work.

Project listing and status visibility
AI-assisted bulk upload for handling project data

02 · Policy detail

Keep the decision and its evidence together.

Policy detail brought key information into a single working context, including coverage status, timeline, and documents.

Visible policy state and key attributes
Timeline and supporting documents in context

Kinetic policy detail screen with coverage status, timeline, and documents

03 · Connected workflow

Support coordination across roles.

Documents, messenger, feeds, notes, and approval checkpoints formed part of the broader operational system.

Documents associated with project and policy context
Communication and activity connected to the work

Kinetic dashboard and project workflow interface

05 / ROLE DESIGN

A shared platform, with role-aware workflows.

The experience needed consistency without pretending every user had the same goal.

Broker

Coordinate project submissions, track progress, and keep information moving between parties.

Carrier

Review project information, work through underwriting requirements, and respond at the right decision stage.

Insurer

Maintain visibility over policy decisions, documentation, and governance requirements.

Super admin

Support platform-level review and oversight through configuration and review-oriented workflows.

Chapter 03Outcome

06 / IMPACT

Growth changed the design problem.

The product had to keep working as the number of live projects and the breadth of workflows increased.

283 →
4,500+

Project enrollments over 18 months · reported product outcome

Kinetic scaled from hundreds to 4,500+ live enrollments, and the experience and its reusable patterns had to scale with it. A product-level outcome, not a claim that design alone drove the growth.

Additional reported context: the platform served organizations including WTW, Lockton, USI, Keenan, and NSI across the USA and France.

07 / MY CONTRIBUTION

Translate business rules into usable systems.

My work covered product design across core workflows and modules, partnering with product and engineering to bring complex requirements into production-ready experiences.

Product and UX: information architecture, user flows, interaction design, high-fidelity screens, and iteration across project/policy management, approvals, documents, and messaging.

Cross-functional delivery: worked with product, engineering, QA, and enterprise stakeholders to clarify requirements, review implementation, and evolve the experience through releases.

Ideas don’t just exist. They evolve.

Got a messy problem?
Let’s make it obvious.

Tell me what’s stuck.

Get in touch ↗Back to selected work ←

← Back to selected work

Product design · EdTech · AI-assisted learning

Learning
ecosystem.

Four roles. One learning loop. Content, teaching and feedback finally connected.

Multi-role platformLearning operationsAI-enabled tools

Have a problem like this? Let’s talk

Learning Management System · Product interface01 / Learning ecosystem

4 role areasSuper Admin, University, Faculty, Student

ConnectedContent, video, assessment, and analytics

AI-assistedContent generation and remedial suggestions

Chapter 01Context

01 / CONTEXT

Learning is a system of people, content, and feedback.

The LMS concept brought together institutional operations and day-to-day learning tasks.

Administrators need oversight, configuration, and reporting. University teams coordinate courses and faculty. Faculty prepare content, teach, assess, and respond to student needs. Students need a clear path through learning materials, assignments, and feedback.

02 / CHALLENGE

Different roles. One learning journey.

The platform needed to balance institutional control with practical teaching and learning workflows.

01 / ROLE CLARITY

Relevant by default

Present the right tools and information for each role, while keeping navigation and interaction patterns familiar.

02 / CONTENT FLOW

From material to learning

Connect course content, video resources, lesson structure, and assessments rather than scattering them across separate tasks.

03 / FEEDBACK LOOP

Make progress actionable

Use assessment and student-monitoring signals to help faculty identify where additional support may be needed.

Chapter 02System

03 / ARCHITECTURE

Separate responsibilities. Connect the information.

The information architecture was organized around four role areas, each with a distinct job within the wider learning ecosystem.

Role 01 · Super Admin

Platform-level configuration, access, oversight, and system administration.

Role 02 · University

Institutional management of courses, faculty, academic structures, and reporting.

Role 03 · Faculty

Content preparation, course delivery, assessment, and student progress monitoring.

Role 04 · Student

Access learning materials, complete assessments, and use feedback to guide next steps.

System principle

Shared patterns. Role-specific priorities.

Consistent navigation, content structures, and task patterns help the platform feel unified.

Role-based information architecture and permissions
Consistent content and course structures

04 / CAPABILITIES

Build a loop from content to feedback.

The product scope connected core LMS functions with AI-assisted capabilities that help faculty prepare material and interpret learning needs.

01 · AI Content Pack Generator

Turn source material into structured learning assets.

A faculty-facing workflow for creating content packs from learning inputs, with generated material kept editable and reviewable before it becomes part of a course.

Organize generated assets around course and lesson context
Keep faculty in control of review and refinement

02 · Video Intelligence

Make recorded learning easier to navigate.

Part of the wider content ecosystem, with the opportunity to organize video into more useful learning units such as chapters, key concepts, and summaries.

Structure long-form video into navigable pieces
Connect video insights to course content

03 · Assessment & remedial suggestions

Connect evaluation to a useful next step.

Assessments and student monitoring can reveal where a learner may need support.

Connect assessment outcomes to visible learning signals
Suggest targeted follow-up material or practice

Community & support · Shared patternsProduct screen

Chapter 03Outcome

05 / DESIGN OUTCOME

A connected structure for academic work.

The core design outcome was a role-based LMS ecosystem that links administration, teaching, learning content, assessment, and student support.

4 → 1

Role areas · one connected learning ecosystem

No adoption or grade metrics are claimed; validated figures weren’t provided. The outcome is structure and capability, not invented uplift.

06 / MY CONTRIBUTION

Design the structure, then the capabilities.

My design scope covered the ecosystem structure and its role-specific workspaces, including Super Admin, University, Faculty, and AI-enabled learning capabilities.

The architecture established a way to connect content creation, video intelligence, assessments, analytics, reporting, and student monitoring within a coherent product model.

Ideas don’t just exist. They evolve.

Got a messy problem?
Let’s make it obvious.

Tell me what’s stuck.

Get in touch ↗Back to selected work ←

← Back to selected work

Product design · AI · Insurtech

AI for
Insurance.

Insurance runs on documents. I made them usable, with people still in charge.

0 → 1 productDocument intelligenceHuman in the loop

Have a problem like this? Let’s talk

AI for Insurance · Product interface01 / Human + AI

0 → 1Product concept to designed experience

Document-ledInsurance information and risk extraction

Human-ledReview, exceptions, and final judgment

Chapter 01Context

01 / CONTEXT

Insurance decisions start with documents. The hard part is making them usable.

Insurance teams work with complex policy language, risk details, coverage information, and exceptions.

The design opportunity was not to add a chat interface to insurance. It was to create a workflow where users could provide source documents, inspect extracted information, understand risk signals, and decide what required attention.

02 / CHALLENGE

Automate the repetitive work. Keep the judgment visible.

The core UX challenge was trust.

01 / INPUT

Dense source material

Policy documents contain varied structures and terminology.

02 / INTERPRETATION

Uncertain outputs

AI-generated fields and risk signals need context, validation, and visible uncertainty rather than unexplained certainty.

03 / DECISION

Human accountability

Underwriters and insurance professionals must be able to correct, override, or escalate results before acting on them.

Chapter 02Trust

03 / WORKFLOW

Make AI legible at every step.

The designed experience follows a reviewable sequence instead of collapsing the process into a single answer.

Step 01

Provide

Upload policy or submission documents and establish the source material for analysis.

Step 02

Extract

Organize relevant policy details and risk information into structured fields.

Step 03

Review

Inspect extracted values, evidence, confidence cues, and exceptions before accepting them.

Step 04

Decide

Correct, override, or escalate findings, keeping the professional in control of the outcome.

Policy comparison · Review stateProduct screen

Interaction principle

AI suggests. People validate.

The experience was framed around a human-in-the-loop model.

Visible extraction and review states
Confidence and exception cues where appropriate

04 / PRINCIPLES

Trust is an interaction pattern, not a badge.

For consequential workflows, trust comes from understandable behavior, transparent limits, and the ability to intervene.

01 / EXPLAIN

Show the basis

Connect extracted details and risk flags to the relevant source context whenever possible.

02 / QUALIFY

Represent uncertainty

Distinguish a strong extraction from a field that needs review or additional information.

03 / EMPOWER

Preserve agency

Let users edit, reject, or escalate AI output rather than forcing acceptance.

Chapter 03Outcome

05 / OUTCOME

Designed from 0 → 1.

The work defined the product structure and the key interaction model for document-driven insurance intelligence.

0 → 1

Product concept to designed experience

A designed concept and workflow. No unverified accuracy, time-saved, or conversion metrics are claimed.

06 / MY CONTRIBUTION

From a blank canvas to a coherent AI product experience.

My contribution included product framing, information architecture, workflow definition, AI-assisted review states, and interface design for the document-driven underwriting concept.

The key design outcome was a connected model for upload, extraction, review, and human decision-making—rather than treating AI as an isolated feature.

Ideas don’t just exist. They evolve.

Got a messy problem?
Let’s make it obvious.

Tell me what’s stuck.

Get in touch ↗Back to selected work ←

← Back to selected work

Web experience · Broker portal · UX

Asure
tify.

A clearer offer. One obvious next step.

Information architectureOnboardingUX research

Have a problem like this? Let’s talk

Asuretify · Web experience01 / Clarity to activation

DiscoveryUnderstand the experience and user needs

StructureRework information architecture and flow

ActivationMake the next step easier to understand

Chapter 01Context

01 / CONTEXT

A broker experience should make value and next steps obvious.

Asuretify’s broker-facing web experience needed a clearer relationship between what the product offers, how information is organized, and what a broker should do next.

The redesign focused on the web experience and onboarding journey, with attention to information architecture, content hierarchy, and the path from first understanding the product to getting started.

02 / CHALLENGE

When structure is unclear, every next step feels harder.

The work was framed around three connected UX concerns: understanding, navigation, and onboarding progression.

01 / UNDERSTANDING

Explain the value

Make the product’s purpose and relevance easier to understand without requiring users to piece together the story.

02 / NAVIGATION

Organize information

Group content and capabilities around user questions and tasks rather than internal assumptions.

03 / PROGRESSION

Guide onboarding

Make the journey from discovery to activation more coherent, with clearer transitions and expectations.

Chapter 02Path

03 / APPROACH

Start with friction. Rebuild the path.

The design process used qualitative and behavioral signals to identify where the experience was difficult to understand or navigate, then translated those findings into a more deliberate structure.

Step 01

Inspect

Review the existing experience and map key pages, content, and onboarding transitions.

Step 02

Understand

Use interviews and UX research to understand user expectations and sources of friction.

Step 03

Restructure

Rework information architecture, page hierarchy, and the order in which decisions appear.

Step 04

Validate

Use tools such as Hotjar and Maze to investigate behavior and test whether the revised flow is clearer.

01 · Information architecture

Make the story easier to follow.

Page structure and hierarchy should help users orient themselves quickly: what the product does, which information matters to them, and where to go next. The redesign focused on reducing ambiguity between discovery content and task-oriented areas.

Clearer content grouping and hierarchy
More direct paths to relevant information
Consistent transitions between pages and tasks

02 · Onboarding

Turn intent into a guided next step.

Onboarding was considered part of the product experience, not a disconnected form. The design direction emphasized understandable steps, useful context, and clearer expectations about what comes next.

Review the sequence from discovery to onboarding
Make progress and required actions easier to understand
Use research and behavior signals to locate friction

Chapter 03Outcome

04 / OUTCOME

A clearer foundation for discovery and activation.

The design outcome was a restructured web experience and onboarding journey, informed by research and behavior analysis.

Discover →
Activate

What changed · From isolated pages to a more connected journey

Information architecture, content hierarchy, and onboarding were considered as parts of the same user experience.

This case study describes the design scope and intended UX outcomes. Numerical uplift is not claimed because a verified before-and-after metric has not been provided.

05 / MY CONTRIBUTION

Review, restructure, redesign.

My contribution included reviewing the existing experience, identifying UX friction, restructuring information architecture, and redesigning the broker-facing web and onboarding experience.

Interviews, Hotjar, and Maze formed part of the research and validation toolkit. The goal was to improve clarity and progression.

Ideas don’t just exist. They evolve.

Got a messy problem?
Let’s make it obvious.

Tell me what’s stuck.

Get in touch ↗Back to selected work ←

Ideas don’t just exist.They evolve.

Make complex things feel clear.

Design for what AI changes.

Consistency that scales.

Frame it before you build it.

Nothing meaningful begins fully formed.

UI/UX Designer

B.Tech, Computer Science & Engineering

Ideas, made tangible.

Kinetic

Learning Management System

AI for Insurance

Asuretify

Start with the real problem.

Make the system legible.

Turn structure into something tangible.

Check it against real behaviour.

Close the gap between design and build.

Launch is not the finish line.

What kind of work do you do?

Are you open to new opportunities?

How do you use AI in your work?

How can I get in touch?

How do you work with product and engineering teams?

Where can I see more of your work?

Ideas don’t just exist.
They evolve.

Nothing meaningful
begins fully formed.