Project Nexus: 15% Win Rate in 2026

When you let your customers into the product development process, I mean *really* let them in, you build something that actually sticks in the market. This isn’t about sending a survey when you’re 90% done. It’s about building a feedback loop right into your design and iteration cycles, which is the only way to genuinely improve product-market fit. A well-run co-creation campaign like this directly produces business results, like the higher adoption and lower churn we saw right out of the gate.

Campaign Teardown: “Project Nexus” – Co-Creating a New Productivity Suite

Back in mid-2025, we kicked off “Project Nexus,” our big attempt at co-creating a new productivity suite from the ground up with our users. The specific goal was to build something so tuned to real-world workflows that it would blow past our previous product adoption benchmarks on day one. To do that, we had to get way past the usual surveys and actually embed a select group of users into our product team, giving them direct access to our process and people.

Strategy: Deep Immersion and Iterative Development

Our strategy was all about getting a small group of users completely immersed in the development process. We went looking for power users in small to medium-sized businesses (SMBs), the ones who were already vocal on forums about the shortcomings of existing tools. Our theory was that by working with these highly motivated people, we’d uncover specific pain points our own team was too close to see, for example, how a common export process required three more clicks than it should. The project wasn’t a single event but a whole progression of work, starting with initial brainstorming and moving through feature prioritization, hands-on beta testing, and the final round of refinement.

We broke the whole thing down into three phases over nine months. “Discovery” was the first phase, where we ran detailed interviews and workshops. Phase two, “Design & Prototype,” got participants messing with early wireframes and mock-ups. In the third phase, “Refinement & Beta,” we gave them access to working alpha and beta builds. This step-by-step process created a constant flow of feedback and made sure we were integrating user input at every stage, not just at the end.

Creative Approach: Exclusive Access and Direct Dialogue

Creatively, our whole angle was based on making this an exclusive thing with a direct line to us. We pitched participation as a genuine opportunity to build the next generation of productivity software alongside our lead developers. We weren’t asking them for a favor. We set up a private, secure online portal where they could drop ideas, vote on feature polls, and log bugs, and we ran regular video calls to make it feel like a real, connected team.

The core message was simple: “Your ideas, our execution.” To prove we were serious, we showed them examples from past co-creation projects (without naming names, of course) where user input directly led to a specific feature being built. This built up a lot of trust. The look and feel for Project Nexus itself was kept professional and clean, suggesting a serious piece of tech without being stuffy or trying too hard to be “fun.”

Targeting and Recruitment: Identifying the True Innovators

We didn’t just spray and pray with recruitment. Our focus was on users who already had a track record of giving a damn: people who’d submitted detailed feature requests or were active in our support forums. We also cut a deal with three online communities for SMB owners to tap into their networks and find people who really needed better tools. This focus was everything. We needed users who could think analytically and clearly explain what they needed, not just anyone with an opinion.

Getting them on board was a two-step process. First, a pre-qualified list of 2,500 users got an email explaining the project and a link to an application form. That form was a filter, screening for their job role, what competitor products they used, and asking for a short essay on their biggest productivity headache. Out of 750 people who applied, we hand-picked 150 to be our core group, making sure we had a good mix of industries and company sizes from the SMB world.

Campaign Metrics and Performance Analysis

Project Nexus ran for nine months, from March to November 2025. Here’s how the numbers broke down:

Overall Campaign Performance

• Total Budget: $185,000 (this didn’t include our internal team’s salaries). It covered things like recruitment costs, platform licenses, and some gifts for the participants.
• Duration: 9 months
• Total Participants: 150 active co-creators
• Engagement Rate: 82% of participants stuck with us through all three phases.

We defined “engagement” as someone actively submitting ideas, showing up to workshops, or filing bug reports. To be counted as “active,” a participant had to engage at least once per month.

Recruitment Phase (Month 1)

The first month was all about getting the right people in the door. We kept advertising tight, using only direct email and a few sponsored posts in those partner communities.

• Impressions (Community Posts): 120,000
• Click-Through Rate (CTR) (Email): 18.5%
• Applications Received: 750
• Cost Per Applicant (CPA): $12.33
• Selected Participants: 150

That $12.33 CPA might look high for a simple lead gen campaign, but these weren’t leads. We were recruiting deeply engaged partners, and for that, the cost was a bargain. These people became our first evangelists.

Co-Creation Phase (Months 2-8)

During the main development period, we kept a close eye on the volume and quality of the feedback we were getting.

• Total Feature Ideas Submitted: 1,120
• Ideas Incorporated into Product Roadmap: 285 (25.4%)
• Bug Reports (Alpha/Beta): 890 unique reports
• Critical Bugs Identified: 45 (this saved us a huge post-launch headache)
• Average Participant Feedback Hours: 8 hours/month

The fact that over a quarter of their ideas made it onto the roadmap really showed us this was working. A lot of these suggestions fixed small but maddening workflow problems that our internal team had completely missed, which is the whole point of a user-centric process.

Product Launch & Post-Launch (Month 9 onwards)

The real test, of course, was how the final product performed when we launched it.

• Initial User Adoption Rate (First 3 Months): 12% higher than our benchmarks from previous product launches.
• Customer Satisfaction Score (CSAT) (First 6 Months): 8.7/10 (our previous launches usually average around 7.9).
• Churn Rate (First 6 Months): 15% lower than what we’d normally see for a new product.

There’s a straight line you can draw from the intense co-creation work to this stronger market reception. That 12% jump in adoption happened because we launched a product that a key part of our audience already loved, starting with the 150 co-creators who were our first and loudest advocates.

What Worked: Specific Wins

• Structured Feedback Loops: Breaking the project into distinct phases with clear goals for each was a huge win. Participants knew exactly how their feedback on, say, a wireframe in phase two would influence the beta build in phase three.
• Dedicated Communication Channels: The private portal and regular video calls made them feel like insiders with real access to the people making decisions, which dramatically cut down on frustration and improved the detail in their feedback.
• Incentivization Strategy: The main motivation was shaping the product, but offering perks like free premium subscriptions and public shout-outs (with their permission) definitely helped keep everyone showing up.
• Focus on Problem Solving: We learned early on to stop asking “What features do you want?” and start asking “What’s the biggest problem you’re facing with X?” That simple change in framing got us much more useful, foundational insights.

One of our biggest wins came from a participant in the “Design & Prototype” phase. She spotted a massive flaw in how we were handling file sharing, sent us a detailed write-up with screenshots of the problem, and even proposed a different workflow. Her insight forced us to completely rethink that module, probably saving us months of patching and support tickets after launch.

What Didn’t Work: Challenges and Learnings

• Initial Overwhelm: In the beginning, we just dumped a bunch of conceptual stuff on participants and some of them felt totally lost. We had to learn to break down complex requests into smaller, more manageable tasks to keep them from checking out.
• Managing Expectations: We couldn’t build every great idea. We learned we had to be very transparent about how we prioritized features, even when it meant telling someone their brilliant idea wasn’t going to make the cut.
• Time Commitment: Even with our screening, a few participants had to drop out because their day jobs got crazy. It just showed that we needed to be even more explicit about the time commitment upfront.

We also completely underestimated the amount of internal team time this would take. Managing the community, running workshops, and actually processing all the feedback was a full-time job. Looking back, we should have budgeted at least 20% more of our own product managers’ time just for feedback integration and community management.

Optimization Steps Taken

We made a few key changes while the project was running:

1. Simplified Task Structure: We started breaking down big feedback requests (like “review this whole module”) into tiny micro-tasks that people could knock out in 15 minutes.
2. Bi-Weekly “Why Not” Sessions: We set up a recurring video call where our product lead would walk through popular ideas we *weren’t* pursuing and explain the reasoning. This transparency was huge for managing expectations.
3. Gamification Elements: A simple points system for participation and quality ideas, with monthly shout-outs for top contributors, helped nudge the quieter folks to speak up more.
4. Dedicated Feedback Integrator: We eventually assigned one PM to do nothing but collect, analyze, and champion the participant feedback within the dev team. This ensured good ideas didn’t fall through the cracks.

These tweaks, especially the “Why Not” sessions, made a noticeable difference in participant morale and cut down our attrition rate in the final months. People felt their time was respected because they understood the logic, even if their pet feature was shelved.

When you do co-creation right, with real commitment, your users stop being passive buyers and start acting like partners. The results from Project Nexus are clear: investing that time and money upfront with users gets you a better product, a stronger launch, and people who stick around longer. This whole approach fits right into how modern teams are using Martech Integration: AI Solutions for 2026 Tech Stacks to get closer to their customers. But it’s also a good warning to watch out for the AI Marketing Blind Spots: 2026 Context Crisis, because you need to make sure your tech is helping you listen, not just automate replies. Getting this right is how you build a direct case for Marketing ROI: 5 Steps to Prove Campaign Value in 2026, because you’re shipping something you already know the market wants.