No-Code Development (Webflow, Bubble)

Webflow = static/marketing sites (blogs, landing pages, portfolios). Best for designers who want pixel-perfect control. Bubble = dynamic apps with databases, user auth, workflows. Best for complex CRUD apps, multi-user platforms, dashboards. Framer = interactive prototypes + marketing sites with motion. Best for design-forward products, design systems, brand showcases. In practice: Webflow for 80% of service work (client websites), Bubble for 15% (startups prototyping MVP), Framer for 5% (design-heavy brands). Mix and match as needed — e.g., Webflow marketing site + Bubble app backend.

No-code hits a ceiling when: (1) Vendor API limits / rate limiting caps revenue, (2) Custom business logic requires complex logic no-code can't express, (3) Unit economics demand 10x efficiency (code pays for itself), (4) Founder needs defensibility / IP (no-code stacks are commoditized), (5) Scaling to enterprise (customers demand on-prem, compliance, SLA). Typical escape: build MVP in no-code (3-6 months, <$30k), validate product-market fit (100+ customers or $10k/mo), then rebuild in code (3-12 months, $50-150k). No-code is fastest path to revenue, code is best path to scale. Best practice: stay no-code as long as growth > technical debt.

Yes and no. Webflow exports HTML/CSS, so you're not truly locked in (though migration requires re-architecture). Bubble exports less gracefully — you'd rebuild from scratch. Airtable data exports via API/CSV. The lock-in = time + sunk architectural decisions, not legal. Lock-in is actually useful: by picking a platform, you're saying 'this vendor's evolution is my roadmap'. Real risk: vendor raises prices (Bubble → Stripe percentage taken), sunsetting (Airtable could 🔪 if WeWork crashes), or feature roadmap misalignment. Mitigation: use platforms with strong communities, avoid single-vendor stacks (e.g., Webflow + Make + Airtable, not just Bubble for everything), keep a migration plan in mind (but don't over-engineer for it).

Partially. Webflow exports clean HTML/CSS/assets that developers can extend. Bubble exports a JSON-like config that's painful to extend (custom code is more reliable). Framer exports React code that developers can refactor. Airtable data exports via API/CSV. Generally: treat no-code as a prototype or permanent solution, not a 'stepping stone' where you plan code-ification. If you know you'll code later, save time and start with code (frameworks like Next.js have no-code-adjacent tooling like Vercel AI SDK, Supabase for databases). No-code + code hybrid = architectural mess unless carefully planned.

Three models: (1) Project-based ($5-50k per site/app, depending on complexity and client caliber). Typical breakdown: landing page $3-8k, e-commerce rebuild $15-40k, custom app $30-150k. (2) Productized ($1-3k/mo recurring for 'website subscription' service, client pays, you own). Margins 70%+ if systematized. (3) Revenue share (agency retains 30-50% of SaaS revenue for 12+ months). Agencies doing (1) end up commoditized; those doing (2) scale faster. Agencies doing (3) become de facto co-founders. Pricing depends on location (US/London command 3x Ukrainian rates) and specialization (e-commerce + Shopify = higher than generic site builders). Pro tip: transition away from (1) ASAP — time is finite, recurring revenue isn't.

Rates: $50-150/hr (junior freelancer, simple Webflow sites), $150-300/hr (mid-level, Webflow + Bubble), $300-500+/hr (senior, complex apps, agencies hire you). Project rates: $2-5k landing page, $8-20k Webflow site, $15-60k Bubble MVP, $50k+ custom Bubble app with integrations. Escape the hourly trap: charge $3-8k per project (fixed), deliver in 2-4 weeks, repeat 10x per year = $30-80k without hourly ceiling. Freelancer in US/UK: $50-80k/year (projects) is realistic, $100k+ possible in tier-1 cities or with productized services. Freelancer in cheaper countries: same projects, 2-4x lower rates (market sets it, competition is global).

No-code tooling itself = commodity (anyone can rebuild your Bubble app in Bubble). Defensibility comes from: (1) Proprietary data / network effects (e.g., your Airtable base is the moat, not the UI), (2) Deep domain expertise (agency that specializes in fitness SaaS or real estate, not generic Bubble shops), (3) Unique integrations (you glued together 5 APIs that no one else did), (4) Distribution / audience (audience is worth more than the product), (5) Code escape hatch (you own the code, platform is just architecture). If you're selling 'a Bubble app', you have a services business, not a product business. If you're selling 'an industry solution that happens to be built in no-code', you have a product. Timing to code shift: when your NPS is 50+, you've hit the ceiling of what no-code can do, and you have paying customers who'll fund the rewrite.