13 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHNeed Feedback on Logo
Leading reported evidence
Replace goto
Suggestion or failed attempt
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I say Logo # 1, minus everything on top of the logo, with the new "Moto" replacing Goto.
Leading evidence: 'Replace goto' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Replace goto' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I'd change the tag line to a simple "group buying power"
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
You need to focus more on how it's going to use browser-window real estate.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
13 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T060112Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Second one down. But lose the drop shadow on the road and move the logo mark to the left of the copy line. Keep it simple and clean. Many of the others are difficult to read from a distance. To see this - squint your eyes and try to read them. It's difficult.
Simplicity is the key for any logo design
C.
PS -any other advice is $100/hr
#1 - with modifications "Use two colors only" It is already a mouthful, rotating three colors is too much. Goto (red) GroupBuy (black). Remove the tag that is encroaching on the readability of the logo.
2&4, dated font
3&5 reverse type is bad enough without adding outline to confuse the matter more
6 refer to #1 comment
7 nothin'
#1 - with modifications "Use two colors only" It is already a mouthful, rotating three colors is too much. Goto (red) GroupBuy (black). Remove the tag that is encroaching on the readability of the logo.
^
What he said.
Gregory and I are of the same cut of cloth. Agree completely on the moto idea. Not so much on the font. Good fonts are timeless. Bauhaus is one of them. Gotta luv Classic Modern...
C.
Agree that the second one is strongest. Don't fuss too much about the colour advice you're getting; this is a web brand, I assume. You need to focus more on how it's going to use browser-window real estate. For my money, the shading behind the logo is going to be a bigger issue when you get to site design.
Speaking of which, you might want to consider protecting more than just the .com version of your domain.
