Client stories: what founders say after their rebrand

There are two client reviews on this site so far, and I add them slowly because I ask each client properly instead of lifting a line out of a WhatsApp thread. Ryan Judd, a music therapist, guitarist and composer I worked with on card design and print production, wrote: “Javeria brought care and precision to every detail, from the card layouts down to the fine-print specs our manufacturer required.” Anvi Shah, Senior Manager at ReliaCare Ltd (USA), wrote: “Javeria delivered excellent work, on time.”

If you came here looking for more brand designer reviews, I can add something slightly different and, I think, useful: a summary of what founders tell me weeks and months after a rebrand, once the work has had time to live inside their business. What follows is paraphrased and pooled from many conversations, so none of it should be read as a direct quote.

Some of it is flattering and some of it changed how I work, but all of it tells you more than a five-star rating would.

Almost every founder I work with has a tic before the project. Before they send a link they say “ignore the website, we’re fixing it”. Before a pitch they apologize for the deck. Before a trade show they apologize for the banner. It is such a habit that they don’t hear themselves doing it.

The thing I hear most, a month or two after handoff, is some version of: I sent the link without the disclaimer. That sounds like a small thing, but a founder who stops apologizing for how the business looks starts talking about what the business does, which is the conversation that actually wins the client.

This one comes from founders who have been burned before. They had a logo as a JPG with a white box around it. The printer asked for a vector and nobody knew what that meant. The sign maker redrew the mark by eye and got the proportions wrong. The embroidery company asked for a one-color version that didn’t exist.

After a proper handoff, that stops. The folder has the vector source files, the one-color and reversed versions, the color values in CMYK and Pantone, and a page that says which file goes where. Founders tell me, in one form or another, that the printer simply confirmed they had everything and asked no questions, and that they hadn’t realized how rare that was.

A brand is tested the day someone who didn’t sit in the design meetings has to make something. Usually that’s a new marketing hire, a VA or an agency, and usually they are working from a screenshot of the homepage.

Founders with a guideline book tell me about the first time that person produced a slide, a post or a proposal and it looked right without a correction. The 21-page Aurexon book and the 45-page Arista guide exist for exactly that moment. A written guide moves the brand out of the founder’s head and into the company.

I hear this one with a bit of pride on both sides. A supplier asks, or a customer, or another founder at an event. That is usually when the brand starts to feel like an asset the founder enjoys talking about. Some of my enquiries arrive this way, which is a better endorsement than any review page.

Founders come to me for a logo and put up with the guidelines. Months later, the guidelines are what they mention, because the questions stopped: which blue, which font to use in Google Slides when the real one isn’t installed, whether the logo can go on a photo, how small is too small. Every one of those used to be a message to me or a guess by someone else; now it’s a page number.

If you are choosing between a slightly bigger logo package and a basic guide, I will almost always tell you to take the guide. The 7 things every guidelines document must include explains what goes in one.

Not every project went smoothly. The complaints have taught me more than the compliments, so these are the main ones and what they changed in my process.

Feedback was chaotic

Early on, feedback arrived as a stream of voice notes, screenshots and “actually, can we” messages over three days, often from three people who disagreed with each other. Revisions kept undoing each other. Now each round is one consolidated set of notes from one decision maker, with a date. I explain this on day one, and projects got faster and calmer.

The timeline slipped

In the first few years, I sometimes let a deadline drift rather than send a difficult message. That is on me. Now the delivery date is written down before we start, and if anything threatens it, from a late questionnaire to a printer problem, you hear about it the same day, with the new date. Founders would rather have bad news early than silence.

Too many concepts, too soon

Some founders found eight directions overwhelming, and they were right. That is why the Direction step now comes before any polished concept: references and palettes first, so we agree on where we’re going, then fewer and stronger concepts shown in context.

Which file do I use for what

A handoff folder full of correctly named files is still a folder full of files. So now every handoff includes a single page that says: this one for the printer, this one for the website, this one for embroidery, this one for Instagram. It is the kind of thing you only add after someone asks for it.

Featured in this post

Arista Living

Arista Living: a 45-page style guide the team, agents and suppliers all work from, which is the thing founders end up thanking me for most.

Read the case study

A review tells you the designer answered messages and was nice. That’s useful, but it won’t tell you whether the logo survives embroidery, whether the color values were written down, or whether the client owns the files. For that, read the portfolio differently.

• Look for applications on real objects. A mark shown on a sign, a bottle, a phone and a shirt has been tested. A mark on a gradient background with a lens flare has not.
• Look for the system around the mark: color codes, type, rules. If every project is a logo and nothing else, the designer may not do the part that saves you time later.
• Check what the handoff includes. Vector files, one-color versions and written ownership should be listed, not assumed.
• Notice the range. Fifty projects in one style means you are buying that style, whatever your business is. You want someone who made Aurexon look like engineering and PuppyDock look like a happy dog.
• Ask what went wrong on a project and what they changed. A designer with no answer hasn’t done enough projects, or isn’t telling you.

Read the reviews on this site with the same eye, including the ones I add later. The useful ones will mention a printer, a hire or a deck. “Lovely to work with” on its own tells you very little.

Alongside the two reviews, the case studies let you judge the work itself. Aurexon Construction, KAE Hair Care and Arista Living show the brief, the thinking and every application, so you can see how I work before you talk to me. The step-by-step process post covers what happens between the first message and the final folder.

If that looks like the way you want to work, book a 30-minute call. You’ll leave with a clear view of scope, timeline and price, and if I don’t think you need me yet, I’ll tell you that too.