OUR STORY
(SO FAR)

building AI that understands a founder as a person, not just a user. · designing with an almost unreasonable attention to what it actually feels like to build for the first time. · building a cofounder. · momentum, and everything it takes to protect it. · earning trust over time, not just in the first session. · craft. · building AI that understands a founder as a person, not just a user. · designing with an almost unreasonable attention to what it actually feels like to build for the first time. · building a cofounder. · momentum, and everything it takes to protect it. · earning trust over time, not just in the first session. · craft. ·
01

tethr started because we kept running into the same wall, and we noticed that every founder we knew was running into it too.

02

both of us have ideas we believe in and the drive to see them through, but what neither of us could find was something that would sit down with us, understand our specific situation, and answer the most fundamental question a first-time founder faces with any real specificity: what to actually do tomorrow. the internet offers no shortage of frameworks. we found validators that score an idea, and ai conversations that are useful only if you already know enough to ask the right questions. every tool we tried gave us some form of output and then stepped aside, with no memory of what we had attempted or where the story had left off.

03

someone would have an idea they genuinely cared about, run it through the available tools, collect a set of outputs that felt reasonable in isolation. they would then find themselves in front of a blank document with no clear understanding of what to build first or why the next step was the next step at all. and yet the gap between having an idea and building something real was exactly as wide as it had been before any of that happened, because output is not direction, and direction is not the same thing as someone who stays and helps you follow through on it.

04

our mission is to close that gap, for every first-time founder who has had a real idea and no clear path toward building it. we are building the infrastructure for a world where ambitious people have access to something that has (until now) been available only to those lucky enough to know the right people at the right moment. a cofounder that understands the full context of their situation, executes the work rather than describing what the work should look like, and remains present for the entire journey rather than concluding its involvement the moment a deliverable is produced.

05

the deeper we go into building tethr, the more precisely we can articulate why this problem has remained unsolved for so long. first-time founders do not fail because they lack ambition or because their ideas are not worth pursuing. they fail in the space between knowing what they want to build and understanding what they should do about it today. no system has ever been designed to occupy that space continuously, with full context and genuine accountability across time. the knowledge that would help them exists. the patterns from thousands of companies that came before them exist.

06

we started building tethr because we needed it, and we kept building it because the more we talked to the people around us, the clearer it became that everyone in our position needed it too.

“output is not direction, and direction is not the same thing as someone who stays and helps you follow through on it.”

THE FOUNDERS
01

niranjan deshpande

university of washington

i have always been most drawn to the problems that exist because something genuinely valuable is accessible only to the people who already have access to everything else, and entrepreneurship education was the version of that problem i understood most personally. every program i wanted to attend had a price tag that made it impossible to justify, and the one that had figured out how to make it free had already shut down. so i built a replacement, starting with a pitch deck and no money, writing hundreds of cold emails that mostly went unanswered, and assembling mentors by showing up wherever the right people were and making the case in person. i walked up to a Meta product manager at a coffee shop, introduced myself, walked him through what we were building, and left that conversation with a mentor and a much clearer sense of what this could actually become. when the first cohort launched, students from countries i had never expected showed up and built things i could not have predicted, and not one of them paid to be there.

i believe that being priced out of an opportunity means losing not just that opportunity but every single thing that would have flowed from it, and the conviction that the highest-leverage thing you can build is something that refuses to let access become the barrier has shaped every decision i have made since, and the only honest test for what is worth working on is whether it would still seem worth the time if you imagined looking back at it from the end. i've also learned the labels you accumulate along the way have a way of making that question harder to answer if you let them grow larger than the actual work, which is why i have tried to keep the work itself at the center.

while launchology was running, i built and shipped stylematch, an outfit recommendation platform, and nothing i found anywhere would sit down with me, understand my actual situation, and give me a clear enough answer to what to do first that i could actually move on it. i had been sitting with that for a while when i reached out to daniel, who i have known since we were kids and who, unlike most people i have brought half-formed ideas to, did not immediately talk me out of it. when i walked him through everything i had been running into, it became clear somewhere in that conversation that he had been circling the same gap from a completely different direction, and that what we were both describing was something that had genuinely never been built. the founders who need tethr most are exactly the ones who have, until now, had the least access to what a real cofounder would give them.

02

daniel kwon

northeastern university

i came to building the way many people do, with more conviction than context, and the ratio has slowly improved. the years of attempting it, across businesses that found their footing and ones that did not, have been less about learning how to execute and more about understanding what actually determines whether something works, which turns out to be a question with a simpler answer than most of the conversation around entrepreneurship suggests. every business i tried to build fell apart in the same place or held together because of the same thing, and what determined which happened was direction, the kind specific enough to act on without spending another week figuring out the starting point. the businesses that had someone who could provide that kept moving while the ones that did not found themselves at the same wall every time. that gap is almost never what people name as the reason things fell apart.

what the version of entrepreneurship that lives on the internet leaves out is the texture of the months that determine whether something becomes real: what gets documented is the outcome, and what never gets documented is the weeks of sitting with a blank document after all the right advice has been received, trying to figure out what to actually do first, which turns out to be the part nobody documents. the businesses that made it through those weeks almost always had someone who could answer that question specifically enough to make the next step obvious.

the side of building i have spent the most time on is marketing and content, and the longer i have worked there the clearer it has become that a product earns its audience the same way it earns anything else, by being genuinely useful to the people who need it most and honest about what that looks like. the most direct version of the story is the only one worth telling.

when niranjan reached out and walked me through what he had been working on, i recognized the gap because i had been running into it myself for long enough to know that nothing had solved it (yet). we have known each other long enough that the conversation moved quickly to what it would take to actually build it, and the further we went the clearer it became that the founders who needed it most were exactly the ones who had always been furthest from anything like it. proximity has never been evenly distributed, and building something that makes that access available to the ones who never had it is the most exciting problem i have found.