@adilaw122Alawode Adejare of Ten Labs: We build products that we really need.
I'm Adisa, founder of Ten Labs, a small product studio in Melbourne. We build the tools we needed ourselves. Harv.ant turns a phone scan of a room into a floor plan, doll house and walk-through. SwiftsReader is a cognitive speed tool that helps busy teams and ADHD minds tear through PRDs, contracts, and dense documentation twice as fast. And, Freebird AI is a coding assistant for VS Code that reads across your codebase, edits files in place, extremely useful for privacy minded developers, and can push to GitHub.
Swiftsreader is what I'm most focused on right now.
Up until now, we’ve focused on individual B2C users and rolling out pilots for high schools and universities. However, I’ve realised that fast-moving tech and SaaS teams have a massive concentration of neurodivergent minds, and drown in PRDs, technical specs, contracts, and research every single day.
I am now aggressively scaling SwiftsReader and testing a B2B team angle alongside our B2C/EdTech growth.
I would love to get the forum brains on two things:
- B2B Positioning: For founders/ops leads here; would you buy a tool like this under a "team productivity / read PRDs 2x faster" angle, or as a "neurodiversity & workplace inclusion" perk?
- Aggressive Growth Channels: For those running dual B2C + B2B tools, what’s been your highest-converting acquisition channel right now (short-form video demos, bottom-up domain capture, cold outbound, or something else)?
I am happy to share anything I’ve learned from scaling Freebird AI to 30k+ downloads/installs organically, and if any founders here want to test SwiftsReader with their team, please drop a comment and I will set you up with free access!
Comments1
Adisa, on your two questions. I would not choose between the framings, I would test them on separate pages. "Read PRDs 2x faster" is what people type into search, so a page per document type (PRDs, contracts, API specs, research papers) with a short before/after example of one real document read in half the time gives you a landing page and a demo at once. The inclusion angle works better as a second page aimed at HR and ops leads, not as a perk line on the same page. In Search Console after 3 to 4 weeks you will see which wording people actually search for, and that is cheap data before you pay for any outbound. For channels, bottom-up works well when one person on a team can try it without a card, so I would keep a free tier tied to one document. How did the 30k Freebird installs split between organic search and store listing? Curious which one carried it.
1 comment
Adisa, on your two questions. I would not choose between the framings, I would test them on separate pages. "Read PRDs 2x faster" is what people type into search, so a page per document type (PRDs, contracts, API specs, research papers) with a short before/after example of one real document read in half the time gives you a landing page and a demo at once. The inclusion angle works better as a second page aimed at HR and ops leads, not as a perk line on the same page. In Search Console after 3 to 4 weeks you will see which wording people actually search for, and that is cheap data before you pay for any outbound. For channels, bottom-up works well when one person on a team can try it without a card, so I would keep a free tier tied to one document. How did the 30k Freebird installs split between organic search and store listing? Curious which one carried it.