August 5, 2026
TechCrunch reported on August 3, 2026 that June, a new startup founded by Efrat Rapoport, Ohad Hen, Barak Goldstein, and Idan Tsitiat, raised a $20 million pre-seed round led by Marc Benioff's Time Ventures, with backing from Michael Dell, Aaron Levie, and George Kurtz. The founders previously built Bonobo AI, which Salesforce acquired in 2019, so this is not a team guessing at the problem from the outside. According to TechCrunch, June's product scans a company's existing systems to understand its business processes and bottlenecks, then builds AI agent-powered workflows with step-by-step implementation guidance, including tasks like removing duplicate database fields and connecting fragmented data sources.
The framing TechCrunch used is the part worth sitting with: enterprise AI deployment is hindered by legacy systems, fragmented data spread across multiple platforms, and technical debt, and the industry's current answer leans heavily on forward-deployed engineers and consultants -- which itself becomes a bottleneck. That's a striking admission to see backed by the CEO of Salesforce, a company whose entire business model has depended on enterprises being willing to pay armies of consultants to make software work.
Founder Efrat Rapoport told TechCrunch: "AI, paradoxically, increases the demand for professional services. The industry's answer to AI implementation is, 'let's hire more and more people.'" That's about as direct a rebuttal to the "AI will just handle it" narrative as you'll get from someone raising money to build in the space. More AI capability, dropped onto systems that were never designed to talk to each other, doesn't shrink the services layer around it -- it can grow it, because now someone has to reconcile what the AI touches with everything it doesn't yet understand.
Look closely at what June's product actually does, per TechCrunch's description: it scans existing systems, maps processes, identifies bottlenecks, and then handles things like removing duplicate database fields and stitching together fragmented data sources. That's not a criticism -- it's an honest description of what's needed once a company already has that mess. But it's still, fundamentally, a services layer. A very sophisticated one, wrapped in agents instead of headcount, but the job is retrofitting AI onto a stack that was never built to support it in the first place.
That's the tell. The entire category of problem June exists to solve -- duplicate fields across systems, fragmented data sources, legacy workflows nobody fully understands anymore -- only exists because a business bought or built five separate tools over the years and never had one shared data model to begin with. Every duplicate field is a scar from a tool that got bolted on without anyone reconciling it against what already existed. Every fragmented data source is evidence of a decision, made years ago, to solve a problem with new software instead of extending what was already there.
When an internal tool or app is built fresh on one platform, with one data layer, one auth system, and one place everything lives from day one, there's no retrofit problem to hire consultants -- or agents -- to solve, because there was never a second system to reconcile against. That's the whole premise behind ViibeStack's platform: CRM, helpdesk, finance, HR, and internal tools running on a shared data model instead of a collection of point solutions that each brought their own schema, their own logins, and their own export formats. Rapoport's quote about AI implementation just meaning "hire more people" is, read the right way, the clearest evidence for why starting on one platform beats layering AI on top of an accumulated stack of tools that were never meant to be neighbors.
We've made a version of this argument before in comparing what it actually costs to keep replacing your stack piece by piece versus consolidating it, and in walking through how teams have gone from spreadsheets to a real system without dragging the spreadsheet's mess along with them, in our guide to migrating spreadsheets to a ViibeStack app. The pattern is the same: the cheapest and most durable fix to fragmentation is never accumulating it. Companies already deep in a tangle of monday.com boards, a Salesforce instance, a Notion wiki, and a Zendesk queue are exactly the customers June is right to target -- see our own notes on what that untangling looks like for teams considering replacing Salesforce or consolidating off tools like HubSpot outright rather than patching around them.
None of this is a knock on what June is building. Their diagnosis of the problem, as reported by TechCrunch, is accurate, and plenty of enterprises are already too deep into a fragmented legacy stack to start over -- for those companies, an AI-agent layer that scans, reconciles, and guides implementation is a genuinely useful thing to buy. But it's worth naming clearly what kind of bet that is: it's a bet on getting better at cleaning up a mess after it's been made. The alternative bet, the one we'd rather help teams make, is not making the mess in the first place -- building the next internal tool, workflow, or customer-facing app on one platform instead of adding tool number six to a stack that already needed a $20 million startup to untangle it.
Sources