Krushna Palwe

Open to senior roles & select freelance

Let’s talkHelp & contact

KRUSHNA PALWE

Website guide

Automated help, with a human next step.

A GOOD PLACE TO START

A little clarity.
Your next move.

Find the right service, explore the work, or plan your next project.

Or ask about

Answers from this website. Quotes come from Krushna.

Information design / B2B SaaS

Make the complex
easy to follow.

I’m Krushna Palwe, a senior visual designer in Pune, India. I design architecture diagrams, product flows and explainer visuals for B2B SaaS teams, with remote collaboration available. I turn the relationships behind your software into a visual language that works across your website, sales deck and product story.

Start with the relationship

A diagram is an explanation.

A useful visual answers a question: where does the data go, what changes, or how does recovery happen? Shape, line and label each need a consistent meaning.

This generic starter example shows a primary path and a separate asynchronous branch. The same discipline applies when building a visual vocabulary for a real product.

Generic labelled product flow with a primary request path and a separate asynchronous queue branch

What a project can include

  • A visual audit of existing product diagrams and explanation gaps.
  • Architecture overviews, workflow sequences and before/after system comparisons.
  • A reusable node, connector and label vocabulary with documented meanings.
  • Layouts adapted for website sections, presentations and other agreed formats.

Deliverables, editable source formats and the number of diagrams are agreed around your actual content. Product accuracy stays a shared review with your technical owner.

From rough map to usable system

  1. Clarify. Identify the audience, the question and the technical source of truth.
  2. Structure. Sketch the relationships and have your subject expert validate the flow.
  3. Design. Apply consistent hierarchy, brand roles, labels and connectors.
  4. Test in context. Review at the intended size, simplify crowded paths and document the reusable rules.

See the approach at Datamotive

The Datamotive work connects three cloud products with a shared brand system and diagram standard. The case study includes a recovery flow and documented colour roles, alongside the website that uses the system.

Explore the Datamotive system ↗

What to bring

A rough sketch, existing deck or product page is enough to begin. Include who needs to understand it, which relationship is currently unclear and who can validate the technical meaning.