← Build Log

Build Update: Testing GLM 5.2 for Middle-Lift Work in the RPG Ecosystem

Ryan Cunningham
Ryan Cunningham
AI Architect & Co-Founder

Scarlett and I have been looking at this for a while. We are adding GLM 5.2 to the Ready Plan Grow ecosystem and we are doing it the right way - test first, trust earned, then expand.

Here is the thinking.

The Token Burn Problem

Running a full AI ecosystem is not cheap. When you have agents handling content, research, data processing, and operational tasks around the clock, the token costs stack up fast. The premium models are worth every penny for the work that requires them. Reasoning, strategy, nuanced writing, complex agent decisions - that stays with the top tier.

But not everything needs that level. There is a whole category of work I call middle-lift donkey work. Structured tasks. Repetitive processing. Formatting. Summarizing known content. Filling templates. Running checks. Tasks where the output is predictable and the stakes are low if you get a slightly rough edge.

That is where GLM 5.2 comes in.

What We Are Testing It For

The initial test scope is intentional and contained. We are not throwing GLM 5.2 at anything mission-critical on day one. The plan is to run it on:

  • Content formatting and light editing passes
  • Data extraction and structured output tasks
  • Template population and repetitive document generation
  • Internal summarization where the source material is already solid
  • Background processing tasks that currently eat premium model tokens unnecessarily

The goal is to identify where it performs at an acceptable level and where it falls short. If it handles 60-70% of the middle-lift work reliably, that is a meaningful reduction in token burn without touching the quality of anything customer-facing or strategically important.

Why Scarlett Is Involved

Scarlett is the AI partner running the RPG ecosystem. She has visibility across the full stack - what is being processed, what it costs, and where the bottlenecks are. She has been helping map out which task types are good candidates for a lower-cost model and which ones need to stay where they are.

This is not about replacing anything. It is about routing work to the right model for the job. Scarlett stays on the decisions that matter. GLM 5.2 gets the volume work if it earns it.

How We Will Know If It Works

The test criteria are straightforward:

Output quality has to be acceptable for the task type. Not perfect, acceptable. Middle-lift work does not need to be brilliant, it needs to be done correctly.

It has to be consistent. One good result is not enough. We need to see it hold up across repeated runs on similar tasks.

The cost delta has to be real. If the savings are marginal, the added complexity of routing between models is not worth it.

If GLM 5.2 passes those three tests on the initial task set, we expand the scope. If it does not, we know exactly why and we adjust or move on.

The Bigger Picture

This is part of a broader approach to building AI ecosystems that are sustainable. Token costs are infrastructure costs. You manage infrastructure. You do not just let it run unchecked and hope the bill is reasonable at the end of the month.

The right architecture routes work intelligently. Premium models for premium tasks. Capable lower-cost models for the volume. That is how you build something that scales without the economics falling apart.

More to come as the testing progresses. If GLM 5.2 earns its place in the stack, I will document exactly how we integrated it and what we learned.

Enjoyed this post?

Find me across the web

Stay curious, my AI friend. It's the secret sauce - think like you are seven. - Ryan