How I Went from Idea to First Sale in 30 Days at Age 60
How I Went from Idea to First Sale in 30 Days at Age 60
TL;DR / Key Takeaways
- The project moved from idea to first sale in 30 days by shipping a focused Python trading system instead of a broad SaaS.
- The initial product was source code and documentation for a Kalshi weather trading bot.
- The launch used Gumroad, Reddit, and transparent technical writing rather than a large marketing funnel.
- The article emphasizes speed, narrow scope, and direct buyer value over polished startup theater.
I am 60 years old. I have been writing software for 30 years. And I still felt impostor syndrome the first time I hit "Publish" on Gumroad.
Make of that what you will.
This is the story of how I went from an idea in my head to a real paying customer in roughly 30 days. No outside funding. No team. No marketing budget. Just a side project built on evenings and weekends while working full-time as a Senior Data Engineer at QTS Data Centers.
If you have been sitting on an idea and waiting for the right moment, this post is for you.
The Idea: It Started With a Weather Model
I had been trading on Kalshi prediction markets for a few months. Temperature contracts, mostly. The concept is simple: will the high temperature in Atlanta exceed 85 degrees on Thursday? Yes or No.
I noticed something. The market prices did not always match what the GFS weather models were saying. Sometimes a contract was sitting at 40 cents when the GFS ensemble was showing 75% probability of yes. That is a 35-cent gap. That is edge, if you can find it consistently.
I thought: I am a data engineer. I can automate this.
So I started building. Not a product at first. Just a Python script for myself. Something that would pull ensemble weather data from the Open-Meteo API, score the mispricing against live Kalshi prices, and alert me when to trade.
It worked. Not perfectly, but well enough to be interesting.
That is when the second thought showed up: other people might pay for this.
The Build: 30 Days of Nights and Weekends
I work full-time. I cannot disappear for a month and ship a product. So I built it the way most side projects get built: in the margins.
Early mornings before work. Lunch breaks. After dinner while my wife was watching something I had no interest in. Weekends. She is patient with me. The kittens were less patient and stepped on my keyboard more than once.
The stack was straightforward:
- Python for everything
- Open-Meteo API for free GFS ensemble data
- Kalshi REST API with RSA-PSS key authentication
- PostgreSQL for trade logging
- A scoring model I designed from scratch based on 4 factors: ensemble spread, ensemble confidence, model vs market price gap, and fee efficiency
I did not gold-plate anything. The goal was working software that I would actually run and trust. I gave it a minimal set of filters: a confidence threshold, a spread check, a fee efficiency minimum, and a contract price floor. When all four cleared, the bot would place the trade automatically.
By week three, it was placing real trades without me doing anything. By week four, I had written enough documentation to package it as something someone else could actually run.
Total development time: probably 80 to 100 hours spread across a month.
The Launch: Gumroad, Reddit, and a Little Courage
I had never sold a digital product before. I picked Gumroad because it was the simplest path to a checkout page with minimal setup. Five percent fee on transactions. No monthly subscription. Simple enough that I could focus on the product instead of the infrastructure.
I wrote the product description myself. No copywriter. I priced it at $67 and made the decision that I would rather sell it to serious buyers at a fair price than give it away cheap to people who would never use it.
Then I posted on Reddit.
I put a thread in r/algotrading and r/SideProject that focused on the technical approach. Not a sales pitch. A real explanation of how ensemble forecasting creates a signal that most Kalshi traders are not using. I explained the scoring system. I showed some sample output. I was honest about the limitations.
The first comment was skeptical. Someone asked "is this a scam?" That stung a little. Then someone else asked about the ensemble scoring logic and we had a genuinely good technical conversation in the replies. A few days later, the first sale notification landed on my phone.
I was at my desk at QTS. A tiny ka-ching sound. Fourteen dollars and change after fees.
I texted my wife.
What Worked and What Did Not
What worked was leading with technical authenticity. The people who bought were not buying hype. They were buying a real system built by a real engineer who was actually running it himself. That credibility matters in algo trading communities. You cannot manufacture it.
What did not work initially was the product page. I spent three paragraphs explaining how RSA-PSS authentication works before I told anyone what the bot actually does or what results it produces. That was backwards. Lead with the outcome, explain the mechanism second.
Spreading too thin also hurt. I tried to be active on TikTok, YouTube, Reddit, Facebook, and a few directories all at once. Reddit was the only channel producing results in the first month. I should have doubled down there and left the other platforms for later.
The other thing I would change: start writing blog posts from day one. The website was live but the blog was empty for the first two weeks. Organic search takes time to compound. Every week without content is a week of delay you cannot get back.
The Numbers at 30 Days
First sale on day 22. Two sales by day 30. Combined revenue of $134 minus Gumroad fees.
Not a living. Not even close. Not the point.
The point was proof. Proof that a 60-year-old Senior Data Engineer who builds enterprise data pipelines for a living could also build a real product, put it on the internet, and find real buyers who thought it was worth paying for.
That proof matters more than the dollar amount. It removes the excuses. Too old. Too busy. Too niche. Too unknown. I had all four of those excuses ready to go. I shipped anyway.
By April 2026, the bot product has generated over $810 in revenue from 12 sales, zero paid advertising, all organic. Small by startup standards. Meaningful by side project standards. Still growing.
The full breakdown is in Month 1 Results: The Honest Numbers from My Automated Weather Trading Bot.
What I Am Building Toward
This is not just about the bot. The bot is one piece of a larger plan.
I am 60. My wife is Filipina. We plan to retire in the Philippines in the next five years. That requires building income streams outside of a W2 salary, because pensions are mostly a myth now and "work until 70 and hope for the best" is not a plan I am willing to accept.
Predict & Profit is the first product in what I intend to be a real catalog of digital tools for technically-minded people who want to trade smarter. It is not passive income in the magazine-cover sense of the phrase. But it is real income from real products that I own and control.
Building in public, shipping real things, being honest about the numbers, all of that is intentional. The prediction market space is still early. Kalshi raised $1 billion at an $11 billion valuation in 2025. Robinhood prediction markets run on Kalshi infrastructure. Polymarket US access is opening up. The timing is genuinely good for people who want to build algo trading tools in this space.
I am one of them. At 60. With 30 years of engineering experience. And the only thing I regret is not starting sooner.
Want to Start With Working Code?
The full Python source code is at predictandprofit.gumroad.com for $67. That is the same code I built during those 30 days, refined and documented, with the HGEFS 62-member ensemble upgrade and full Kalshi API integration.
If you are an engineer who has looked at Kalshi and thought "I could probably automate this," you are right. The question is whether you want to spend 100 hours building from scratch or 67 dollars to start from something that already works.
Frequently Asked Questions
Q: What made the first sale possible in 30 days?
A: The scope was narrow: ship working Python source code, documentation, and a specific Kalshi weather trading use case. Avoiding a full SaaS build kept the launch small enough to finish.
Q: Why sell source code instead of hosting the bot?
A: Selling source code avoids custody, account-management, and infrastructure obligations while giving technical buyers direct control over the system. It also matches the audience: developers who can run Python themselves.
Q: What was the minimum technical product?
A: The minimum product was a runnable bot, setup documentation, model explanation, and a clear purchase path. It did not require a complex web app or subscription backend.