1. Background & Context
Why a veteran CS leader decided to break the cycle of "Building vs. Buying" to satisfy a new investor mandate.
The Expert: Sylvain Guerry
Sylvain Guerry is a veteran of the Customer Success world. With 20 years in the field and over a decade in leadership roles, he has built CS teams for startups, scale-ups, and massive public companies like SAP.
Currently, he is the VP of Customer Success at CO2 AI, a Series A startup (~50 employees) that raised $12M two years ago. His mandate: build a "Value Consultant" team capable of serving high-stakes Enterprise clients.
The "CS Tech" Trap
Having seen the evolution of Customer Success operations across multiple companies, Sylvain had identified a recurring failure pattern in how organizations handle data and tooling:
- The "Build" Trap: Companies try to build their own internal CS tools. According to Sylvain, "They get it wrong 100% of the time." The build is easy, even if very basic, but the maintenance is impossible, eventually turning the tool into a sunk cost.
- The "Buy" Trap: Companies purchase top-tier, expensive SaaS solutions. These tools are rarely "off-the-shelf" ready, take months to implement, and often fail to capture the nuance of complex Enterprise relationships and transformation strategies.
"Even with the most expensive tools, we ended up with 30% of activity in the system and 70% of the reality living in spreadsheets, PowerPoint decks, emails, and local files."
— Sylvain Guerry, VP of Customer Success at CO2 AI
The Status Quo at CO2 AI: "A Messy Notion Page"
When Sylvain joined CO2 AI, the company was in a typical early-stage operational void.
- The Stack: No dedicated CS tool. Just a Notion spreadsheet that was "dirty," with columns marked "outdated" that no one trusted.
- The Reality: With a small roster of very large clients, the team managed by "brute force": spending 30 minutes per week manually reviewing every client.
The Trigger: The "AI First" Investor Mandate
Unlike many startups that look for tools because they are currently drowning, Sylvain’s trigger was foresight. He presented a roadmap to scale CO2 AI to 250 Enterprise clients by 2030. He knew that if they waited until chaos struck to implement technology, it would be too late.
Furthermore, the economic reality of SaaS has changed. Investors are no longer satisfied with the traditional ratio of managing $3M - $5M ARR per CSM.
"To raise funds today, you have to be 'AI First': not just in your product, but in your operations. Investors expect us to break the old ceilings. They want to know how one person can manage huge portfolios without dropping the ball. I knew I couldn't achieve those new efficiency ratios with traditional and rigid toolsExcel and PowerPoint.."
2. Building Experience
How a non-technical leader turned static PowerPoint slides into functional software by leveraging visual prompting.
The "Non-Technical" Builder
Sylvain is a VP of Customer Success, not an engineer. His last technical experience was creating an Access database in college 22 years ago. Yet, he built CO2 AI’s entire Customer Success platform himself in just two weeks.
- The Learning Curve: Sylvain describes the experience as surprisingly easy because he approached it with logic, not code. "I’ve been prompting ChatGPT for a few years, so I understand the logic. I just explained my business needs, and Vybe translated that into software."
- The "Senior Junior" Partner: Sylvain found that Vybe acted like a "Junior developer with Senior instincts." It knew standard patterns without being explicitly told.
- Example: "I asked it to create a template, but forgot to ask for a way to edit it later. Vybe realized the intention and automatically built a settings page to manage all templates. It anticipated the need."
Visual Building: From Slide Deck to Software
One of the biggest accelerators for CO2 AI was Vybe’s ability to interpret visual data. Sylvain had years of methodology trapped in static PowerPoint slides.
- The Workflow: Instead of writing long requirement documents, Sylvain simply uploaded screenshots of his existing PowerPoint frameworks.
- The Result: "I explained the logic, uploaded the screenshot, and boom: it recreated the entire interface instantly. It understood the visual hierarchy and turned a static slide into a functional app."
The "Aha" Moment: Calendar Integration
The feature that immediately won over his team wasn't a complex dashboard, it was the calendar automation.
- The Pain: Project management in CS is a heavy lift: scheduling meetings, writing agendas, taking minutes, tracking action items, and ensuring follow-up.
- The Solution: Sylvain integrated his calendar with Vybe. Now, the system transcribes meetings, automatically extracts action items, and drafts follow-up emails and Slack messages.
- The Reaction: "When I showed this to the team, they immediately saw the time savings. Even the Head of Sales ops asked for a meeting to build her own version because HubSpot couldn't do it."
3. Impact & Results
Moving from "managing chaos" to "enforcing harmony," and why custom building is actually more efficient than buying bloated software.
Immediate Efficiency: Killing the "Copy-Paste" Cycle
Although CO2 AI is just entering the Go-Live phase, the projected impact on the "Value Consultant" team is immediate and tangible. The workflow for client meetings (Weekly, Monthly, and Quarterly Business Reviews) was previously a manual grind of Excel trackers and email follow-ups.
- Before: Consultants managed action items "à la mano" (by hand), copying and pasting between spreadsheets and emails.
- With Vybe: The system automates the administrative layer. It tracks the agenda, captures the minutes, and centralizes action items automatically.
- The Gain: It’s not just time saved; it’s pertinence. The data is accurate and available, removing the friction of "who promised what?"
Leadership Control: The "Friday Morning" Ritual
For Sylvain, the most significant shift is Visibility. In previous roles, managing large teams meant chasing information across disparate drives and spreadsheets. With Vybe, he has established a "Command Center."
- The New Routine: "I can sit down for 30 minutes on Friday morning, review every single client, and prepare my challenge questions for the team. Before, gathering that intelligence took 8 hours of chasing updates."
- Enforcing Harmony: The app prevents the team from "reinventing the wheel." In typical CS teams, everyone creates their own shadow Excel sheets. Now, the process is centralized.
The Cost/Benefit of Building
Sylvain estimates he spends 5 to 7 hours per week building inside Vybe. The process has forced CO2 AI to audit their existing SaaS subscriptions, realizing that legacy tools were costly and only matched ~40% of their actual business needs.
"We are starting to question our expensive licenses. We pay for bloated packages where we only use a fraction of the features. With Vybe, we aim for a 90% match because we build exactly what we need, bridging the gap between a generic tool and our specific reality."
4. Reflection & Looking Ahead
How CO2 AI plans to replace Notion for their Solutions Architects and why Sylvain calls Vybe "The Lovable for Internal Apps."
What’s Next: From CS to Solutions Architecture
Sylvain’s vision is to replicate the Value Consulting team's successsuccess of the Value ConsultingCustomer Success team across other technical departments. The immediate next step is migrating the Solutions Architect and Implementation teams.
- The Problem: Currently, Resource Planning and Project Management live in Notion. The Director of that team has already hit the "ceiling" of what Notion can do: it’s static, and manual, and we face many limitationsThe Vybe Solution: Sylvain plans to build a dynamic Resource Planning tool using the Google Calendar integration to automate time-tracking and billing.
- The Goal: "Remove the limitations of static tools so consultants can focus on delivery, not reporting."
Defining Vybe: "The Lovable of Internal Apps"
When asked how he describes Vybe to other leaders, Sylvain offers a precise market analogy. He compares it to Lovable (a popular AI web builder), but with a critical distinction in purpose.
"If you want to build a public website, use Lovable. But if you want to build a robust internal application, use Vybe. It is the 'Lovable' of internal tools."
Why bet on Vybe now?
For a Series A executive, choosing an early-stage tool is a risk. Sylvain explains why he took the bet:
"It’s not just the product; it’s the velocity. Looking at your investors and your execution, it’s clear you aren’t just building a tool: you are building the infrastructure for how companies will operate in the future. Integration is the cornerstone, and Vybe is moving fast enough to be the backbone of our operations."
