JobNimbus’ Post

I turned my competitor into my customer. 1 year ago, I saw a company called "AIMixingMastering" popup, and they were also offering a human-adjusted automated mixing service. I was upset to have such a direct competitor at first. 1 year later, AIMixingMastering has installed a Stemmer auto-mastering widget on their homepage. They wanted to make their company more of a one-stop-shop, as well as earn some extra passive income. They certainly have been earning passive income. In January, their mastering widget generated over $900 in sales! Additionally, we're starting to build out a sales funnel for them. They can drive traffic right to their widget, maybe make a sale, but more importantly collect user contact info. Then they can retarget the users with their higher-ticket services. ---------- Stemmer's white-labeler pipeline is saturated, and I'm spending my days adding requested customizations for each white-labeler. I was getting ready to delegate sales, but the real bottleneck is actually programming custom features that white-labelers mandate before they launch. It will take personal-growth for me to delegate programming work; I fear losing control of my product. I'll have to take that step eventually. Here's to another great month!

Design vs Engineering? What we pride ourselves on at Scriptive is that we have built a business that truly understands what matters when developing and building digital products, regardless of what they are. There is no denying the importance of design and user experience, but we have seen scenarios too often where the engineering takes a back seat. At the core of Scriptive, everything we do – from our processes, hiring, requirements gathering, and ultimately our product development – always respects the balance between amazing design and engineering. Any business building a product, be it a custom web application or a Shopify Plus store, is doing so to achieve success and growth. So it is critical that engineering is aligned with these goals and plays a positive part in achieving this success rather than holding it back. If you are in the early stages of planning and preparing to build a product, we would love the opportunity to connect and see how and where we could help.

Steve Jobs had a simple rule for designing the perfect user interface: The 3-click rule. Steve was intimately involved in the design and development of the original iPod. Those that knew him said he had the same response to nearly every problem - “Simplify!” During product demos, he would go over every screen and apply a rigid test: If a user wants to use a core feature (eg play a song) ... they must be able to get there in three clicks. The success of the iPod changed the industry forever, and the 3-click rule quickly spread across product development circles. Airbnb founder Brian Chesky was always adamant users are never more than 3 clicks away from a booking. Same as reading trending content from your favourite subreddit. Or watching your favourite Youtuber’s latest video. If you're building a consumer product, ask yourself: How many clicks does it take for a user to reach your unique-selling-point? -- 👉 P.S. If you enjoyed this post, you'll love my newsletter - a 3-minute breakdown of the strategy playbooks and growth hacks behind the world’s greatest companies. Join 50,000+ strategy nerds from companies like Google, Meta, Atlassian, and Netflix: https://lnkd.in/g2FWfXGR

Patience is a virtue, even in the tech world! 🚀 Figma's community-led growth strategy teaches us the value of taking time to build and cultivate a community. From emerging out of stealth to tailoring content for early adopters, Figma's approach proves that slow and steady can lead to lasting success. Check out their unique journey in this insightful article.

Our product team is knee-deep in the final stages of our new app. We're all bleary-eyed, surviving on caffeine and determination. Enter Mike from Sales, strolling in with his usual upbeat energy. "Hey folks! How's our game-changing app coming along?" Mike chirps, oblivious to the tension in the room. Jessica, our project lead, manages a weak smile. "We've hit a snag. The app keeps crashing when users try to save their progress." Mike, ever the problem solver, asks, "Can I take a look?" The team exchanges glances but shrugs. Why not? Mike starts tapping away, narrating his actions like he's giving a sales demo. Suddenly, he exclaims, "Oops! I think I broke it!" But instead of breaking it, Mike's random button-mashing somehow reveals the issue. The team crowds around, eyes wide. "Mike, you genius!" Jessica exclaims. "You've just shown us exactly what's causing the crash!" Turns out, sometimes you need someone who doesn't know the "right" way to do things to show you what you've been missing. Moral of the story: Sometimes, all your engineering team needs is a fresh perspective and a bad analogy. Keep a Sales rep on deck – they might just save your sprint (and bring donuts). 🤤

Imagine getting stuck in a never ending product walkthrough... I can already see you rage by even thinking about it And you're not alone 87% of users groan and feel the same way Huge drop-offs are bound to happen And chances are... users might not even comeback again Is this how you think of treating your user? Let me tell you a better way! Ask user to share why they're here right away And this time, show them what they need No lengthy features parade Skip the boring intros. Forget feature overload, focus on value. This is PLG for you. Swift Aha! No Drama. #ProductDiscovery #productledgrowth

Release is not a finish line. It’s another chapter in your product’s life. And you’d better be prepared for the next pages. Users will always want more. They can’t be satisfied with the first dish for long. Our team helps to create a backlog for future development, including: ✓ additional features that weren’t released in the first version, ✓ potential features that users might anticipate based on their feedback. The cherry on top is that a robust tech strategy boosts general product growth: ☞ User retention Users welcome new experiences and features. Their loyalty strengthens with constant product upgrades. ☞ 1st choice People don’t change habits and familiar services easily. Unless your product stays relevant to their needs, users won’t explore alternatives. ☞ Sales dealbreaker Functionality backlog helps your Sales to convince potential users. Awaiting users can join your base with a new upgrade. The features backlog allows you to steadily improve your product, even if at some point you decide to end our collaboration. If there's a need, you can still maintain the product within your internal team. We care just as much about delivery as the groundwork for your product’s evolution. #baseblocks #techdevelopment #productdevelopment #databasedevelopment #appdevelopment

One mistake = $527 lost = Invaluable lesson Countless hours into finding the team... We hired Sam - an ideal fit.  We trusted his expertise and advice. We made a server setup that he suggested. And one day we discovered that: For 3 months we had been overpaying Sam has made a big mistake in the setup We lost one week to fix & $527 in additional fees Nobody is perfect. Making mistakes is part of the business. But what you do after that makes the difference. For us, this meant improving the development process. P.S. Would you fire someone who has made a big mistake? —---------- Hi, I’m Bogomil S. and I have: ↳ 2x successful brand exits ↳ scaled a brand from 0 to 7-figures in 6 months ↳ spent hundreds of thousands on advertising online Now, I am trying to make Commenter AI the most helpful commenting tool.

I’m big on building the Nostra brand in public. Each quarter we give retrospective updates on product changes, team growth, as well as our plans to improve user experience in the future. Here’s our Q3 update, in summary: → Meta Case Study: Meta published a case study featuring our shared client, Beachwaver Co., on how the Nostra product improved CVR (2.1X!) — this was a huge win and shoutout for our team. → Platform upgrades: Including expanded service to Salesforce, adding self-serving to A/B testing, and upgrading customer portal design. → Hiring: Bringing on experienced individuals in key roles, including our Revenue, Customer Success, Operations, and Engineering teams (there are too many talented people to tag, but you can see them in our full update) → Clientele: Onboarding major clients, such as Jolie, Monos, Birdies, Kaged, 310 Nutrition → Q4: Exciting new capabilities coming to Nostra, including further GA4 integrations and a new challenge for a global top-20 fashion house. As we’re pushing through the busy holiday season, it’s nice to take a step back and reflect on the amazing work from the Nostra team — without them, none of it’s possible, and I’m proud of what I’ve seen so far in Q4. I’ll drop the full update in the comments.

Reminder that it’s easier to add features than remove them. Challenge yourself to see what you could cut from your product, design or process… Can you simplify to amplify what really matters? Some classic quotes on simplifying from the greats… “I’m never troubled losing material. I cut everything to the bone. When you're shooting, you want to make sure you don't miss anything and you cover it as fully as time and budget allow. When you're editing, you want to get rid of everything that isn't essential” - Stanley Kubrick “Make every detail perfect and limit the number of details to perfect.” - Jack Dorsey “I would have written you a short letter, but I didn’t have the time”. - Blaise Pascal “Simplicity is not the absence of clutter, that's a consequence of simplicity. Simplicity is somehow essentially describing the purpose and place of an object and product. The absence of clutter is just a clutter-free product. That's not simple. - Jonny Ive Simple can be harder than complex: You have to work hard to get your thinking clean to make it simple. - Steve Jobs In the world of apps this may be at the very start as we design out a full spec advanced product and decide the true MVP USP’s to develop first. Or with an existing product where data touch points are low on a feature, or where feedback suggests users just don’t like or don’t care for it. Perhaps something has no real financial returns isn’t worth the maintenance hassle (regular bugs) Does a feature play a part in your long term vision or is it a distraction? All things to consider! Be bold! Would love to hear if anyones had success from cutting something from their product and not regretted it. I said product, not employees this time thank you! ✨Here to help you build apps and simplify your products. #productmanagement #appdevelopment #productdesign #simplicity