AI Prompting Kills Small Website Fees | Analysis by Brian Moineau

TL;DR

  • Business Insider’s Kelsey Vlamis copied Sam Altman’s exact ChatGPT prompt and, in under two hours, shipped a functioning group‑trip website—no hand coding required [1].
  • The business story is bundling: OpenAI’s Sites (public beta) turns a $20/month ChatGPT Plus subscription into an all‑in‑one builder‑and‑host, compressing the entry‑level website market and rerouting demand away from third‑party hosts [2][5].
  • If “vibe coding” becomes the default for simple apps, the first losers are low‑end hosting fees and small “brochure site” gigs; the winners are platforms with free or near‑free deployment paths (Cloudflare Pages, Render static sites) and any incumbent that pairs distribution with opinionated AI workflows [3][4][7].

What the source said

Kelsey Vlamis took Sam Altman’s prompt—asking ChatGPT to mine her chat history, plan three long‑weekend options for nine friends, build a coordination website, and draft an email—and got a live site within two hours, without writing code [1]. ChatGPT walked her through Terminal basics, GitHub, and deployment; she briefly paid $7.25/month on Render before being nudged toward free options [1][7]. OpenAI also pointed her to “Sites,” a public‑beta feature that lets Plus users create, edit, and host sites from inside ChatGPT [1][2]. The shipped site handled voting, budgeting, dates, and task assignment, and she iterated small changes via chat and redeploys [1].

Why it matters

Two business levers just moved. First, “vibe coding” converts intent into working software for non‑developers at consumer price points. Second, hosting is collapsing into the chat surface: a $20/month ChatGPT Plus plan with Sites (public beta) makes “ship a simple web app” feel like a zero‑incremental‑cost add‑on for millions of subscribers [2][5]. That threatens paid tiers where traditional builders and hosts monetize basics (Wix entry plans and managed static hosting) and reshapes the freelance “simple site” market [6].

Stakeholders include consumer site builders (Wix, Squarespace), infra and JAMstack deployers (Cloudflare, Render, Vercel), and small agencies that sell brochureware. Near‑term winners are platforms with generous free tiers and frictionless deploys—Cloudflare Pages and Render static sites—because they catch graduates who outgrow Sites or want custom domains and integrations without a surprise bill [3][4][7].

Original analysis

Consensus says “vibe coding” will steamroll no‑code and hosting; that’s lazy. The real motion is bundling: the point of creation (chat) is swallowing scaffolding and commodity hosting, just as Heroku (2007) and Google App Engine (2008) bundled deploy + runtime for developers before recommercializing around add‑ons and scale [10][11]. Distribution, commerce, and governance will re‑differentiate, echoing earlier cycles from GeoCities (1994) to GitHub Pages (2008) that started simple and later pushed users into richer stacks [9][10].

  • Back‑of‑envelope math

    • Replace a template site: A solo user on Wix will likely pay $17–$159/month when billed annually to remove branding, attach a domain, and access basics [6]. ChatGPT Plus is $20/month and, per OpenAI, Sites is available in public beta to Plus users—i.e., build/edit/host from the same surface [2][5]. If you already pay for Plus, the incremental cost to ship a simple public site is roughly $0/year versus at least $204/year for Wix’s entry plan ($17×12), before any transaction add‑ons [6]. Cloudflare Pages and Render static hosting both offer free routes, so if you outgrow Sites you can still deploy at $0 hosting cost and keep total spend near the $20/month you were paying anyway [3][7].
    • Arithmetic takeaway: Basic “presence” sites and micro‑tools will consolidate into Plus for subscribers.
    • Cost floor on hosting: Cloudflare Pages’ free plan supports up to 20,000 files per site on the Free tier—ample for personal projects and small marketing sites—undercutting paid entry hosting tiers for many use cases [4]. Render static sites are also free with managed TLS, which erases the old “but SSL and build pipelines are hard” objection [7].
  • 2x2: Complexity vs. Stakes (who wins where)

    • Simple + Low‑stakes (trip‑planners, checklists, RSVP pages): ChatGPT Sites wins. Fast iteration beats pixel‑perfect control.
    • Simple + High‑stakes (lead‑gen with compliance, data capture): Cloudflare/Render/Vercel + human review. You need auditability and integrations.
    • Complex + Low‑stakes (hobby SaaS, side projects): AI‑assisted frameworks (export from Sites or start on Pages/Render) with code‑level control.
    • Complex + High‑stakes (payments, PII, regulated workflows): Traditional engineering with AI copilots. Governance, testing, and SLAs dominate.
  • Named‑stakeholder breakdown

    • OpenAI: The moat is bundling. Sites keeps users “in the chat,” raises Plus stickiness, and pressures incumbents on the first dollar of spend [2][5].
    • Cloudflare: Quiet beneficiary. Pages’ free tier (20k file limit; Workers/Functions on a free allotment) absorbs migrations when users need domains, CI, or edge logic without a new bill line [3][4][8].
    • Render: Mixed bag. Free static sites blunt churn from Sites, but the “$5–$10/month” habit on entry hosting will deflate if “basic hosting” becomes a feature, not a product [7][12].
    • Wix/Squarespace: Risk on the bottom rung. If “Plus already in wallet” becomes normal, willingness to start a paid builder at $17+/month erodes; their counter is integrated commerce, templates, and distribution [5][6].
    • SMB agencies/freelancers: Fewer paid “brochure site” tickets; more paid “prompt ops + integration + QA.” The unit of work shifts from pages to workflows.
  • Historical analogue

    • GeoCities (1994–2009) proved that bundling creation + hosting pulls in amateurs first, then hits limits on commerce and control, which competitors monetize later [9].
    • Google App Engine’s 2008 beta and Heroku’s 2007 launch set the template for “free or cheap deploy, monetize on scale/add‑ons,” the same gravity now visible with Sites + free static hosts [10][11].

Contrarian read: The hot take is that Sites kills hosts; short‑term, the larger casualty is the “I’ll just spin up a $7/month server” tier. Cloudflare Pages is free and good enough for many; Render static sites are also free [3][7]. Hosting gravity is pulling to $0, not because OpenAI wants to be your forever host, but because free deploy paths make vibe‑coded prototypes stick. The money reappears in higher‑order services: payments, auth, analytics, compliance, and marketing—domains where Wix/Squarespace still have leverage and where infra players monetize usage instead of seats.

What others are missing

Governance at the creation layer will decide who captures value; OpenAI’s Sites help page states that conversations may be used to train models if “Improve the model for everyone” is on, and that Sites can include chat context, files, hosted URLs, logs, and operational data [2]. It also advises reviewing any feature that collects user content (forms, message boards, sign‑ins) before you publish [2]. That means a chat‑born site can become a data‑collection surface whose inputs might feed future training unless settings are managed. Enterprises and regulated SMBs will demand explicit controls, audit trails, and export paths—pressure that will either force OpenAI to harden Sites for compliance, or push serious users to Cloudflare/Render/Vercel where data boundaries are familiar [2][3][4].

What to watch next

  1. By November 30, 2026, at least one of Render, Vercel, or Cloudflare will ship an official “Import from ChatGPT Sites” workflow (CLI or dashboard), enabling one‑click export‑to‑deploy.

  2. By March 31, 2027, OpenAI will disclose a milestone of at least 1,000,000 ChatGPT Sites published (public or private) as part of a Plus/Pro retention update.

  3. By June 30, 2027, either Wix or Squarespace will launch a chat‑first builder that ingests prior user content (docs, posts, galleries) to auto‑scaffold an entire site—GA, not beta.

My take

Vibe coding for simple software wins because a $20/month Plus plan with Sites collapses scaffolding and hosting into one step, siphoning demand from $17–$30/month starter plans whose chief value was convenience [5][6]. The shift doesn’t end website builders or hosts; it ends charging rent for friction. The next wins accrue to whoever pairs chat‑native creation with distribution, commerce, and governance at named‑brand scale (Wix, Squarespace, Cloudflare, Render). If I ran Wix or Squarespace, I’d ship a ruthless “AI + go‑live” funnel now and make exporting to Cloudflare/Render painless.

Sources

  1. I tried the same ChatGPT prompt Sam Altman used to build a website and finally learned how to vibe code — Business Insider — First‑person test of Altman’s prompt; confirms Sites exists in public beta and that a non‑coder shipped a live site in under two hours.

  2. Creating and managing ChatGPT Sites — OpenAI Help Center — Documents Sites (public beta), hosting behavior, export/permissions considerations, and data‑use language relevant to governance.

  3. Cloudflare Pages — Cloudflare — Describes Pages as a free JAMstack deployment platform suitable for small apps and marketing sites.

  4. Limits for Cloudflare Pages — Cloudflare Docs — Specifies free‑tier constraints (for example, up to 20,000 files per site), anchoring the “free deploy is enough for many” claim.

  5. What is ChatGPT Plus? — OpenAI Help Center — Confirms Plus pricing at $20/month and clarifies subscription scope and data‑use settings.

  6. Wix Premium Plans — Wix — Lists current Wix plan price ranges ($17–$159/month when billed annually), used for cost comparison.

  7. Deploy static sites for free — Render Docs — States that static sites can be deployed on Render for free with managed TLS.

  8. Cloudflare Workers pricing — Cloudflare Docs — Details the free monthly allotment for Workers/Functions that pair with Pages.

  9. GeoCities — Wikipedia — Establishes a 1994–2009 precedent for bundled creation + hosting aimed at amateurs.

  10. Google App Engine — Wikipedia — Documents the 2008 launch of a managed app‑hosting platform that bundled deploy and infra.

  11. Heroku — Wikipedia — Notes the 2007 launch and the model of bundling deploy + runtime with monetization on add‑ons/scale.

  12. Render pricing — Render — Provides context for entry‑level monthly hosting habits in the single‑digit range.

Traders Flee Giants to Forge Leaner Funds | Analysis by Brian Moineau

Traders Are Ditching Giant Hedge Funds to Set Their Own Terms

Introduction

There’s a quietly disruptive migration on Wall Street: traders are leaving giant hedge funds and starting smaller shops that let them “set their own terms.” That phrase — set their own terms — captures the new calculus for many market veterans: give up multimillion-dollar pay packages and access to billions in firepower, in exchange for autonomy, simpler economics and the freedom to run strategies on their timetable.

This trend shows up everywhere from proprietary desks spinning out to senior portfolio managers taking a smaller balance sheet but a bigger slice of the upside. It feels less like a rush to become celebrities and more like a return-to-basics: control risk, keep the upside, cut the bureaucracy.

Why traders are walking away

  • Pay structure friction. Big multi-strategy firms can offer juicy headline compensation today, but they also centralize profits, allocate capital across many teams, and use internal performance hurdles. Starting their own shop lets traders control fee splits, carry and vesting — even if the dollar amount initially looks smaller.
  • Cultural and operational drag. Giant firms have layers of compliance, comms, and process. For a trader whose alpha relies on quick decisions and nimble positioning, that drag can erode returns and morale.
  • Technology and infrastructure are cheaper. Cloud providers, third-party execution/prime services, and low-latency platforms have lowered the fixed cost of operating a fund. That makes it feasible to run a boutique with professional infrastructure but far lighter governance.
  • Brand and investor appetite. Institutional allocators who once preferred big brands are more willing to back small, high-performing teams — if they can show a clean track record and robust risk controls.
  • Risk appetite and diversification. Some traders want to focus on a single niche (event-driven, macro, relative value) rather than being shoehorned into a multi-strategy firm’s allocation mix. Running a boutique lets them concentrate on what worked for them historically.

A different bargain

Leaving a giant firm is not simply a lifestyle choice; it’s a new deal structure. Traders who spin out tend to renegotiate three things:

  • Capital: Instead of hundreds of millions or billions, they may start with tens of millions raised from seed investors, family offices, or former colleagues.
  • Economics: Boutiques often offer founders a larger share of management fees and carry, and they can tailor compensation or clawback terms to attract talent.
  • Governance: Less committee oversight, fewer reporting layers, and a direct line between desk performance and compensation.

That bargain isn’t risk-free. Boutique founders shoulder fundraising, investor relations, and operational headaches. They must buy or rent prime broker relationships, set up compliance, and often put more of their personal capital at stake. But for many, that trade-off — greater upside per dollar and less internal friction — is worth it.

Context matters: why now?

This movement isn’t brand-new. Over decades, regulatory shifts (think post-crisis reforms) and the growth of multi-strategy giants nudged talent toward or away from different platforms. What’s changing now is the combination of investor sophistication and low-cost infrastructure.

  • Allocators are more discerning. Due diligence has gotten more standardized; investors can evaluate small teams quickly and scale allocations if performance persists.
  • Tech lowers barriers. Outsourced trading systems, cloud data, and institutional service providers let small teams run complex strategies without building everything in-house.
  • The market’s scale paradox. Some strategies don’t scale well to billions; they generate alpha only at modest sizes. That structural reality makes small, nimble shops more attractive for certain approaches.

Examples and early results

  • Some boutique launches have been quietly successful, growing from a seed allocation to several hundred million AUM in a few years by sticking to their playbook and preserving risk discipline.
  • Other spinoffs stumble on fundraising or operational missteps — a reminder that skill at trading doesn’t automatically translate to running a business.

Lessons for firms and allocators

  • For large firms: retaining top traders may require reassessing how capital and carry are allocated, and where bureaucracy can be trimmed without sacrificing controls.
  • For allocators: diversification via small, specialized managers can offer exposures that large funds cannot supply — but it requires operational diligence and realistic sizing.
  • For traders: the decision to leave should account not only for potential upside, but also for the commitment to raise capital, negotiate service providers, and manage investor relationships.

What success looks like

Successful boutiques share a few traits:

  • A clear, defensible strategy that doesn’t rely on scale to produce alpha.
  • Strong, transparent risk management.
  • Reasonable initial capitalization and a credible plan for growth.
  • Discipline in investor communications and realistic performance expectations.

Transitioning smoothly often means partnering with experienced ops people or third-party providers who can shoulder the back-office load while founders focus on trading.

My take

The shift toward smaller, trader-led shops is less a revolt than a rebalancing. Big firms still matter for massive, diversified mandates and infrastructure-heavy strategies. But the market is making room for focused operators who trade less to chase headline AUM and more to preserve edge.

For traders, the choice comes down to trade-offs: security and scale versus speed and upside alignment. For investors, the opportunity is to access targeted alpha if they’re willing to do the homework.

Either way, the headline — traders ditching giant hedge funds to set their own terms — captures a deeper market evolution: the democratization of fund infrastructure and a renewed focus on alignment between decision-makers and owners.

Final thoughts

Expect more of this mosaic: big funds remain, boutiques proliferate, and allocators stitch exposures together. The winners will be traders who understand not only markets, but the operational and investor-relations work that turns trading skill into a durable business. The smart ones aren’t just leaving — they’re building a different kind of platform.

Sources




Related update: We recently published an article that expands on this topic: read the latest post.


Related update: We recently published an article that expands on this topic: read the latest post.

Will Lawyers Embrace AI or Resist Change | Analysis by Brian Moineau

Two questions haunting lawyers about AI — and why the industry still moves slowly

I walked into a packed legal-conference ballroom expecting a tech pep talk. Instead I left wondering the same thing the Business Insider reporter did after 17 hours of panels: how many lawyers are actually using the tools? That core question — how many lawyers are actually using the tools? — sits at the center of billions of dollars of investment, a handful of discipline-worthy courtroom errors, and a simmering debate about the future of legal work.

The mood in the room was equal parts excitement and anxiety. Vendors promised speed and margin; partners worried about billing models; regulators and bar leaders warned about responsibility and hallucinations. Those conversations reduced to two persistent questions that every panelist, judge, and GC seemed to be circling back to.

The first question: Is the AI good enough — and safe enough — to use on client matters?

This is about accuracy, explainability, and risk. Lawyers aren’t just writing marketing copy — they’re giving advice that can cost clients millions or expose them to sanctions. So a model that hallucinates a case citation or invents a legal doctrine isn’t a novelty; it’s malpractice risk.

Recent reporting shows this tension plainly: firms have faced real sanctions when attorneys relied on generative models that produced fake cases, and vendors are racing to add hallucination checks and provenance features. That high-stakes context means many lawyers treat AI like an unclassified chemical: promising in the lab, suspect in the courtroom. (archive.ph)

But accuracy isn’t the only technical worry. Lawyers also ask whether tools reliably surface the whole legal universe they need — not just the most convenient answer — and whether outputs can be audited for conflicts, privilege, and source provenance. Firms longing for “copilot” productivity also need guardrails that turn AI from a black box into a supervised assistant. Studies testing legal copilots suggest progress but underscore important limits. (fortune.com)

The second question: Who pays when AI makes lawyers faster?

This is the business question that keeps partners awake. The legal economy is structured around the billable hour, and AI changes that math. If a task that used to take an associate 10 hours now takes 90 minutes with AI plus 30 minutes of review, how do firms price their services? Do they lower rates, keep rates and increase margin, or move toward value-based fees?

The answer matters because it determines incentives for adoption. If partners believe AI will hollow out revenue, they’ll stall investment and restrict use. If clients demand lower-priced, faster results, firms will be forced to pivot — but that pivot still faces cultural and billing inertia. The industry’s confusion shows in surveys: personal experimentation with generative tools often outpaces firm-level policies and billing strategies. (americanbar.org)

Transitioning from those two questions brings us to the real adoption dilemma: enthusiasm vs. institutional readiness.

So how many lawyers are actually using the tools?

Short answer: it depends which survey you read and which “use” you count. Personal, informal use of ChatGPT or other assistants is widespread; firm-sanctioned, regular use for client work is far less uniform.

  • Large, tech-forward firms and in-house legal teams report higher adoption rates and dedicated copilots, while many solos and small firms lag. (americanbar.org)
  • Some surveys show a modest minority using generative AI daily (roughly 20–30% in certain snapshots), while others report broader “some use” figures (30–60% depending on methodology). (news.bloomberglaw.com)

Put another way: a lot of lawyers have tried the tools, but fewer have woven them into audited, firm-wide workflows that handle privilege, provenance, and billing. That gap — between curiosity and trusted operational use — is where most of the money and friction live.

What’s holding the profession back?

Several practical and cultural brakes show up repeatedly at conferences.

  • Ethical and regulatory uncertainty. Bars and courts still debate disclosure, competence, and supervision rules for AI-assisted work. That uncertainty chills firm-wide rollouts. (americanbar.org)
  • Risk of hallucinations and errors. High-profile sanctions stories make partners risk-averse. The lesson: AI needs human checks, and those checks cost time. (archive.ph)
  • Billing and business-model friction. The billable-hour legacy makes firms ask whether to profit from AI efficiency or pass savings to clients — and that debate slows adoption. (lawyerist.com)
  • Data hygiene and integration. Many firms’ document ecosystems are messy; effective AI needs clean, well-governed data, which requires investment. (sbo.consulting)

These are solvable problems — but they require governance, training, and leadership decisions that many firms haven’t fully made.

Where investors and vendors fit in

Venture capital and vendors see a huge runway: legal AI deals and product launches have attracted billions. Investors are betting that once the ethical and billing knots are untied, adoption will accelerate and generate substantial efficiency gains across litigation, corporate work, and compliance. That’s why conferences feel equal parts product demo and sales pitch. (allaboutai.com)

But vendor enthusiasm must pair with sober legal risk management. The winning products will be those that embed verifiable sources, offer audit trails, and mesh with law firms’ billing and records systems — not just flashy drafting demos.

My take

AI in law is already real, but it’s not yet ubiquitous in the professional, accountable sense that matters for clients and courts. The two questions haunting lawyers — “Is it safe?” and “Who benefits financially?” — are practical, not philosophical. Answer those, and the rest follows.

We should expect uneven adoption for a few more years: rapid uptake among in-house teams and large firms that can invest in governance; slower movement among smaller shops where the billing model and compliance risk cut differently. The real measure of success won’t be how many firms claim to “use AI,” but how many can show audited, client-safe workflows that improve outcomes without inviting sanctions.

Final thoughts

When billions of dollars are riding on lawyers moving faster with AI, the overriding challenge isn’t the models themselves — it’s the profession’s risk calculus and business incentives. Conferences are useful because they surface those debates, but the practical work happens back at the firm: cleaning data, writing policies, training people, and rethinking pricing.

If the industry solves the two questions — safety and billing alignment — adoption will accelerate. Until then, expect a lot of pilots, a few headline failures, and steady, incremental progress.

Sources




Related update: We recently published an article that expands on this topic: read the latest post.