When we started Native Softwares, the plan was one product at a time. That lasted until the second idea arrived before the first one was finished. Today we run two live products, ExpertNest and OptionsLab, with a team small enough to fit around one table. People ask how we split our time, and the honest answer is: imperfectly, and on purpose.
One product has the week
The rule we landed on is that one product owns the week. Monday morning we pick which app gets the team's building time, and the other one gets maintenance only: reviews answered, crashes triaged, payouts processed, nothing new started. Alternating weeks sounds slow, but it beat the alternative. When we tried splitting every day across both apps, nobody finished anything and both backlogs grew at the same rate.
Shared code, separate brands
ExpertNest and OptionsLab look nothing alike, and that is deliberate. ExpertNest is bright and teal, built for someone learning AI skills in a chat-shaped lesson. OptionsLab is indigo and dense, built for traders arguing about a setup in a feed. Underneath, they share more than you would guess: the same auth, the same payments and payout plumbing, the same analytics, the same way of shipping a build. Every hour spent on that shared layer pays out twice, so it gets priority even when it feels less exciting than a feature.
What hurts
Context switching is the real cost. A trading community and an education marketplace have different users, different support questions and different moderation problems, and switching between them on a Monday takes real mental effort. We also under-invested in OptionsLab's LearnCenter content for a stretch because ExpertNest's expert onboarding needed all hands, and the community noticed. Being a small team means those trade-offs are visible to users, not hidden behind a roadmap slide.
Why we keep doing it
Two products make the studio more honest. Lessons from one show up in the other within weeks: the XP system in OptionsLab shaped how ExpertNest tracks course completion, and the conversational lesson format from ExpertNest is changing how we write TradeLab breakdowns. Neither app would be as good alone. We are not planning a third product this year, but if we ever do, it will be because the shared layer is strong enough to carry it, not because we got bored.
Keep reading
More from the studio
Why We Build Everything In-House
The case for owning your entire product stack — and why it makes us move faster, not slower.
Designing OptionsLab: from idea to App Store
How we designed and shipped a trading community — not another signal group — as our first mobile product.