Logology
Logology was a polished logo-design product with explicit pricing and founder-reported revenue. The non-recurring model still required more than 100 new customers each month, leaving the team exposed to crowded logo-market competition and AI uncertainty.
Visit productProduct snapshot
What it was
Logology was a logo and brand identity product that sold startup logo packages.
Who it was for
Problem / value
It helped customers choose and buy a polished logo package through a guided brand identity workflow.
Core workflow
Customers described brand preferences, reviewed logo options or packages, and purchased a one-off brand identity package.
Core dependency
The business depended on continuous new customer acquisition because purchases were mostly non-recurring.
Product form
Competitors or alternatives
What happened
Summary
Dagobert Renouf wrote that he and his wife decided to give up on Logology after five years and almost all of their savings bootstrapping it.
Core risk
Survival Profitability Without Recurring Revenue
Before you build
Why it matters
Logology was a polished logo-design product with explicit pricing and founder-reported revenue. The useful pre-build question is whether startup founders, small businesses, and solo makers needing brand identity will repeatedly use and pay for choose a startup logo and buy a brand identity package through a channel you can keep reaching.
Primary check
Model repeat purchase, recurring revenue, or a reliable acquisition channel before relying on one-off logo sales in a crowded market.
Checklist
- Who owns the budget for this problem?
- What repeated event triggers the buyer to use this every week or month?
- Which channel reliably reaches startup founders, small businesses, and solo makers needing brand identity without a one-off launch spike?
- What evidence would show Survival Profitability without Recurring Revenue before you build more?
- Define which segment among startup founders, small businesses, and solo makers needing brand identity pays first and why the problem is urgent now.
- Prove the workflow happens often enough to justify buying.
- Test one acquisition channel for startup founders, small businesses, and solo makers needing brand identity before relying on launch traffic.
- Write down why a buyer would switch from logo marketplaces, freelance designers, and AI logo generators.
Relevant if
- You are building a web app for startup founders, small businesses, and solo makers needing brand identity.
- The main value is specific: It helped customers choose and buy a polished logo package through a guided brand identity workflow.
- You have interest, signups, usage, or founder confidence but have not proven paid repeat use.
- Buyers can already use logo marketplaces, freelance designers, and AI logo generators or avoid switching altogether.
Less relevant if
- You already have paying startup founders, small businesses, and solo makers needing brand identity who repeatedly use the workflow and renew or expand usage.
- The product is an internal tool with a mandated user base and no external go-to-market risk.
Pre-build tests
- Run the workflow manually for a small group of startup founders, small businesses, and solo makers needing brand identity.
- Ask one buyer to pay, renew, or sign a dated pilot before building the next version.
- Test one non-launch acquisition channel and count qualified conversations, not page views.
- Put the offer next to logo marketplaces, freelance designers, and AI logo generators and ask what would make the buyer switch now.
Transferable lessons
- Validate whether startup founders will pay for the workflow, not only say it sounds useful.
- Treat Survival Profitability without Recurring Revenue as the first assumption to test.
- Compare the product against logo marketplaces, freelance designers, and AI logo generators before adding more features.