
What it really takes to be a non-technical founder in legal tech

Francesco de Chirico
October 12, 2026
7
min read
Being a non-technical founder is still treated as a weakness in a lot of pitch rooms. You can't write the code, so how will you build the product? It's a fair question. But it misses what non-technical founders often bring instead: a deep, lived understanding of the problem.
Elena Tsalanidis is a good example. She's a lawyer turned co-founder of Deeligence, an AI-powered due diligence platform that helps lawyers review contracts faster. On this episode of Now or Never, she spoke with Fra and Megha Sevekari about leaving private practice, building a tech team without a technical background, what AI has changed in legal tech, and why design matters so much when your customers are time-poor corporate lawyers.
From lawyer to legal tech founder
Elena always knew she wanted to be a lawyer. She worked in litigation and as an associate to a Supreme Court judge. But once she landed at a law firm, it didn't feel like the right fit. There was an entrepreneurial side of her that a junior role didn't use.
So she moved to London and pivoted into a legal tech startup, working in operations and helping another founder build and scale a product for lawyers. Back home, she figured she'd done it for someone else, and there were plenty of thorny, repetitive problems in legal work left to solve. Deeligence started there: find a painful problem lawyers have, then build a really good solution for it.
Her advice for anyone weighing a similar move is refreshingly simple. Starting feels much harder in the abstract than it is once you begin. If you've got a good idea and you're that way inclined, explore it.
The non-technical founder "mark against your name"
Elena doesn't sugarcoat how investors can see it. In her words, "being a non-technical founder, and we've encountered it when we went through our fundraise, is sometimes seen by investors as being a mark against your name."
She gets why. Software is expensive to build and great engineers are hard to find. But her co-founding team are subject matter experts. They've done legal due diligence themselves and felt how painful it is. That changes the conversation with engineers.
As she puts it, "sure, I might not know how to build it, but I know what I am looking for and I am not necessarily constrained by how we get there." The founders know what the workflow needs to look and feel like. They aren't attached to a particular technical answer, which leaves room for the team to push back and come up with something better.
Building a tech team as a non-technical founder
A lot of the conversation was about the practical side of this. Three habits stood out.
Learn fast, then bring in experts
Elena admits to a bit of founder naivety: "how hard could it be to learn this thing? Answer, it's really hard". Her approach is to learn what you can from books, podcasts and your network, and be honest about where that stops. For some things you'll cobble together something passable. For others, like designing a legal tech product people love using, you go to specialists.
Make sure the best idea wins
Elena talks about deliberately building a psychologically safe team, where "the best idea wins every time. It doesn't matter if it comes from the most junior team member." They interview for it, telling candidates to bring their expertise. For a non-technical founder, that openness is part of the job. You set the destination. The team helps you find the route.
Prioritise with your tech lead, not around them
Elena calls prioritisation the founder dilemma she hates most, and also most of her job. Once a month, the team revisits its list of what's next. They rank by importance, then their tech lead gives each item a t-shirt size (small to extra large) for effort. Customer feedback keeps feeding in, and small requests sometimes jump to the top. The list itself stays fairly stable. The order changes often.
AI in legal tech and the expectations problem
Elena describes the shift AI has brought to law as seismic. Lawyers have a reputation for being risk averse, but she now hears partners and senior buyers at major firms asking whether there's AI for a given task, because they want to stay competitive. Some of that tips into overhype. Her view is to understand the problem deeply first, then pick the solution, which might be AI or might just be great low-code automation.
There's a funny footnote here. At a recent strategy day, the team pulled up their original business plan, which said Deeligence wasn't going to be an AI company because the technology wasn't ready. They're now an AI company. Their point of difference, she says, is that AI was layered on top of a workflow tool that was already solving a problem, rather than being a shiny feature at risk of becoming shelf-ware.
The bigger challenge is expectations. Lawyers are perfectionists who live in polished consumer apps all day. Elena's customers are busy corporate lawyers running deals, so "our platform has to be nearly perfect to fit into the way they work or they'll never use it again." That's a high bar for a growing startup still adding features. Deeligence handles it with very high-touch support: an in-app chat widget, and founders literally on the other end of a mobile number. It doesn't scale, she admits, but the feedback goes straight to her co-founder who runs product, and repeated questions move up the roadmap.
Can a non-technical founder just vibe code it now?
Fra raised a question many founders are asking: if shipping software gets close to free, does the ideal founding team change? Elena mostly agrees. Deeligence went from a hand-drawn sketch, to a Figma design, to a low-code prototype, testing with lawyers at every step. With vibe coding, she thinks they could have shortcut a lot of that.
But she adds an industry caveat. Selling to major law firms means "you can't put something in their hands that's half baked or kind of like MVP. They'll never use it again." Law firms also have security requirements, much like banks, that many low-code and no-code tools don't meet. Vibe coding is a great way to validate an idea. It isn't always a way to ship to your real customer.
That matches what we see. AI makes building fast and cheap, which raises the bar on everything around the build: the quality of the experience, the trust it creates, and how well it fits the way people actually work. For more on what to get right first, see our guide to UX design for startups.
Why design matters for a legal tech startup
For Elena, design isn't decoration. If you're asking people to change how they work, the product has to feel seamless. Deeligence's goal has always been that a lawyer could open the platform and not need training.
Deeligence is an UntilNow client (at the time of recording, we'd been working together for almost a year), so we'll keep this part brief. What Elena values about an external design partner is breadth. When they designed a commenting feature together, they didn't just look at other legal tech tools. They looked at how the best products across many industries handle it. For a startup without the need for a full-time designer, that flex up and flex down model made more sense than an early hire. We've written about that trade-off in why tech startups should rethink in-house hiring and how founders should buy design.
She also credits early design with early demand. Being able to show lawyers something that looked easy to use, and ask if they'd use it, created interest before launch. If you're at that stage, our UX/UI design work is built for exactly that moment.
What non-technical founders can take from Elena's story
- Your domain expertise is the asset. Know the problem cold and stay open on the solution.
- Learn what you can, then go to experts for the rest, without ego.
- Build a team where the best idea wins, wherever it comes from.
- In demanding industries, polish and security aren't optional, even early.
- Stay close to customers while it's still possible. It's your fastest feedback loop.
The full conversation also covers Elena's views on investing in women founders and her team's "stumble of the week" ritual. Listen to the full episode with Elena Tsalanidis on Now or Never.

