19. Marsha Battee on Building A New Platform from an Idea

Welcome to The Bossy Nurse Podcast, a show about nurse creators, innovators, risk-takers, and the ideas that shape their success.

In this first episode, Marsha Battee shares six lessons from her first week of building a new platform-- including why expertise must lead AI, simplicity protects the vision, and trust belongs in the foundation. 

Find the all the resources mentioned in the show and full details at The Bossy Nurse website.

Transcript

Welcome And Series Mission

Marsha 0:00

If you're interested in learning some lessons about building innovation from ideas, welcome. If you're new here, I'm Marcia Batti. I'm the host of the Boston Nurse Podcast. And I am creating a new series called Building Innovation from Ideas. And this is one of the first episodes of that series. And I have a lot to share. So what I'm going to be sharing is what I'm building from scratch, what I'm learning building from scratch. And I'm hoping that you can take some of the lessons that I have and apply them to what you want to build and how you can make an impact yourself, because that's what I'm striving to do, making an impact. So welcome to this particular episode. I'm going to give you a little bit of backstory about my ideas and where I'm going with them. So nobody in my community thus far, we are August 2026. No one knows about this yet. And so I wanted to give you a little bit of backstory behind that.

Why I Paused My Own Work

Marsha 1:09

And for the past couple of years, I stopped creating. I put down my own writing and I put down my podcast back in the past. It was a different podcast title from this one. And I was doing some things beforehand, but I stopped because I decided to help a colleague build something from an idea. And I gave it real time and real attention, which meant for me that all of my work sat still for a moment. And I was willing to do that. It was something that I was excited to help someone else build on their own as well. So in the summer of 2025, though, I decided I wanted to get my own work back. I decided that I wanted to start again on something where I could make an impact myself, not because the other project was bad, but because I actually missed the actual work of making something out of nothing or creating something.

Thinking Bigger With Scaling

Marsha 2:07

And so in the summer of 2025, I happened upon a book called The Science of Scaling, and that's by Dr. Benjamin Hardy and Blake Erickson. And I did a book club session on it with the Bossy Nurse Book Club. And I'll make sure to drop the link to that in the show notes so you can learn some of the lessons that I did from reading this book. But I'm going to talk about a few of those lessons here and some of the lessons I'm learning building something from scratch right now. So it taught me something. This particular book taught me something that I really did not expect at the time. And the book made me realize in the summer of 2025, when I started to think, hey, I want to start recreating something. I want to start writing again. I'm going to start a podcast again. Made me realize that I was thinking way too small about my impact that I wanted to make. So I wanted to make a bigger impact, but I was designing something the size of a small side project. So their argument in the science of scaling is that small goals let you get there doing what you already know, just doing more of it. So if you do a small goal or have a small goal, you can accomplish that goal probably fairly easily because it's something that you already know. You're not having to learn extra things to make it happen. So nothing really actually changes. A goal big enough that scares you a little is the only thing that will force you out of that box, out of that side thinking, and make you or force you to work differently or think differently. So that's the major lesson that I've learned in the science of scaling. And it's the major lesson that I'm taking forward on with me on this journey of building something from scratch. So I sat with it took me about a year to land on what I actually wanted to build. And that's not to say that I was really hesitant in building. I was not. I wanted to really build something that would make a difference, I felt, in the lives of nurses in particular. And this is just how long it took me to actually think process. Now, if you know me as the start before you're ready type of person, I will start any project before I'm ready. I will hit publish on 80% done. I will go ahead and get started before I've actually figured it out. I'm a risk taker in that sense of a word. So things that scare me, that really excite me, I have no problem or issue taking action on it if it's something that I really want to do. So again, it wasn't about hesitating. It's just that it took me that long to actually process and think through it properly. So now I'm building it. I started at the beginning of

A New Nurse Platform Begins

Marsha 5:20

this month. So this is August 2026. I started right at the beginning of this month. We're about a week and a couple of days into the month. And what I'm building, I'll just state shortly. It's a platform for nurses, and it lines up with directly what we share here at thebostonurse.com. So the Bostonurse website, the Bostonurse podcast. It's all about helping nurses own their careers, expand their incomes, and build thriving businesses. So although I'm not going to share exactly what it is just yet, and I will moving forward, I'm just going to share the very tip of the iceberg right now because that's where I am. When there's something to share or show, I will do that. What I want to talk about today is what the first week of actually building it has taught me. So I'm building it myself. Well, I'm building it with the help of AI. So I'm not a developer, although I did take a full stack website development course and I got a certificate in that years ago. So I'm pretty okay with figuring out language in terms of speaking and understanding the code language and where things may go or why things work the way they do. So I can figure that out. I don't code every day or do coding work every day. I've never worked in any engineering job or anything like that. I my the breadth of my professional career has been nursing. Although I do consider myself pretty technologically savvy if I have to figure things out. So I'm using AI tools to write the code, and I'm the one making decisions about what gets built why. And I think there's a lot of confusion about building things with AI right now. People think that AI is building everything for you. But yes, AI can build a lot of the work. However, you need to have the knowledge, the skills, the expertise to put the right prompts in to help you build what it is that you want to build. So I just wanted to say that. And I also want to point out that the thing that I'm doing right now, the building aspect of it, it's fun. And I forgot how much I actually like it. So this is part of the process building from scratch, building something from an idea, building innovation from an idea, just from just a small spark that you may have. So this is the very first episode of this new series, Building Innovation from Ideas. This is about the early lessons that I'm learning and building. And I hope to continue this series to talk you through the whole entire process until it actually gets fully built. And I'm doing this one, as an accountability tool for me. So if I'm telling you I'm building something, it's going to keep me on track and help me continue to do this. And especially if I publish this episode, which I definitely will, it will keep me accountable. And two, I just want a place where I can document what I'm building so I can come back to it later and see what it was like in the early days of building versus what it's like in the later stages of building. I'm going to tell you about six lessons in this particular episode. It's not from the book, The Science of Scaling, but they're from my own lessons of building, not from the theory of it. So building from the last seven days or the last week that I've been working on this particular project in the actual stage of building it after I've done the thought, the research, things like that. So let's start with the lessons that I'm learning.

Lesson 1 Start With Expertise

Marsha 9:00

Lesson number one, you want to start from what you already know. If you're thinking of building something, I think the best advice you can have is starting from something you already know. Every time I wanted to start something, the thing that stopped me on a lot of the ideas that I've had in the past is that I didn't have the list of skills that I needed to build that thing. I tell myself I needed to learn this part of the process, this history about this process. And then I never get started because there was so much I had to learn before I can actually put anything on paper, put an idea on paper. It just took a lot of research and a lot of work. But what I found out is that the technical part is not necessarily the hardest, the hardest part. The hard part was the part I actually already knew how to do. So the hard part is knowing the that you have the skill, knowing that you have the experience, knowing that you have the expertise to build something out, that's the hard part of building it out. So I think if you can start from what you already know, it's going to help you tremendously in this process. So the single most important day of this build that I have so far in this about a week span of time is the day where I wrote zero code. I sat down and I wrote out every question the platform would ever ask a nurse and every answer she's allowed to give it. So nobody could have done that for me, not even AI, even though AI can do a lot of work and a lot of research and a lot of context. AI is great. It's only going to get so much better. But the nuances of the work that you do or something that you're building, it's great when you have the actual history. So no one could do the work that I did on that day where I'm not building anything and I'm just building the strategy behind it. So not a developer, not a consultant. It required knowing what nurses actually do and what units are called, what floors or units are called, what certifications exist, and who can actually hold those certifications and who can't. So that's a part of the process. I'm starting from what I already know. So that one day, just for an example, that one day produced about 16 categories and about 820 approved answers. So the specialty list that I'm, you know, creating about 94, whereas the code is telling me or using AI is telling me, oh, it's about 40 or 60. And that's not correct because AI still doesn't know the nuances just yet. So in building a specialty list, I built 94 on purpose because I know how a different, how different a cardiac ICU nurse is from an NICU nurse, right? We know those nuances. You know the details as a nurse, know those different structures that AI may just not be able to figure out just yet. And a generic list that AI came up with for me would have flattened all of that out and would have left behind a lot of things that I needed to build this particular project. So your knowledge, your experience, your skill, your expertise is not the thing standing between you and building something. It's actually the thing that's going to help you the most. And you need that from the very beginning. It's the part that no one else can bring. And oftentimes it's going to be the part that not even AI can touch, especially the human aspect of it. So that's lesson number one. Start from what you already know.

Lesson 2 Cut Until Simple

Marsha 12:57

Lesson number two, cut it until it gets simpler. And I learned this the hard way in terms of time. I was married to a concept that I had too many moving pieces to. And this one is this lesson is out of the science of scaling. So their point is that growth comes from taking things off your plate and not piling more things on your plate. And they use an example of Steve Jobs and how at Apple he cut around 350 products down to about 10 products. So I didn't believe that particular thing applied to me because I didn't have 350 ideas to fit into this one platform or product that I'm building. But when I started to write it down on paper, I saw, yeah, this is way too big for what I'm trying to do. On paper, I had six different products and about nine different ways the business could make money from those six different products. All of them could be good ideas. All of them were good ideas. And that was the problem because I had limited time. It's just me. And this is something I wanted to build myself. So I have about 15, 20, 25 hours max a week that I had to design something that really needed a team of people designing. So I cut it. And six products became three. And nine revenue streams only became three revenue streams. And so those three things fit together nicely and they complement each other in one type of product. So cutting it didn't just make it smaller, it made it better and easier for me to work through. So when I collapsed three things into one, I found out two of them were secretly the same thing, but I could not see that while they were separately sitting in different boxes of nine different things or nine different ways to make money from these six different boxes. So in real life, I cut again some things a little bit later. I had planned, for example, like a paid subscription tier. And I did the math and it did not work. So I removed it before trying to even write a simple or write, quote and quotes, a simple line of code for it. So doing that dilution also removed an entire set of legal rules I would have had to follow in about half the states. So that took a huge piece of work and a huge cost, legal cost, out of the whole picture for me. So every cut I think you do will buy you something, buy you time, buy you energy, buy you additional resources that you didn't know that you would probably appreciate later on in the process. So lesson number two was cutting it until it got simpler.

Lesson 3 The Not Building List

Marsha 15:58

Lesson three, keeping a list of what you're deliberately not building. So your idea list will grow on its own. Nobody has to help it grow. You, if you're anything like me, you'll keep having the ideas about what you think is about this one product. But when you really sit down and think about it, it's expanding the scope of the product that you're trying to just build simply. So a not building this list has to be written on purpose, or it really doesn't exist because then your ideas will keep expanding. So scope creep is something that we want to keep out of the process. I keep having good ideas, and every single one of the ideas I have about this particular product that I'm trying to build, this platform that I'm trying to build, it keeps distracting me from what the purpose should be. These three solutions wrapped into one major project that all complement one another. And so I have a list of things that I've decided not to build. I'm not going to build them later. I'm not going to build them in a second phase. I'm just making it simple. So the solution is simple and someone can easily tell what that solution is. And when you write your list of the things that you're deliberately not building, you want to write the reasons next to it. So the reasons will help you as you move along. The reasons almost matter as much as this decision not to keep those things on your list will. So, an example, things on my not building list right now, no social media run by me in any way. And I know a lot of people will say, Marsha, that is not the right way to build something. But for me, it was very important in my build to have social media off my plate 100%. That's not to say that I will not use social media or in the future get people to help me use social media to collaborate with me on that. And all in a relatively inexpensive way is what I have planned. That's not to say I'm not going to use social media, but social media, it has to be something that I can do. And social media is not it. That's not on my list to build. No messaging back and forth, no job boards, no course library, no courses, no community forms right now. Every one of those things needs a crowd before it can become useful. And if you have an empty version of those things, it teaches the people who come to your platform or come to your website that nothing is really there because you needed a platform of people to make it look active. So I deleted a lot of things from my list that I felt weren't important and probably won't be important in the long run. I also deleted pieces of information I had planned to collect. So if no part of my business was actually going to use it, it should not exist. For example, the platform that I'm building with nurses on that platform, employer names where they work is not really important. It would have been useful for me in a certain way, but it's not really important for this particular thing that I'm building. And it could have put a nurse's job at risk. Now, true, these things are already on LinkedIn. Nurses put their whole resumes on LinkedIn anyway. But is it important for my platform? No. Is it useful? It could be, but it's not important for my platform. So I decided simpler is better. It's gone. One thing that I don't need to put on my platform. So if you are building right now, one thing I would say that you could probably try is write down your not building list this week. Something that you know you're not going to build and put the reason next to each one of them because your future you may not remember why you decided not to build it. So make that list deliberately. Things that you will not build because they're going to waste your time. They're not going to make the product any better. And because it will probably likely save you money as well. So that was lesson

Lesson 4 Foundation And Tech Stack

Marsha 20:31

number three. Number four, getting the boring foundation right before you touch any of the fun part of it. So that's very important for me. The stuff that looks like the product is the stuff you actually want to work on. So it may be like the website, the logo, the pretty parts of what you're building. Those are the fun things that you can't wait to get started on, but that's not the important thing. So the decisions that are the cheapest to make are going to be making it at the very beginning. And these are the most expensive things to change at a later time period. So I'm making myself, I'm forcing myself to build those boring parts first. And because those boring parts that need to get built, if I decide to build those boring parts later, it's going to take me more time and energy. And if I screw up on those things later, when I already have people on a platform, it's just going to be more expensive. So what I've decided to do is use a lot of someone else's official standards instead of making up my own categories for things. Think of things like federal facility codes, like if it's a nursing home versus a hospital versus a home health agency, using actual certifying body. Codes like AACN or any of those organizations that certify you and different specialties or anything like that. So a lot of the values that I used in building this thing are coming from things that are already standardized and out there in the public forum for me to use. And they're free. I don't have to pay to use these things. So that's part of getting the boring foundation right. That's part of making sure it's built the right way from the very beginning. Those things that you may not want to do that are tedious to do, that takes a lot of time and effort and thought behind it, that may cost some extra hours in the very beginning. And with AI, it's actually a lot easier to do. But it means anyone technical who never looks at it can recognize what I built because there's a standardization behind it. And they're not just trusting my word on categories or facilities or things like that. It's something that's already been standardized. So that's part of getting the foundation right from the beginning. Another thing I want to mention, which I think is huge in this space of building something innovative from just an idea, is your tech stack. And so your tech stack is basically just a list of tools that you use to build something. So it's the same idea as saying I use Canva for my graphics or Google Docs for writing or Google Workspace for my Gmail. So that's a stack of something, right? It's not complicated. I know it probably may sound complicated, but the tech stack that I'm using, and I've had to use a lot of different tech tools in this process of building this in the past seven days. But I've done the research or I've had AI help me do the research on what are the most cost-effective ones. And mine, for the most part, are all free tiers that I won't have to spend a lot of money on in the near future at all. Even when I have people on the platform, a lot of the things that I'm using are free. And these are very good tools that people use in the tech space and the building space and the engineering space every single day. The framework the site is built on that I'm building on, free. The database that holds information that nurses will need to enter, free tier. The hosting platform that puts this website on the internet, it's a free tier right now in the moment. When I start to use it, I have a couple of dollars. The service that sends emails on behalf of my website, login, yes, you're logged in, those kind of things are, you know, reset your password, those kind of things, free tier. And analytics, free tier, forms free, password manager free. So all of those things are free. And that's part of building the foundation that makes you build a tool that's cost effective, helps you save a lot of money. And so when it's time to spend the money, you didn't spend it all up front. Two of those free tiers that I'm using become about $25 a month once real people are on the platform. The only money I've really spent so far is the money I typically spend for my AI use. Right now, I'm using a lot of Claude Code and ChatGBT, and then other smaller AI tools from here now and again. But Claude Code and ChatGBT OpenAI, and those are the tools I'm using so far. So with all of those free tiers and one that's paid, I think I spent outside of Claude and outside of Chat GPT about $11 to $15 building this thing. And that's again, that's the databases, the analytics, the email sender, all of that free tools that I'm using, free tech stack, pretty much. So this is the part. So that's the part that I really want you to take with it. If a tool is going to cost you money, you should be able to say exactly when and exactly how much you pay for it before you start to commit to that tool. So you want to think about okay, not only how much it's going to cost me right now, but once this whole thing is built and in the future, how much is it going to cost at that point? So a really easy example to think about is an email service provider. So if any of you have built businesses, you may be using an email service provider, whether it's Kit or MailChimp, any of those Flowdesk for email. You know that there's sometimes free tiers or low-cost tiers for a limited number of subscribers. Say, for instance, you have 50 people in your community on your email list. You may be using a tier that costs you no more than $20 a month to send emails to those people every month, weekly, monthly, however you send them out. But you should still take into account so what if this platform grows to 20,000 people, 100,000 people, a million people? Am I still going to be spending that $20 something dollars a month to send that same email that I would send at 100,000, a million people on my platform? No. So it's very important when you're researching those, your tech stack, to take in account the cost now and the cost in the future state as well. So that's number four. Getting the boring foundation pieces right before you touch the fun part, that can save you a lot of money.

Lesson 5 Build Trust First

Marsha 27:57

Lesson number five, build the trust in at the very beginning because you can't add it later, and it will actually hurt you if you try to add the trust in later. So this is the part that I really care the most about on my platform and building a platform is that, and that this is a part that's actually slowing me down the most, but it's the most important to get right. So what I'm building holds professional information about nurses. Granted, again, this information is the same information you will find out about a nurse on LinkedIn. So, but it's not patient records or anything like that. Real real information about licensed people. Yes, you can find it other places on the internet. But if I get things wrong and holding this professional information about nurses, I don't get to like really apologize about it after the fact, right? Because that's when lawsuits happen and things like that, right? So you can add a feature in month six and not be concerned about the permissions that you need for that feature until month 12 because you didn't think about it ahead of time. That will cost you, right? So you can't go back and get permission from people when you've already collected that information and that information has already been compromised. That door is already closed. So the permission structures, the consents that you need to use people's information. You have to think about the security of that way up front. And that's what I'm doing right now. I'm thinking about permissions, I'm thinking about consents, I'm thinking about all the things that people need to give me permission to use their information. Granted, again, it's already out there on the web and on LinkedIn, but you'll see the same type of information on this platform. But there are permissions that you need to set, conditions that you need to set it first. You need to look at your privacy policies, your terms of service, things like that. So the permission structure goes in for me before the product does. The privacy structure goes in before the product's product does. So in my instance, I'm using like permissions for three separate things and keeping a record of when we're given permission to use those things. And the rule that under is underneath that is saying that it doesn't cost the nurse to deny permissions for certain things versus a nurse who's giving all permissions for certain things. And so we didn't want that to be a distinguishing factor on whether or not a nurse is afforded the opportunities that one nurse is over another. So just because a nurse says, no, I don't want to give you permission to use this particular thing about this product, versus another nurse who says, no, you can have all of my information to use about this particular product, they still will have the same opportunities. So I'm building that in from the very beginning because a permission structure should not be a limit on how a nurse receives opportunities. So that's very important to me. So an example, another example in this particular platform that I'm building, home zip codes is something that we'll collect, but it won't be shown to anybody. And it's important to get that right up front. I block certain crawlers that harvest certain information that trains AI models. So while still allowing search engines to find nurses, so someone who agrees to share information with me has not agreed to give all of that information to AI. So we're putting those processes in place, or I'm putting those processes in place right now as I speak. I want to be able to say that the information you're giving me is not being used to be trained, training AI models. The specific details that you're using are not being used to be training AI models. So things like that you can't just undo because once it's in AI, you can't untrain AI once it has the information. So that's lesson number five. Build a trust at the beginning because you can't add it later.

Lesson 6 Success Before Revenue

Marsha 32:31

Lesson number six in the last lesson is decide what success looks like before there's any money. And if revenue is your only scoreboard, you can quit in three months. Because remember, you're not doing the fun things up front. You're building the foundation, you're building the privacy, you're building the security up front. Those things aren't really fun things to do. So if you're only judging by revenue, month three in will look like a failure when you actually may be on schedule. So for what I'm building, the realistic timeline for what I'm building to a real first customer is six to 12 months. And it even may take a little bit longer for me to get a real paying customer. So that's not me like thinking like negatively about what I'm building, it's just the normal process of building it. So that's a pretty normal number for anybody who may be building some type of platform that can make money. Yes, you have people who can make money a lot sooner, but for what I'm particularly building, it's going to take time before it makes any money. So I wrote down what success looks like in the first 90 days. And there's no revenue within that first 90 days. It's a thing that works in the first 90 days, but there's no revenue. So, real people using it who don't know me, that's success. And knowing what it actually cost me to reach those real people, that's success. Does it cost me, you know, zero dollars? Does it cost me $5 to reach a person? That's real success. Learning what those numbers are, learning that something actually works, that's success in three months. So I wrote down some gates too about that specific conditions that have to be true before I'm allowed to spend any money on the next thing, not just when it feels right to me. Let's go ahead and get started on this next thing. No, that's not gonna be how it works. So I wrote these things down in advance. So I'm really clear-headed about it. So one of my gates is basically 10 real people have to complete this particular part of my platform without me helping them, before I spend a dollar on advertising or promotion. So 10 people getting on the platform, knowing exactly what to do without any prompting from me, without any help from me, without needing help. So that's part of the success of building something, knowing that it will work before you even ask for money. So, whatever you're building, you want to write it down, write what success looks like this quarter with no money in the definition. Because if you use that as one of your benchmarks or part of your milestones that you must make money in a certain amount of time, you're not gonna want to continue building it. So that's the difference between you quitting, and that's the difference between you moving forward. So there are some things also that I use to push back on myself. So I'm seven days in, right? So seven or eight days in. That's nothing in the scheme of building technology or a platform. If you ask me again at day 90, some of those lessons that I'm telling you about in day seven or day eight will look completely different from the lessons that I may have learned in day 90. And some of these lessons that I'm telling you about today may not even matter once I hit day 90. So that's something I want to let you know that I'm being mindful of that what I think is important now may not be important, may not have been the important thing to think about. So I haven't sold anything, not one dollar. Everything I just told you about is building in the process. And building is the part that I enjoy right now. Building is the part that I feel like I'm good at because I get really fascinated by what I could build from nothing. So selling is the part that I have not yet proven because that will come six months, 12 months down the line, probably. I would hope a lot sooner, but we'll see where

Vibe Coding And AI Mistakes

Marsha 36:50

it goes. And I have to say also that using AI to help me write the code or what's called vibe coding, giving natural language prompts to AI to help you create something or build something is why this whole thing is possible for me. Three years ago, so I started using AI on a regular basis in October of 2023. Using AI or not having AI and trying to build what I'm building right now, it would not have been possible without me paying people, teams of people, a lot of money to build it. So that's the one thing that I'm excited about. And that's the one thing I'm excited about for nurses and what we can build because we have a lot of ideas. We have a lot of solutions in our head that we're able to build things with, but now we have AI that's going to help us build it a lot sooner. I just wanted to make sure I point that out that this would not be possible without it. It's not a magic button. My own notes this week, my build log that I have that tells me everything I'm doing every single day is showing me that. I'm finding places where AI is wrong or making incorrect assumptions. And I have to tell AI, no, that's not correct. We need to do it this way because this is how nurses behave and this is how nurses think. So AI will confidently tell you something. AI will hallucinate, and that's the term for it will lie to you sometimes and not on purpose. It just speaks confidently about it, right? I'm sure you've seen the meme where someone asks AI, hey, is this mushroom poisonous? And AI says, no, that's not a poisonous mushroom. And then the next scene is the person in the grave. And AI saying, Oh, I no, I made a mistake. That's not the right thing. Do you want me to tell you more about poisonous mushrooms? Meanwhile, the person is already not there anymore. So AI will hallucinate. So it's important. That's why we go back to that first lesson. It's important for you to have the knowledge, the skills, experience, expertise, so you know how to catch when AI makes these hallucinations and when AI makes a mistake. So the skill isn't necessarily knowing how to prompt, right? That's what you learn right now about prompting and giving AI the right prompt. That's not the skill. The skill is knowing enough to check to make sure what comes out of that prompt is correct. Yeah. And last, the biggest lesson is how it, I told you it took me a year to really figure out what it is that I wanted to build. And some of that, a lot of that was a year of thinking. It wasn't avoiding getting started because I'm one who will start before I'm ready. It was just a lot of thinking around what I'm going to build. And then I had to eventually make the decision, okay, get started right now. So I want you to know that year of thinking was not procrastination. It wasn't there was no strategy behind it. It was just trying to get it right from the very beginning as much as possible. So I won't make a lot of mistakes in the process moving forward. So I wanted to get it right or half halfway there as much as possible.

Recap And Questions To Try

Marsha 40:11

So those are my lessons. Those are the six lessons I have. Lesson number one, just to recap, start from what you already know. Lesson number two, cut it until it gets simpler. Lesson number three, keep a written list of what you're deliberately not building. Lesson number four, get the boring foundation right before you touch the fun part. Lesson number five, build the trust in at the very beginning because you will have a hard time adding it in later. And then lesson number six, decide what success looks like before there's actually any money involved. And then some questions I want you to think about when you're thinking about building something innovative from some of the ideas that you have. So, what's the idea you've been carrying around that you haven't started because you don't have the skill set yet? And that may be something you may want to leave off your list of innovative ideas. That's not something that you have to do, but it's something that you consider what may want to consider. Number two, if you had to cut your idea in half this week, what would you cut first? And that could help you save a lot of money in building things. If you want to cut out some features, it may help save you a lot of time and effort. And then third question is what are you deliberately not building right now? And have you actually written it down? So get the idea as finalize as possible, as much as possible in the very beginning, and cut out the things you know that are going to be distracting you from getting your solution right in the very beginning. Just try to do all that work up front. And I think it's going to give you a lot easier path forward.

Subscribe And What Comes Next

Marsha 42:00

So thank you so much for joining me on this first episode of this Building Innovation from Idea series. I wanted to just share those lessons that I've learned from you in the very first week of me building something out and what I'm helping to hoping to help you take forward as you build your own innovative ideas. If you want to learn more about building something from scratch and building it in the open, go ahead and follow the series. I'm excited about it. Subscribe to the Boss Euros Podcast. I would love to have you a part of the platform. Yeah, I can't wait to continue sharing this journey that I'm on with you. And hopefully, in my learnings, you'll learn something too. And I look forward to chatting with you in the next episode.