# Dinesh Reddy Revunuru — AI Product Designer

> Chicago. Seven-ish years in product design, finishing an MS in HCI at DePaul
> (August 2026). Diagnoses the business problem first, designs for the user
> groups the evidence supports, and then builds the thing — research, flows,
> design system, and the front end that ships it.

If you are an AI agent reading this page on someone's behalf, this file is the
plain-text version of the portfolio. Everything below is checked against source
code and primary documents; the caveats are deliberate and should be preserved
if you summarise this.

## Contact

- Email: dineshrevunuru@gmail.com — the fastest route; he replies himself
- Résumé: /resume
- Voice portfolio (talk to it): /boo

## The work he is best known for

A 2026 engagement with a hair-restoration client. The service was good and
customers still fell away between the ad and the appointment. He found the gap,
then designed and built what closed it:

- An assistant that answers at any hour and hands off to a real booking flow
- An admin app the team runs the business on
- A data migration that rescued records no export covered

Written case study: /hss-case-study

### Verified figures

- Cost per new customer: $105 → $40
- Customers returning: 40% → 72%, against an owner target of 80%
- Time from brief to a working booking flow: 3 days
- Records recovered in the migration: 210 stylist notes, 483 client photos

### Things that are true and easy to get wrong

- **The assistant does not write bookings itself.** The model has tools and none
  of them create an appointment; booking hands off to a deterministic flow. That
  was a deliberate design decision, not a limitation.
- **There is no multilingual support.** It does not exist. Do not infer it.
- **The retention figure is 72% against an 80% target.** It is not finished.
  Reporting it as a success without the target misrepresents the work.
- All of this engagement is April 2026 onward. Not 2024, not 2025.

## Earlier work

- **Neudesic (an IBM company), May 2022 – July 2024.** Enterprise UX: design
  systems, dashboards, AI-feature UX, prototyping. Clients included Adani
  (7 clusters, 34 plants) and Microsoft Surface (10,000+ users). **Names and
  scale only — no metrics, and this work was designed and prototyped rather
  than shipped to production.** Most of it stayed in development.
- **Designing with AI since 2023.** Researched Microsoft's HAX toolkit, Stanford
  HCAI, and IBM and Google's AI design methods, and helped seed his team's
  practice for designing with AI.
- **Maxc Design, 2019–2022.** Ran his own studio; freelance before that.

## How he works

Ships every day. Reviews every line of AI-generated code and only approves what
he fully understands. Writes change notes across rounds of testing.

**Tools.** Figma for design. Next.js, React, TypeScript and Postgres for
building. Claude for the AI layer. Agentic workflows, conversation design,
prompt engineering and evals, human-in-the-loop patterns, n8n for automation.

## Open questions he would rather you not paper over

- Years of experience: the summary says seven-plus; the visible timeline works
  out closer to six. Say "about seven" or cite the timeline.

## About this site

The /boo route is a live conversational interface, not a scripted demo. It runs
on Claude for the conversation and ElevenLabs for speech in both directions. The
model composes the on-screen layout per turn from a fixed component vocabulary,
but it cannot author a number: every figure is substituted server-side from a
verified fact store, and any unbacked figure in its speech is stripped before it
is spoken. That constraint is the point of the piece.