There's a guy in LA who films squirrels for a living. His name is Derrick Downey Jr., his squirrel is named Hoodrat Raymond, and last month he vibe-coded the number one paid app on the entire App Store. By himself. In about a weekend.
I read that and felt two things simultaneously: genuine admiration, and the specific kind of envy you get when someone casually does the thing you spent a decade learning how to do.
Welcome to one person business dev in 2026, where the barrier to shipping real software has dropped so low that a wildlife content creator can build DualShot Recorder - and where those of us who've been doing this for twenty years are sitting here like, "Cool, so my entire skill tree was a side quest."
Except it wasn't. And that's what I want to talk about tonight.
One Person Business Dev Doesn't Mean One Weekend of Work
Here's what the DualShot story doesn't tell you: Downey tried buying rigs, gimbals, extra phones, and editing workflows before he ever wrote a line of code. He spent months living with the problem. The app took a weekend. The understanding took a year.
That's the part that matters for anyone running a small business.
I've been a one person business dev for over two decades now. I build websites, AI tools, and automation for small businesses around the Bay Area - HVAC companies, dog groomers, wedding photographers, the whole spectrum. And the single biggest misconception I run into is that "solo" means "fast and scrappy."
Sometimes it does. But usually it means you're the developer, the project manager, the QA tester, the sysadmin, the copywriter, and the person who has to explain to a florist why her contact form sends emails to spam. You're not scrappy. You're a full org chart in a hoodie.
The Actual Setup Behind a One Person Business Dev Shop
People ask me about my editor setup like it's the interesting part. It's not. VS Code. Some extensions. Done. The interesting part is everything around it that lets one person ship what used to take a team.
Here's what my daily stack actually looks like:
Claude Code CLI - I pipe research, outlines, and prompts into Claude directly from the terminal. It writes first drafts of blog content, generates structured data, and handles the boring parts of code scaffolding. I still read every line it outputs, because AI that writes code without a human reviewing it is just a very confident intern.
A real deployment pipeline - Not a fancy one. A cron job, a Python script, and an API endpoint. That's the whole thing. It runs every day, and when it breaks, I fix it, because there's no DevOps team. There's me and a cup of coffee and tail -f on a log file.
Gemini for image generation - Because hiring a designer for every blog hero image when you're a solo operation is like buying a food truck to make one sandwich. The AI handles it. It's not perfect, but it's Tuesday and I have twelve other things to do.
A marketing suite that doesn't require a marketing degree - I built links.autom84you.com specifically because every small business owner I worked with needed QR tracking and link management, and every existing tool wanted $49/month for what amounts to a redirect with analytics.
None of this is glamorous. That's the point. A one person business dev setup isn't about having the coolest tools. It's about having the fewest tools that still let you ship.
Why the Squirrel Dad Story Actually Matters

That's the cheat code for one person business dev: you don't need market research when you are the market.
I see this with my clients constantly. A taco truck owner who knows exactly what's wrong with every online ordering system because he's used nine of them and they all handle modifier pricing badly. A yoga studio owner who can describe her ideal booking flow in three sentences because she's manually handled five thousand bookings.
The people closest to the problem build the best solutions. They just usually don't know they can.
That's where someone like me comes in. Not to sell you a $30,000 custom platform. To build the specific thing you actually need - the one feature, the one automation, the one integration - so you can go back to running your business instead of fighting your software.
What Big Tech Is Doing (And Why You Shouldn't Care Much)
Meanwhile, in a completely different universe: Coatue, a venture capital firm, just launched a company called Next Frontier to buy up land near power plants and turn it into data centers. They've partnered with a startup that signed a fifty billion dollar deal to build infrastructure for Anthropic.
Fifty. Billion. Dollars. On buildings to house the computers that run AI.
I mention this not because it affects your day-to-day, but because it's useful context. The tools that make one person business dev possible - Claude, Gemini, the whole ecosystem - exist because someone is spending GDP-of-a-small-country money on the infrastructure behind them. You're basically getting subsidized superpowers while venture capitalists figure out whether this whole AI thing will make them richer than they already are.
Enjoy it. Use the tools while they're cheap. Build things. The window where a solo developer has access to the same AI that billion-dollar companies use won't last forever.
The One Person Business Dev Toolkit in Practice
If you're a small business owner thinking about building something yourself - or hiring someone to do it - here's what actually matters in 2026:
Start with the pain, not the tool. Downey didn't set out to build an app. He set out to stop juggling two phones on a gimbal while a squirrel named Maxine waited impatiently for cashews. Your version of that is the spreadsheet you update manually every Friday, or the booking system that doesn't talk to your invoicing, or the Instagram posting you do by hand at 9 PM.
AI is the assistant, not the architect. I use Claude Code every single day. It's remarkable. It also confidently generates nonsense about 8% of the time, which is exactly the failure rate you'd expect from a very smart coworker who never asks clarifying questions. A one person business dev still needs to understand what they're building. The AI just means you spend more time thinking and less time typing.
Simple beats clever. My entire blog publishing pipeline is a Python script and a cron job. It's not microservices. It's not Kubernetes. It's a file that runs at 6 PM and either works or tells me why it didn't. When you're the only person who has to maintain something, simplicity isn't a compromise - it's a survival strategy.
Automate the repeatable, not the creative. I built tools to handle social media posting, image generation, and content scheduling automatically. I did not automate deciding what to write about, because that's the part that requires having opinions and a pulse. Know the difference.
The Real Flex Is Boring
Being a one person business dev isn't about the dramatic launch story. It's about the Wednesday afternoon where you fix a client's contact form, update your own blog, deploy a small automation for a dog groomer in San Jose, and still have time to walk your actual dog before dinner.
Downey's DualShot Recorder is a great story. But for every overnight App Store hit, there are thousands of solo devs quietly building tools that serve fifty people really well, and those fifty people are grateful, and the dev makes a living, and nobody writes a Verge article about it.
That's fine. That's the actual job. And if you do it well - if you pick the right problems, keep your tools simple, and treat AI like the useful-but-fallible assistant it is - one person really can ship what used to take a team.
Just maybe not in a weekend. And definitely not while feeding squirrels.
If you're running a small business and something about your website, your tools, or your workflow is making you want to throw your laptop into a lake - I get it. I've been that one person business dev for twenty-plus years, and I'm pretty good at building the thing that makes the laptop-in-the-lake feeling go away. Custom sites start at $500, AI chatbots at $1,000, or just email nerd@a84y.com and tell me what's broken. I'll probably know the fix before you finish describing the problem.
Comments
No comments yet. Be the first to share your thoughts!
Leave a Comment