This is a YouTube video titled "Copywriting and problem awareness stages #buildinpublic #startup" containing a monologue-style daily update from June 19, 2025. The speaker discusses improvements in onboarding a new developer, experimenting with AI tools for lead sourcing and cold email campaigns, templating GitHub repositories for client scalability, and elaborates on the concept of stages of problem awareness relevant to AI product development and customer education. The content is a single-speaker update without conversational interaction.
Build in public daily update today solved a couple problems and started onboarding a new developer. So that was really great. I think we tightened up our onboarding process. I also started looking at the problem of sourcing new leads and I'm using instantly AI for that. I don't know if I have a definitive recommendation yet, but it will allow me to test more cold outbound email campaigns and AB test things such as the copy first line, second line, third line, etc signatures, even the, you know, everything you want in an email subject line too. So that's gonna be good because then we could really figure out positioning and conversions based on copy. Another problem we solved was figuring out how to template GitHub repos so that when we take on clients, our throughput could be really high, meaning we could fulfill many clients at once. So we figured out what are all the touch points in the customer journey for getting client value and things like, oh, we probably need a terminology sheet because there's some level of education required to do the AI, you know, user centric evals work or even just application centric evals work. So lots of terminology like AI alignment, TPRS, TNRs and then simpler stuff like hallucination rates. And so just every touch point of when we bring on somebody new as a customer, how aware are they of the problems that we're solving that they have? Right, because there's levels of problem awareness. Step one, for example, let's say you're about to go running. Step one, I probably need running shoes, huh? Maybe I should be eating different. Gatorade is something I might have heard of that runners do, you know, like that's problem awareness. Then maybe you go to the store and somebody helps you out. You buy running shoes, you get fitted. You don't know what kind of running shoes to buy, there's a lot. But you get fitted and you get some recommendations that electrolyte drinks are good for you. So then you'd solve that problem and you'd run your first few miles or whatever, right? And then you were sore. So then now you're aware of another problem which is you get sore, so what do you do about that? And then maybe lacrosse balls for massaging or theraguns or whatever. Right? That's what I mean by stages of problem awareness. Same thing applies for an agentic builder or product manager that's building an AI or developer building an AI. There's different stages of problem awareness of oh hey, my thing hallucinates. Okay, well like then you're really trying to fine tune your rag and you're evaluating your retrieval step. Right. That's a whole different level of problem awareness. So that was really good to go over. Anyway, that was it for today. Have a good one. Bye. Bye.