Technology

Dessn Raises $6M to Bring Design Closer to Code

Martin HollowayPublished 2w ago4 min readBased on 2 sources
Reading level
Dessn Raises $6M to Bring Design Closer to Code

Dessn Raises $6M to Bring Design Closer to Code

London-based startup Dessn has secured $6 million in funding for an AI-powered design platform that lets product teams design and build directly in their actual code, rather than switching between separate design and development tools, according to TechCrunch. Founded in 2024 by Gabriella Hachem and Nim Cheema, Dessn positions itself as an alternative to the traditional workflow where designers work in tools like Figma and then hand off their mockups to engineers to rebuild in code.

Closing the Gap Between Design and Code

The core problem Dessn tackles is a familiar friction point: the translation gap between what a designer creates in a mockup and what engineers actually build. Today, designers and developers typically work in separate worlds — designers in design tools, engineers in code editors — and then try to align the results. Dessn flips this: it lets both roles work directly within the actual codebase, on the same project.

The platform uses AI to help bridge the gap between design thinking and technical reality — for instance, understanding that a layout designed for desktop also needs to work on mobile, or that a color choice has performance implications. The company hasn't revealed the technical details of how this works, but the basic idea is to eliminate the back-and-forth that slows down modern product development.

Notably, Dessn deliberately doesn't integrate with Figma or other traditional design tools. The company sees this as necessary: if it simply plugged into Figma, teams would fall back into the old design-to-development handoff pattern, which is exactly what Dessn is trying to escape.

A Shift in How Design Tools Work

Dessn's approach represents a real departure from how design tools have evolved over the past decade. Companies like Figma have focused on building centralized design systems — shared libraries of components and rules that designers and developers reference. Dessn is saying: why not just work in one place from the start.

This aligns with how modern software development itself has changed. In the era of continuous integration and continuous deployment — practices where code changes are tested and shipped constantly — the speed of feedback matters enormously. A tool that cuts down context switching and eliminates handoffs can shave weeks off a project.

Having covered the tools that shaped software development since the early days of version control, I'd note that this pattern keeps repeating: the most successful tools tend to succeed not by making existing workflows slightly better, but by questioning whether the entire workflow is the right one. Dessn is making that kind of bet here.

What the AI Actually Does

While Dessn hasn't detailed its AI, we can infer what it likely handles. In a production-focused environment, the AI probably helps with tasks like generating responsive layouts that work across screen sizes, enforcing design constraints that respect how code actually works, and helping non-technical designers make choices that won't create problems for engineers.

Think of it as a smart translator between design intent (the way something should look and feel) and technical reality (how it actually needs to be built). This is quite different from generative AI features in traditional design tools, which tend to create decorative assets or suggest layouts. Dessn's AI is more about understanding the relationship between design decisions and code.

What This Means for Teams

The $6 million funding round gives Dessn money to grow its team and refine the platform based on what early customers actually need. For a two-year-old company aiming at enterprise product teams, this funding level signals investor confidence that the team can execute and that the market wants what they're building.

The broader angle here is worth considering: Dessn is betting that the future of product development means tighter integration between design and engineering rather than just better handoff tools. If that bet pays off, it would likely mean some teams need to reorganize — not just switching tools, but rethinking how designers and developers collaborate day-to-day.

The real test will come in the next couple of years. Dessn will need to show that teams actually ship faster, that code quality improves, and that both designers and developers are happier. Those are the metrics that matter in engineering-driven organizations far more than traditional design satisfaction scores. How quickly Dessn grows its customer base and how many of those customers stick around will tell us whether production-first design is actually the future or simply an interesting experiment.