Praffulchandra Jain Get in touch
Case 004 · Personal project

Building the site you're reading right now

This portfolio started as "make me a website" and went through a dozen real direction changes before it looked like this. The interesting part isn't the animations — it's what had to be figured out underneath them.

My roleProduct owner & reviewer
Built withClaude, iteratively
AudiencesHiring managers + mentees
ConstraintClient confidentiality

01 The situation

The brief started as "I want to level up and be the best PM at my company," widened into "let's build a portfolio," and widened again into "make it look cool, like a top design studio." None of those are a spec. Each one had to be turned into an actual decision before anything could get built.

The harder problem showed up once real content entered the picture: this site needed to do two contradictory jobs. A senior hiring manager scanning it needs proof of delivery under pressure. A nineteen-year-old deciding whether to send a cold email needs it to feel warm and safe to approach. Most portfolios pick one register. This one had to hold both without either undercutting the other.

02 What made it hard

Three constraints stacked on top of each other, and each one changed what "good" meant.

  • Client confidentiality — the strongest work stories involved a named employer and named enterprise partners, none of which were mine to publish. Every case study had to carry full weight while naming nothing specific.
  • Two audiences, one page — Services needed to sound like a rate card for hiring managers; Mentorship needed to sound like the opposite, with no ambiguity that money was involved anywhere near it.
  • Aesthetic drift — "cool" is not a specification. The direction changed from a ledger aesthetic, to neubrutalist, to a dark studio look, to a full interaction-design rebuild, and each pivot had to fully replace what came before rather than compromise between them.
A portfolio that lists everything is a résumé with animations. The résumé already exists.

03 What I did

Reframed before building. Early on, the instinct was to make requirements literal — "add branding," "make it flashy." Instead each request got pushed back to the actual problem underneath it: not "what animation," but "what does this page need to prove, to whom." That's the same move described in the Services section here — it wasn't just written about, it's how this page itself got made.

Anonymised rather than dropped. Rather than deleting the two strongest work stories once the confidentiality issue surfaced, they were rewritten around the transferable problem — holding a date across four parties, making an ownerless failure someone's job — with every identifying detail removed. The substance survived; the exposure didn't.

Separated the two audiences structurally, not just tonally. Mentorship was moved to sit beside About and Contact rather than inside Services, so a hiring manager reading proof of delivery never has to wade through a charity offer, and a prospective mentee never has to read it as a sales page. The section also deliberately uses less motion than the rest of the site — calmer, warmer, on purpose.

Worth saying

The visual craft got well ahead of the actual content more than once — a polished animation pass would ship while half the page still read "[X]" in metrics and placeholders in the case studies. Motion is the easy part to get right and the part most likely to be mistaken for progress. The harder, slower work — real numbers, a real testimonial, a real photo — is still open at the time of writing.

04 What happened

  • A single-page site with distinct hiring-facing and mentee-facing zones, deliberately different in tone and pacing
  • Two work case studies rebuilt around transferable problems instead of named clients
  • A structure ready to hold a third, real case study and a testimonial the moment they exist

05 What I'd take into the next one

Scope creep isn't only a client-work problem — it happens just as fast on a project of one, especially when every new idea is easy to say yes to. And the thing that actually kept this project honest wasn' more polish; it was periodically asking "who exactly is this for, right now" and letting that question override whatever looked coolest in the moment.