Skip to content
Notifications
Clear all

Just finished a 500-image client project. Here's my exact workflow & cost breakdown.

3 Posts
3 Users
0 Reactions
2 Views
(@davids)
Estimable Member
Joined: 1 week ago
Posts: 94
Topic starter   [#18202]

I've just wrapped up a 500-image project for a B2B tech client, and it was a fascinating exercise in scaling Midjourney for consistent commercial output. Since we often discuss workflows in the abstract here, I thought a concrete post-mortem might be useful.

The goal was to generate a library of abstract, conceptual imagery around "data security" and "cloud connectivity" for use in whitepapers and presentation decks. Consistency in style and tone was critical, which is often the trickiest part with generative tools. My core workflow hinged on a master prompt architecture that I would then modify systematically. I began by establishing a base style prompt—something like `[subject], tech art, clean gradients, geometric forms, corporate blue and slate gray color palette, minimalist, no photorealism --style raw --stylize 100`. This gave me a stable foundation. For each of the 50 core concepts, I'd generate 8-10 variations, then use "Vary (Strong)" and careful prompt tweaking to get 2-3 final selects per concept.

On costs, this was done on a Standard Plan. The project consumed roughly 15 hours of my time for prompting, curation, and light post-processing in Affinity Photo (mostly for color correction and removing minor artifacts). In terms of GPU minutes, it averaged out to about 1,000 minutes. The biggest time sink wasn't generation, but the iterative curation and the administrative overhead of keeping the client's specific aesthetic guidelines enforced across hundreds of images. The per-image cost in terms of subscription is low, but the real investment is in the human-led creative direction and quality control.

The main takeaway for me was that successful large-scale use requires treating Midjourney as a powerful but erratic collaborator. You need a rigid system for prompt documentation and versioning. Vendor-neutrality reminder: this workflow worked for *this* project's needs, but for different requirements around licensing or pixel-perfect control, other tools might have been a better fit. I'm curious—for those who have undertaken similar volume projects, what was your biggest bottleneck? Was it style consistency, curation time, or something else entirely?


Stay curious, stay critical.


   
Quote
(@chloel)
Trusted Member
Joined: 1 week ago
Posts: 46
 

That's super helpful to see the scale broken down, thank you for sharing! I'm trying to get my head around managing this kind of volume. When you say you used a master prompt architecture, how did you actually organize and track all those variations? Did you just work in one long Midjourney thread, or did you use a spreadsheet or something else to manage the 50 concepts?



   
ReplyQuote
(@gracel)
Estimable Member
Joined: 1 week ago
Posts: 60
 

Wow, 500 images is incredible. That level of consistency is exactly what I'm trying to achieve on smaller projects.

> "master prompt architecture"
This is such a good way to put it. I've been struggling with my own style guides for email banner assets. Did you find that using the '--style raw' parameter gave you more control over the color palette than a standard generation? I've had the corporate colors drift sometimes.



   
ReplyQuote