# #221 – Rahul Bansal on Using AI Everywhere at rtCamp > [!question] Lingering Questions > - At what migration price floor does quality or sustainability actually break, if AI keeps driving per-project cost down? > - Rahul repeatedly credits luck for rtCamp's early data consolidation — how much of the AI advantage is replicable vs. a pre-AI decision that happened to pay off? > [!tip] Article Ideas > - "Apply AI, don't invent it — consolidate your data first" — a short piece for the WordPress agency audience, using rtCamp's Frappe/ERPNext consolidation as the concrete precondition example. > [!link] Cross Reference > - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] > - [[3. Resources/MOCs/Product & Startup Instincts MOC]] > [!quote] Vocabulary > - **Growth engineer** — Rahul's term for the role replacing pure coding hires: someone who can make first-call promises to clients and combine technical judgment with sales/consulting skill ## Metadata - Source: [221 – Rahul Bansal on Using AI Everywhere at rtCamp](3.%20Resources/Readwise/Articles/%23221%20–%20Rahul%20Bansal%20on%20Using%20AI%20Everywhere%20at%20rtCamp.md) - Author: Nathan Wrigley (host) interviewing Rahul Bansal, founder/CEO of rtCamp - URL: https://wptavern.com/podcast/221-rahul-bansal-on-using-ai-everywhere-at-rtcamp ## Author's thesis rtCamp's "AI everywhere" mandate works because it sits on top of a pre-existing unified, first-party data backbone (Frappe/ERPNext, consolidated years before AI made it valuable) — the lesson generalizes: apply AI to boring, high-volume, already-understood work rather than trying to invent new AI-native products, and the data consolidation is the actual precondition, not the AI adoption itself. ## Key arguments (≤3) 1. **Hire your complementary set, not copies of yourself.** rtCamp's most-repeated founding lesson: deliberately hire against your own weaknesses rather than replicating your own strengths. 2. **A unified open-source data backbone is the real AI prerequisite.** rtCamp consolidated its back office onto Frappe/ERPNext pre-AI to scale headcount; that first-party, unified data is now the lever letting them apply AI more aggressively than competitors scattered across 6-7 SaaS tools. 3. **Apply AI to boring high-volume work to grow the pie.** Make an already-understood problem (WordPress migrations) cheaper and faster; lower price floors bring in fence-sitting demand, and the bigger pie more than offsets shrinking per-project hours. ## Claim atoms ### Hire your complementary set, not copies of yourself > [!quote] ID:rw_bansal_001 > "I literally listed down my weakness and found people who were opposite of me." Audience's #1 remembered takeaway from his WordCamp Asia talk; he calls it "timeless" and still how he'd start any agency today. Replicate skill sets only later, at scale. ### A unified open-source data backbone is the AI prerequisite > [!quote] ID:rw_bansal_002 > "The data is first party. Like sitting duck there to query in any way we can. We are not limited by SaaS providers, enterprise plan or this AI capability." Frappe/ERPNext single source of truth, built pre-AI to scale headcount, became the AI lever — an edge over agencies scattered across 6-7 SaaS tools. ### Apply AI to boring high-volume work to grow the pie > [!quote] ID:rw_bansal_003 > "We are agency. Our job is to apply AI, not invent AI." Making migrations cheaper/faster brings fence-sitters into the market. The failure mode he names: vibe-coding products nobody buys, then blaming AI. ### Coding is commoditizing; value shifts to imagining what to build > [!quote] ID:rw_bansal_004 > "coding is race to bottom … You will need people who can imagine what needs to be built." "Growth engineers" who make first-call promises are the next 50 hires — not engineers. Prompt/context engineering is the rising skill. ## Permanent candidates - **AI advantage is downstream of data consolidation, not AI adoption itself** — no existing Permanent Note found covering this claim. Promoted this run: [[3. Resources/Permanent Notes/AI Leverage Requires a Consolidated Data Backbone Built Before the AI Need]]. ## Processing checklist - [x] Checked existing Permanents for duplicates — none found - [x] Connect into [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] and [[3. Resources/MOCs/Product & Startup Instincts MOC]] ## Links - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — AI-driven agency restructuring - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — founder-level agency-building lessons