You do not need the right words. "Make it pop" is a perfectly fine place to start, and "I will know it when I see it" is allowed too.

You do not have to speak design to get great design. You do not need to know what kerning is, you do not need the name of the font you like, and you do not need to write a polished paragraph that explains exactly what is in your head. Tell us in your own language, the way you would describe it to a friend. The translation from that language into design is the part we handle.

Most People Freeze Before the Ask, Not for Lack of Something to Say

There is a familiar moment that happens to a lot of founders and business owners right before they send a request to a designer. They open a blank screen, start typing, and then stop. Because suddenly it feels like they are supposed to sound professional. Like they should show up with references, a color palette, and a tidy explanation of why this and not that.

And that freezes people. You know exactly how you want a customer to feel, but you do not know what that is called in design terms. So you either write a long scroll out of fear of being misunderstood, or you apologize up front that "I am not really a design person," or you simply push it off to next week. The request that should have taken a minute turns into a stressful chore.

The mistake here is the assumption that the burden of translating your wish into professional language falls on you. It does not. That is precisely the work you are paying for. When you go to a doctor you do not arrive with a diagnosis, you arrive with "it hurts here." Translating the complaint into a diagnosis is their job, not yours. With design it is exactly the same.

Here Is How It Works With Us: You Say It Plainly, We Ask the Right Questions

Let us start with the part that takes the pressure off. Your request can be a single sentence. "The banner looks boring, give it more energy." "I want this to feel more expensive." "Our competitors look serious and we look amateur, fix that." Every one of those sentences is a great starting point. It tells us the most important thing: what feels off to you, and where you want to get to.

What happens after you send it is the part that makes the difference. Instead of dumping a form with twenty required fields on you, our system asks you a few short, smart questions, exactly the ones we need to turn your gut feeling into something a designer can nail. We will not interrogate you and we will not ask you to become an expert. We ask the two or three things that genuinely change the outcome: who this speaks to, where it is going to live, and what feeling you are chasing.

Those questions are the quiet secret. They pull out information you did not know you had. You know you want it to "pop," and after one good question it turns out that what you actually mean is "make it look self-assured, not loud." That is a huge difference for the designer, and it is a difference you felt from the start but did not know how to put into words. We just helped it come out.

And then you approve. You see exactly where this is heading before any work begins, in your own language, and you say "yes, exactly like that" or "almost, just make it less formal." That is it. That is all that is asked of you in the entire process.

Notice what does not happen here. You do not have to sit for an hour in front of a blank page trying to think of everything in advance. You do not have to worry that you forgot a critical detail, because if a detail matters that much, a question will surface and draw it out of you along the way. You do not have to know what a "good" request looks like, because there is no such thing as a bad one. There is a request, and there is us turning it into something we can work with. The burden of thinking of everything comes off your shoulders, and that is maybe the biggest change you will feel compared to how you have worked until now.

And there is one more thing worth noticing: the questions are not there to stress you, they are there to protect you. Every question we ask before we begin is a question you will not have to answer later, after we have already invested effort in the wrong direction. It is better to ask "who is this for" at the start than to discover at the end that we designed for one audience while you meant another. The questions are not bureaucracy. They are your insurance.

Why This Is Not Just Pleasant, but Also Gets You a Better Result Faster

There is a benefit here that is easy to miss. When the right questions get asked before the designer begins, the first round comes back nearly spot on. Not because we guessed well, but because we asked well.

Think about how it usually goes without us. You send a general request, get back something that is a polite guess, discover it is not what you meant, try to explain what is wrong, get a second version that is still not there, and so on. Every one of those rounds costs you days and costs you energy. Most of the time wasted in a design project does not go to the design itself. It goes to misunderstandings that one good question at the start could have prevented.

That is exactly what we zero out. We take the mess of "let us guess and then fix it" and replace it with a few minutes of smart questions up front. The result is that you get work that feels like we read your mind, when the truth is much simpler: we just asked the right things before we started, instead of after.

Fun fact: our experience says the shortest requests lead to the best designs. Not because they contain less information, but because they describe a feeling instead of trying to write instructions. A feeling we know how to translate. Half-professional instructions actually muddy the water, because they try to do our job for us, and usually not in favor of the result.

There is also something here that simply feels good. When you know it is okay to say it wrong, that it is okay not to know the professional word, that it is okay to say "I cannot explain it but that is not it," you are free to ask for what you actually want. A lot of good requests die at birth because someone worried they were not phrased well enough. With us there is no such thing. A request does not have to be well-phrased. It only has to be honest.

And this changes your pace as a business, too. When a request is easy to send, you send more of them. You stop hoarding small updates until you have "enough to bother a designer with," and you start simply asking the moment you need to. The email that needs an image, the story that needs a refresh, the ad that needs a new version, none of them get stuck in the queue of "I will do it when I have the energy to phrase it." That shifts your whole relationship with design inside your business: from a thing that stresses you and therefore gets postponed, to an available thing you reach for without friction. A business that asks for design easily is a business that looks better over time, simply because it keeps itself maintained instead of putting it off.

The Invitation: Tell Us How It Sounds in Your Own Head

So here is the invitation, and it is a simple one. The next time you need something designed, do not write a brief. Do not open a search engine to learn what the thing you want is called. Do not apologize for not being a design person.

Just tell us what you want, in the same words you would use to tell your business partner. "Make it pop." "I want it to feel more like us." "Something here is off and I do not know what." Each of those is exactly the right amount of information for us to start with. The rest we will draw out of you with questions, and the translation into design we will do for you. That is how it works at Duble//Slash, and it is also the part clients are surprised by, how easy it turns out to be.

Here is the reframe worth taking with you: your job is to know what you want. Our job is to know how to ask. You bring the feeling, we bring the questions that turn it into design, and the designers bring the hand that nails it. Neither side has to do the other's work.

So tell us: what is the thing you have been meaning to ask for but kept putting off because you did not know how to phrase it? 🙏