Yalo Marketplace

It worked because it turned a cost that felt impossible into one that felt manageable, and somewhere in the middle of that product's growth, the obvious question started nagging at me: why stop at rent?

Rent was never really the point. The point was that a large one-time cost, even one someone can technically afford, feels psychologically out of reach when it lands as a single payment. Spread across twelve months, the same amount stops feeling like a decision you have to steel yourself for. That logic doesn't only apply to housing. A refrigerator, a laptop, a generator, the kind of appliance or electronic that a household genuinely needs but keeps postponing because the upfront number is the wrong shape. I wanted to know if the insight would transfer, not assume it would.

So I led discovery on extending the model to goods and services. I talked to customers directly about what they'd actually want to finance this way, which categories felt urgent versus aspirational, and where the friction really sat. Rent works as collateral of a sort because it's tied to a lease and a fixed monthly obligation people already budget around. A blender or a phone doesn't carry that same structure, and the basket sizes were much smaller, which meant the risk math didn't just scale down from the rent product, it changed shape. I had to design a verification and KYC flow suited to smaller, more varied purchases rather than porting over what worked for a year-long lease. That was the harder problem: building enough confidence in repayment at a basket size where the usual signals are thinner and the cost of getting it wrong on volume is easy to underestimate.

Rent was never really the point.

Financing only works if there's something real to finance, so I partnered with external vendors in electronics and appliances, including CDCare, to actually source the goods. That meant negotiating how sourcing and fulfillment would work alongside the payment plan, not just designing a checkout flow in isolation. On the build side, I worked with a small squad, one designer, one backend engineer, one frontend engineer, and we took the idea from a discovery conversation to a live pilot in about three months. With a team that size and a timeline that short, scope discipline mattered more than ambition. We weren't building the full marketplace vision, we were building the smallest version that could tell us whether the transfer held.

The pilot reached around fifty customers. That's a small number, and I'm not going to dress it up as more than it was. It launched as a side product specifically to test the model before anyone committed to scaling it further, and it did what a pilot is supposed to do: it gave us a real, if early, read on whether people wanted to finance goods the same way they financed rent, and whether the verification approach we'd built could hold up against actual repayment behavior rather than assumptions. What I care about looking back isn't the fifty number. It's that we took an insight from one product, rent payments feel impossible in one lump sum and manageable in monthly pieces, recognized it wasn't specific to housing, and got a working test of that idea in front of real customers within a quarter, with three engineers and a designer. That's the part I'd want another team to be able to do: spot where an insight generalizes, then prove it cheaply before asking anyone to bet big on it.

Skills demonstrated

Zero-to-one product development · KYC / risk & verification design · Vendor partnerships · Small cross-functional team leadership · Fintech domain