Why an Immigrant Parent Built an AI Infrastructure Company

Published Feb 21, 2026 6 min read Nicholas Y., PhD

Founder Story Mission Community MyKidSpots

When my family moved to a new city, I expected the usual adjustment period — learning the roads, finding the grocery store, figuring out which neighbors were friendly. What I did not expect was how hard it would be to answer one simple question: where can I take my kids this Saturday?

That question — and the months of frustration that followed — is why Yapplify exists.

The Information Barrier

As an immigrant parent in a new community, I quickly discovered that the most useful local information was invisible to outsiders. Not hidden deliberately, but scattered across channels that assumed you already knew the right people.

The best playgrounds? Mentioned in a private Facebook group I had not been invited to. The splash pad schedule? Shared in a parent text thread I was not part of. The indoor play space that accommodated sensory-sensitive kids? Word-of-mouth from a neighbor I had not met yet. The pediatric dentist who was actually accepting new patients? A referral network I had no access to.

Google was not helpful. It returned generic results — lists of parks that existed but no indication of which ones were actually good for a toddler, which ones had working water features, or which ones were worth the drive. AI assistants were worse — confidently suggesting places that had closed months ago or inventing details about amenities that did not exist.

The information I needed was real, current, and human-verified. And it was locked behind an invisible barrier: social capital. You had to know someone who knew. If you were new, isolated, or did not speak the dominant language in your community, you were on your own.

What I Built First

The first thing I built was not a platform. It was not infrastructure. It was a simple app called MyKidSpots — a search-and-submit tool for parents to find and share local children's activities.

The idea was deliberately simple: remove every barrier between a parent who knows something useful and a parent who needs that information. No paywalls. No login walls. No social graph requirements. Just search what is near you, and submit what you know.

I built it because I was the parent who needed it. Every design decision started with a single question: would this have helped me during those first confusing months?

No account required to browse — because a tired parent with two kids in the car does not want to create a login.
Submissions accepted without verification delays — because the information is time-sensitive and waiting 48 hours for moderator approval defeats the purpose.
Simple categories and clear language — because not everyone navigating the app speaks English as their first language.

MyKidSpots was not a tech company. It was an empathy project — born from the lived experience of being the person the system was not designed for.

The Realization

Six months into building MyKidSpots, something clicked. I was reading about advances in AI assistants — how ChatGPT was evolving from a chatbot into a platform that could use tools, access external data, and execute tasks on behalf of users. And I realized something:

AI agents are going to need exactly the same information I could not find as a new parent.

When someone asks ChatGPT "find a toddler-friendly park with a splash pad near Raleigh," the AI faces the same barrier I did — the answer is not on the public internet. It is in group chats, in the heads of local parents, in word-of-mouth networks that no crawler can reach.

The difference is that while I eventually found the answers by making friends and joining groups over several months, an AI assistant cannot do that. It either has access to structured, verified data — or it guesses. And guessing is how you get hallucinated playground reviews and directions to parks that closed last year.

That realization is where the dual-native philosophy was born: one codebase that serves both human users and AI agents. Not as an afterthought. Not as a separate API bolted on later. From the ground up, every piece of community knowledge structured so that a parent browsing the app and an AI agent answering a question can access the same living, verified data.

The Outsider Advantage

My background is an unusual combination: systems thinking from Yale, and a deep admiration for the scrappy, builder-first ethos of Y Combinator. But the credential that matters most for what I am building is not on my resume.

It is the experience of being an outsider.

When you are new to a community — when you do not know the shortcuts, the right groups, the unwritten rules — you see gaps that insiders take for granted. The parent who has lived in a city for twenty years does not notice that playground information is trapped in a private Facebook group, because they are already in the group. The person who speaks the dominant language does not notice that community resources assume fluency.

Insiders build products for people like themselves. Outsiders build products for everyone else.

That perspective is not a disadvantage. It is the entire reason Yapplify approaches community data the way it does — with zero gatekeeping, minimal friction, and an assumption that the next user might be someone who just arrived and knows no one.

The Principles

Everything we build at Yapplify follows a small set of principles that came directly from that early experience:

"We don't build for the people already being served. We build for everyone else."

If existing tools work well for people with established social networks and local knowledge, we are not competing with those tools. We are building for the family who just moved here, the parent who does not speak the majority language, the caregiver who works odd hours and cannot attend the meetups where information gets shared.

Never gate information.

Paywalls kill the data engine. When you charge for access to community knowledge, you exclude the people who need it most and discourage the contributions that keep it current. Human access must always be free — not as a growth hack, but as a structural requirement for the system to work.

Community contributions should generate value for the community.

When Sarah reviews a playground, that review should benefit other parents for free — and it should also generate revenue that flows back to the local ecosystem, not just to a technology company in Silicon Valley. The Agent-Pays model exists because of this principle: AI platforms pay for structured access to community knowledge, and that revenue supports the people and apps that produce it.

Why This Matters Beyond Technology

Yapplify is an AI infrastructure company. We build developer tools, MCP servers, and federation architecture. But the reason we build these things is not technical — it is personal.

I remember what it felt like to stand in a parking lot with two small children, trying to figure out if the splash pad was working today, with no one to ask and no app that could tell me. That moment — the isolation, the frustration, the sense that everyone else had information I could not access — is the emotional core of everything we build.

When AI works well, it can be the great equalizer. A parent who just arrived in a new country should be able to ask an AI assistant where to take their kids on a Saturday and get an answer that is as good as what a ten-year resident would get from their closest friends. That is not a technology problem. It is a data problem — and it is a problem that only community-powered, human-verified, freely accessible data can solve.

We are building Yapplify so that being an outsider matters a little less. So that the splash pad question has an answer for everyone — not just for the people who already know.

If that resonates with you — whether you are a parent, a domain expert, or a builder who wants to turn community knowledge into infrastructure — we would love to hear from you.