Growth is easier to study when you can see the mechanism.
Hi, I’m Rakha and I made Tactern because useful growth research is usually scattered across product screens, help docs, and launch posts. I wanted a place where the actual mechanism can be followed from company behavior to a reusable pattern.
From company behavior to a reusable idea
A company is the subject. A tactic is the specific implementation. A pattern is the reusable mechanism. A flow makes the handoffs between user and product easier to inspect. Together, they make it possible to ask a more useful question than “What should we do?”: “What is this company doing, and why might the sequence work?”
Built for investigation
Tactern does not publish generic advice, performance claims, or reconstructed product screens. Each record starts with a public source and separates what the source documents from Tactern’s interpretation of the growth mechanism.
A library that can be challenged
Product surfaces change. Sources can become outdated. If you find a tactic worth studying, submit the public evidence anonymously. It enters an editorial review queue before it can appear in the library.