AI Can Build It, But Can AI Ship It?

Speaker A: If I were to have to choose one, I would say the iteration cycles have become massively compressed. We don't want to start taking for granted, which maybe are being taken for granted, things like security and resilience and reliability and availability and. And again, these are some of those like core fundamental like underlying principles that make AWS the way that I like to think about it is like it's my little AWS like CTO on my shoulder. Right.

Speaker B: I didn't even know those terms to begin with.

Speaker A: Right, exactly. Yeah, right. And that's exactly it. You know, AWS now with over 200 services, it can be a lot for even experts. And so asking the startup advisor saying, hey, here's what I'm building here is presumably who the customer is, here's how they're going to access how I think they're going to access my software, help me plan out what I should be aware of from an AWS perspective, such that, you know, I am aligning myself to the best practices at aws.

Speaker C: Welcome humans to the Neuron AI Explained. I'm Corey Knowles here today with Grant Harvey. How are you today, man?

Speaker B: I'm doing good, I'm doing good. I'm excited to have this chat. Um, so am I. That's because starting a software company once required either deep technical experience or the resources to hire someone who had that. And uh, AI coding tools have kind of begun changing that equation and AWS is now extending the idea beyond writing code with Startup Advisor now, which is an AI powered assistant designed to guide founders through architecture, infrastructure, security, cost management and scaling decisions. And today we're joined by Deep ubi, Director of Global Head of Technology for Startups to tell us all about AWS Startup uh, Advisor.

Speaker C: And before we get started, please take just a quick second to like today's video and subscribe to the channel so you never miss an interview or one of our wacky live streams because we'd love to have you there. Deep, welcome to the Neuron. It's great to have you.

Speaker A: Yeah, it's really good to be here and thank you for the invite, of course.

Speaker C: Excellent.

Speaker B: So I'm basically your target audience. Uh, I'm a non technical founder using AI to handle the technical side for me as I've been building a bunch of coding stuff, kind of teaching myself how to code in the process. Um, but AI has made that possible when before I would have had to raise a bunch of startup capital or hire people who knew what they were doing. And I'm trying to build tools that I wish Existed that, uh, no one else is building. Um, so give me the pitch. How can you help me?

Speaker A: Yeah, I mean, so, um, thank you all for, again the time and thank you for mentioning in your preamble the AWS Startup Advisor that is here. That is what I am here to, uh, explain a little bit more to your audience about, to you about Grant and to really anyone else that is just interested in, um, taking an idea and really exercising their creativity and feeling unfettered from some of the constraints that existed in the past. As you mentioned, you know, having a computer science background, knowing how to code and then knowing how to do that at sort of a high fidelity and high quality thinking about things like, well, okay, if I put this out into the world, is it going to be safe for people to use? Are they going to get hacked? Are their accounts going to get hijacked? And all those kinds of things that come into consideration kind of once you're beyond the sort of proof of concept phase. And that is kind of like, you know, I, um, would say, you know, Corey and Grant, like the, the difference between vibe coding something that you and friends and maybe close peers can play around with and start feeling good about and developing a thesis around and taking something like that and then delivering it to a customer who is going to presumably pay you for that particular, um, usage or that software at some point in time in the future. There's a difference between those, obviously. And of course, if you have been in around startups, um, you very much understand that there's a journey that you go through, like you're going to show your close friends and your peers and then you got to take the steps to say, hey, I think I've got something here that I'm excited about that I'm getting good signal from my prospective customers about, and it's time to take this to the next level. That's where the Startup Advisor, I think, really comes into play here, where you could use a Startup Advisor from day one. You could use it to help you do a lot of that vibe coding in whatever vibe coding harness you know, of your choice, if you like to use cursor or Codex or Claude code. You know, the AWS Startup Advisor is available in every sort of coding harness that's available today. Um, and by sort of, you know, the way that I like to think about it is like, it's my little aws, like CTO on my shoulder, right? So I can hop on this little guy or gal and say, hey, look, you know, I really need help with authentication. Now, right. I need my users to be able to authenticate into this service I'm building and I'd like for them to basically authenticate with their, their Google workspace, uh, you know, aliases. So the Startup Advisor is really, really good at saying, okay, well, you know, here's what you want to consider when you're doing something like that. Here's how to do that on aws, by the way, if that's something that you want to do. And you know, we also have a plethora of third party technologies and partners that are big AWS customers themselves. The AWS Startup Advisor will also make recommendations across, you know, and is fluent in those technologies as well. So you get like a really good, grounded, um, you know, high fidelity, uh, production grade guidance from, uh, you know, a tool that is effectively codified, like all of the resident knowledge that, you know, internal experts at AWS have on building software for the broader, you know, sort of, you know, enterprise ecosystem, if that makes sense. Yeah, yeah, yeah.

Speaker C: Well, you've been a founder yourself several times along your journey. When you compare starting a company today with starting one before generative AI, uh, what do you think is the biggest difference?

Speaker A: If I were to have to choose one, I would say, Corey, it is. The iteration cycles have become massively compressed. Right. I think again, like you, you, you have to tip your hat and give all the credit to the coding agents. You know, Grant mentioned that that's something that he's been really like, toying around with and playing with and feeling empowered by. But because you're able to take an idea, um, to POC and that POC into the hands of a prospective customer, get that, like, rapid feedback, incorporate that feedback into the next iteration of your software. Like those cycles now are hours and days maybe, and not months and quarters and years anymore. That I would say is the biggest difference. And so what does that allow you to do? Well, startups are all about speed and what we call sort of time to value. So, like, how quickly can I deliver a wow experience to my customer? Like, that's a big thing in the startup world, right? Like what they call time to wow. You now can have many more at bats. Right? Before me, you had three or four at bats. You know, um, you're always thinking about your Runway. You're always thinking about, well, is this, you know, how many more months do I have where I can do this now?

Speaker C: Or you could swing twice a week now. Exactly.

Speaker A: Or more exactly.

Speaker B: I've had sessions where I'll, I'll be playing a game with my friends that I created and they'll be giving me real time feedback on it and I will literally feed it to Claude while I'm working on it and then it will update and it like, you know, the game will crash for a second and then it'll update and it's like, oh, there it is.

Speaker A: Yeah, yeah. And that, that's like, that is, I mean feedback in any form, you know, whether it's professional or personal, is such a gift. And so to be able to like take feedback and to do something about it, you know, it makes it more actionable. Um, that is the, that's the biggest difference Corey, that I see. You know, if I were to start a company today, you know, I would likely do it with fewer, um, people and I'd be very confident. I have many more at bats, you know, for the same amount of capital that I had available to me in a previous iteration.

Speaker C: Most people are only using about 5% of what AI tools can actually do. They open ChatGPT, ask a few questions, maybe write an email and that's it. Meanwhile, other people are out there building workflows, automations, research systems, custom agents and saving hours every single week.

Speaker B: AI is moving so fast right now that most people don't even know which tools are worth learning anymore. ChatGPT, Claude Gemini, Codex, AI agents, Automations 5 coding. It's a lot.

Speaker C: And that's exactly why we built the Neuron Academy.

Speaker B: We built a practical, self paced AI learning platform that helps working professionals like you understand the tools that actually matter and how to use them in real work.

Speaker C: Built by us, the team behind the Neuron newsletter and the podcast, designed to help busy professionals actually level up their AI skills.

Speaker B: Inside you'll learn prompting AI workflows, research systems, automations, productivity strategies and practical use cases across the entire AI ecosystem.

Speaker C: Everything is hands on, beginner friendly and built around real world use cases. You can apply immediately.

Speaker B: These are real skills that help you work faster, think better and stay ahead in AI.

Speaker C: Right now you can join Neuron Academy for just $499 a year, unlocking 50, 50 plus lessons. From full AI courses to quick hit micro trainings you can apply immediately.

Speaker B: So if you're serious about leveling up your AI skills this year, this is where you need to start. Join the Neuron Academy today.

Speaker C: You can literally now go from, you can have an idea dummy, uh, out a quick plan, have it in a prototype that's hosted and be getting that feedback you're talking about, you know, before bed. That's the Craziest thing.

Speaker A: Exactly. That's exactly right. And I think that this is kind of where I think there will continue to be ongoing debates and like, healthy dialogues around this, you know, well, what does that mean, you know, for, you know, the shape of workforces in the future? And you know, like, are engineering teams going to shrink and are we going to, you know, uh, and again, like, I don't have a crystal ball. What I can tell you is that, you know, there are two things. One is, and I'm sure you guys have had maybe conversations around this on the pod, or maybe other folks have mentioned this to you, but there's a sort of like this like, new skill or capability that's being highly valued and touted in the Valley, which we're calling taste. Right? Which I think is a new moniker for like, hey, do you have a sense of like, how to create a really, really good end user or developer experience? And that's again now moving away from the world of like, purely thinking about it in the frame of a GUI to like, can I have like a really good conversational experience with an agent? Right. And is it going to say the right things? Is it going to have the right tone of voice? Is it going to have like the, is it going to understand sort of like, you know, the, the right terms in the conversation? Like all those things are like, now, like new experiences that you have to have good taste around? I think that's still going to very much be a human endeavor. And I think the second thing is like, you know, Corey, you were mentioning how in a day before you hit the sack, you could get multiple at bats and basically try multiple iterations. Yes. And I think that there's going to come a point where you're going to feel really, really good about the ongoing commercial viability of what you're building. You're like, okay, wait a minute, I need to turn this into a business now. This is actually becoming a thing. That's when you really need to be very, very thoughtful and intentional about maybe some of the things that we don't want to start taking for granted, which maybe are being taken for granted. Things like security and resilience and reliability and availability. And again, these are some of those core fundamental underlying principles that make aws, AWS right and Startup Advisor just for that reason, because it's got all of that as like requirements, right? Like, I'm going to help Grant and Corey build what they're going to build. And at the right time, I'm also going to make sure that Those underlying key, like foundational principles that make software durable and usable and commercially viable. Like, it is an expert at that. Right. And those things that, again, like vibe coding platforms are amazing and empowering and enabling. And at the same time, like, you want to make sure at the right time that you have that, you know, the guidance from what we call, like the neck beards, like we used to call it the sre that are in the basement. Like, they know where all the bodies are buried. They know precisely how to make sure that these applications stay up, that they are, you know, secure. They're not going to get. So anyways, like, that's, that's a very important aspect of like, going from.

Speaker B: And that's the stuff that you don't know. Like, you, like you might have your own product taste or your own, uh, opinions about, like, the actual user experience, maybe even the agent experience. But as a, you know, gentech, uh, engineer who's just doing this for the first time, Vibe coder, you know, you don't necessarily have the priors to know that information.

Speaker A: Totally. Yeah.

Speaker C: Well, you know, and what's nice now is that it sort of flips the paradigm a little because previously what you would have done is you'd have had an idea, you'd have gotten with some people, you'd have talked through it with people who knew things you didn't know. And then you'd have been like, we need to hire a developer. You go and you find a developer, you find an engineer, and then you get on their queue and you give them a lot of money and you wait only then to find out your product sucks. Uh, but now what you can do is have an idea, dummy it out and find out if anyone likes your product, and then go find an engineer and then go find a security person and invest after you have an idea of whether people are into this.

Speaker A: This is a thing 100%. Corey. Absolutely right. Because I think, you know, I think anyone who is thinking about building a business and thinking about building software, I'm sure we can rally the support of a couple of dozen friends and acquaintances that kind of mimic the ICP of the customer base you're going after. That is probably not the constraint. And that not being the constraint, to your point, Corey hugely enables this early iterative cycle. M. I can't imagine a better time to be starting up than right now. Same. Yeah, I mean, I think the things that obviously you have to think of are the things that we don't talk about enough, which are, you know. Well, you know, can you float your rent or your bills or whatever for time, and, like, you know, are you going to put your family through undue strife? Those are things that I think are really important. We don't talk about those enough. I wish we did. Um, but if you. If you are in a place where you can take a risk for some finite period of time, um. Boy, you're really going to have a lot of opportunity and attempts, many, many attempts at getting something right and pivoting and, like, you know, you're just. You know, I think there's a quote. I think they attribute it to Louis Pasteur, but, like, they say that, you know, fortune, uh, favors the prepared, and it basically means that, like, you have to put yourself in a position to get lucky. Like, talk about how crazy it is right now where, like, how many times can you put yourself in a position to win the lottery? You know, there's like dozens and dozens of times a month where you're just, like, trying new things. And it's just. It's. Yeah, it can be a bit addictive, too. You know, it is totally all.

Speaker B: I mean, we were just joking.

Speaker C: Grant, between us, how many of. How many things have we built this month?

Speaker B: Oh, well, I, uh. Mean, I've been working on stuff for a little bit longer than one month only, but, I mean, between the two of us, like, it's.

Speaker C: We.

Speaker B: We have 15 projects that we are developing at various stages. Um, but I was going to say, to your earlier point, the iteration, uh, timeline has condensed. But also, I feel like the urgency of focus has never been more important because it is so easy to get sidetracked on side quests and, like, oh, we can develop this. We can develop that feature. That's the new challenge, I think, is how do you stay focused?

Speaker C: And right now's the hot time, too, because right now, not everyone realizes they can do this yet. Like, a couple of years from now, everyone you work with is going to be doing things like this, and it's

Speaker B: not everyone starting a business, but definitely making their own software to solve their own problems. Yeah, 100%.

Speaker A: Totally.

Speaker B: Yeah.

Speaker A: And, Grant, I think you hit on a really, really important point there, which, again, is, like, the very necessary human input to this creative process, which is now an exercise in whittling things down. And, like, how do you eliminate some of the ideas? Right? Like, you've got all this stuff. You guys have 15 projects that you're working on, like, which ones are worth your, like, extremely valuable time going forward, you know? Um, and not being in a place where you are putting out a bunch of above average things. But, like, how do you get to a place where you're maybe one or two products and projects or software that, you know, what we call here? Like, you know, you might have heard the phrase, like that have a right to win, you know, like, yeah, you are uniquely positioned to bring to market. You are uniquely positioned to evangelize, uh, you know, to your customer base. Right. Like, that then becomes a very human judgment, intentionality, input into this process. And that's. I'm so glad you brought that up.

Speaker B: Totally. No, totally. Um, I do have one, One question, which is, okay, so imagine me, I'm using Claude code. I'm building, you know, like we said, like, between Corey and I, we're both building like 15 things. Um, how does Startup Advisor fit in? Do I go to it before I start coding a session? Do I go to it, hey, I have this code base on GitHub or whatever. Can you take a look at it or. Right. When I'm ready to deploy on AWS or wherever else. When do I actually bring Startup Advisor into the process?

Speaker A: Yeah. Yes, again, we'll go through that hypothetical example. Um, Corey and Grant. So you're using Claude code as your coding harness. Awesome. So do I. It's amazing. Um, and, um, you know, you can go to, um, the AWS Startup Advisor, um, you know, webpage on aws. I'm happy to share that or maybe put that in the POD notes at some point.

Speaker C: Yeah, we'll do that.

Speaker A: Yeah. Um, uh, and again, you're going to be redirected to, uh, you know, an anthropic page where you can download the aws, uh, Startup Advisor agent plugin. So an agent plugin, in Claude code parlance is just like a collection of underlying skills. Right. And the skills are again, um, sort of these acute capabilities that the, um, Startup Advisor has right across a number of different sort of vectors. Security authentication, observability, migration. If you're migrating from like, you know, an existing thing that you've built it in and you want to come to AWS and so on and so forth. So it's got a number of these different skills. And again, the skills are all, again, sort of codified from, you know, expert humans at AWS that are in the field with customers and have done that precise work and have, like, understood the best practices and have like, basically built that into the AWS Startup Advisor agent plugin.

Speaker B: Awesome.

Speaker A: So once you're in Claude code and you've installed the agent plugin, um, as I'M sure you're aware, like, you can invoke that plugin at any given point in time. Right. Like within, like just the natural language prompt, you'll be like, typing stuff in and you might say, hey, Startup Advisor, like, within the context of this current thing I'm trying to do, you know, can you tell me if, you know, there are any, you know, security implications I need to be aware of from an AWS perspective? And so invoking it is just like invoking any other agent plugin or, um, uh, you know, skill within even a skill.

Speaker C: Yeah.

Speaker A: Whatever coding harness you're using. Um, so it's very much like just, you know, invoke it when you need it, but it's. It's not, it's not something that you need to be in constant contact with, like, in the sort of course of like your, your coding session. Right, Grant? So like, you'll be sitting there writing and you're doing stuff and you're talking in natural language. Claude code is outputting either code or terraform or whatever it is, you know, application code or infrastructure as code. Um, and then within any of those, like, sort of conversations that you're having with Claude, you can just invoke the Startup Advisor to give you that sort of like, AWS specific context.

Speaker C: Yeah.

Speaker A: And that's how I use it. That's how most of the folks that have downloaded use it. Um, yeah.

Speaker B: So have it help you set up if you want to do S3 buckets or stuff like that. That's AWS specific. Totally.

Speaker A: 100%. Yeah. Yeah, absolutely. And again, I think where it's more useful. Yes. For those acute things as well, like, hey, can you please help set up, uh, this S3 bucket with this IAM policy? Um, I think where it's more useful, though, is even left of that, like, helping you plan. Right. So, like, think about the planning phase, which is like, hey, this is.

Speaker B: I don't even know those terms to begin with.

Speaker A: Right, exactly. Yeah, right. And that's exactly it. You know, AWS now with over 200 services, it can be a lot for even experts. And so asking the Startup advisor saying, hey, here's what I'm building here is presumably who the customer is, here's how they're gonna access. How I think they're gonna access my software. Um, you know, help me plan out what I should be aware of from an AWS perspective, such that, you know, I am aligning myself to the best practices at aws. And so it'll do the planning for you, and then really up to your, you know, how you work and how you kind of like vibe code. Like you can do it in one shot, you could like do it over many days. You could have it like execute, you know, you know, autonomously. So there are just different ways and like, that's very much a personal preference. But yeah, I mean, I actually think that it's very helpful in the planning phase as well.

Speaker C: At its core, we're talking about having your own little, uh, AWS consultant and engineer, uh, checked right into your harness, which is great. And it works with harnesses other than Claude code. Correct?

Speaker B: Do you say it does.

Speaker A: It works with Cursor, it works with Codex, you know, VS code plugin. It works with Kiro as well, which is, you know, the aws. The AWS one, yeah, yeah, Coding harness. And so.

Speaker C: Well, great logo by the way. I just want to high five on, uh, the branding of Zero.

Speaker A: The brand is, uh, you know, it's, you know, another 30 minute pod. I think they did an amazing job with the brand.

Speaker C: Yeah, they did, they did, they did. Well, Deeb, thank you so much for joining us today, man, this has been fascinating. We're going to have a link below where anyone who wants to can go check out AWS Startup Advisor and get it downloaded into their harness and go to town.

Speaker A: Thank you, Dee Dee. Thank you so much for having me, guys. And yeah, happy building.

Speaker C: Absolutely. Where can people keep up with you if they want to?

Speaker A: Yeah, I, uh, you know, I'm on X, uh, you know, at Deep Booby and I'm on LinkedIn as well. You can find me. My name is somewhat unique. Uh, you know, I realize that when people see the Deep, they think of like, you know, is this the suffix and prefix of a traditional Indian name? The answer is yes, it is. But my dad grew up in the 60s. He was a bit of a hippie, so he just changed the spelling and that's why it's got a kind of a wonky spelling, but it's.

Speaker C: I love it.

Speaker A: Yeah, D, E, A, P and it's easy to find me on LinkedIn or X.

Speaker C: We'll make sure and have your Twitter and LinkedIn links in the description below as well. If you're watching and haven't yet, please take just a moment to like and subscribe. Make sure you also pop over and check out the Neuron Academy M, our latest offering where you can learn all about AI, especially if you're a working professional and still finding your way through the, through the maze that we live in today. And on that note. That's all we have for this afternoon. So farewell for now, humans.