Founder and CEO of @MarketBeatMedia.
Sioux Falls, South Dakota
Joined March 2008
- Tweets44.2K
- Following3.3K
- Followers76.7K
- Likes92.7K
Pinned Tweet
THE MONEY PROMPT:
Do a full analysis of the revenue generating aspects of our code base. Your mission is to identify opportunities to improve revenue. You have my full permission to perform read-only database queries to accomplish this task. You may also read the entire code base, as well as past git commits. Focus on the largest revenue drivers that will drive the biggest impact. Also focus on straightforward changes and adjustments, rather than major strategy changes. The aim is to identify the top 20 opportunities for human review. For each opportunity, give it a revenue impact score (1-5) and a likelihood of success score (1-5). Each opportunity should have a description, how big of an opportunity it is revenue wise, and how to implement the idea in the code. While you may report important bugs that you find, we are not looking to fix minor bugs that do not impact revenue. We are not performing a compliance audit or making legal interpretations over existing practices. Do not rely on the work of past agents or existing documentation. Do your own research and analysis. Put the final report in a claude artifact that can be shared.
Growth is the one job you can't hand off before you understand it yourself. A hire can run channels, but someone has to know what moves customers. If the founder hasn't figured out what works, a new hire just spends money guessing faster. Learn it first, then delegate.
The worst distractions look exactly like productivity. Reorganizing the project board, tweaking the logo, answering every email right away. It feels like progress because you're busy, but nothing that pays the bills moves. Ask what actually grows the business, and do that first.
Matt Paulson retweeted
I still use my never obsolete eMachines PC to this day.
Sure it runs Windows 98, is infected by SubSeven and a bunch of other vintage trojans, and is really only useful for playing Chex Quest, but man it plays Chex Quest like a champ.
Start with market need, not the product. A weak product in a hungry market can be fixed, because you control how fast you iterate.
You can't control whether people care, and pull can't be manufactured.
It's easier to improve a product than to make a market want it.
When you realize you weren’t actually shadow banned and you just write bad tweets.
Under the Hood now shows you which posts received a visibility-limiting label, making it easier to see what’s affected: nitter.cf/i/jf/under_the_hood
This was a top request — thanks for the feedback.
You’ll see the specific posts listed when fewer than 5% of your posts during the report period have that label.
ALT Screenshot of X's Under The Hood feature, showing a list of posts that have a given label.
In a young company, everyone should talk to customers and help them get value, even people who've never sold anything.
It's the fastest education available. You learn what people care about, where they get stuck, and which words actually make them say yes.
You can't plan how the pieces of your career will connect. You only see it looking back.
The odd job, the side project, the topic you got curious about. Most look random when they happen.
So keep collecting skills and relationships. Some will pay off in ways you can't predict.
"You've helped us out. You've driven a lot of sales. You gave us a lot of breathing room."
When a client tells you this, and they have also paid you $2 million in the last 6 months, you have product-market fit.
You A.I. is only "not good enough" because you are not giving it enough context.
Let Claude read your email, slack messages, websites, Google Drive files, etc. and it will give you much better ideas and advice.
Describing an idea is cheap. A mockup beats a description, and a working prototype beats a mockup.
But a real product in customers' hands teaches you more than all three combined.
I'd rather put something rough in front of people early than keep polishing the pitch in private.
Matt Paulson retweeted
All newsletter operators should study game from Agora/MarketWise.
Sign up for one of their newsletters that speak the most to your personality and dreams.
If you invest in the stock market, sign up for Oxford Club or Brownstone.
If you love traveling, sign up for one of their travel newsletters.
You get the point.
And see how their copy just sucks you in.
It wasn't until I signed up for a newsletter that actually spoke to me on a deeper level that I realized how insanely good at marketing they are. I was MOVED.
Matt Paulson retweeted
We have had ZERO ai related layoffs or firings.
AI has not lead to any downsizing or job loss at Ridge.
BUT-
It is skyrocketing productivity.
We will add over 100 million dollars in new revenue next year, and I might only need 10 hires to do it.
Revenue per person is going to start hitting wacky numbers- not just at ridge, but everywhere.
I dont know what this means or how it will change the world.
But expect NVIDIA level revenue per person to start being common.
Email designers are doing 10x the designs.
Product devs are doing 5x the interations.
Media buyers are getting deeper insight, from more accounts, instantly.
Anyone who wants to can be superhuman now.
The difference between a beginner and a pro isn't fancy tactics. Pros keep doing the basics, even when they're bored of them.
In email that means cleaning the list, testing subject lines, and sending on schedule long after it stops feeling exciting. The boring routines compound.
New Money Prompt with More Context:
This is a new project. Do a full analysis of the revenue generating aspects of our code base and our overall business -- MarketBeat.
Your mission is to identify opportunities to improve company revenue.
You have my full permission to perform read-only database queries to accomplish this task.
You may also read the entire code base, as well as past git commits. You may also read .md files left by Claude and other agents. You may also read my slack messages, marketbeat-related email in my inbox, marketbeat related files in Google Drive, and content from our website.
Focus on straightforward changes or strategies that will drive meaningful revenue impact ($25K per year or more).
The aim is to identify the top 15-20 opportunities for human review.
For each opportunity, give it a revenue impact score (1-5) and a likelihood of success score (1-5).
Each opportunity should have a description of the change/initiative, how big of an opportunity it is revenue wise, and how to implement the idea either in the code or i nthe business.
While you may report important bugs that you find, we are not looking to fix minor bugs that do not impact revenue or create significant risks for the company.
We are not performing a compliance audit or making legal interpretations over existing practices.
Do not rely on the work of past agents or existing Claude artifacts. Try to come up with new ideas.
Put the final report in a new Claude artifact that can be shared/reviewed.
Please spin up as many agents as necessary to complete this task successfully. You have several hours to complete this task if needed
THE MONEY PROMPT:
Do a full analysis of the revenue generating aspects of our code base. Your mission is to identify opportunities to improve revenue. You have my full permission to perform read-only database queries to accomplish this task. You may also read the entire code base, as well as past git commits. Focus on the largest revenue drivers that will drive the biggest impact. Also focus on straightforward changes and adjustments, rather than major strategy changes. The aim is to identify the top 20 opportunities for human review. For each opportunity, give it a revenue impact score (1-5) and a likelihood of success score (1-5). Each opportunity should have a description, how big of an opportunity it is revenue wise, and how to implement the idea in the code. While you may report important bugs that you find, we are not looking to fix minor bugs that do not impact revenue. We are not performing a compliance audit or making legal interpretations over existing practices. Do not rely on the work of past agents or existing documentation. Do your own research and analysis. Put the final report in a claude artifact that can be shared.
