# Embrace Your Tagline at Every Opportunity

DevFeed: [Embrace Your Tagline at Every Opportunity](<https://devfeed.tech/articles/embrace-your-tagline-at-every-opportunity-28343.md>)

Original publisher: [Read original article](<http://fuzzyblog.io/blog/startup/2020/07/03/embrace-your-tagline-at-every-opportunity.html>)

Author: Fuzzygroup

Published: 2020-07-03T00:00:00Z

Content type: opinion

Language: en

Sources: [Scott Johnson](<https://devfeed.tech/sources/scott-johnson.md>)

Topics: [Code](<https://devfeed.tech/topics/code.md>), [version-control](<https://devfeed.tech/topics/version-control.md>), [ui](<https://devfeed.tech/topics/ui.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [marketing](<https://devfeed.tech/tags/marketing.md>), [project](<https://devfeed.tech/tags/project.md>), [startup](<https://devfeed.tech/tags/startup.md>), [startups](<https://devfeed.tech/tags/startups.md>), [user-interface](<https://devfeed.tech/tags/user-interface.md>), [validation](<https://devfeed.tech/tags/validation.md>), [version-control](<https://devfeed.tech/tags/version-control.md>)

## AI overview

The author recommends treating a startup tagline as a concise description of what is being built, preserving candidate taglines in code under version control, and displaying the selected tagline in the project's user-interface footer. The article also recommends seeking early validation.

## Source excerpt

I have been, since my very first foray into startups, a huge advocate of the tag line. A tag line is that one to 10 word phrase that encapsulates exactly what you are building. I talk about this in my document on Opportunity Profiles where I identify it as one of the first things you write down when planning a new venture. This morning, as I engaged in my "just out of bed, the brain is fresh, work on something new and interesting" moment of my day, I found a new way to embrace the tag line. Yesterday was I brainstormed on something and what felt like a new perfect tag line was uttered. So I did two things today: I put that tag line and the other candidates into code. This means that not only are the written down but they are under version control so I can get back to them as needed. You never know how a project morphs and changes as it weaves its way towards the market and being able to get back to a tag line, I've found, is vital. I added it to the project's user interface as part of its footer. This means that every time that I look at what I'm building, I will see it and, hopefully, be inspired by it. Here's an example of #2 (this is just the footer not the project itself). The tag line is the text on the left in bold. And if you find that tag line intriguing then: That's great; it means it might be right; validation on these things is key and should be sought as early as possible You know where to find me if you want to ask about it (contact info is on the bottom of every page; look down)