Lore

Do Things That Don't Scale, First

Overview

Sequencing principle: build structure, tooling and systems only after the business has been run and understood manually, in its substance — not before. Tolga Önal applies this to elopage's own growth: early operations (including support, see Support as Marketing) were handled manually and unsystematized until the underlying mechanics of what worked were well understood, and only then were processes/systems layered on.

Application

When a function of the business feels premature to systematize, check whether it's actually been run manually long enough to know what is worth systematizing — premature systems risk encoding the wrong assumptions.

Example: elopage Support

Tolga Önal cites elopage's early support handling as a direct application: support was run manually, entirely without dedicated software, so the team could understand the actual substance of customer problems before building structures or systems around it. Only after that substance was understood did elopage invest in CRM and support-scaling infrastructure (see Support as Marketing, Optimize for Usage, Not Locked Revenue).

Case: ConvertKit's "Powered by" Badge

Nathan Barry credits part of ConvertKit's climb from roughly $2,000/month toward $100M/year to organic, word-of-mouth growth generated by the "Powered by ConvertKit" badge/link that appeared wherever customers used the product publicly — a small, manual, non-scalable touch layered onto a repositioning of the product specifically for professional bloggers, which compounded into durable inbound growth. He paired this with a second lever: changing the peer group he spent time with (see Peer Group as a Growth Lever).