See all guests

Guest Spotlight: Kameron Tanseli

Kameron Tanseli
Fyxer | Engineer

About Kameron Tanseli

Kameron Tanseli is Head of Growth Engineering at Fyxer, where he helped scale the AI startup from $1M to $35M ARR. He focuses on the growth engineering playbook behind that run: product-led growth loops, AI-assisted development, and a culture of shipping roughly 1,000 experiments to find out what actually compounds over time.

Notable Quotes

"I'd rather have a 50–50 test to give me direction than YOLO ship to 100%."

"If I'm launching something and I don't see it impact the ARR chart, I'm not doing something correctly."

"You're going to be really bad at it for the first few months—even I am at a new company—but you'll learn the customer and find your groove."

Kameron Tanseli
Fyxer | Head of Growth Engineering

Fyxer's engineering playbook to go from $1M to $35M ARR

Go to S1 | E7

Subscribe to the podcast

Takeaways

All Takeaways

Democratize experimentation with a centralized platform and self-serve tooling; reset baselines regularly.

Go to S1 | E7

Scale experimentation with AI: use Cursor desktop/cloud agents for parallel builds and visual QA; orchestrate docs/analysis via Claude; automate cleanups and reporting.

Go to S1 | E7

Test “obvious” UX changes; preserve helpful friction and align with user mental models.

Go to S1 | E7

Build capabilities, not just tests—use experiments to unlock platform features (e.g., metering, paywalls).

Go to S1 | E7

Make experimentation company-wide: centralize data (BigQuery), broadcast wins/losses in Slack via GrowthBook, and auto-correlate metric dips to releases.

Go to S1 | E7

Build growth loops from habits: design shareable artifacts and personalized signup paths; drive users back to your domain to capture value.

Go to S1 | E7

Ship first, then optimize: launch PLG features and immediately run experiments to increase adoption; track daily active usage per feature.

Go to S1 | E7

Test big levers—not just UI: pricing models, usage limits, onboarding pathways—and judge success by ARR movement, not micro-metrics.

Go to S1 | E7

Prioritize by risk: run rigorous A/B tests where you have volume; use before/after or non-inferiority for low-risk in-product changes.

Go to S1 | E7
The experimentation edge podcast logo with a picture of host Ashley Stirrup