The TV is on in the background, the kids are asleep.

My wife turns to me and asks “any idea what you’re building for this month?”.

She knows that the start of the month means it’s time for a new project on my journey of building 12 products in 12 months for 2024.

“Good question.” I say.

Mind you, I’m just a few hours removed from an absolute mad dash to get my May project, Domain Copilot, out the door.

But I’ll save that for another post.

So yeah — what am I going to build for June.

I crack open my laptop and open up my “build list” and start going through some of the more recent idea.

This is the spot where I jot down all the ideas I might want to build. Some better than most.

As I’m talking through some of the ideas, we’re filling the gaps talking about an upcoming trip to the tropics.

This is our first proper vacation in a long time, and with a 1.5yr old and a 6mo. old, we’re definitely ready.

With all this vacation talk going on, we start talking about how it’d be great to plan a vacation with friends.

Y’know, not just a weekend getaway, but more of a sit-by-the-pool, drink-in-my-hand, in-some-tropical-location, week-long type of vacation with friends..

By now my idea juices are flowing.

The build list is open, we’re talking about vacations.

Naturally my maker mind is pulled in that direction.

“I’ve know! What about an app where you can plan trips with your friends?” I say.

My wife, humoring me “That sounds like a cool idea.”.

Friends can suggest trip destinations, budgets, the whole-nine.

Friends can opt-out if the timing of the trip isn’t right. Friends can invite their friends.

And so on.

The app would have an inherent viral component baked in to it’s DNA.

Brilliant!

So I say to my wife, “Someone has to have built this already.”

Sure enough, someone has.

In fact, many people have.

I found a small handful of these apps in the first 10 seconds of searching Google.

And I’m sure I’d uncover more if I kept looking.

So what did I do next?

Well, nothing.

I didn’t even download the app to check it out. I just discarded the idea as if it was an old toy.

And that’s when it hit me.

This is a great Litmus test for these types of fleeting ideas.

This idea was simply a solution in search of a problem.

As a builder in search of an idea. This sounded great.

As an end user, this idea felt like an unnecessary tool.

In reality, I’d rather just start a group chat if we we’re going to plan a trip with friends.

Sure, an app for this niche problem might add some value somewhere along the lines, but is it something I want to build?

Well, it sounded good in the moment. But at the end of the day, no.

That’s where a lot of us end up wasting our time, building things that no one really cares about, sometimes things that we don’t even really care about.

So before you build that next idea, have an honest conversation with yourself:

Would I really use this app?

Still buzzing from a #1 Product of the Day a month earlier with Botroast.io, I was poised for another successful launch.

My tweet earlier in the day was getting solid traction and a lot of positive sentiment from the indie hacker community.

Things were shaping up.

Subscribe now

Launch day

It’s 12:17am and I finally close my laptop. I just pushed up some last minute bug fixes and finishing touches.

I’ll be asleep before the launch goes live at 3am PST, but I’ll be waking up with a smile because I’ll be in that top spot.

6am rolls around and my 3 month old daughter is stirring. She’s must be able to sense it too. Feedbrew is on it’s way to the moon.

I open up the Product Hunt app on my phone.

Holy shit my phone is bright. Let me turn the brightness down a bit.

The page finally loads and Feedbrew is no where to be found.

What???

Oh, right.

In the early hours of launch day the votes are all hidden and the products are shuffled so that they all have a fair shake at getting some organic traction.

Cool. So where’s Feedbrew?

Turns out that not every launch gets “featured”, meaning you’ll have no chance of getting Product of the Day, any badges, and any traffic that you might’ve gotten had you been featured was pretty much out the window.

Good luck on the “All” tab chump.

All my Easter eggs in the Product Hunt basket

This Easter weekend launch could be summed up in 1 word.

Lackluster.

37 upvotes is a far cry from the #1 POTD launch I had just one month earlier.

This was flat out embarrassing.

But it was my fault.

I put all my eggs in one basket.

No backup plan. No plan B. Nothing.

Stats

Here are some stats from when I first shared Feedbrew to Twitter on 3/29/24 ‘til today on 4/29/24.

App Stats

• 79 user registrations

• 52 products posted

• 5,397 swipes

  • 2,022 right swipes (likes)

  • 3,375 left swipes (dislikes)

• 417 product clickthroughs

• 30 ad clickthroughs

• 19 pieces of feedback left on products

Revenue

• 1 customer for $5 🥲

Twitter launch thread (here)

• 23.5k views

• 152 likes

• 118 bookmarks

• 42 comments

• 16 retweets

Product Hunt launch (here)

• 37 upvotes

• 29 comments

Google Analytics

• 1.2k users

• 1.1k uniques

Monetization

I built in two ways to monetize Feedbrew.

1.) A credit-based system that allows makers to ask specific feedback about their product, as opposed to a generic feedback form. Credits range from $5 to $19.

2.) Ad slots for $249.

Didn’t sell any ad slots, but I used that to promote my agency.

Experiments

After the Product Hunt flop, I shared Feedbrew to Hacker News.

Another flop.

Then I had the idea of baking in a way to claim products on Feedbrew so that I could curate new products myself, and then reach out to the makers and let them know.

I did this for a small number of people with a very limited response rate. Something like 1 out 10 people had responded.

I specifically went after products that were snubbed on the Product Hunt “featured” tab, much like Feedbrew.

I figured that would be a good way to break the ice.

Overall, it’s been too small of a sample size to glean any meaningful insights from, but I’ll keep chugging trying things out.

Distribution > > >

For someone who is a builder at heart, I love the product side of things.

I love building eye-catching, memorable, and delightful digital experiences.

I’ve never put much effort into the other side of things — the distribution side.

The sales, the marketing, the partnerships, etc.

So it’s time to experiment some more with that, but admittedly, this challenge of building 12 products in 12 months doesn’t lend itself well to “distribution”.

So far, it’s been a whirlwind of juggling family life with 2 small kids, being back at my 9-5, and cobbling together my projects with any time that I have left over.

It’s time to rework things a bit and set myself up for success.

I’m thinking I will spend less of the month building, and more of the month focusing on distribution.

As I write this, it’s already towards the end of April so my April project will likely suffer from lack of distribution, but I'll look towards May to try something new.

Stay tuned for more — the debrief of my April project will be coming real soon!

Share

So for February, as part of the Indie Hackathon, I built and launched BotRoast.io, a simple app that gives you design feedback in 1 click.

This app took me 2 weeks from idea to launch, and it ended up hitting #1 Product of the Day on Product Hunt.

Follow along and I’ll share some insights on how I launched Botroast.io, and the experiments I’ve been running for it.

Ideation

Leading up to the start of the Indie Hackathon, I had kicked around a few ideas of what I wanted to build.

Pretty much every time I would scroll my Twitter feed, I’d see somebody asking for others to “roast” or provide feedback on their landing page.

That’s when the lightbulb went off.

With GPT Vision models becoming more and more available — why not just use AI to roast your landing page?

Save time and money.

This project would also fit well within the scope of the Indie Hackathon, where each participant has 4 weeks to make their first dollar from their project.

A kinda-stupid-but-kinda-cool project to hack on that I could monetize in some way.

And funny enough, one night as I was working on it, I saw this tweet from Tony Dinh that really made things click.

The more you build and experiment, the more you’ll begin to identify things that work and things that don’t.

Prototyping

My first thought was “let’s see if this thing is even possible”.

The initial prototype was dead simple.

I made an API request to OpenAI’s GPT 4 Vision model, passing in the prompt and the URL to a landing page screenshot.

Since I hadn’t messed around with any of these vision models prior to Botroast.io, it was mostly just a matter of tweaking the prompt a number of times to get the output close enough to what I had envisioned.

Soon after, I was able to get an output that I could build an MVP with.

MVP functionality

The goal here was to keep things very simple, just as I did with the prototype.

The MVP would let the user:

1. Enter a URL

2. Click a button to start the roast

3. View their roast when complete

Under the hood, in order to enable this functionality, I had to:

1. Configure a simple API to accept the landing page URL entered by the user

2. Capture a screenshot of the landing page

3. Pass the screenshot to the GPT Vision model along with a prompt

4. Format the response from the AI model

5. Return it back to the client

All things considered, this was pretty straightforward stuff.

I opted to use a stack I’ve never tried before — the T3 stack.

Overall, it was fine. It just wasn’t my usual stack so I naturally moved a little slower.

It was easy enough to setup the roast tRPC procedure (essentially an endpoint) that would accept the URL provided by the user.

I also got authentication out of the box since the T3 stack uses NextAuth.js.

Next I needed a way to automatically capture a screenshot of this user-provided URL.

Now — I could’ve opted to go with an image upload input that would allow the user to manually upload their own screenshot, but it would’ve added more friction to the user experience.

It was just “one more thing” for the user to do, and naturally some people would drop off and not do it.

So instead, I decided to automate the screenshot capture.

I’ve been following Dmytro Krasun on Twitter for some time now, and he’s always sharing interesting insights into what he’s building. His main project these days is ScreenshotOne.com and so it immediately came to mind when I needed to automate screenshot capture for my app.

Super easy to use, and within 5 minutes I had a core piece of my MVP working.

I also wanted a way to store the screenshots, so I configured an S3 bucket on AWS, and automatically uploaded the screenshots to my bucket after capturing them with ScreenshotOne.

Next up, I needed to integrate with OpenAI’s API.

Another simple API call, passing in a prompt and a URL to the screenshot.

This was mostly just prompt engineering (*cringe*) a.k.a a ton of trial and error.

After getting the model’s output mostly to my liking, I needed to parse the OpenAI response and return it back to the frontend.

But because GPT-4 Vision doesn’t support structured JSON output (yet), I needed to get creative with my prompt and my parsing logic to massage the data into a predictable and reliable format.

I found that giving the model an example payload of the output your expecting goes a long way here.

And yeah, that was mostly it.

At this point, I had pretty much all of the functionality I needed for a user to successfully roast their landing page in 1 click.

Monetizing this thing

This wouldn’t be an Internet Money post unless we talked about monetization.

For Botroast.io, the clear path to monetization was to charge for roast credits.

So I integrated Stripe Buy Buttons along with a webhook so that users could purchase credits to roast their designs.

Baking in virality

Roasts in general strike me as something inherently “shareable”.

Bot roasts, even more so. They’re automated and fun.

I felt that people would naturally just want to show off their roasts on social media and share them with friends because it was a funny, novel thing.

Then their friends would sign up, share their roasts, rinse, and repeat.

Especially since the roasts had scores on them, people could brag or make fun of themselves.

Not to mention, both parties earn free roast credits with a referral.

Easy enough.

At the time of this writing, BotRoast.io has 1,285 users and 17 of them signed up via a referral code.

That means just over 1% of sign-ups have come from a referral link so far.

My initial reaction is to say that adding the referral code functionality was a bust, but I think it has mainly been a miss on where I’ve placed referral links for sharing and sign ups.

This is something worth experimenting with for sure.

Nonetheless, a lot of people have still shared their Roast Reports as I expected they would.

I don’t have hard data on this, but I’ve been tagged in a number of tweets and seen a lot of Roast Reports shared, which is a good sign.

Eat with your eyes first

Most picky eaters know this.

We, as humans, “eat” with our eyes first.

Our perceptions are largely influenced by appearance, whether it’s food or products.

Probably more than we’d like to admit.

I spent a lot of time putting together a fun brand image for Botroast.io, starting with the name.

A play on pot roast, a delicious food — but instead, it’s a bot…that roasts.

*Cue the laugh track*

I took my time curating the colors of the site, the fonts, and the design assets to make for a cohesive, fun, and almost sarcastic brand.

You might argue that none of that matters, but I beg to differ.

A cohesive brand greatly enhances the perception of your product, especially nowadays.

As they say, the devil is in the details.

And by the way, I wouldn’t consider myself a “good” designer.

There’s plenty of design theory and best practices I’m not privy to.

But I have built enough things on the internet where I’ve been able to sharpen my eye for design and come up with some semblance of my own style over the years.

Balancing act

If you’re building an MVP, by definition, you can’t — and shouldn’t — spend time on things that don’t matter.

But it doesn’t mean your product shouldn’t be polished.

If you’re launching on Product Hunt, there’s a lot of stiff competition out there, so to stand out, you should sweat at least some of the small stuff.

But of course, you’re left with a decision.

How much time do you spend on the “other” things?

The things other than your core feature set.

That’s up to you at the end of the day, but the more of those finishing touches you can add to your product, the greater returns in perceived quality you will get for your MVP.

Just be sure to strike the right balance.

Don’t enter the territory of diminishing returns.

Don’t delay your launch because every pixel isn’t perfect, every feature isn’t working 100%.

Stick to the 80/20 rule.

The stats

So far, BotRoast.io has:

• 3,100+ unique visitors

• 1,285 registered users

• 1,574 total roasts (1.22 roasts per person)

• 3 paying customers totaling $47 of revenue

• 17 users registered via referral code

Experimenting a bit

I would love to have made more sales so far, but it’s likely because the product in it’s current state is just not compelling enough.

For the initial launch, every user received 3 free roast credits.

That’s probably more than enough for the average person to never need to pay for a BotRoast ever again, or at least for a long time.

So last week I ran an experiment.

I made it so new users would not receive any free roast credits upon registering.

Over a 1 week span:

• 42 new users registered

• 1 new paying customer for $9 revenue

This boils down to a 2.38% conversion rate.

Now, contrast that with the first 1,243 users accounting for only 2 sales at a 0.16% conversion rate.

That’s a 1,387.5% increase!

Ok ok, this is such a limited amount of data that it’s hard to really say for sure whether or not this will continue, but I like where it’s headed!

Here’s to some more internet money for all of us!

Stay tuned for more posts like this where I share insights on the products I’m building, and the experiments I’m running.

For my January project I built Theodore AI, a basic Google Chrome extension that simplifies complicated topics in a couple clicks.

I launched it on Product Hunt and the next morning I was stoked to see that it reached #7 spot for Product of the Day!

Not a bad day at the office.

Or so I thought…

🫠

It was broken.

The app was broken.

Here’s a comment someone left:

This would be very helpful. I'm trying to install it. A couple of issues: 1) Where do you add the coupon? 2) When installing getting 'Could not find icon" error. Looking forward to your response so I can start using it.

But before I get into more of the details of this launch day fiasco, let me give you some more of the backstory…

The idea

This project stemmed from a simple annoyance I would encounter fairly often.

I’d be reading some technical docs, or trying to decipher some smart sounding tweet or blog post and it just didn’t make sense to me.

So then I’d take the text, copy it, open up a new tab, write a quick prompt to ChatGPT telling it to explain the text in simple terms using a practical example.

Easy enough.

Buuuuut, also annoying enough to interrupt my workflow every time I had to do this.

Checks all the boxes

This year is all about getting reps in and quickly launching products that I can monetize.

No more spending a year in a cave building some crazy platform that no one even wants.

I wrote a little bit more about this in my last post.

And because I didn’t “formally” decide to build 12 projects this year until January 18th, that left me exactly 2 weeks to build my January project.

That means I would need to keep features to a minimum. Something I haven’t always been good at.

The cool thing, though, was that this little project idea checked all the boxes:

• Feasible to build and ship within 2 weeks

• Solves an annoyance that I have encountered multiple times

• Can definitely monetize it in some way

• Bonus: Never built a Chrome extension

Subscribe now

Building the MVP

For the initial feature set, I wanted to include one basic piece of functionality.

Allow users to simplify whatever text they highlight in their browser.

On any webpage, the user can highlight some text, right-click, then select “Simplify with Theodore”.

See the screenshot below to get a better idea of how the extension works.

In terms of building this thing, already had a good starting point for my extension because I decided to use ExtensionKit.io.

That got me most of the way there — saving me at least a day or two of trial and error and learning Chrome extension best practices and conventions.

I mostly just needed to write the backend logic that would integrate with OpenAI’s API so that I could give it a set of prompts along with the text highlighted by the user and it would output the simplified version.

A “ChatGPT wrapper”, if you will.

After building a very basic MVP, I put together a quick landing page wired up with Stripe and a simple feedback form.

It turns out that details still matter

One thing I found, that even though this app and it’s landing page were super basic, little details matter to people.

As I started sharing screenshots on Twitter of the progress I was making on my project, a lot of people commented on the graphics I used, how “cohesive” the branding was, and a number of people let me know my copy was solid.

I was really excited to hear that. Especially the copywriting part.

I’ve been experimenting quite a bit with copywriting the last few months, so that felt good.

People also loved these little graphics I added to my landing page.

100+ little scribbly graphics for only $5, and they were seemingly making for such a delightful landing page experience.

In turn, this delightful experience also helps to build trust with potential customers.

Especially when you’re asking them to open up their wallets.

$5 well spent.

So yeah details still matter.

Even for your MVP.

And as it turns out…

So does the icon size of your production Chrome extension.

If your app icon isn’t the perfect size, people won’t be able to install your extension.

If it’s not exactly 128px x 128px, you’ll see this error when trying to install it:

“Could not find icon”

That’s what broke my Chrome extension on launch day.

Because my little teddy bear icon was a little too chunky at 512px x 512px.

If this was a web app, a fix would’ve been rolled out in 5 minutes.

However, with Chrome extensions, similar to mobile apps, there’s a bit of a delay before your updated app gets released to the marketplace.

This usually take between 24-48hrs.

So I uploaded a new artifact to the Chrome Web Store, and here I am.

My app is featured on Product Hunt, and it’s broken.

All because of this stupid little icon.

And yet — it’s still climbing the Product Hunt rankings.

How I still landed the #7 spot

Of course I don’t actually know how I landed the #7 product of the day with a broken app.

But I can tell you this:

I didn’t care where I ended up.

In my 5 Product Hunt launches prior to this one, I always treated them like this grand spectacle.

Reaching out to all my family and friends, urging them to create accounts on Product Hunt and upvote what I had built. It was always this big celebration.

This time around was different, though.

I hardly told anyone that I was launching ahead of time.

Just gunna launch this thing and get going on my February project.

The other thing I can say is that it all just boils down to solving problems for people.

Super cliché and insightful — I know.

But if you’ve ever built a feature-rich, robust product with all kinds of features, only to constantly feel as though you’re pushing a boulder up a hill trying to get users — you’ll know exactly what I mean.

When the market pulls you it’s a much different feeling.

And luck. I think luck had a little bit to do with my product being featured on Product Hunt.

But I’ll just say, it feels pretty good to spend such a short amount of time hacking on a project and showing it to the world.

Not to mention…

My first internet dollars of the year!

After I fixed the launch day issues, I was stoked to see my first Internet Money™ of the year.

it_aint_much_but_its_honest_work.jpg

I’ll be sure to share more any additional updates on Theodore AI throughout the year.

Stay tuned for more details on my February project, Botroast.io next!

Subscribe now

TLDR; I’m setting up a simple system for my code and for my time.

For 2024, I am building 12 products in 12 months.

Like most indie hackers, I have a 9-5 job.

But to kick this challenge up a notch, I’m also a dad of two young kids — a 16 month old and a 3 month old.

The only real time I’ll have to hack on these projects is early mornings and late nights, and maybe during their nap time on the weekends.

Needless to say, a lot of my ideas, and even features, won’t make the cut simply because they require too much effort given the circumstances.

However, that doesn’t mean these products won’t be cool as hell.

These 12 products will be badass.

It just means I have to be super intentional and efficient with my every move — something that hasn’t always been my strong suit.

So if you’re ready for a wild ride, hop in and join me as I share my entire process with you over the course of the year.

I might fail or I might succeed.

Also, since it’s now March 2024, be on the lookout for my next couple of posts which will get you caught up on my January and February projects!

But I’ll add a few more details below…

Subscribe now

Why am I doing this?

I love building and creating. It’s my “infinite game”. Hell, I even learned to code because I’ve always had so many ideas that I’ve wanted to build. I could never just be the “idea guy”.

So this year I’m taking my passion for building and supercharging it with a dash of intention and a handful of efficiency so that I can start marching towards my end game.

What’s my end game you ask?

Freedom

Financial freedom, freedom to do whatever I choose with my time, freedom to live life on my terms.

I’ve always had an oddly specific barometer to measure this freedom.

Here it is:

If I ever decided one night that I wanted to travel to, say Tokyo, that my family and I could hop on the next plane that night or the following morning and go — with no repercussions. No having to let my boss know, no planning ahead, no saving up for the year, none of that. Hell, we could go without suitcases and buy some clothes when we land. And even bring some friends with us too.

That’s the freedom I’m looking for in the long run.

But what about in the short term?

To get there, I’ve realized I should start to work backwards.

Ship more

It’s simple. I need to get more reps in.

The reason I’m launching 12 products this year is to build my shipping muscle.

No more wantrepreneur shit where I make a logo and a landing page then feel some false sense of accomplishment.

Even with 5 Product Hunt launches under my belt prior to 2024, and a number of other products I’ve built and shown to the world, this year is about shipping.

No time to get everything pixel perfect. No time to add tons of features (that no one wants anyway). No overthinking every little detail.

Some projects will succeed and others will not.

It’s a numbers game.

With each new project, I will get better, and the products I ship will get better.

My marketing skills, my sales skills, my positioning, my branding, my copywriting, my code — all of it will get better.

The knowledge gained from each product launch will begin to compound exponentially.

Creating a system

For starters — every product I ship will be monetized in some way.

No more “playing house”, no more wantrepreneur shit. You can read more about my struggle with that in my last post.

The goal is to make that sweet sweet internet money from every project.

But simply monetizing my products won’t help me launch them any faster.

Building a boilerplate for my stack

In order to move quickly — to solve bugs and add new features, to support my customers in a timely manner, all while still being a great father and husband, I need to come up with a system.

I wish I could tell you that I had every corner of my system ironed out, but I don’t.

To start, though, I’m creating Yet Another Boilerplate™.

That’s one of the lowest hanging fruits if I want to ship quickly.

My preferred stack is:

• GraphQL

• React

• Nest.js (Not NeXt.js)

• Prisma

• Postgres

• Tailwind

I can move quickly and confidently with it.

This boilerplate will also be wired up with everything else I (typically) need. Things such as:

• Auth

• RBAC

• Admin dashboard

• Web sockets

• Cron jobs

• Email integration

• Stripe integration

• Various frontend components

• Layouts

• Landing pages

• …and more

And yeah, I know what you’re thinking.

“Isn’t this the same thing as ShipFa.st by Marc Louvion?”

Yes, it’s just my own version of it. One that I can ship fast with.

Scheduled time for deep work

In addition to setting myself up for success when it comes to actually building, I’m also aiming to be more intentional with my time.

I write code for my side projects nearly everyday, but I’ve never been one to schedule time for this creative work.

Scheduling time for creativity? That has always felt like the least creative thing to do.

Creativity ebbs and flows.

I can’t just get into a flow state at 7am every morning or 9pm every night.

But I’ve realized — now more than ever — that I need some semblance of order with my schedule so that I can make sure I cover all my bases.

Family, fitness & health, my day job, my projects.

I need more of a structured routine for deep work and I’ve been inspired a lot by Pat Walls’ post about it here, so I’m taking a similar approach.

I’m slotting out time from 7am-9am every weekday, and from 9pm-11pm every weeknight.

Weekends will be more of a wildcard, but mostly reserved for family.

I’ll keep you posted on the specifics of where I land with this part of my journey, but would love to hear what’s working for you!

Subscribe now

Internet Money

/ˈ in(t)ərˌnet mənē /

Money earned from internet-based business endeavors.

4.07 projects per year

Since 2010, I’ve worked on 53 projects (that I can remember).

That’s an average of ~4 projects per year.

Not bragging though. A lot of these projects (if you could even call them that) were more or less just a logo and landing page, stemming from some late night idea I had.

I found some type of comfort and accomplishment in all of these little projects that I would never see through.

Odds are that I’m a better wantrepreneur than most people.

Here’s how it would usually go:

• 💡 I’d have an idea

• 🏡 Buy a domain

• 🎨 Create a logo

• 🖼️ Find some graphics

• ✍️ Write some copy

• 👨‍💻 Create a landing page

• 🥸 Feel a false sense of accomplishment

• 🔄 Repeat

My project list

See below for a list of my projects.

🟢 = Launched and talked to potential customers

🔴 = Never launched and/or never talked to potential customers

👉 View the spreadsheet

As you can see, most of this spreadsheet is red.

Nearly two-thirds of it.

Although there’s been a lot of projects that have fizzled out or never saw the light of day, I’ve still managed to show a handful of them to the world.

Some of them are still making a (very small) amount of internet money, and others have long since been forgotten.

So why am I sharing all this?

Accountability

I’m ready to buck the trend.

To put myself in uncomfortable situations. (Example)

To ask for the sale.

I’m ready to build with intention.

To monetize my projects.

To talk to users and potential customers often.

To make more green rows in my spreadsheet.

To not spend another year building a project with features people don’t even want.

I’m ready to experiment like a mad scientist.

To ship a bunch of MVPs and let the market pull me.

To make some serious internet money.

I’m ready to share this journey with you.

and lastly…

I’m done being a better wantrepreneur than you.

Maybe there’s something you can learn from my journey — past, present, or future.

Or maybe not.

There’s only one way to find out 👇

Share Internet Money