A lot of early stage founders are incredible engineers, but lack the ability to make things look “right”. We’ve seen a bunch of our friends launch products to no reception, some of which seemed due to poor design decisions (like, making buttons hard to find or a landing page that looks like it might steal your credit card).
Two years ago, two of my closest friends started a company, raised a small round, and spent tens of thousands of dollars on their initial branding. That was a substantial percentage of their funding, and then their brand entirely changed once they learned more about their customer. After I saw them waste a ton of time and money on this, I realized that it ought to be possible to build software that could have done just as good of a job as the design agency. At the core of it, the designers asked my friends a bunch of questions about how they want their company to be perceived by customers, offered them colors and fonts and a design aesthetic that conveyed those feelings, and then created a mockup of a website that incorporated those elements. So, I decided to build software to do just that.
With Parade, we have taken a traditional brand design interview and turned it into a self-serve software product. You answer a series of questions about how you want your brand to be perceived and receive design aesthetic suggestions based on them. We use machine learning to identify design elements (such as fonts, colors, layouts, use of color, density of information, line and button styles, and visuals) that project the way you want your brand to feel, then present them to you as simple choices. To power the suggestions, we collected training data from both designers and non-designers to understand what emotional reactions these design elements evoke. Because of this technology, we are able to identify the design aesthetics that you want without having to iterate repeatedly or spend hours searching for inspiration. After you make your choices, we use the math behind design theory (such as an algorithm to expand one color into a range of colors that accounts for the difference in perceived contrast based on hue, saturation, and lightness) to flesh out your brand [0].
Right now, after onboarding, you are able to access all of your design elements in a style guide for free through the dashboard. It includes your colors and your fonts, plus a place to download your logo and icon in a few colors. You can see an example of what this looks like here: https://app.getparade.com/hackernews/style-guide or here: https://app.getparade.com/hooli/style-guide. This is similar to the output startups get from a first engagement with a designer, which helps you set up basic, consistent styling for your website and social media profiles.
At this point, we’ve helped thousands of companies create their brands, including YC-backed companies like WellPrincipled (https://www.wellprincipled.com/), Enable (https://www.enable.us/) and MeterFeeder (https://www.meterfeeder.com/).
The next step beyond style guides would be to automatically generate brand assets—things like pitch decks, landing pages, and social media posts. We're working on that. We haven't completely automated it yet, but we are able to create these assets with very rapid turnaround time. Once we get it fully automated, we plan to add subscription features that enable founders to make ready-to-use assets themselves.
In the meantime, we run an agency, serving customers using our work-in-progress software. It’s different from a traditional agency, though—while traditional agencies spend many days asking you about how you want your brand to look, seeking inspiration, and iterating based on your feedback, we are able to capture what you describe through our onboarding survey and create assets with your design elements algorithmically. We are able to deliver most designs within 48 hours, and almost all of our customers have been satisfied without any iteration. Right now, a lot of the algorithmic design work happens via an in-house Figma plugin, which we plan to move onto our platform in 2022 and open up to self-service.
Something that’s surprised us while working on this: we’ve found that our users don’t always believe that their choices are really great. Design is intimidating—you’re aware that there is some psychology of color and also some color theory rules, but aren’t exactly sure what they are. You’ve built things in the past that just didn’t look quite right—how can you be sure the choices you made on Parade are good? Oftentimes, designers will even use words to make themselves seem to know some secret you don’t. We’re trying to reassure our users by surfacing more of the science behind the suggestions we make, and to make sure we encode rules that prevent certain common mistakes.
We would love to hear your thoughts, questions, concerns, or ideas about what we’re building - or about your experiences with automating design in general. We appreciate all feedback and suggestions!
[0] See https://www.w3.org/TR/AERT/#color-contrast for math on color contrast, or https://alienryderflex.com/hsp.html for a good writeup on perceived brightness.
by Andrey
Azimov