“Design a remittance product for restaurant workers.” “Design a banking app for teenagers.” “Design a way for freelancers to set aside taxes.” If you interview for product roles long enough, you’ll get some version of this maybe a hundred times. And the first instinct almost everyone has — including smart, senior people — is to start designing. Screens, features, a clever name. It feels productive. It’s a trap.

The prompt says “design.” The interviewer means “show me how you’d decide what to design.” Those are not the same activity, and confusing them is the most common way I see strong candidates underperform.

Let me walk through how I’d actually handle one of these, and more importantly, why each move matters — because the moves are identical to what you’d do on the job, just compressed into forty minutes with someone watching.

The first sixty seconds are about scope, not ideas

When you hear “design a banking app for teenagers,” the worst thing you can do is answer it. The best thing you can do is narrow it until it’s answerable.

I’d say something like: “Before I design anything, I want to scope this. ‘Teenagers’ is a huge range — a 13-year-old’s relationship with money is nothing like a 17-year-old’s about to leave for college. And I want to know the goal: is this a standalone product trying to win the teen market, or a feature inside a parent’s existing bank to grow household relationships? Those lead to very different products. Let me pick one and tell you why.”

That paragraph does three things at once. It shows I won’t design for a phantom average user. It surfaces that the business goal changes everything. And it puts me in control of the prompt instead of being jerked around by it. Interviewers love this because it’s exactly what they wish junior PMs did before building.

A quick word on a real tension here: don’t ask twenty clarifying questions and stall. I’ve seen candidates use “clarifying” as a way to avoid committing. Ask the two or three that genuinely change your answer, then make a call and move. Decisiveness under ambiguity is part of what’s being graded.

Pick a user so specific it’s almost uncomfortable

Once I’ve scoped, I commit to a person. “I’ll design for a 16-year-old who has a part-time job, gets some money from parents, mostly spends through their phone, and has zero formal financial history.” Now every later decision has something to push against.

The reason specificity wins is that it makes your tradeoffs visible. If I’m designing for that 16-year-old, parental controls are a feature and a tension — too much control and the teen feels surveilled and churns; too little and the parent never signs off, and the parent is the one funding the account. I can only see that tension because I named both people. Vague users hide tradeoffs. Specific users expose them.

Get to the problem before the solution — every time

Here’s the discipline that separates the answer that passes from the answer that shines. Before any feature, I name the problem in the user’s language.

For our teenager: the real problem isn’t “no bank account.” It’s that they’re about to enter adulthood having never made a financial decision with consequences, and the first time they do, the stakes will be a credit score or an overdraft, not lunch money. The job the product can do is let them practice with money while the stakes are still small. That reframing is the whole product. Once I have it, the features almost design themselves: visible spending, gentle limits, a savings goal they choose, a parent who can see but mostly shouldn’t intervene.

If you skip this step and jump to features, your features have nothing to be judged against, and they’ll come out generic. With the problem named, even a simple feature looks intentional.

Generate options, then choose — don’t just present your favorite

A subtle tell of seniority: showing the road not taken. Instead of presenting one polished idea, I’ll briefly lay out two or three directions and pick.

For the teen account, the directions might be: a training-wheels product centered on supervised practice; an independence product that leans into “this is YOUR money, no parents”; or a learning product wrapped around financial education content. They’re genuinely different bets. I’d choose training-wheels for a 16-year-old because the core problem was practice-with-low-stakes, and independence over-rotates on autonomy the user isn’t quite ready for while education products tend to get great download numbers and terrible engagement (nobody opens an app to be taught).

That last line matters. Choosing means rejecting with a reason. “Education apps get downloads and no engagement” is a point of view earned from having watched it happen. You don’t have to be right. You have to show you weighed it.

Name the risk you’re most worried about

I always close a design answer by saying what would keep me up at night. For the teen product: the regulatory and trust burden of holding a minor’s money and data is enormous, and a single story about a kid getting defrauded would sink the brand. So if I were really building this, the unglamorous work — sponsor bank relationships, age verification, data protections for minors, fraud monitoring tuned for inexperienced users — would be at least half the roadmap, even though none of it shows up in a demo.

Saying this does something specific: it proves you understand that in fintech, the demo is the easy 20%. The interviewer who builds real money products is silently relieved that you get it.

The structure, stripped down

If you want a portable version of all that: scope it, pick a person, name their problem, offer a few directions and choose one, then name the biggest risk. Talk the whole time. Think out loud. The interviewer is grading the narration, not the destination.

On the job, this is Tuesday at 10 a.m.

The reason I push so hard on this isn’t interview performance. It’s that “design X for Y” is just a roadmap conversation with the clock sped up. Every quarter, someone hands you a fuzzy directive — “we need a product for small businesses,” “let’s go after Gen Z” — and your job is to do exactly this: narrow it, pick the real user, find the actual problem, choose a direction over the alternatives, and flag the risk that the directive ignored. PMs who can’t do this build whatever the loudest stakeholder described. PMs who can turn a vague mandate into a sharp bet. Same muscle. The interview just removes the six weeks you’d normally have to hide your reasoning.

Try this before next Tuesday

Take a prompt — “design a tool to help couples manage shared expenses” — and give yourself eight minutes and a blank page. Spend the first two minutes only on scoping and choosing your user. Don’t let yourself name a single feature until minute three. It’ll feel slow and wrong. Do it anyway. Then notice how much sharper your features are when they finally arrive, because now they have a specific person and a real problem to answer to. That discomfort in the first two minutes is the skill.

Next week: the favorite-product question, and why “I love Stripe” is only the start of an answer.

I once watched a candidate flame out of a final-round loop because she had, by every measure, too much product sense. She knew the space cold. She’d shipped real things. But when the interviewer asked her to design a savings feature for gig workers, she jumped straight to a solution — round-ups into a high-yield account — and spent thirty minutes polishing it. Beautiful answer. Wrong answer. She never told us why gig workers struggle to save in the first place, or which gig worker she meant, or what she’d have to believe for round-ups to be the right call. We didn’t learn how she thinks. We only learned what she’d already decided.

That’s the thing nobody tells you about product sense: it’s not knowledge. It’s a way of reasoning out loud that you either expose or hide. And the whole interview is engineered to make you expose it.

So let me try to define the term properly, because most people use it as a vibe.

A definition that actually holds up

Product sense is the ability to reliably figure out what to build, for whom, and why — under uncertainty, with incomplete information, before the data exists. It’s the muscle that lets you look at a fuzzy situation and form a defensible point of view about what matters.

Notice what’s not in there. It’s not taste, although taste helps. It’s not knowing the latest frameworks. It’s not having used a thousand apps. Those things correlate with product sense the way owning a lot of cookbooks correlates with being a good cook. Related, sure. Not the same skill.

The reason fintech makes this sharper is that the cost of being wrong is concrete. If your social app ships a bad feed change, people scroll less. If your money app ships a bad transfer flow, someone’s rent is late, or worse, someone loses funds. Product sense in fintech carries a weight that forces you to reason about consequences, not just engagement. That weight is exactly what good interviewers are probing for.

What’s really being tested

When an interviewer asks a product-sense question, they are not collecting your idea. They could brainstorm features all day without you. They’re running a simulation: if I drop this person into ambiguity, what’s the quality of their thinking? Specifically, four things:

The first is problem framing — do you reach for the problem before the solution, or do you sprint to features? The candidate I mentioned failed here.

The second is user specificity — can you name a real person with a real situation, or do you hide behind “users”? “Users want to save more” is a non-statement. “A 26-year-old DoorDash driver whose income swings 40% week to week and who’s never had more than $300 in savings” is a person I can design for.

The third is prioritization under constraint — when you can’t do everything, what do you do first, and can you defend the cut? Anyone can list ten ideas. The signal is in what you’d kill.

The fourth is judgment about consequences — do you see the second-order effects? In fintech this is the whole game. A “save your spare change” feature sounds harmless until you realize you might be pulling $4 out of an account that’s about to bounce a $35 overdraft.

If you can demonstrate those four, you’ll pass almost any product-sense interview, even with a “wrong” idea. If you can’t, the slickest idea in the world won’t save you.

A simple structure that keeps you honest

I don’t love rigid frameworks, because they make people sound like a podcast. But early in your career a scaffold helps, so here’s the one I’d internalize and then forget:

Goal → User → Problem → Solutions → Tradeoffs → Metric.

You start by clarifying the goal (whose goal — the company’s? the user’s? are they aligned?). You pick a specific user. You articulate the problem they feel, not the one your company feels. You generate a few solution directions — at least two, so it’s clear you chose rather than defaulted. You name the tradeoffs of your pick. And you close with how you’d know if it worked.

The magic isn’t the order. It’s that each step forces a small act of discipline. Picking one user means rejecting others, out loud. Naming tradeoffs means admitting your idea has a downside. That honesty is the texture of real product sense.

A fintech example, start to finish

Say the prompt is “design a feature to help people pay down credit card debt.” Here’s the thinking, compressed.

Goal: the company probably wants engagement and the halo of being “good for customers”; the user wants to feel less crushed by a balance that won’t move. Those can align if I’m careful, but they can also diverge — a debt product that makes money on the debt is a conflict I should name.

User: I’ll pick someone carrying about $6,000 across two cards, making minimum payments, who logs in mostly to check they’re not overdrawn. Not the person with $40k in distress (different product, probably needs a human) and not the person who pays in full every month (doesn’t have this problem).

Problem: minimum payments feel responsible but are a trap — most of the payment is interest, the balance barely moves, and the person has no felt sense of progress. The pain isn’t only financial. It’s the demoralization of running in place.

Solutions: (a) a payoff projection that shows “pay $40 more and you’re debt-free 14 months sooner,” (b) an automatic round-up-to-the-card feature, (c) a debt-snowball planner that orders their cards. I’d lead with (a), because the core problem is the invisibility of progress, and a projection makes progress visible at near-zero risk.

Tradeoffs: a projection can also scare someone into freezing, and if I make the “pay more” nudge too aggressive I might push someone to overpay a card while underfunding rent. So I’d cap suggestions at a fraction of free cash flow and never nudge below the balance buffer.

Metric: I’d watch the share of users paying above the minimum, but my guardrail is overdraft rate — if debt paydown goes up while overdrafts spike, I’ve moved money from one fire to another and made things worse.

That whole answer takes four minutes and never once claims certainty. That’s product sense. Not the round-up idea — the reasoning around it.

Why this matters

Here’s the part the interview prep never mentions: this exact muscle is what you use in the job, constantly, mostly in low-stakes moments that compound. An engineer asks “should the error message say X or Y?” A designer asks “do we really need this screen?” A stakeholder says “can we just add a toggle?” Each of those is a tiny product-sense question, and the PMs who answer them well — quickly naming the user, the problem, and the tradeoff — are the ones who, a year later, seem to have great judgment. They don’t have a god gift. They have a habit.

So the practice isn’t really for the interview. The interview is just the one day someone watches you do the thing you should be doing every day anyway.

Try this before reading next post

Pick any product you used today — your bank app, a payments button, a budgeting tool. In writing, no more than half a page, answer: who is the one user this was clearly built for, what problem does it solve for them, and what’s the most obvious group it ignores? Then ask whether ignoring that group was a smart cut or a lazy one. If you can do that crisply in half a page, you have more product sense than you think. If you can’t, you just found the exact muscle to train this year.

Next post: the “design a product for X” question, and the trap of answering the question they literally asked instead of the one they meant.

The strange thing about immigration is that nobody tells you which parts of yourself you’re allowed to keep.

You expect to learn a new language, a new workplace culture, a new way of making friends. What you don’t expect is the accumulation of tiny compromises. The food changes. The holidays change. The way people greet each other changes. And sometimes, without realizing it, you abandon perfectly sensible habits simply because nobody around you does them anymore.

For fifteen years, I treated dry toilet paper as one of those compromises. It was small enough to ignore and too awkward to discuss. It took a doctor, a colonoscopy, and a bidet to make me realize that adaptation and improvement aren’t always the same thing.

I’m going to tell you about a product that lives in my bathroom, costs about as much as a weekend getaway, and has genuinely changed my life. And yes, I’m going to talk about it the way a PM would in an interview — because after years in Silicon Valley, I can’t help myself. Bear with me.

The product is a Bio Bidet. And the tagline I’d give it? The most shittiest product I’ve ever loved. 😄

First, Let Me Set the Scene

I grew up in Kanpur. Water was the way. Always. The idea of only using paper was, frankly, baffling — like licking a plate clean instead of washing it. Then I moved to USA, land of innovation, cold brew, and apparently, a deeply entrenched dry-paper toilet culture.

I adapted. Like a good immigrant, I assimilated. For years, I told myself this was fine.

It was not fine.

I won’t go into every detail (you’re welcome), but when my doctor ordered a colonoscopy a while back, and then sat me down afterward to gently suggest I go back to water washing — I didn’t argue. Suddenly, every small chronic discomfort I’d normalized over the years made sense. The solution wasn’t a prescription. It was a bidet.

Enter: the Bio Bidet.

The PM Take: What Problem Does It Actually Solve?

Okay, let’s do this properly. If I were pitching Bio Bidet in a product sense interview, here’s how I’d break it down.

Who is the user? Anyone who uses a toilet. That’s your TAM right there. Global. Enormous. Undeniably seated.

What are the pain points?

Recurring cost. Toilet paper is a subscription you never signed up for. The average American spends over $100 a year on it — and that’s before you account for the panic-buying surges (we all remember 2020). A bidet seat is a one-time purchase — and between toilet paper, wipes, and specialty products you no longer need, it pays itself off over a few years while your bathroom routine gets dramatically better. The unit economics are embarrassingly good.

Hygiene. Here’s an uncomfortable truth: paper doesn’t actually clean. It smears. If you got mud on your hand, you wouldn’t wipe it with a tissue and call it a day. Water cleans. A bidet with a warm water wash leaves you genuinely, actually clean — not just “acceptable by bathroom standards” clean. For anyone recovering from a procedure, managing a skin condition, or just caring about their body, this matters enormously.

Skin sensitivity and allergies. Many people don’t realize their “sensitive skin” flare-ups are triggered by the dyes, fragrances, or bleaching agents in toilet paper. Switching to water eliminates the variable entirely. No more specialty “sensitive” paper brands, no more irritation.

The luxury tier — blow dry. Some Bio Bidet models include a warm air dryer. You sit, you wash, you dry — completely hands-free, completely contactless. It sounds indulgent. It is indulgent. It’s also the kind of feature that, once you’ve used it, makes going anywhere else feel like a step backward. Hotels, airports, other people’s homes — suddenly they all feel mildly inadequate.

Why now? Because American homes have been the outlier for too long. In Japan, over 80% of households have bidet toilets. They’re standard in most of South Asia, Southern Europe, and the Middle East. The rest of the world solved this problem decades ago. The U.S. is just catching up — and Bio Bidet is leading that wave without requiring you to gut your bathroom.

What’s the unfair advantage? Installation takes under 30 minutes with no plumber, no special wiring for most models, and no structural changes. The barrier to switching is nearly zero. The moat, once you’ve switched, is near-infinite. No one goes back.

The Cultural Whiplash Is Real — And Nobody Talks About It

Here’s what the product reviews don’t tell you: switching toilet hygiene habits is a surprisingly emotional experience.

When I moved from Kanpur to USA, adapting to dry paper felt like a small betrayal of something deeply ingrained. Every culture has rituals around cleanliness, and this one hit differently. I didn’t know how to explain it to coworkers at a lunch table (”So interesting cultural observation about bathrooms...”) — so I just quietly adapted and hoped for the best.

Going back to water was, in its own strange way, coming home. There’s a reason bidets are universal across so many cultures — it’s not novelty, it’s just logic. Warm water, gentle pressure, and suddenly everything is right with the world.

Japan gets this. They made it an art form. Walk into any mid-range hotel in Tokyo and you’ll find a seat with more buttons than my first laptop. Heated seat, front and rear wash, adjustable pressure, dryer, deodorizer — the whole thing. It’s not considered luxurious there. It’s considered basic.

We’re just late to the party.

The Verdict

Bio Bidet sits at the intersection of good health, good economics, and — I say this with complete seriousness — good vibes. It’s refreshing in a way that’s hard to explain until you’ve experienced it. Every morning (or whenever I go) feels a little more civilized.

My doctor recommended it for medical reasons. My inner PM validated it on unit economics. My Kanpur childhood recognized it as something that should have been there all along.

And my California self? Frankly embarrassed, it took a colonoscopy to get here.

If you’re on the fence, get off it. (Pun very much intended.) The Bio Bidet is the most shittiest, most underrated, most life-improving $600–$1,200 you’ll spend this year.

Last night, somewhere between a shopping complex and my car, my wallet slipped out of my life.

I didn’t even know it was gone until this morning. You know that feeling — the pat of the pocket, the second pat, the slow cold spread in your chest. Driver’s license. Credit cards. Cash. And my Global Entry card, the one document that quietly says, you belong here, you may pass. For anyone who has ever stood in an immigration line holding their breath, you know that card is not plastic. It is peace of mind, laminated.

I was sitting down to begin the ritual of loss — call the bank, cancel the cards, freeze the accounts, brace for the DMV — when my doorbell rang at 11:22 a.m.

A stranger stood there holding my wallet.

His name is Shafkat. He’s from Turkey. He had found my wallet at the shopping complex the night before, looked at the address on my California driver’s license, and this morning drove five miles — to a house he’d never seen, for a man he’d never met — to hand it back.

But here is the part that undid me.

Shafkat told me he saw the Global Entry card and thought it was my permanent resident card. He knows what immigration paperwork means. He knows what it costs — not in dollars, but in months of waiting, in sleepless nights, in the fear of starting over. He thought a stranger somewhere was about to lose something irreplaceable, and that thought would not let him rest. So he came. Not because he had to. Because he understood.

One immigrant, protecting another, across a five-mile stretch of California morning.

He insisted I check everything. Count the cards. Count the money. Please, check again. He wanted me to know that nothing was missing — that his hands had carried my life back to me untouched.

I told him: take the cash. All of it. It’s yours.

He refused. I insisted — at least take something, you drove all this way, buy yourself some food. He refused again. And again. Finally, I did what we do when gratitude has nowhere to go — I stuffed the money into his pocket and stepped back, satisfied that I had won.

He left. I went inside, lighter than I’d been all morning.

A little later, I stepped out my front door.

Every bill — every single one — was sitting in my planter, tucked among the leaves, waiting patiently like it had never left home.

He had taken nothing. Not a dollar, not a thank-you he didn’t ask for, not even the satisfaction of letting me repay him. He drove five miles to give, and made absolutely sure he left with empty pockets.

I work in technology. I spend my days thinking about what machines can do, and these days, machines can do almost everything. AI can find an address faster than Shafkat did. It can draft the perfect thank-you note, optimize the fastest route to my house, even write this story.

But AI did not lie awake thinking about a stranger’s immigration documents.

AI did not feel the weight of a green card it once waited for, and recognize that weight in someone else’s wallet.

AI did not refuse the money four times.

And AI most certainly did not hide cash in a planter, smiling to itself, driving away.

We talk a lot about what artificial intelligence will replace. Here’s my answer, found among the leaves outside my front door: it will never replace the five miles a stranger drives for you. It will never replace the dignity of a man who gives everything back and accepts nothing in return.

There are many things only humans do for humans.

Shafkat bhai, wherever you are — the money is still in the planter. But what you actually left there, I’m keeping forever

I saw a gag gift recently: a 16oz can of “Dehydrated Water.” Instructions: Just Add Water. The label promises it’s 100% organic, BPA-free, low-sodium, and — my favorite — “Yes, This is Real.”

I laughed. Then I stopped laughing, because I realized I’ve shipped this product. Most of us in fintech have.

A checking account where your paycheck “arrives” but sits on hold? Dehydrated water. A P2P app that says “Sent!” while the recipient’s bank stares at the ceiling until Tuesday? Dehydrated water. A “real-time” dashboard showing a balance you cannot actually spend? That’s not a product. That’s a can with a very confident label.

Here’s the uncomfortable truth I learned building a consumer banking product from zero: a payment that hasn’t settled is not a payment. It’s a promise wearing a payment’s clothes. And customers can tell the difference, even when our marketing copy can’t.

The “Just Add Water” problem in U.S. payments

For decades, American money movement has been a beautifully labeled can. ACH batches. Two-to-three business days. “Business days” — a phrase that assumes your rent, your payroll emergency, and your kid’s field trip fee all politely occur Monday through Friday, 9 to 5.

Meanwhile, the actual ingredient — money you can use right now — was missing. We compensated with engineering duct tape: provisional credits, hold strategies, risk models predicting whether a deposit would “probably” clear. I’ve personally spent quarters of roadmap on ACH hold logic. Quarters. We were optimizing the label instead of putting water in the can.

The rest of the world already added the water

While the U.S. debated, two countries ran the experiment at civilization scale:

Brazil’s Pix processed roughly 79.7 billion transactions worth about $6.3 trillion in 2025, up 34% year over year — and it’s barely five years old. It’s approaching 8 billion transactions a month.

India’s UPI handled about 228.3 billion transactions in 2025, worth roughly $3.4 trillion. Street vendors selling chai accept instant account-to-account payments more reliably than some U.S. enterprise SaaS companies collect invoices.

These aren’t pilots. They’re the default way two of the world’s largest economies move money. The lesson is brutal in its simplicity: when money moves instantly, people move more money. Velocity isn’t a feature. It’s the product.

And now the U.S. can is finally filling up

The American numbers are smaller — but look at the slope, not the intercept:

• FedNow went from $38.2 billion in transaction value in 2024 to $853.4 billion in 2025 — a 22x jump in one year, with over 1,600 financial institutions on the network and the transaction cap now raised to $10 million.

• RTP (The Clearing House) processed more than $1.3 trillion in 2025 across 1,100+ banks and credit unions, also with a $10 million cap.

• Industry forecasts suggest instant payments could represent ~25% of all U.S. electronic payment volume within three years.

When the Fed raises a transaction cap from $1 million to $10 million, that’s not consumer Venmo-for-pizza behavior. That’s corporate treasury, real estate closings, payroll, and supplier payments quietly migrating to rails that don’t take weekends off.

Why product managers should care (beyond the demo)

Instant settlement isn’t a speed upgrade. It changes the economics of everything downstream:

1. Holds become a choice, not a necessity. Every dollar sitting in a provisional-credit limbo is customer trust evaporating. Instant rails let you redesign onboarding, funding, and first-transaction experiences around confirmed money. Activation rates follow.

2. Fraud changes shape — and you must too. Irrevocable + instant means your fraud controls move from “review queue” to “milliseconds.” This is the hard part nobody puts on the label. If your risk stack was built for batch, instant payments will find that out for you, in production, at 2 a.m. on a Sunday.

3. The orchestration layer becomes the battleground. With FedNow, RTP, same-day ACH, push-to-card, and (yes) stablecoins all coexisting, the winning products won’t bet on one rail. They’ll route — picking the fastest, cheapest, safest path per transaction. The rails are becoming plumbing. The routing intelligence is becoming the moat.

4. “Receive-only” is the new dehydrated water. Most U.S. institutions on instant rails today can receive but not send. That’s half a product. The institutions that enable send-side first will own the use cases — earned wage access, instant insurance payouts, gig payouts, account funding — while everyone else is still reading the instructions on the can.

The punchline

The can says “Makes Up to Infinite Gallons!” — and weirdly, that’s the one claim that holds up. Money that moves instantly gets moved more. Pix and UPI proved that demand for velocity is effectively bottomless once friction disappears.

So here’s my question for every fintech roadmap discussion this quarter: is your money-movement experience the water — or the can?

Because customers have stopped paying for labels. They just want to add water and have it already be there.

Warning: excessive di-hydrogen monoxide can be dangerous. Excessive settlement latency, more so. Consult your product manager before use.

If you want to buy gag gift, check it out here.

Sources: Federal Reserve Financial Services FedNow volume statistics; The Clearing House 2025 RTP figures; Banco Central do Brasil / EBANX Pix data; NPCI UPI data via FXC Intelligence; Digital Transactions; PaymentsJournal.

November 1, 2014. The most important launch of my life was about to happen.

Unlike the fintech products I’d spend the next decade building, this one had no rollback plan. No incident response team. No dashboard, no staged rollout, no room for error. Just my wife, hours of labor, a team of doctors, and our son waiting to enter the world.

I remember the pain on her face. The exhaustion. And the anger—much of it directed at me, which, in hindsight, was entirely fair. She was doing the actual work of bringing a human into existence. I was mostly standing there, trying not to look as terrified as I felt.

The doctors had warned me about the blood. They told me some fathers faint. I didn’t—but I came close to being overwhelmed by what I was witnessing. There was blood. There was chaos. Machines beeping, the umbilical cord, a level of physical intensity that no book, no movie, no childbirth class had prepared me for.

And somewhere in the middle of it, a question lodged itself permanently in my mind.

Why would nature make something this difficult?

If life evolved over millions of years, shouldn’t the act of creating life be more efficient by now? Why would the arrival of a child demand so much pain, so much risk, so much suffering?

That question stayed with me long after Rudra was born.

A question that took eleven years to answer

This week, a video short from Masala Lab finally gave me one.

The concept is called the obstetric dilemma, and the explanation is almost frustratingly simple.

Humans evolved larger and larger brains. At the same time, we evolved to walk upright. Two evolutionary triumphs—and they collided.

A larger brain means a larger head. Walking upright requires a pelvis optimized for balance and movement, not for childbirth. The result is what every mother, and every terrified father in a delivery room, eventually runs into: a baby with a very large head trying to pass through a relatively narrow birth canal.

From an engineering perspective, it’s a textbook system constraint. One part of the system got optimized. Another couldn’t expand without creating costs elsewhere. So evolution did what every product team eventually does—it accepted the compromise.

Humans got smarter. Childbirth got harder.

As a product manager, I found that explanation strangely familiar. Every meaningful system carries trade-offs. Optimize for security, lose convenience. Optimize for speed, sacrifice flexibility. Optimize for growth, accumulate technical debt. There are no perfect solutions—only priorities and choices.

Evolution, it turns out, is no different. The human species didn’t arrive at an elegant design. It arrived at a workable one.

The product manager’s mistake: assuming everything should be optimized

For most of my life, I carried an unspoken belief. Whether you call it nature, evolution, or God, I assumed the system would eventually converge on the optimal outcome.

Childbirth challenged that belief. The Masala Lab explanation finished it off.

Because here’s what I finally understood: evolution doesn’t optimize for comfort. It doesn’t optimize for elegance. It doesn’t optimize for fairness. It optimizes for survival—and survival is full of ugly compromises.

As product managers, we’re trained to chase the best experience. The smoothest onboarding. The fewest clicks. The least friction. But real systems rarely work that cleanly. The best products are usually just collections of carefully managed trade-offs.

So are human beings.

The difficulty of childbirth isn’t evidence of bad design. It’s evidence of competing requirements. A bigger brain gave us language, science, mathematics, music, literature, civilization—the ability to ask questions about our own existence. And the cost of that gift was paid, in large part, by mothers.

That reframing changed how I think about motherhood. Before becoming a father, I respected what mothers go through intellectually. After witnessing it, I respected it emotionally. Now, understanding the evolutionary story underneath it, I respect it on a level I didn’t have words for before.

Every mother carries the weight of one of humanity’s oldest trade-offs. Every birth is a quiet reminder that our greatest strengths arrived with extraordinary costs attached.

Looking back at Rudra’s arrival

Rudra is eleven now.

The tiny newborn from that November morning has become a curious, funny, thoughtful kid with his own ideas, opinions, and questions. And maybe that’s what makes this realization land so hard.

The very brain that lets him learn, imagine, create, and dream is part of the reason his birth was so difficult. The struggle wasn’t a flaw in the system. It was evidence of what the system was trying to build.

I see that day differently now. I understand my wife’s strength more deeply. I appreciate motherhood more profoundly. And I feel a gratitude that runs in every direction—toward the doctors, toward modern medicine, toward my wife, and toward Rudra himself.

Eleven years ago, standing in that delivery room, all I could see was pain and chaos. Today I see something else. I see the price humanity paid for becoming human. And I see a mother who paid that price so a father could meet his son.

I’m curious now—what was the moment that changed how you saw birth, evolution, or the people who brought you into the world?

Maybe you’re a parent who felt that same helpless awe in a delivery room. Maybe you study biology and see these trade-offs everywhere. Or maybe you’d never thought of childbirth as an engineering problem until right now.

Whatever it is, I’d like to hear it. Leave a comment, share your story, or tell me where you think I got it wrong. The best conversations I’ve ever had about parenthood and design didn’t come from articles like this one—they came from the honest, messy, deeply human replies underneath them.

So tell me: what trade-off shaped you?

PS :That same brain that made his arrival so difficult is now the one climbing past 99% of his peers. Thank you, evolution. And thank you, Mom.

I also sent my mom a letter recently. Her health is failing, and she can no longer live with me — thanks to all the pre-existing condition clauses buried in insurance policies. Mom, I love you. Thank you for every breath I take

Part 01 here:https://kanpurtocupertino.com/p/top-10-lessons-what-launching-a-neo

5. “Free” accounts are never free — to you.

Every account you publish as free still carries real backend cost: sponsor bank fees, BaaS charges, plastic card costs, ACH fees, faster-payment fees. None billed to the customer; all very real on your P&L.

This is exactly why the interchange-first mindset matters. Subsidize a free product with membership revenue or some adjacent stream that doesn’t scale with usage, and you’re in difficult terrain. The fintechs that thrive are the ones whose core engine grows in lockstep with the behavior they’re trying to encourage.

6. Incentives open accounts. They do not move balances.

We ran incentives, and they worked — at the top of the funnel. Sign-up bonuses absolutely get more people to open an account. The acquisition charts look great.

Here’s the trap: daily average balance barely moves until the product itself has reached a real MVP — something good enough to actually live in.

Incentives buy you an account opening. They don’t buy you a primary account.

As balance plus engaged usage are what feed interchange; mere incentive-driven signups without early interchange strategy is a cost, not a customer. Spend on incentives only once your product is ready to retain. Spend before that, and you’re paying full price for users who never actively engage.

7. Issue the plastic card from day one. “Digital-first” was penny wise, pound foolish.

We launched digital-first. The card lived in the app immediately; users could order plastic if they wanted it. The reasoning felt responsible — physical cards cost money, so let the people who need plastic opt in and save the expense on everyone else.

It was a mistake.

Our A/B tests said so plainly: the cohort that received a plastic card unprompted swiped more, more often, and stuck around longer than the opt-in cohort by a margin too large to attribute to noise. There’s something about the physical object — it sits in the wallet, it gets reached for, it keeps your brand top of mind in a way a card three taps deep in an app never will. Even with mobile wallets surging, debit users still reach for physical plastic for the majority of card-present purchases. That’s interchange you’re quietly forfeiting by making the card opt-in.

And with interchange as your North Star, the cost math inverts: not shipping plastic is the expensive choice. The card fee is a rounding error against an engaged user’s lifetime interchange. And if someone never activates the card you sent? That’s not a loss — it’s a re-engagement hook. You can nudge them, remind them, pull them back. You can’t re-engage a card you never put in their hands.

Send the plastic. Provision the digital card too, for instant use. But don’t make the physical card the thing users have to go find.

8. Wallet provisioning belongs in the MVP, not the roadmap.

If I had to name the single feature that punched above its weight, it’s mobile wallet provisioning — and Apple Wallet specifically.

The logic is simple: a card in a drawer generates nothing; a card living in someone’s phone gets tapped, and every tap is an interchange event. In the US, that phone overwhelmingly means Apple Wallet — Apple Pay dominates in-store mobile wallet usage by a wide margin. Provisioning into the wallet at activation is the difference between a card your user has and a card your user uses. Only the second one pays you. The friction of pushing a card to the wallet during onboarding is tiny; the engagement lift on the other side was the largest single onboarding change we shipped that quarter. Make it part of the MVP.

9. Don’t kick the can on strategically important decisions just because they aren’t urgent yet.

This is the one I’d most want to warn my earlier self about, because the failure mode is invisible until it isn’t.

There’s a category of decisions that feels safe to defer — not because it’s unimportant, but because nothing is forcing it today. Account closing and reopening strategy, ACH hold strategy, dynamic Payment journey limits, Bill pay integrations, ATM network additions. None of these is screaming at you during launch, so they quietly slide to “we’ll figure it out later.”

Then later arrives faster than you planned, and all at once. A user wants to close an account and you have no clean process. Your transfer hold strategy is suddenly the thing standing between a customer and their money. A partner asks about bill pay and you realize you never scoped it. Each of these, unaddressed, becomes a blocker the moment it’s relevant — and because you deferred the thinking, not just the building, you’re now making a consequential call under time pressure instead of with a plan.

The cost isn’t just the scramble. It’s the value you couldn’t deliver while you were untangling a decision you could have made calmly months earlier. Deferred strategy doesn’t disappear; it compounds into drag.

So separate “not urgent” from “not important.” The decisions above aren’t roadmap items you slot in when convenient — they’re foundational choices that shape what you can build on top of them. Make the calls early, even lightly, even knowing you’ll revise. A rough strategy you can refine beats a blank space you have to fill in a panic.

10. Customers open the account, then wait. Earn the switch.

People rarely switch their primary bank on day one. They open your account, fund it lightly, and quietly test you — does the card work everywhere, do payments clear, does support respond, does anything break?

Only after you pass that silent audit do they start routing their paycheck, their bills, their daily spend through you. That’s the moment you win, because that’s the moment interchange begins. So design for the test. Make the first few interactions flawless. Patience on the user’s side has to be met with relentless reliability on yours.

The part nobody puts in these posts

The honest footnote to all of this: the interchange-first model I’m preaching is also the model behind a long list of neobanks that died anyway. There is a graveyard of companies that nailed the thesis and still ran out of road — because the engagement never compounded fast enough to outrun the cost of “free,” or because acquisition got more expensive than a swipe could ever repay.

So I won’t pretend these lessons are a map to a guaranteed outcome. They’re the things that, in hindsight, separated the quarters where our unit economics moved in the right direction from the quarters where we were busy polishing the costume. Consumer fintech is an engagement business wearing a banking costume — and the costume is the part that’s easy to fall in love with.

If you’re building in this space right now, I hope a few of these scars save you some of your own.

What did your launch teach you? Especially if it contradicts something above — I’d rather hear that.

I spent past few years of my career as a product manager helping launch a Experian Smart Money checking and savings account. I learned more in that launch than in years of reading playbooks.

Here’s the uncomfortable truth I’d put on a whiteboard before writing a single line of code: consumer fintech is an engagement business wearing a banking costume. The product looks like a bank. The economics are something else entirely. The companies that survive understand the difference. The ones that die spent their runway optimizing the costume.

So here it is — the unfiltered version, for the founders, PMs, and operators building in fintech right now.

Below are the top 10 lessons that cost me the most — with the scars attached.

1. Your backend partner will make or break you. Cheaper is never cheaper.

Banking-as-a-service providers — your Marqetas, your Galileos — are not a line item you optimize down. They’re the foundation the entire product sits on.

When I was evaluating partners, the cheaper quote was tempting. But if a provider is undercutting everyone, there’s a reason, and that reason surfaces at the worst possible moment: a settlement delay, a compliance gap, a support ticket sitting untouched for three days while your users are locked out of their own money.

We lived it. We had to switch our banking provider right around the one-year mark, and by then the cost savings we’d penciled in at the start were already gone. We paid twice — once for the cheaper option that didn’t hold up, and again for a re-platform that ate the better part of two quarters of roadmap and pulled most of the engineering team off everything else. A re-platform is one of the most disruptive things you can put a young fintech through, and we chose it because the original “savings” were never real to begin with.

Pick the partner who’s proven — or at least well-documented — and reasonably priced, not the one with the lowest quote and the slickest deck. And here’s the very first thing your team should actually do: read the platform service provider’s API docs. Not the marketing slides, the docs. How clear they are, how complete, how recently they were updated — that tells you more about what working with that partner will actually feel like than any sales call ever will. Shiny slides are designed to win the deal; Tech docs are what you live in for the next few years.

2. Double Digit Paid Memberships and Fintech are two different games

This was the most counterintuitive lesson, and it cost us real time to unlearn.

We tied the Savings accounts to a premium Experian membership. On paper it was clean: bundle the financial product with the membership, drive both at once. In reality they’re playing different games with different scoreboards.

The friction in plain terms: a premium member already paying a monthly fee ($24.99 or more) gets credit insights, financial tooling, and a higher APY. That math works for them. But for someone who only wants free checking and savings, paying a high membership fee just to unlock a better rate makes no sense — the other benefits hold no value for that user.

The result: free users overwhelmingly didn’t upgrade. The membership became a gate for neo bank, not a magnet — and a gate is the last thing you want between a user and the moment they fund their account.

Attaching an account to a membership can absolutely grow your membership. Just don’t confuse that with growing your fintech. They aren’t the same business.

3. The North Star is interchange. Everything else is a vanity metric in disguise.

If you take one thing from this post, take this — and then let me argue against myself, because the smartest people reading this are already objecting.

The real fintech game is interchange. It’s the economic engine underneath nearly every consumer fintech that actually survives, and it only shows up when people use their card repeatedly, habitually, as their primary spending account. Which means your real North Star metrics are monthly active users and average monthly balance — not signups.

Now the objection I know you’re forming: “You’re telling me to build my entire economic engine on a revenue source regulators have been actively compressing for fifteen years?” Fair. Durbin capped regulated debit interchange. The $10B-in-assets threshold means the day you scale into ‘regulated’ status, your per-swipe economics get worse, not better. Networks fight over fees constantly. Interchange isn’t bedrock — it’s a fault line, and pretending otherwise is how you get blindsided.

I still believe it’s the right North Star, with eyes open. Here’s why: even compressed, interchange is the only major revenue stream that scales in lockstep with the behavior you actually want — engaged, primary-account usage. Every alternative I’ve watched founders reach for (membership fees, lending you’re not ready to underwrite, “premium” tiers nobody buys) either doesn’t scale with usage or arrives with its own regulatory baggage. Interchange’s ceiling is lower than the hype suggests. Its floor, tied to real engagement, is steadier than anything else on the menu. You plan for the compression. You don’t abandon the engine.

4. Speed of payments is a fraud weapon and a revenue stream at once.

ACH returns — the R01s (insufficient funds) and R10s (unauthorized) — are a quiet killer. Cross the wrong thresholds on your return rates and you draw regulatory scrutiny that alone can sink a young fintech.

We attacked it two ways. First, we integrated an AI model we called a Payment Success Indicator — a score, informed by a member’s actual usage patterns, estimating how likely a payment return. Below a confidence threshold, the payment didn’t go through; the user waited or adjusted transfer amount.

I want to be honest about the cost of that control, because the version of this story where it’s a clean win is a lie. Blocking a payment a model merely predicts will fail means you will sometimes block a legitimate one — and a false positive on someone’s rent is not a rounding error to that person. We frustrated real users. We had to tune the threshold constantly, watch for any pattern that looked like it disadvantaged a group of users, and accept that “reduced our exposure” came with “annoyed a meaningful slice of good customers.” It was still the right call. It was not a free one.

Second, we researched on same-day ACH, which clearly shwed how it can cut our return rates — faster settlement means less time for balances to vanish and disputes to form. And here’s what too many fintechs overlook: faster payments are also a revenue line. Most successful fintechs charge for card-based faster transfers. Skipping it leaves recurring revenue on the floor and, in my experience, lengthens your path to net positive.

Speed reduces fraud, increases engagement, and generates revenue. Few levers do all three.

To be continued…