published jun 20, 2026
Members get every guide, course, and $1,000+ in partner perks.
In this guide, you will learn how to use Codex and Airtable to build an infinite business idea generator. If you build websites, apps, or automations with AI, this will help you find the painful problem people may pay you to fix.
This is useful if you can already build with AI, but you are not sure what painful problem someone might pay you to fix.
The goal is not to ask AI for random startup ideas. The goal is to create an AI Pain Radar: a repeatable system that finds public complaint signals, stores the raw evidence, and turns repeated pain into business ideas that stay linked to the posts that inspired them.
It is especially useful for:
You will build a two-table Airtable base and connect it to recurring Codex automations.
The first automation mines public complaint signals and turns them into linked business ideas. The second automation, in the Going Further section, looks at the top-rated idea from the day before and creates a simple landing-page proof of concept in a local folder.
By the end, Airtable becomes your evidence database. Codex becomes the research and build agent that keeps adding new ideas and tests.
The next step is to make the system build a tiny proof of concept for the best idea.
Create a standalone folder inside the guide or project:
proofs-of-concept/Then add a few tracking fields to your Business Ideas table:
Now set up a second Codex automation. This one should run after the idea miner, look at the top-rated business idea from the previous day, and create a single static landing page in a new local folder.
Use this prompt:
Set up a recurring Codex automation called Daily Airtable Idea Landing Page POC.
Every morning, look at the Business Ideas table in Airtable and find the top-rated idea created during the previous calendar day.
Rank ideas by opportunity_score, then confidence, then evidence strength. Prefer ideas that do not already have prototype_status = generated.
For the selected idea, create a new local folder inside:
[PROJECT_FOLDER]/proofs-of-concept/
Slug the folder from the idea name. Inside that folder, create:
- index.html
- styles.css
- README.md
Build a simple static landing page using the Airtable fields for the headline, target persona, problem, proposed solution, evidence summary, validation metric, next action, and weakness or risk.
The page should include:
- a hero
- a product workflow or product preview
- an evidence/proof section
- a waitlist or interview CTA stub
After the files are created, update the selected Airtable record:
- prototype_status = generated
- prototype_path = the local index.html path
- prototype_generated_at = the current local ISO timestamp
If generation fails after selecting an idea, set prototype_status = needs_review and explain the issue in reviewer_notes.
If there are no qualifying ideas from the previous day, do not create a project.This turns the Pain Radar into a full idea loop: find pain, store evidence, score opportunities, and create something small enough to test.
You can use the landing page as a waitlist, a cold outreach asset, a tweet thread anchor, or a quick prototype brief.
The important part is that the landing page still traces back to the Airtable idea, and the Airtable idea still traces back to raw evidence.
That chain is what keeps the system useful.
Start by signing in to Airtable. If you are new to Airtable, think of it like Google Sheets with stronger field types, views, AI fields, and automations.
Then open the Codex desktop app, go to Plugins, search for Airtable, and add it.
After the plugin is connected, start a new Codex thread and mention Airtable directly with @Airtable. Before you ask it to create anything, ask it to inspect the connection.
Pro tip: Have Codex inspect a new plugin before it builds with it. This prevents a lot of failed prompts where the model guesses what the connector can do.
Use this prompt:
Check my Airtable connection.
List the bases I can access, identify the most recently used base, and tell me whether you can create tables and records in it.
Do not change anything yet.This gives Codex a chance to learn what the Airtable connector exposes in your account. Once Codex can see Airtable, Airtable becomes the database layer for the research agent.
The clean version of this system uses two tables:
This matters because raw posts are evidence. Business ideas are conclusions. Keeping them separate makes the system harder to fool.
Ask Codex to create the schema for you instead of pasting a long list of columns manually.
Use this prompt:
Create an Airtable schema for an AI Pain Radar.
Use two tables:
1. Raw Reddit Posts
- one row per raw public complaint signal
- fields for source, URL, thread title, post/comment text, quote, persona, company stage, job to be done, pain summary, pain cluster, intensity, urgency, willingness to pay, evidence quality, discovery date, research status, duplicate notes, and reviewer notes
2. Business Ideas
- one row per synthesized opportunity
- fields for idea ID, idea name, status, pain cluster, target persona, problem summary, proposed solution, supporting posts, evidence summary, best quotes, scoring rubric, confidence, business model, landing-page headline, landing-page test, validation metric, next action, weakness/risk, and reviewer notes
Link Business Ideas back to Raw Reddit Posts through a supporting_posts linked-record field.
Seed a few fictional demo rows so I can verify the relationship.After Codex finishes, open the Airtable base and check the two tables.
The raw table should hold the source evidence.
The ideas table should hold the synthesized opportunities.
The important field is the linked-record field from Business Ideas back to Raw Reddit Posts. Every idea should point back to the raw posts that support it.
If an idea cannot point back to evidence, it should stay marked as weak evidence or stay out of the ideas table entirely.
You can use Airtable as a plain database, but a few views make review much faster.
For Raw Reddit Posts, ask Codex to create or suggest views like:
For Business Ideas, create views like:
Use this prompt:
Suggest useful Airtable views and AI classification fields for this AI Pain Radar.
For Raw Reddit Posts, suggest views for:
- Ready for Review
- High Intensity
- Needs Source Check
- Linked to Ideas
For Business Ideas, suggest views for:
- Top Opportunities
- Landing Page Tests
- Weak Evidence
- Rejected or Parked
Also suggest Airtable AI field instructions that classify pain clusters, evidence quality, and idea quality without inventing facts.Airtable AI can help classify and score rows after the evidence is already in the base.
The key limitation: Airtable AI is not the recurring web researcher here. Use it to classify, summarize, and score the records Codex adds.
Now have Codex set up the recurring research job.
This automation should check public communities, find complaint signals, dedupe against Airtable, write raw evidence first, and only create business ideas when there is enough support.
Use this prompt:
Set up a recurring Codex automation called Reddit Pain Radar.
Every weekday morning, find 10-20 fresh public complaint signals from Reddit-style discussions, public forums, product reviews, and founder/operator communities.
Write accepted evidence into Raw Reddit Posts first.
Only create or update Business Ideas when there is enough evidence or a clearly high-intensity workflow pain. Every Business Ideas record must link back to supporting Raw Reddit Posts.
Respect source terms, avoid private or login-gated communities, do not store personal identifiers, dedupe before writing, and label weak evidence instead of overstating it.You can swap in your own sources:
Every weekday, check [SUBREDDIT_1], [SUBREDDIT_2], and [SUBREDDIT_3] for complaints about slow, expensive, confusing, or repetitive work.Do not make the job create an idea for every post. That defeats the point. Most posts should stay as evidence until there is a pattern.
A good business idea record should include:
Once Codex has added raw evidence and a few candidate ideas, use Airtable AI or another model to score the ideas. The rule is simple: the score has to come from linked evidence.
Use this prompt on a Business Ideas record:
Classify and score this idea using only linked supporting posts.
Return:
1. pain cluster
2. buyer/persona
3. evidence summary
4. best customer quotes
5. intensity score 1-5
6. frequency score 1-5
7. specificity score 1-5
8. willingness-to-pay score 1-5
9. buildability score 1-5
10. 100-point opportunity score
11. one weakness or risk
12. next landing-page test
If the linked evidence is weak, say weak evidence instead of improving the idea.This keeps the system honest. AI is allowed to score the idea, but it is not allowed to make the evidence sound better than it is.
If the model starts inventing details, use this recovery prompt:
Pause and revise using only linked raw post evidence.
For each claim, point to the supporting post ID or quote. If there is not enough evidence, mark it weak evidence.
Keep the output to:
1. pain cluster
2. evidence quotes
3. score
4. weakness
5. next landing-page testBefore you let the automation run every day, ask Codex for one bounded test run.
Use this prompt:
Run a small test of the Reddit Pain Radar.
Find 5 public complaint signals across the target communities, add them to Raw Reddit Posts, and create Business Ideas only when the evidence supports them.
After writing to Airtable, read the records back and confirm that each idea links to its supporting raw posts.In our test, Codex added five raw complaint signals and three business ideas. The strongest idea was a freelancer payment reminder assistant, supported by two posts about the same pain: freelancers need to get paid without sounding pushy or damaging client relationships.
That test became the landing-page proof of concept shown at the top of this guide.
Keep going
Members get all guides, courses, live sessions, and $1,000+ in partner perks.