August 2, 2026
TechCrunch reported this week that Imagi, a K-12 edtech platform founded in 2018 by Dora Palfi and Beatrice Ionascu, raised a $4.5 million seed round from Brighteye Ventures, Day One Capital, and artist Will.i.am. Imagi teaches schoolchildren and their teachers coding, basic computer skills, and AI literacy. Last November it partnered with vibe-coding platform Lovable so teachers can build lessons that give students controlled, safety-screened access to AI-assisted coding: every prompt and response is screened before it reaches a student, the platform is COPPA, FERPA, and GDPR compliant, it retains zero data, and OpenAI donated $1 million in credits so schools can use it for free. Imagi has already worked with more than 700,000 students across 140 countries.
The examples in the TechCrunch piece are the part worth sitting with. A teacher used the tool to build an app that translates curriculum into 15 languages. A student built a full website, booking functionality included, for his own lawn-mowing business. Neither of them is a professional engineer. Neither of them thinks that's a strange thing to have done.
Plenty of businesses are still treating 'can our non-engineers actually build usable software with AI' as an open question -- something to pilot cautiously, maybe next quarter, maybe next year, after legal signs off and IT runs a proof of concept. Meanwhile, that debate simply isn't happening in a K-12 classroom in 140 countries. A twelve-year-old with a lawn-mowing side hustle isn't weighing the merits of AI-assisted development against hiring a contractor. He's just building the thing he needs, because that's what he was taught to do with a laptop and a prompt box.
That's the real story underneath the funding round. Imagi isn't selling a coding elective. It's teaching AI-assisted building as a basic literacy skill, the same category as touch-typing or knowing how to use a spreadsheet a generation ago. Once a skill gets taught at that level, at that scale, the question of whether it's 'real' skill or a toy is already settled. The workforce this generation enters won't debate whether non-engineers can build software. They'll just assume it, because it's how they learned to make things in the first place.
We hear a version of the same objection from prospects constantly: our team isn't technical enough to build their own tools, even with AI in the loop. That objection has always had a shelf life, but Imagi's numbers put a date on it. Somewhere between 700,000 students in classrooms today and those same students walking into their first job in five to ten years, that objection stops being a reasonable caution and starts being a competitive liability. The businesses still asking 'should we try this' when that cohort enters the workforce won't be competing on whether they adopted AI app-building -- they'll be competing for talent that already assumes it's normal and will wonder why your internal tools still take a six-week ticket to change. We've made a version of this argument before when writing about why non-technical teams should build their own internal tools instead of waiting on IT backlogs, and Imagi's raise is exactly the kind of evidence that makes the case sharper, not softer.
This isn't just a hiring-pipeline story either. It's a preview of what 'normal' looks like for internal software. If a school-age kid can spin up a booking system for a lawn-mowing business over a weekend, there is no good reason your sales team should still be waiting on IT to adjust a CRM field, or your support team should be stuck inside a helpdesk tool that doesn't fit how they actually work. The technical bar for building your own software has been dropping for years. Imagi's raise is a signal that the bar is about to drop for an entire generation at once, everywhere, starting in childhood.
Our point of view is simple: if your organization is still treating AI-assisted, non-engineer software building as an unproven experiment, you're not being cautious, you're falling behind a curve that a generation of schoolchildren has already crossed. The right response isn't to wait for a mature market or a definitive case study. It's to run the same low-stakes pilot this quarter that a classroom runs in an afternoon -- give a non-technical team member a real problem and a tool built for exactly this, like our AI app builder, and see what they ship in a week.
Read the pieces you already have internally on buy vs. build vs. ViibeStack or how our customers have replaced parts of their SaaS stack, and you'll notice the pattern: none of it required a computer science degree, and the tools kids like the ones at Imagi are using aren't fundamentally different from the ones your team could be using today. The skill gap that used to justify waiting is closing faster than most companies' internal review timelines. The businesses that treat 2026 as the year they actually tested this, rather than the year they scheduled a meeting about testing it, are the ones that won't be scrambling to catch up when this generation graduates.
Sources