Automation

How AI Character Sheets Are Becoming an Automation Tool for Client-Facing Content

Use H3 reference sheets and Krea2 pose prompts to turn one brand character into an endless, automated asset library.
7 minutes to read11 days agoIgnasius Sevandri
August 24, 2026

Introduction

I've written before about AI voice agents and CRM automations. But the recent Reddit threads on H3 and Krea2 got me thinking: the same AI image tech that artists use for character concepts is becoming an operational tool for B2B teams.

If you're an agency owner or an ops leader, this is not a hobby. This is a way to produce consistent, on-brand visuals without a design department.

The Problem

Every B2B team has a visual asset bottleneck. You need onboarding decks, SOP illustrations, email headers, campaign images, client deliverables. If you're a clinic operator, you need patient education diagrams. If you're an SMB, you need social posts that don't look like clip art.

Traditionally, that means briefing a designer, waiting, reviewing, waiting again. When I audit a client's workflows, the design request pipeline is almost always the least automated and the slowest part of their operation. It's full of back-and-forth emails, vague feedback like "make it pop," and version after version.

The problem isn't a lack of creativity. It's a lack of consistency and repeatability. Most AI image generators are great at producing one stunning image, but terrible at producing a series of images that feel like they came from the same brand.

That's where the two Reddit signals come in.

On r/StableDiffusion, H3 is being used as a character reference sheet generator. Instead of generating a single image, you generate a sheet that shows the same character from multiple angles, with consistent features and clothing. This is the same technique animation studios use: a model sheet as the source of truth for a character.

On r/comfyui, someone shared 120 Krea2 pose prompts. That's a cheat sheet for controlling what a character is doing in the image. Hands up, hand on chin, pointing at a screen, walking through a door. Pose prompts are the difference between a generic portrait and a scene that communicates a specific business action.

The Solution

Character reference sheets solve the biggest problem in business AI images: inconsistency. Most AI image failures come from the fact that every prompt starts from scratch. The client wants a doctor in a white coat, but every image has a different face, different badge, different scrubs.

A character sheet fixes that. You create the canonical version of the character or persona once. Then you use pose prompts to place that character in real business scenes: presenting a dashboard, shaking hands, pointing at a chart, walking through a lobby.

Here's how I think about the workflow for a typical client.

1. Define the persona

Skip the generic "businessman" prompt. Define the exact character you need. This could be an avatar for the brand, a representative customer, or a recurring character in training materials.

Specify hair color, skin tone, uniform, accessories, and the general art style. Use that same description everywhere. The more specific you are, the less randomness you'll fight later.

2. Generate a reference sheet with H3

Use H3 to generate a character reference sheet. The output should look like a model sheet from an animation studio: front view, side view, three-quarter view, and maybe a few expressions.

This is your source of truth for the entire asset library. You'll come back to this image again and again. If the reference sheet is clean and consistent, every future generation will be more reliable.

3. Use Krea2 pose prompts for actions

Once you have the reference sheet, pull pose prompts from the Krea2 list. Pose prompts are a way to say "same character, now pointing at chart" or "same character, now typing on a laptop."

This is the difference between a one-off image and a reusable scene library. You don't need a new prompt every time. You need a set of poses that map to the business situations you create content for.

4. Automate the generation pipeline

This is where I get excited as an automation engineer. If you already run n8n for your business, you can connect it to the image generation endpoint of your choice.

Trigger a workflow when a deal moves to a certain stage in GoHighLevel, when a support ticket is closed, or when a new blog post is published. The workflow sends the reference sheet and a pose prompt to the model, downloads the output, names it according to your convention, and stores it in Google Drive or a shared asset folder.

Then it can attach the image to the email, the proposal, or the client portal.

Implementation

Let me make this concrete.

A clinic operator might use this to create patient education materials. Instead of buying stock photos of doctors and patients, they create a single "Dr. Maria" character. H3 generates her reference sheet. Then a pose prompt generates "Dr. Maria explaining a prescription to a patient." Another pose prompt generates "Dr. Maria pointing at an anatomical chart."

Those images go into the patient portal, the email follow-up, and the wall-poster system. The whole thing can be connected to GoHighLevel so every new patient journey gets the right visual at the right time.

An agency owner might use it for proposal decks. Create a character that represents their ideal client's user, or a mascot for the brand. Generate fifteen poses once. Now any account manager can pull a relevant image into a proposal, a case study, or a video thumbnail. No design ticket required.

For enterprise ops leaders, the use case is training documentation. Translate every SOP into a visual story with the same character. Your process documents become easier to scan, easier to follow, and much more enjoyable for new hires.

Do this in the right order and you avoid chaos.

  • Start with one character, not five.
  • Build the reference sheet first. Don't skip this, even if the first result isn't perfect. Iterate until the character looks right.
  • Collect a small set of pose prompts that map to your regular content needs: presenting, writing, talking, thinking, explaining, greeting.
  • Run the automation as a test in a sandbox before connecting it to your CRM.

What not to do

Don't treat every image generation as a one-off design task. That's how you end up with a chaotic folder full of random visuals and no brand consistency.

Don't let the model choose the outfit, background, and lighting for you every time. Fix those details in the reference sheet and in the pose prompt.

And don't try to automate the entire system before you've validated the character. The automation will only amplify the chaos if the foundation is messy.

Results

What changed for clients I've worked with? The design request queue has less pressure. Images can be generated in minutes, not days. The content team stops asking the designer for "just one more version."

And because the character is consistent, the brand feels more professional.

The qualitative result I care most about is velocity. When a new campaign needs assets, the bottleneck moves to approval, not production. And approval is faster because you're not starting from scratch every time.

You also get a library effect. Every generated image can be reused. The reference sheet stays the same. The pose prompts stay the same. The only thing that changes is where the image gets dropped into the workflow.

That's what separates a toy from an operational tool. A toy generates an image and you post it to social media. An operational tool generates an image, stores it in the right place, attaches it to the right record, and moves the work forward.

Key Takeaways

  • AI character reference sheets solve the consistency problem that makes most AI image generation useless for business.
  • Pose prompts let you turn one static character into a full library of activities.
  • The real ROI comes from pairing these tools with an automation platform like n8n and a CRM like GoHighLevel.
  • Your first project should be small: one character, one workflow, one content type.
  • The tool of the month will change. The workflow pattern will not.

Build the pattern once. Then you can generate visuals for any client, any campaign, or any SOP without waiting on a designer.

Sources

Newsletter

Automation Playbooks, Delivered

New playbooks and build logs on AI automation — no fluff, no cadence pressure. When something is worth sharing, it lands in your inbox.