MVP Development Optimization and Finalization for Fluint: The Challenges of Re-Planning an Existing Product
Turnarounds in MVP development are tough, but with the right approach, success is within reach. Explore how we revitalized a struggling project, transforming it into a thriving MVP using Agile methodologies.
Imagine being mid-way through your MVP development, and suddenly it feels like you're sinking. You've got a B2B SaaS startup, a solid idea, but the agency you hired is 8 hours ahead and barely speaks your language (literally, or otherwise). It's a real mess. That's where Fluint found themselves: stuck between an agency that wasn't working out and the scary possibility of losing all progress with a switch.
Cue NaNLABS, a software development team that doesn't fear a little mid-project chaos. We dived in, worked out the kinks, and got Fluint's MVP sailing smoothly to production in just 90 days. So buckle up, because we're about to tell you how skepticism turned into success, proving that changing horses mid-stream isn't always a bad idea.
Table of contents
The brief: Creating a streamlined, intuitive MVP for dual users
The solution: Transparency, technical enhancement, and Agile teamwork
Ready to build your own custom software with a team that cares about you and your processes? We’re not code monkeys, we care about you.
Meet Fluint: Pioneering a new approach to B2B sales
Fluint, a B2B SaaS solutions company, is the champion whisperer for sales reps. They help reps better equip their internal champions, ultimately boosting the probability of closing deals. They had a clear vision backed by first-hand experience and market validation, and they knew the problem inside out:
“Everybody likes to think about sales reps as closing the deal but they don't, it's actually the buyer because they're talking to their own team in their own language at the point that a decision is being made. And so [the key to closing is] being able to create content based on a deep understanding of the customer's problem, guide those internal conversations and the champion that's selling you.”
To address this, Fluint aimed to create content based on a deep understanding of the customer's problems, guide those internal conversations, and back the champion that's selling them with ready-made content in their own words.
Nine months into their Minimum Viable Product (MVP) development with a different agency, however, things were going from bad to worse. The initial plan of three months had tripled, the codebase was low quality and non-scalable, and communication inefficiencies were rampant. That's when the technical co-founder stepped in, identified the chaos, and made the critical decision to seek help.
In their search for a new development partner, Fluint resonated with one of NaNLABS' case studies involving Propr.ai, who were also trying to escape an underperforming agency and get their product back on track.
They saw in us a team that had successfully navigated these troubled waters before and so, Fluint took a leap of faith, choosing NaNLABS to salvage and finish their MVP.
The Brief: Creating a streamlined, intuitive MVP for dual users
Fluint came to us with a clear but challenging brief. Their main objective was to transform their MVP into a user-friendly and efficient tool that would enable quick content generation from sales reps to buyers. This platform had to serve two user types - the fast-paced sales reps and the buyers.
The brief was threefold:
Refine the scope and the user experience. They needed a streamlined, intuitive platform that could satisfy both their user types. Sales reps, known for their fast-paced work style, needed to navigate the platform effortlessly. Buyers needed an easy, collaborative platform to engage with the sales reps and take ownership of the sales process.
Enhance existing features. Drastic measures were needed to debug the existing codebase and enhance the functionality of the platform. Key to this was the development of an in-app editor, allowing sales reps to pull content from their call notes to effectively create sales plans and assets.
Deliver a scalable MVP. All these improvements had to be integrated into a solid, scalable MVP, ready to launch in just 90 days.
Of all the agencies that we engaged with, NaNLABS provided the most thoughtful and in-depth evaluation and report. It demonstrated a deep understanding that instilled confidence for us from the very beginning.
The Challenges: From legacy code to a seamless UX
With a clear roadmap, we were set to kickstart a development journey that would not only solve Fluint's immediate problems but set them up for future success.
But as we stepped up to the starting line, we were faced with a few daunting roadblocks. To dodge or to demolish, that was the question.
Tackling the bug-infested codebase. Inherited from a previous agency, Fluint's app codebase was fraught with bugs and errors - our first obstacle. Our initial task was to debug and stabilize the codebase to provide a firm foundation before we could even start improving upon the platform.
Racing against the clock. We had a strict 90-day window to not just understand the existing product and its shortcomings, but also to propose a roadmap for essential improvements and execute it. This meant we had to rapidly identify critical areas of improvement and swiftly action them.
Navigating client reservations. Complicating matters further was the presence of certain 3rd-party libraries that had become a bottleneck for the product's growth. While these libraries were impeding the product's evolution, our client had reservations about swapping them out, which created an additional challenge for us to navigate.
Similarly to previous projects we’d undertaken (this digital learning app, this privacy management MVP and a relationship management expert’s personal project, to name a few), we were facing a mixture of technical, logistical, and UX/UI challenges.
We knew this demanding task called for in-depth technical expertise, innovation, and a steadfast commitment to the project.
The Solution: Transparency, technical enhancement, and Agile teamwork
Navigating the complexities of software development is like conducting an intricate symphony - every component needs to play in harmony to create the desired output. In our collaboration with Fluint, we orchestrated a solution that was music to their ears. Here's how we fine-tuned their project to hit all the right notes:
Building trust through transparency
At the heart of our work with Fluint was the task of building trust with their understandably skeptical founders, Nate and John. We kicked things off with a comprehensive and thoughtful evaluation of their project, demonstrating our understanding and instilling confidence from the get-go. Trust isn't just about talking the talk, though - it's about walking the walk. We didn't just throw out a number of billable hours; our approach to creating an MVP scope involved estimating based on levels of complexity. This approach reassured Fluint that we were clued into the project's complexity and its inherent unknowns. We weren't just clocking hours; we were laser-focused on achieving their goals and outcomes.
"[Something] I notice a lot of the time when developing MVPs is that clients want to know how many hours it's going to take. And for any software developers that's impossible to say. Estimations are hard because there are so many unknowns and yes - things can go wrong. But we can at least try to compare each scope item and understand which are the ones that are more difficult and which ones are easier,"
“[Other agencies] are keen on expanding the project and increasing the scope. NaNLABS came at it from the opposite angle, which was really encouraging for us. Not many people would say, okay let's curb some of the planning and let's just focus on doing this specific thing really well.”
Diving deep into the legacy codebase
Next, we rolled up our sleeves and got down to business. Our team dove headfirst into Fluint's legacy codebase, combing through thousands of lines of code. We tidied things up, got rid of problematic parts, and reinforced the essential bits. All in an effort to keep the technical debt from spiraling out of control.
Enhancing the codebase and incorporating advanced features
Once we had a cleaned-up codebase, we squashed existing bugs and started adding advanced features. We suggested new third-party libraries, explaining how these tools would give the project more flexibility in the long run. One major switch we made was swapping the library used for the editor - moving from Quill to Froala.
Taking a customer-first approach
We didn't just build code; we built it with the customer in mind. Throughout the MVP development process, we steered Fluint down the path that would be most beneficial for their product - even if that meant suggesting they back away from certain directions they wanted to take. We kept our eyes on the prize - the customer's desired outcome - and then we laid out the tech plans to get us there. By striking a balance between speed and product excellence, we kept the project on track and efficient, prioritizing quality over feature overload.
Promoting Agile collaboration
Our Agile approach and super-responsive team were key to this project. We obliterated the communication barriers Fluint had encountered with their previous agency, ensuring seamless communication and bridging language and time zone differences. Plus, Fluint's co-founders were hands-on throughout the project. This fostered a true Agile team environment, sparking rapid progress and sharp decision-making.
“In development you can never assume any project is going to be at 100% all of the time. But what's different about NaNLABS is they take feedback and get back to 100% as quickly as they can."
“One piece of a drag-and-drop interaction was very tricky but in a stand-up with the product team, we asked how it was going - could we start to get some user feedback? Everyone, including the technical co-founder said it would be weeks of time and wasn't going to work out. Next day I expect to be talking about a new approach and one of the NaNLABS team is demoing it, saying they figured it out with some extra creative work. And now they could actually validate it with users without spending weeks working on it.”
The Results: A successful MVP launch, and beyond…
In just 90 days, Fluint and NaNLABS pivoted to launch a Minimum Viable Product (MVP), validating their strategic shift. The MVP featured a user-friendly UX catering to two user roles, thanks to thoughtful navigation and smooth interfaces designed by NaNLABS.
Significant outcomes off the back of this project included:
Scalable, quality codebase. The product's improvements extended beyond the interface, with a fortified, scalable codebase comprised of reusable, high-quality components.This foundation enabled Fluint to carry out extensive restructuring of the UX, paving the way for future scalability.
User feedback and early monetization. With the MVP launched, Fluint collected valuable user feedback that informed product roadmap decisions. This real-world insight even led to Fluint acquiring its first paying customers, marking a critical milestone for the company.
A flourishing long-term partnership.This wasn't a one-off project for NaNLABS and Fluint. Our relationship has evolved into a fruitful long-term partnership, built on quick problem resolution, transparent communication, and a deep commitment to Fluint's success.
Fluint's review says it all.
"After a poor experience with our previous agency, we came into this project from a very skeptical place with extremely high expectations - and NaNLABS exceeded them in every way."
Post-MVP launch, Fluint has started building their in-house team to provide more in-depth support to users and optimize the app based on user interaction data. Larger projects and feature enhancements continue to be entrusted to NaNLABS.
The partnership is already poised for a second iteration of the product, focusing on further improving the front end and other key areas identified in their collaboration.
Looking for help with your MVP?
Every SaaS startup needs a solid MVP to get off the ground quickly, learn from initial users, and rapidly enhance the product.
Think about employing MVP development services if:
Tech isn't your strong suit, and you need to create your product
You're in the dark about setting up a dependable tech stack
You want to save precious time and resources through automation
Launching fast on a tight budget is your aim
Agile methodologies are new to you, or you need a hand introducing them to your team
Here at NaNLABS, we specialize in custom software solutions for budding startups and small-to-medium enterprises. Our team partners with you to turn your product dreams into a working reality, ensuring your software can scale and perform to meet your success goals. Let's join forces!
Ready to build your own custom software with a team that cares about you and your processes? We’re not code monkeys, we care about you.
More articles to read
Previous blog post
09/07/2023
9 Things You Need to Know Before Building Your First MVP
Read the complete article
Next blog post
08/08/2023
Why The Scoping Stage is Crucial when Creating an MVP
Read the complete article