Key takeaway: AI accelerates some studio work dramatically (content, code scaffolding, research) and moves the needle zero on others (strategy, client alignment, QA) — honest economics means knowing which is which before quoting.
Every studio in our inbox says the same sentence now: "we use AI to go faster." Most of them have no idea where it actually saved time and where it didn't. We've shipped fifteen-plus projects since the tooling matured, and the honest breakdown is less flattering than the LinkedIn posts suggest. AI accelerates some parts of studio work dramatically. It moves the needle zero on others. Pretending otherwise is how clients get burned.
Here's the real shape of the numbers, from our own projects.
Where AI actually changed the math
Four categories. These are defensible ranges from direct studio experience — not benchmarks, not marketing figures, just what we measure against our own prior baselines.
Scaffolding — around 60% faster. Setting up a Next.js project, wiring auth, seeding a component library, boilerplating API routes, generating migration files, writing initial test scaffolds. The work that used to eat the first three days of a new build now finishes in an afternoon. This is the single largest real gain. It's also the least impressive one, because scaffolding was always the least creative part.
Research and competitive analysis — around 70% faster. Scraping competitors, pulling out patterns, building a snapshot of the market, drafting a first-pass positioning matrix. What used to be a week of a strategist reading tabs is now a day of running a pipeline and editing the output. The catch, and it's a big one: the output is only honest if you grounded it. We covered that in the Apify plus Claude article. A "research" agent that hallucinates costs you a week of client trust, not a week of time.
Copywriting first drafts — around 80% faster. Headlines, section intros, microcopy for empty states, meta descriptions, ad copy variants. The first draft was always the slowest part of copywriting. Now the first draft arrives before lunch. The second, third, and fourth drafts still take the same amount of time they always did — because that's where the actual voice work happens.
Strategy documents — 30 to 40% faster. This is the most honest number in the list, and the most nuanced. AI speeds up the framing, the boilerplate, and the "what do we normally include in this section" muscle memory. It does not speed up the thinking. A product strategy document is 30% structure and 70% judgement. AI halves the structure time. It does nothing to the judgement time.
Where AI saved zero
This is the list nobody puts on their homepage.
Client calls. A two-hour discovery call is still a two-hour discovery call. You can't AI your way out of listening. Transcripts help, but the transcript wasn't the bottleneck — the attention was.
Final QA. The last 10% of a build — the edge cases, the accessibility passes, the weird tablet breakpoint that one stakeholder cares about — is still done by a senior engineer clicking through the product. AI can generate test scaffolds (see scaffolding, above). It cannot decide which failure modes actually matter for your users. That's a human call every time.
Edge-case handling. Any system with non-trivial business logic has edge cases the LLM has not seen. Construction dispatch logic for Tough Commerce. Solar yield modelling for Enurgen. When the domain gets specific, the model's usefulness drops off a cliff, and senior engineers are back to writing code the old way — carefully, with domain stakeholders in the room.
Subtle UX decisions. The choice between a modal and an inline editor. The decision to break a form across two steps or keep it on one page. The call on whether a destructive action deserves a confirmation or an undo. These are judgement calls grounded in knowing the user. AI will cheerfully suggest all three options. It won't tell you which one is right for your product.
Any conversation where judgement matters more than pattern-matching. This is the whole category. Pricing. Scope negotiation. Team dynamics. Telling a client "no, don't build that." AI is fluent at pattern-matching. Studio work is still mostly judgement.
A worked example: our own AI Business Analyst
We shipped AI Business Analyst in about three weeks. Two years ago we'd have quoted a similar project — a grounded pipeline, a five-agent architecture, a typed report, a full interactive frontend in a custom design system, deployed on Render with webhook integrations — at six to eight weeks.
Where did the time come out? The scaffolding of the server, the routing, the JSON-call utility, the agent prompts — all accelerated. The first draft of the report-to-markdown serialiser arrived in an hour. The initial agent prompts were generated, then heavily rewritten. The Render blueprint was near-instant to produce.
Where did time not come out? Deciding what not to ship. Deciding that SOV rank, per-competitor DA, the 2D positioning matrix, keyword rank claims — all had to be dropped because we couldn't ground them. That conversation took days. It was the most valuable part of the project. No AI in the world replaces it.
Net effect: three weeks instead of six to eight. The project was faster. The hard thinking took the same amount of time it always would have.
Getting AI-timeline quotes that feel too good to be true?
Most of them are. Send us your scope — we'll tell you what actually ships in two weeks versus what doesn't.
What this means for pricing
Three things, and only one of them is flattering.
One — we quote timelines we used to laugh at. "Full SaaS MVP in fourteen days" is a real offer now, not a marketing stunt. Discovery plus strategy plus a shippable first version, driven by AI-accelerated scaffolding and a senior team that knows what to keep. Clients get product in hand while their old vendor is still writing the SOW.
Two — we bill for outcomes, not hours. This isn't new, but AI has made hour-based billing actively misleading. If the scaffolding took four hours instead of forty, should the client pay for four? No. The client is paying for the fact that we knew which scaffolding to generate, which pieces to keep, which to throw away, and how to get from "generated" to "production-stable." That's the service. Hours don't price it.
Three — we are not cheaper per project. This is the part that surprises people. AI speed gains get absorbed into scope expansion, not price cuts. A budget that used to buy a marketing site now buys a marketing site plus a thoughtful first-draft content strategy plus an A/B test plan plus the groundwork for an organic channel. Oscar Chat was a full-cycle engagement — UX audit through design, branding, marketing, SEO and GEO — because AI acceleration let us add the SEO and GEO layer without blowing the timeline. The client paid for a full-cycle project, because that's what they got. Just more of it, faster.
The part the homepage doesn't say
AI is making studios better at the parts of studio work that were always closest to commodity. It is making no difference on the parts that were always closest to craft. The delta between an average studio and a senior one is not getting smaller with these tools. If anything, it's getting larger — because senior teams know where AI lies, where it saves time, and where it can't help. Juniors using AI ship plausible work fast. Seniors using AI ship correct work fast. Clients eventually notice the difference.
Takeaway
AI didn't turn studios into magic factories. It made the boring 40% of the work trivial and left the hard 60% exactly where it was. Buy from a team that knows which is which.
If you want a senior team that can ship in weeks where others quote months, book a call.
Ship in weeks where others quote months.
Senior team. AI-accelerated where it helps, human-paced where it matters.
