The Startup Ideas Podcast

Get Your Complete Financial OS at https://startup-ideas-pod.link/brex_SIP

I welcome Ras Mic back to the pod to explain the phrase "software factory." Mic shares his screen and walks through the exact system that he runs today. His factory has four steps: isolate, build, prove, and ship. He keeps the whole system in five or six markdown files, so it works with any model and any harness. By the end of this episode, you can boot up your own factory, run many agents in parallel, and trust the code that comes back.

Create your own Software Factory: https://startup-ideas-pod.link/ras-software-factory

Timestamps

00:00 – Intro

02:17 – Software Factory Definition

03:44 – Why the Software Factory Matters

05:23 – Step 1: Isolate With Git Work Trees

11:34 – Step 2: Build With the Code Structure Skill

14:48 – Step 3: Prove With Evidence-Driven Testing

22:25 – Step 4: Ship With Grep Loop and Greptile

26:52 – The Physical Factory Analogy

29:21 – A Software Factory Is Markdown Files

30:02 – Closing Thoughts

Key Points

A software factory is a workflow of skills and domain knowledge, so it runs with any model and any harness.

Isolate: every feature starts in a fresh git work tree branched from origin main, so each agent keeps its own station.

Build: a code structure skill makes the agent write service layer code that a human developer can read.

Prove: the agent records a before state and an after state as video, screenshots, or numbers.

Ship: Greptile scores the PR, and the agent loops back to build until it earns five out of five.

Mic runs up to 15 features in parallel and reviews the visual proof instead of the raw code.

The #1 tool to find startup ideas/trends - https://www.ideabrowser.com

LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/

FIND ME ON SOCIAL

X/Twitter: https://twitter.com/gregisenberg

Instagram: https://instagram.com/gregisenberg/

LinkedIn: https://www.linkedin.com/in/gisenberg/

FIND MIC ON SOCIAL

X/Twitter: https://x.com/Rasmic

Youtube: https://www.youtube.com/@rasmic

I talk with Ras Mic about GPT-6 Astra. We skip the game demos and the 3D toys, and we focus on use cases to earn money or improve products. I share 9 Astra prompts that I posted publicly, and Greg Brockman reposted. Ras then shows his hardware project: he moved from a speaker idea to a parts list, a Blender layout, and merged code in about 30 minutes. The takeaway is simple: use this model for the ideas that felt too large for you last year.

Timestamps

00:00 – Intro

01:53 – Astra Overview

04:14 – 9 Astra Prompts

11:48 – Jarvis Speaker Idea

16:21 – Think Bigger with Astra

18:29 – Vibe Coding to Vibe Manufacturing

21:16 – Closing Thoughts

Key Points

Astra costs more per task, and it uses fewer steps, so the value per dollar stays high.

A performance audit moved one of Ras’s apps from 800 ms to 20–30 ms.

A security audit on his live payments app found real risks in production.

Ras went from a speaker idea to a $561 parts order and a merged pull request in about 30 minutes.

Ras’s point: intelligence keeps climbing, and bravery stays flat. Ask for bigger things.

The shift that vibe coding brought to software now reaches physical products.

The #1 tool to find startup ideas/trends - https://www.ideabrowser.com

LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/

FIND ME ON SOCIAL

X/Twitter: https://twitter.com/gregisenberg

Instagram: https://instagram.com/gregisenberg/

LinkedIn: https://www.linkedin.com/in/gisenberg/

FIND MIC ON SOCIAL

X/Twitter: https://x.com/Rasmic

Youtube: https://www.youtube.com/@rasmic

I run this episode solo. I explain local AI in plain terms: the model runs on hardware I control, and a cloud model runs somewhere else. I map the four pieces of the local AI landscape — the model, the warehouse, the software, and the workflow — and I define the words that beginners meet first: parameters, tokens, context window, quantization, and GGUF. I walk through the Google open model stack (Gemma 4, Google AI Edge, LiteRT-LM, AI Edge Gallery), compare the other open model families, and show three ways to run a model today. I close with a first workflow you can copy and three startup ideas that use local AI as the wedge.

And a special thank you to Google for supporting the podcast.

Timestamps

00:00 – Intro

01:35 – The Open Model the Landscape

03:09 – Vocab Decoder

06:48 – Google Gemma Clearly Explained

10:29 – Other Open Model Families

14:20 – Path 1: Run Gemma in LM Studio

18:17 – Path 2: Ollama

20:15 – Path 3: Google AI Edge

21:07 – Hardware Cheat Sheet

21:52 – First Workflow to Build

22:47 – Workflows Before Fine-Tuning

25:06 – Local vs Cloud vs Hybrid Eval

26:33 – Framework for Local AI Startup Ideas

27:22 – Startup Idea 1: Home Health QA Reviewer

29:24 – Startup Idea 2: Offline Field Report Copilot

32:10 – Startup Idea 3: Pre-Send Reviewer for Professional Services

34:47 – Build Your Local AI Lab

37:55 – Closing Thoughts

Key Points

Ask whether the model is good enough for the job, and the business opportunities become clear.

Local AI has four pieces: the model, the warehouse (Hugging Face), the software (LM Studio or Ollama), and the workflow you build around them.

Gemma 4 E4B is my practical starting point; E2B fits phones and older machines.

Hybrid architecture wins: local does the private first pass, cloud does the heavy reasoning, and a human approves anything important.

Start with one repeated workflow — one folder, one model, one output — and run it 10 times.

I see a 24-month window to build local-AI-native software for verticals that still run early-2000s tools.

The #1 tool to find startup ideas/trends - https://www.ideabrowser.com

LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/

The Vibe Marketer - Resources for people into vibe marketing/marketing with AI: https://www.thevibemarketer.com/

FIND ME ON SOCIAL

X/Twitter: https://twitter.com/gregisenberg

Instagram: https://instagram.com/gregisenberg/

LinkedIn: https://www.linkedin.com/in/gisenberg/

On this solo episode, I review five free, open source GitHub repos that help you build products, make money, or save time: Peter Yang's No AI Slop Skill, the CRM by TryComp AI, Video Use by browser use, SkillSpector by NVIDIA, and Phone Harness. For each repo I explain what it does, why it matters, how to install it, and the first small workflow to try. I close with a simple three-step method: install the repo, make one small workflow work, then decide to productize it or keep it as your own leverage.

Timestamps

00:00 – Intro

01:44 – Repo 1: No AI Slop

05:20 – Repo 2: Agentic-first CRM

10:52 – Repo 3: Video Use

15:15 – Repo 4: SkillSpector

18:49 – Repo 5: Phone Harness

22:25 – Closing Thoughts

Links to repos:

petergyang/no-ai-slop — https://github.com/petergyang/no-ai-slop

trycompai/crm — https://github.com/trycompai/crm

browser-use/video-use — https://github.com/browser-use/video-use

NVIDIA SkillSpector — https://github.com/NVIDIA/SkillSpector

phone-harness — https://github.com/ShawnPana/phone-harness

The #1 tool to find startup ideas/trends - https://www.ideabrowser.com

LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/

FIND ME ON SOCIAL

X/Twitter: https://twitter.com/gregisenberg

Instagram: https://instagram.com/gregisenberg/

LinkedIn: https://www.linkedin.com/in/gisenberg/

In this solo episode I explain a role that I call the marketing engineer. I believe this person becomes one of the most valuable hires in tech in the next 18 to 24 months. I define the job, I show the four eras of marketing that lead to it, and I give the tool stack that makes it work. I use a commercial HVAC software company as a worked example, and I list six systems that a marketing engineer builds. I close with four ways to earn money from this skill and a 30-day plan to learn it.
Timestamps:
00:00 – Intro
01:46 – The Evolution of Marketing
04:29 – What is a marketing engineer
07:19 – Build the Growth OS
10:18 – Marketing Engineer Tool stack
13:23 – Live Data Workflow
14:32 – Agent Job Description
16:56 – Example: vertical SaaS for HVAC contractors
18:27 – System 1: Customer Truth
20:20 – System 2 - 4: Founder content, Outbound signal and Creative Testing
23:31 – System 5: AI search visibility and the growth cockpit
24:19 – System 6: Eval Loop
25:06 – Ways to Monetize
29:41 – The 30-day plan
32:24 – Closing Thoughts
Key Points
I expect the marketing engineer to command salaries from 250K to more than 1 million dollars.
I build the growth repo first, because it holds the marketing memory of the whole company.
I write a job spec for each agent, in the same way that I write a job description for a person.
I measure qualified replies and pipeline, because business results show the true signal.
I treat taste and judgment as the moat, because agents become a commodity.
I recommend one working system over five half-built ones.
The #1 tool to find startup ideas/trends - https://www.ideabrowser.com
LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/
FIND ME ON SOCIAL
X/Twitter: https://twitter.com/gregisenberg
Instagram: https://instagram.com/gregisenberg/
LinkedIn: https://www.linkedin.com/in/gisenberg/