Turning on Shopify’s password page takes about four clicks. Undoing what it does to your search traffic takes months.

The mechanism is worth being precise about. Every product page Google has indexed starts returning the same login screen: same title, same content, no product, no price, no structured data. So from the crawler’s side of the glass, a catalog of four hundred pages that each said something different has become one page repeated four hundred times, and Google responds to that the way it always does. It comes back less often. Then it stops.

The store hasn’t become private. It’s become invisible.

Those are very different things, and almost every tool that promises the first one quietly delivers the second. If you’re going trade-only, members-only, or invitation-only, the gap between them is the whole problem you’re solving.

The three usual ways this goes wrong

Search for how to hide prices on Shopify, and you’ll be handed one of three answers. Each of them breaks something.

The password page. The blunt instrument. One password for the whole store, nobody in without it, nothing indexable behind it. It’s a shutter rather than a lock, and it’s the right tool for exactly one job: a store that isn’t open yet. For a store that’s open to some people, it’s the wrong tool. We wrote up where that line falls, including the cases where it’s still the right call.

A theme edit. You go into your Liquid and wrap the price and the buy button in a check for customer. It's free, it takes ten minutes, and for a store where every buyer has an account, it genuinely works. The Liquid for it is in our guide. The catch is that the price still ships in the HTML if you aren't careful, the edit doesn't survive a theme swap, and there's no answer to "how does a new retailer get in?" beyond "email us and we'll set up an account for you."

Login-required apps. Better, but they inherit the assumption. Access equals account. So every visitor you want to sell to has to make a password before they can see a number, and a stylist who found you on Instagram at eleven at night will not.

None of these fail for technical reasons. They fail because all three treat seeing and buying as the same permission.

Split the permission in two

Let people see everything. The photography, the descriptions, the collections, the search results, the schema markup Google reads. All of it public, all of it crawlable, still doing the job it did before.

Gate only the transaction. The price, if you want it hidden. The buy button, always.

Now a crawler is a visitor like any other. It sees a complete product page, indexes it, ranks it, and sends you people. Those people land, want the thing, and find a door where the checkout used to be. That’s the moment you want them in, because someone standing at a door they can’t open will tell you who they are to get through it.

Which is the whole idea. Someone who can’t buy yet is still a lead. The password page throws that person away before they ever arrive.

There’s a longer version of this argument, with the indexing detail, in a members-only store Google can still find.

What a gate has to get right

Here is where implementations diverge, and where you should be skeptical of anything that sounds easy. Four things separate a gate that holds from a gate that’s decorative.

It has to be enforced on the server. If the price ships in the page and JavaScript hides it afterward, you’ve obscured it rather than hidden it. Right-click, View Source, there it is. Anyone who has ever compared a competitor’s trade pricing knows to look. The check has to run before the page is built.

Nothing can flash. The related failure: the real price renders, then a script wipes it a beat later. Merchants find this the first time they demo their own store on a slow connection. It’s worse than having no lock at all, because now you’ve shown the number and advertised that you were trying to hide it.

It has to fail open. Ask this of any app you’re evaluating, and don’t accept a vague answer. When your service goes down, what does my store do? The only acceptable answer is “keeps selling.” A gate that fails closed turns somebody else’s bad afternoon into your blank storefront. Nobody asks the question until the second time it happens.

Access has to survive. A customer who unlocks on their phone and comes back on a laptop should still be in. For signed-in customers, that part is easy: tag them, the access follows the account, and it works with Shopify segments and discounts while it’s there. Guests are harder, and more interesting, because you need something the storefront can hold on to and replay on every check without a cookie, without an account, and without carrying anything in it that says who the person is.

A gate that gets all four right is boring to run, which is the point. Miss one and you’ll hear about it from a customer first.

The part most people skip

Everything so far is about keeping people out. The more valuable half is what happens to the ones you kept out.

A visitor who wants to buy and can’t is at peak intent. They’ve seen the piece, they want it, and there’s a door. If all that sits behind the door is a code field they don’t have, you’ve lost them and learned nothing.

So give them a second path. Let them build a list of what they wanted, a stand-in for the cart they couldn’t fill, and hand it over with their details. What you get out of that is a named lead with a stated basket, which is considerably more than an abandoned cart would have told you, and you can do the obvious thing with it. Turn it into a draft order, put your own pricing on it, send the invoice.

For wholesale, this is a better sales motion than checkout ever was, because trade pricing was never going to be one public number anyway. We went through the setup in full in wholesale pricing without a second store. If you’re weighing up Shopify’s native B2B first, the cases it doesn’t cover are worth reading before you commit either way.

If you’re paying creators, measure it

The same machinery answers a question that’s normally guesswork.

Give each creator their own code. Every redemption is attributed to whoever’s code opened the door. At the end of a campaign, you’re not running a debrief on which post felt like it worked. You have a count of unlocks, people, and requests per creator, and how to set that up is here.

The thing to watch is honesty about what you can actually see. An app that gates a store knows a draft order was created. It usually cannot know that draft order was paid. Show a creator the word “orders” and they’ll hear “sales I’m owed commission on”, and you’ll be having an awkward conversation two months later. Say “draft orders” and mean it.

Do you actually need an app for this?

Sometimes not, and I’d rather say so here than have you work it out after installing something.

If every buyer has a customer account, if you’re content hiding the price from everyone who isn’t logged in, and if you don’t mind editing your theme, a Liquid conditional will do the job. It’s free and it holds. Our own guide on hiding prices opens with that instruction and tells you to stop reading if it fits.

You need more when the answer to “how does a new person get in?” is more complicated than “they already have an account.” Codes handed to an audience. Requests you approve one at a time. A launch that opens on a date. Several groups seeing several different things. Attribution across people you’re paying.

That’s roughly the line. Below it, edit your theme. Above it, the bookkeeping is the product, and the bookkeeping is what you’d be paying for.

What we built

I’ve spent nine sections describing the shape of a solution, so I should be straight about the fact that we built one.

Inner Circle is a Shopify app that does what’s above. The storefront stays browsable and indexable, and buying sits behind either an access code or a request you approve. Prices are hidden before the page paints, the check runs on the server, and it fails open, so an outage on our side doesn’t blank your store.

Per lock, you choose what a gated visitor sees: price shown, hidden, or replaced with your own wording; buy button gated or not; access code button, request button, or both. Codes can be shared with a whole audience, single-use so they burn on redemption, or capped by date and count. Every redemption is attributed, so you can tell which creator actually drove unlocks. The whole flow, screen by screen.

There’s a free plan with no card and no time limit, which exists so you can watch the gate work on your own theme before deciding anything. Plans and prices, or install it from the Shopify App Store.

Further reading

All free, none of it gated, and one or two will talk you out of installing anything:

• How to hide prices on Shopify, starting with the theme edit that costs nothing
• A members-only store Google can still find
• The Shopify password page, and when it’s the wrong tool
• Wholesale pricing without a second store
• Shopify B2B, and the case it does not cover
• Shopify access control apps, compared, us included, and not always winning
• Running a drop on Shopify
• Running a private sample sale
• Influencer campaigns, and knowing which one worked

If you’re running a private catalog, a members-only range or a launch: those four failure modes are the ones we built against. I’d like to know which one we’ve missed, and that isn’t a rhetorical question. The comments are open.

Your Shopify store can be private and still rank on Google was originally published in monochrome.digital on Medium, where people are continuing the conversation by highlighting and responding to this story.

Last week, a potential client slid into my inbox with what I can only describe as a haiku of vagueness:
“Need website redesign. Competitors are killing us. Make it convert better.”

I blinked twice, checked if I’d accidentally enabled some experimental telepathy feature, then realized: I wasn’t being treated like a designer. I was being treated like their favorite AI tool.

The Great Client-Designer Miscommunication of 2025

Remember when client briefs contained actual information? These days, I’m expected to extract an entire brand strategy from what essentially amounts to a fortune cookie message.

It’s as if they’ve gotten so used to prompting AI systems that they’ve forgotten humans don’t have access to the entire internet’s worth of knowledge about their specific business problems.

We’ve gone from collaborators to prompt-fulfillment machines expected to operate on vibes and telepathy.

Why We’ve Entered The Brevity Apocalypse

The culprit is clear: AI tools have conditioned us humans to believe that creativity works like a vending machine. Insert minimal coins of information, receive maximum creative output.

The more I think about it, the more I realize we’re experiencing three simultaneous phenomena:

1. The Great Context Drought: Why provide details when an AI can hallucinate them for you? Similarly, why tell your designer what your business actually does when they can… um… hallucinate it too?
2. Prompt Efficiency Syndrome: If ChatGPT can generate a 1,000-word article from “write blog content marketing,” surely a human with decades of experience needs even less direction, right? RIGHT?
3. Patience Extinction: When you’re used to getting creative work in seconds, waiting for a human to do thoughtful work feels like watching paint dry. Except the paint is artisanal and actually worth waiting for, but who has time for that?

Tales From The Front Lines Of Minimal Communication

Just yesterday, I received this comprehensive brief from a tech startup:

“Landing page. Conversion focus. Blue?”

That’s it. That’s the brief. Not even a question mark after “blue” — just a vague suggestion that perhaps the color blue might be involved somewhere.

When I asked for clarification about their product, target audience, and unique selling proposition, they responded with what I can only describe as annoyed surprise: “We’re in tech. Just make it look like we know what we’re doing.”

Ah, yes, the classic “tech company that knows what it’s doing” aesthetic. I’ll just press my “generic tech credibility” button and be done by lunch.

Breaking The Cycle Without Breaking Your Client Relationships

Rather than simply lamenting this new reality, I’ve developed some strategies that seem to be working:

1. The Reverse Uno Card Approach

When clients send me AI-style prompts, I respond with AI-style clarifying questions:

“I’d be happy to design your website! To ensure optimal results, please specify:

• Primary business goal (acquisition/retention/awareness)
• Target audience demographics
• Top three competitor websites
• Your definition of ‘better conversion’”

Framing it this way often works because it mimics the interaction style they’re comfortable with.

2. The Show, Don’t Tell Method

I now keep a folder of “prompt-based designs” versus “proper-brief designs” to visually demonstrate the difference. Nothing communicates the value of good communication like seeing the stark visual evidence.

“Here’s what we can create with your current brief, and here’s what we could create with more information.”

Suddenly, they’re typing paragraphs of context.

3. The “AI Surcharge”

My contracts now include a “contextual deficit fee” that kicks in when clients refuse to provide adequate information. Each round of revisions that could have been avoided with proper upfront information incurs this fee.

It’s amazing how quickly clients develop the ability to articulate their needs when there’s a financial incentive.

The Human Advantage: We Can Actually Ask “Why?”

The irony in all this is that human designers’ greatest advantage is precisely what these prompt-style briefs eliminate: our ability to question assumptions and dig deeper.

While AI will dutifully create a “premium-feeling website,” humans can ask: “What does premium mean to your specific audience? Are you sure that’s what they actually value? Have you considered that maybe ‘premium’ is overplayed in your industry and ‘authentic’ might differentiate you better?”

That’s the stuff no prompt can capture.

Finding A New Equilibrium

I’ve started addressing this shift directly in my onboarding materials:

“Working with a human designer is different from working with AI tools. I don’t hallucinate missing information — I ask for it. I don’t make statistically likely design choices — I make strategically appropriate ones. My superpower isn’t mind-reading; it’s mind-expanding.”

This usually resonates enough to get the conversation flowing in a more productive direction.

The Light At The End Of The Prompt Tunnel

Despite my complaints, I’m seeing early signs of prompt fatigue. Clients who went all-in on AI-generated creative work are starting to notice that their marketing materials look suspiciously similar to their competitors’. Turns out, when everyone prompts with “modern, clean, professional,” everyone gets the same output. Who knew?

Some clients are circling back with a newfound appreciation for human creativity and strategic thinking. One recently told me, “I spent six months trying to prompt my way to a unique brand identity. Can we start over with a real conversation?”

Music to my ears.

In the meantime, I’ll be here, patiently explaining that “make it pop” is neither a design direction nor a spell I can cast on your PowerPoint presentation.

Though sometimes I’m tempted to respond to these minimalist briefs with equally minimalist work:

Client: “Website. Modern. Fast.” Me: delivers a white page with black text that says “WEBSITE” and loads in 0.003 seconds

“As requested: Modern. Fast. Website.”

Hey, a designer can dream.

Have you been treated like a human prompt machine? Share your best “client thinks I’m Claude” moments in the comments!

When Clients Treat You Like Their Favorite AI Tool was originally published in monochrome.digital on Medium, where people are continuing the conversation by highlighting and responding to this story.

A slightly bitter love letter to the profession we thought we signed up for

It was my first day on the job. With a fresh diploma, Adobe shortcuts memorized, and enough design thinking methodology to solve world hunger, I was ready to change the world one pixel at a time.

“Here’s your first project,” my manager said, sliding over a brief. “The client needs it by Friday.”

I nodded confidently. Four days to craft a beautiful solution? No problem.

“Oh, and you’ll need to present it to the leadership team. They’re not really ‘design people’ but they have… opinions.”

And just like that, my design career began not with a creative bang but with the quiet realization that I’d need to become fluent in executive speak overnight.

The Education We Got vs. The Job We Face

What They Taught Us:

• “Iterate through the design thinking process”
• “User research is the foundation of good design”
• “Solve real problems with empathy and intention”
• “Balance aesthetics with usability and accessibility”

In design school, they trained us for a world of research sprints, user interviews, and endless presentations. We spent hours crafting personas, building wireframes, and defending our solutions with data. We’d emerge as problem-solvers, armed with prototyping tools and strong opinions about user flows and accessibility guidelines.

Nobody mentioned I’d spend 60% of my time in meetings about meetings.

What We Actually Do:

• Translate business jargon into workable solutions
• Explain for the 47th time why we can’t just “make the logo bigger”
• Facilitate workshops where nobody understands what we do
• Write documentation nobody will read
• Defend our decisions using data we had to gather ourselves

Last time, I spent three hours in a “quick sync” explaining why we can’t fit seven call-to-action buttons “above the fold” on mobile. Also, I created a 20-slide presentation justifying why we need user testing. The day before that, I was asked if I could “just quickly” redesign the entire app by Friday — while also handling the social media graphics because “it’s all design, right?”

A Designer’s Life: The Unwritten Timeline

Design School: I create meaningful experiences that solve human problems!

Year 1: Why is the client asking me to make the logo bigger? Didn’t they already approve this?

Year 3: Create a 15-page document explaining the ROI of a design system while simultaneously facilitating a “team alignment” workshop

Year 5: Open email: “Just wondering if you could hop on a quick call to discuss the 37 pieces of conflicting feedback on the homepage design”

Year 7: My job title says “Designer,” but my calendar says “Professional Meeting Attendee.”

Year 10: Stares blankly at Figma, trying to remember when I last designed something

Year 11: Client calls “Have you tried using AI for that? My nephew made something cool with Midjourney last weekend.”

The Undocumented Job Requirements

No one warned me about my first design review with the CEO. There I was, proudly presenting weeks of research and careful design decisions, when he looked at my meticulously crafted UI and said: “I don’t like blue. My competitor uses blue. Make it orange.”

That was the day I realized my actual job description included:

• Stakeholder Therapy: “I hear that you don’t like blue. Let’s explore what feelings blue brings up for you.”
• Diplomatic Immunity: Surviving cross-departmental warfare while pretending everyone’s feedback is equally valuable. “That’s an interesting suggestion to add flashing text. Let me see how we might incorporate the spirit of that idea.”
• Creative Translation: Deciphering feedback like “make it pop,” “add some wow factor,” and my personal favorite, “it needs to be more intuitive” (which usually means “I don’t want to learn anything new”).
• Budget Wizardry: “No, we can’t afford user testing, but yes, we expect you to know exactly what users want.”
• Time Bending: Delivering two-week projects in two days because someone promised the client impossible timelines.

I once watched a junior designer burst into tears after a stakeholder said, “I’ll know what I want when I see it” for the fifth time in one meeting. We don’t talk about that day.

The AI Plot Twist: From Designer to Prompt Engineer

Just when I thought I’d mastered the art of juggling impossible expectations, AI entered the chat.

“This will make your job so much easier!” they said, dropping yet another tool into my already overflowing toolbox.

Now, instead of just designing, I’m:

• Teaching AI to understand that “professional and modern” doesn’t mean “blue gradient with a swoosh”
• Explaining to clients why AI-generated logos all look suspiciously similar
• Justifying my job’s existence: “No, the robot can’t replace me because someone needs to tell the robot what to make”
• Learning prompt engineering, which is basically “design by typing very specific instructions and praying”

Last week, a client asked me why they needed me at all when they could “just use ChatGPT to design everything.” I smiled and asked if they’d like me to write the prompts or if they’d prefer their website to look exactly like everyone else’s.

The Ironic Punchline

The supreme irony? After all this evolution — from designer to project manager to business analyst to AI wrangler — we’re still judged by how pretty the final product looks.

I once spent three weeks conducting user research, building complex user flows, and crafting a solution backed by data and best practices. The client’s feedback? “The green doesn’t pop enough.”

Embracing Our Identity Crisis

So what exactly are we now? Designers? Digital therapists? Meeting enthusiasts? Professional explainers-of-why-seven-calls-to-action-is-six-too-many?

Yes. All of the above.

Perhaps there’s beauty in our evolution. We’ve graduated from pixel-pushers to business-critical problem solvers who occasionally get to make beautiful things (when the timeline allows). We’re in more strategic conversations. We help shape products from the beginning rather than just making them pretty at the end.

Sure, I didn’t expect to become fluent in spreadsheets or spend my days crafting persuasive emails about the importance of white space. But somehow, against all odds, we’re making a difference — even if half our job is explaining what our job actually is.

The next time someone at a party asks what I do, I might just say: “I translate business problems into visual solutions while managing unrealistic expectations and defending the user’s needs against an army of stakeholders who think they’re designers because they use Instagram.”

Or maybe just say, “I’m a designer,” and watch as they completely misunderstand my job.

P.S. If you’re reading this during yet another meeting that could have been an email, try the “thoughtful nodding while taking fake notes” technique. Works every time.

P.P.S. If a stakeholder asks if an AI could have written this blog post, smile knowingly and say, “It could try, but who would write the prompt that explains what ‘make it pop’ actually means? Oh right, still me.”