The message showed up on a Monday morning, the kind of morning that looks like every other one: coffee still too hot to drink, laptop not yet open, a group chat lighting up with a single link and one line, have you seen this. It was Tasco announcing that it had led a $500,000 investment round into BonBon, with GenAI Fund joining in. I read it twice, standing in the kitchen, before it actually landed. The number itself was not a surprise; I had seen an earlier version of it months before, as a line in a slide deck nobody outside the room was meant to see. Seeing it in public, with a byline and a headline, felt like a different kind of real. VietnamPlus picked up the same news not long after, which somehow made it feel even more real.
From the outside, a funding round reads like a single moment: an announcement, a number, a headline. From where I sat, it was assembled out of a long list of unremarkable choices that never made it into any press release. A login flow that has to disappear the moment it works. A session kept only in memory, so it leaves nothing behind if it fails. A kill switch feature flag you build hoping it never has to be used. A Playwright test written late at night for a screen almost nobody will ever see fail. None of that is dramatic on its own. It compounds.
What I actually built was the product integration that helped BonBon move from an MVP to a live field pilot in three months, and helped it stand in front of investors as a Top 3 finalist at Tasco x GenAI Fund's Wash3000 MVP Demo Day. Concretely, that meant architecting a twelve screen Mini App and getting it to run safely inside VETC's app, in front of 4.3 million existing users, with silent partner code login, deep links, serialized foreground polling, and analytics kept to a strict privacy allow list. It meant making releases boring on purpose: kill switches, deterministic rollout, transactional audit, checksum and CSP gates, over 800 unit tests, across a Go API, a backoffice, a web app, and mobile, all shipping together. None of that shows up in an investment announcement. All of it decided whether the announcement could happen at all.
I feel genuinely grateful for the chance to have been in that room, even as one of the smaller names in it. Grateful to a founding team who let an outside engineer touch their MVP at the exact stage where every decision still costs something. Grateful to Tasco and GenAI Fund, for building a venture builder model, Wash3000, that gives a small and largely unnoticed product team a real shot at a real pitch instead of asking them to already be big before anyone will look. And grateful to the teammates who caught the bugs I missed and asked the questions I had not thought to ask.
Working at this pace teaches a specific kind of engineering discipline that a mature product rarely demands in the same way. There is no slack to hide behind. Every release sits closer to a bet than a routine, because the team, the runway, and sometimes the entire pitch depend on it holding up through a demo, a pilot, or a due diligence call. It made me faster and more honest at deciding, with evidence rather than instinct, what genuinely needs to be bulletproof this week and what can wait. That is a skill built from judgment, not cleverness.
If you are doing the equivalent work somewhere right now, the login flow, the flag, the test written at midnight, the thing with no name that appears in no announcement, I do not think that work is small just because it is invisible. It is usually the reason the visible thing was allowed to happen at all. I did not need my name in the headline to know what part I played, and I do not think you need yours in one either to know what part you are playing. That is reason enough to be proud of it quietly, and keep going.