What You'll Learn
From Filmmaker to Fortune 500 AI Trainer: A Non-Technical Journey
The traditional path to building software has always felt like a locked door for non-technical founders. You need a CS degree, a technical co-founder, or a six-figure development budget just to get started. But what if none of that were true anymore?
JJ Englert's story proves that the rules have fundamentally changed. Today, he travels the country training Fortune 500 companies on AI adoption. But in 2017, he was a filmmaker in Los Angeles who couldn't even get a simple marketplace app built without spending $50,000—and still failing.
The $50,000 Lesson in Traditional Development
When JJ had his first startup idea—a marketplace to help traveling filmmakers hire local crew—he did what most non-technical founders do: he found a developer. An ex-Microsoft engineer quoted him $50,000 to build it with .NET.
After raising the money and waiting six months, JJ had exactly three pages: a homepage, a signup page, and a login page. Nothing else.
The problem wasn't just the money or the time. It was the complete loss of control. As a founder, he couldn't respond to customer requests. He couldn't iterate quickly. Every feature decision carried enormous weight because each change meant weeks of development time and thousands of dollars.
"If I spent three months building a feature, that feature better work," JJ recalls, "because I don't have much money left after that."
This experience crystallized a painful truth: the traditional software development lifecycle was fundamentally broken for non-technical builders. You had to get everything right on the first try, which is nearly impossible when building something new.
The No-Code Breakthrough
By 2020, JJ had raised more money and was running out of runway. Rather than admit defeat, he made a different choice: learn to build it himself.
He discovered Bubble through one of their classic blog posts—"Build Airbnb in One Day." The promise seemed almost too good to be true, but he found a course on Udemy by instructor Gregory John and decided to commit.
Three lessons in, everything changed.
"I went from talking to a developer to just dragging and dropping onto the screen," JJ remembers. "I was shouting to my wife: 'Can you believe this? I'm actually signing a user up. I'm creating this.'"
The immediate feedback loop of visual development—seeing results instantly rather than waiting weeks—was transformative. JJ spent nights and weekends learning, not because he had to, but because he genuinely loved the process.
No-code didn't just make building faster. It gave him back ownership of his vision.
When AI Coding Tools Entered the Picture
While no-code solved many problems, JJ's journey didn't stop there. As AI coding assistants emerged, they added another dimension to what non-technical builders could accomplish.
AI tools enabled even faster experimentation. You could describe what you wanted to build conversationally, get working code, iterate on it, and deploy—all in a fraction of the time traditional development required.
This combination of no-code platforms and AI assistance created a new category of builder: people who could turn ideas into working software through curiosity and repetition rather than formal training.
From Personal Tools to Viral Community Apps
One of JJ's post-no-code projects was a community app that unexpectedly went viral. The key insight: he built it to solve his own problem first, then shared the process publicly.
This approach—build for yourself, share what you learn, iterate based on real feedback—became his framework for creating products that actually mattered to users.
Today, JJ applies these same principles when training Fortune 500 executives. His grandmother once asked what he does for a living. His answer: "Remember when the internet was born and everyone had to learn how to use it? That's what I do now, but with AI."
Why Credentials Matter Less Than Curiosity
JJ's story challenges the persistent myth that you need to be "technical" to build software. Throughout his journey, he repeatedly felt he "wasn't smart enough"—not good at math or science in school, no engineering background, no CS degree.
But modern tools have changed the equation. Success comes from:
- Consistent practice: Nights and weekends spent learning compound over time
- Genuine curiosity: Loving the process of building keeps you going when things get hard
- Community support: Learning alongside others who share knowledge freely
- Willingness to share: Teaching what you learn reinforces your own understanding
The old gatekeepers—expensive developers, long timelines, technical jargon—are increasingly irrelevant. The new requirement is simpler: show up, experiment, and keep building.
The Compounding Effect of Building Publicly
One of the most powerful patterns in JJ's journey is how small personal projects compounded into larger opportunities. Building tools for himself led to community engagement. Community engagement led to knowledge sharing. Knowledge sharing led to teaching roles. Teaching roles led to training Fortune 500 companies.
This isn't a traditional career path. It's what happens when you combine modern tools with consistent, public practice.
What This Means for You
If you have an idea you wish existed, the barriers have never been lower. You don't need to:
- Spend $50,000 on developers
- Wait months for a single feature
- Learn to code from scratch
- Have a technical co-founder
- Possess a CS degree
You need to:
- Pick a no-code or AI-assisted platform and commit to learning it
- Build something small that solves your own problem
- Share what you're learning publicly
- Join communities of other builders
- Keep iterating based on real feedback
The question isn't whether you're technical enough. It's whether you're curious enough to start.
