Build

179 principles in this stage

Making smart product and technical decisions

Product Strategy

138 principles

  • ✓Solve one problem exceptionally well
  • ✓Ship fast and iterate based on real usage
  • ✓Say no to features that dilute your core value

Tech & Tooling

41 principles

  • ✓Use boring technology you already know
  • ✓Optimize for speed to market, not perfection
  • ✓Technical debt is fine if it gets you customers
PrincipleStrengthCases

Build minimal single-feature products rather than complex multi-feature apps

→
Proven
56

Refine product based on customer feedback before scaling

→
Proven
21

Resource constraints should drive niche focus

→
Proven
14

Keep your team minimal to maximize margins and maintain agility

→
Proven
13

Extract one feature from incumbent tools and make it dramatically better

→
Proven
9

Build embarrassingly simple MVP then validate with immediate hard paywall

→
Proven
8

Build products so remarkable that users naturally spread the word without prompting

→
Proven
6

Launch with freemium model to lower barrier to entry and build large user base

→
Proven
5

Use radical simplicity to set the market pace and force competitors to react

→
Proven
5

Products can identify real problems but still fail by providing wrong solutions

→
Proven
5

Focus on the problem first, then determine which technology enables the solution

→
Proven
5

Start as done-for-you service, then automate the proven process into software

→
Proven
5

Tack to win. Build a fundamentally different product, not a better version of the leaders

→
Proven
4

Resist chasing competitor features - stay true to your products character

→
Proven
4

Ship one key feature to early users and iterate in tight feedback loops

→
Proven
4

Ship MVP quickly by repurposing code from previous projects

→
Proven
4

Open source plus managed hosting is a proven business model to significant recurring revenue

→
Proven
4

Rebundle from feature to solution when enterprise buyers think in categories, not point products

→
Proven
3

Enforce strict stack ranking - adding priorities requires removing others

→
Proven
3

Users want answers, not homework - simplify from DIY to done-for-you

→
Proven
3

Route support to social DMs until 10K MRR for daily user feedback flow

→
Proven
3

Build portfolio of complementary products serving same audience to maximize customer value

→
Proven
3

Build composable systems that let customers configure 20% for differentiation in competitive markets

→
Proven
3

Pivot quickly through multiple experiments until you find real traction signals

→
Proven
3

Evolve from selling products to selling complete business opportunities

→
Emerging
2

Design for the least tech-savvy user in your target market, not the most advanced

→
Emerging
2

Reuse code and technical assets from past projects to accelerate time-to-market

→
Emerging
2

Start naming with positioning work—your positioning statement generates naming candidates

→
Emerging
2

Pivot from sales-led to product-led growth when hitting capacity constraints

→
Emerging
2

Choose a hard version of your problem to pressure-test your model and avoid over-fitting

→
Emerging
2

Defer enterprise features to build foundational infrastructure that will last decades

→
Emerging
2

Design content for participation and interaction rather than passive consumption

→
Emerging
2

When incremental experiments plateau, step back and consider a complete overhaul to reach a higher local maximum

→
Emerging
2

Remove authentication and use local storage to reduce friction and costs

→
Emerging
2

Maintain waitlist-only access post-launch to sustain scarcity

→
Emerging
2

Build features users actually want, not just what goes viral in marketing

→
Emerging
2

Make apps either highly sharable through assets or high retention through utility

→
Emerging
2

Build portfolio of apps serving same niche audience to compound marketing advantages

→
Emerging
2

Design content funnels to move users one step at a time, not explain everything

→
Emerging
2

Launch with one core feature that delivers the aha moment, even if everything else is incomplete

→
Emerging
2

Build no-code versions of technical products to expand addressable market

→
Emerging
2

Partner 50/50 with co-makers who handle coding while you handle operations

→
Emerging
2

Master one growth pillar completely before spreading resources across all pillars

→
Emerging
2

Build painkillers that solve urgent problems, not vitamins that are nice-to-have

→
Emerging
2

In boring industries, differentiate by doing the opposite of category norms

→
Emerging
2

Choose high-demand, low-touch services to maximize solo leverage

→
Emerging
2

Define specific service deliverables rather than unlimited offerings to manage margins and expectations

→
Emerging
2

Invest disproportionate time researching your audience to deliver breakthrough value

→
Emerging
2

Solve integration gaps that competitors leave for customers to figure out

→
Emerging
2

Focus on one genuinely hard problem beats building feature-complete tool that does everything mediocrely

→
Emerging
2

Start with narrow AI use case that works today to fund expansive future vision

→
Emerging
2

Prune profitable products to refocus all energy on your strongest offering

→
Emerging
2

Build a minimum delightful product instead of a minimum viable product when entering high-trust categories

→
Emerging
2

Rebrand when the company outgrows the original product scope to signal platform evolution

→
Emerging
2

Insufficient moderation infrastructure will destroy a social platform regardless of product-market fit

→
Emerging
2

Build AI-native architecture rather than bolting AI onto legacy approaches

→
Emerging
2

Keep scope tight and solve one job well instead of expanding features. Appraiva focused solely on automating property discovery using street-level images + AI, resisting the urge to add complexity.

→
Emerging
2

Switch from one-time courses to free recurring content to build audience and trust before monetizing

→
Emerging
2

Invest in painful rewrites when they unlock long-term scale and capabilities

→
Emerging
2

Pivot from consumer to B2B when you find product-market fit with developers

→
Emerging
1

Choose boring, obvious ideas in established markets over novel concepts when you have deep domain expertise

→
Emerging
1

Quality-first beats quantity-first in education businesses

→
Emerging
1

Build in stealth if you need time for product-market fit without public opinion noise

→
Emerging
1

Let customers self-select their outcome to identify which converts easiest

→
Emerging
1

Let distribution constraints drive product evolution - pivot the form factor when the core experience can't reach users

→
Emerging
1

Apply speed tests: if users cannot complete main action quickly, it is a design problem

→
Emerging
1

Organize teams around problems to solve, not products to build, to stay open to better solutions

→
Emerging
1

Map partner's existing processes before building to ensure integration fit

→
Emerging
1

Prioritize branding and polish even in MVP to signal professionalism

→
Emerging
1

Offer identical self-hosted version as zero-cost free tier for developer evaluation

→
Emerging
1

Catch emerging tool waves early by building adjacent services before competition

→
Emerging
1

Design quality differentiates in commoditized AI-generated markets

→
Emerging
1

High trial conversion with low paid conversion signals users love idea but hate execution

→
Emerging
1

Build reusable component library to ship apps in hours not weeks

→
Emerging
1

Let App Store boost reveal winners, then double down with ads

→
Emerging
1

Treat simplicity as expensive separate feature requiring thousands of hours

→
Emerging
1

User experience multiplies all other metrics - onboarding, retention, conversion, referrals

→
Emerging
1

Design onboarding for your actual usage context, not theoretical best practices

→
Emerging
1

Compete on reliability and accessibility rather than technical features when entering established markets

→
Emerging
1

Make value proposition instantly clear in headline - design polish is secondary

→
Emerging
1

Build one-click competitor data migration to reduce switching friction

→
Emerging
1

Build for best-case scalability from day zero to avoid technical debt crises

→
Emerging
1

Make your product visually and experientially distinct instead of copying competitors

→
Emerging
1

Use template-based design with minimal customization to ship faster

→
Emerging
1

Tie product value directly to customer revenue metrics to associate your tool with success

→
Emerging
1

Position on outcomes not outputs to differentiate from competitors

→
Emerging
1

Curate for quality over quantity in high-trust environments to build reputation moat

→
Emerging
1

Distribute existing products before manufacturing custom versions to test demand

→
Emerging
1

Pull-based UX beats push-based for user assistance

→
Emerging
1

Expand product catalog within focused category to increase AOV and unit economics

→
Emerging
1

Offer to solve customer problems manually in exchange for structured feedback calls

→
Emerging
1

Fix defective inventory manually when capital constraints prevent reordering

→
Emerging
1

Build a cashflow business to fund your creative vision rather than monetizing the creative work

→
Emerging
1

Purchase and analyze competitor products to learn quality standards and structure

→
Emerging
1

Focus exclusively on highest-leverage revenue activities and kill everything else

→
Emerging
1

Build operational tools that reduce supplier costs to secure premium partnerships

→
Emerging
1

Package services to address customer's end goal, not just deliverable

→
Emerging
1

Identify the emotional outcome you sell, not just the functional feature

→
Emerging
1

Systemize content creation with AI and assistants to remove founder dependency

→
Emerging
1

Diversify when your market shifts from physical to digital alternatives

→
Emerging
1

Design self-contained tools that function without your ongoing infrastructure

→
Emerging
1

Provide experiential demos that let users verify tool behavior before commitment

→
Emerging
1

Build AI systems with traceability - require explanations for every decision not just outputs

→
Emerging
1

Build feedback loops that compare AI predictions against actual outcomes to improve over time

→
Emerging
1

Not knowing tech can be an advantage—naivety keeps you focused on outcomes instead of implementation constraints

→
Emerging
1

Teach instead of build for infinite scale—shift from 'we will do it for you' to 'we will teach you how' unlocks product leverage

→
Emerging
1

Being newer can be a technical advantage—skip legacy infrastructure and build for the future, not the past

→
Emerging
1

For enterprise AI, build on customer infrastructure—data gravity wins over convenience

→
Emerging
1

Filter custom deals by asking: will this integration generalize to 5+ future customers?

→
Emerging
1

Dominate franchise verticals by templating entire AI workflow for specific industry

→
Emerging
1

Define your constants - the timeless customer needs that will never change

→
Emerging
1

For gift products, market to purchaser aspirations not recipient preferences

→
Emerging
1

Build infrastructure for multiple revenue models simultaneously so you can flip between them

→
Emerging
1

Live-code solutions during sales meetings to prove technical competence and speed

→
Emerging
1

Build every customer-requested feature to be generalizable across your entire user base

→
Emerging
1

Use frequent product updates as the primary growth driver instead of marketing campaigns

→
Emerging
1

Turn down misaligned revenue early to protect product vision and team morale

→
Emerging
1

Structure portfolio with free traffic-driving products that funnel users to premium revenue generators

→
Emerging
1

Act as the AI manually until data volume justifies automation

→
Emerging
1

Write your product manifesto publicly before building to create alignment between vision and market demand

→
Emerging
1

Add deliberate friction as a feature when your users want to be restricted from their own behavior

→
Emerging
1

Design content for founder self-service submission using structured templates that guide non-writers to produce publishable content

→
Emerging
1

Build features that unlock new customer segments rather than adding capabilities for existing users

→
Emerging
1

Build the context layer for AI tools rather than another AI tool itself

→
Emerging
1

Radical niche reduction during a growth plateau can be the catalyst that unlocks explosive growth

→
Emerging
1

Position compliance as growth-enabling rather than risk-reducing to align with founder priorities

→
Emerging
1

Productize a service by constraining delivery to sequential single-task execution with fixed turnaround times

→
Emerging
1

Build native OS integrations that work everywhere rather than another standalone app

→
Emerging
1

Add intentional friction to AI output to increase user engagement and conversion

→
Emerging
1

Reduce integration time by orders of magnitude to remove the primary adoption barrier for infrastructure products

→
Emerging
1

Use a successful but unscalable product as a data-collection vehicle to power a venture-scale AI product

→
Emerging
1

Use human operators to simulate AI capabilities while building automation, progressively replacing manual work

→
Emerging
1

80% annual retention indicates exceptional product value

→
Emerging
1

Mac app customers expect lifetime deal options alongside subscriptions due to platform conventions

→
Emerging
1

Say no to deals that don't align with your future vision, even if lucrative

→
Emerging
1

Autopilot blog management: customers pay subscription and get posts uploaded to their blog without lifting a finger. Simplicity of "set it and forget it" appealed to busy founders.

→
Emerging
1

Build value ladder with low-friction entry points that drive conversions to core product

→
Emerging
1

Focus on engagement metrics over completion rates to differentiate and justify premium pricing

→
Emerging
1