I made AI video answers verifiable at VeedoAI, as sole designer on a four-person founding team.
The 30-second read
The full story
What is VeedoAI
VeedoAI is an AI video understanding platform for legal, education, and enterprise teams. As the sole designer on a four-person founding team, I designed four product surfaces and the component library behind them, zero to 7,000+ users in four months.
In a $23.8B enterprise video market, design was the only wedge a four-person team had
Every incumbent solved one slice: Twelve Labs had search without collaboration, AnyClip monetization without summarization, Gemini tagging without multimodal interaction. We could not out-model any of them.

Sources: market size from MarketsandMarkets, Enterprise Video Market report (2024). Competitor positioning based on public product pages, Feb 2025.
That changed what my job was. I wasn't designing screens for an AI product. I was designing the company's differentiation — which meant every decision below is also a decision about where a team with no resources chooses to compete.
The brief was "make video searchable." That was the wrong problem
27 interviews — 9 educators, 7 legal teams, 11 creators — showed the brief was aimed one layer too shallow. Legal and training participants said the same thing in different words: one wrong summary and they would stop using the tool.
Users weren’t failing to find things. They were failing to trust what they found.
So I changed what we were building: not a search tool with good AI, but a comprehension tool that is honest about being probabilistic. Search accuracy wasn’t the product problem. Verifiability was.

The synthesis that moved the brief. Read the right column: every stated need is about acting on what the video contains, not locating it. That asymmetry told me the problem was one layer deeper than search.

The reframe cost the team features it had already planned: verification affordances went into the MVP, collaboration surfaces moved to a later phase.
Nobody could say what the problem cost or what success looked like, so I built both numbers
Across 27 interviews one figure kept recurring: 3–5 hours per video lost to search and distribution. Nobody had multiplied it out. I did. It gave the founders a number to price against and told me which segment to design for first.

A summary that saves you four hours and is wrong once costs more than the four hours it saved.
There was no metric for “the AI understood this,” so I proposed three

I wasn’t designing to make people trust the AI more. I was designing to make trust proportional to stakes.
Four surfaces, one loop: ask, answer, verify
Ask a question against footage. Get an answer. Verify it against the second it came from.
Ask → Answer → Verify
One interaction connecting search, AI summaries, source moments, and recommendations across four surfaces.

Comprehension starts before you open anything
Every project carries its summary at the list level — the first place "extract, don't watch" shows up, and the reason this isn't a file browser.

The summary and its source never separate
Recaps generate from the timeline, not a detached transcript — so verification stays one click away at the point where a wrong claim would get baked into a shared clip.

Where attention actually went
The evidence layer under Surface 04. Without it, Refine would be the AI having opinions — the thing the rest of the product argues against.

Advice carries its evidence too
Every suggestion links back to the behaviour that produced it — the verification rule applied to recommendations. One principle, four surfaces.
The live prototype
Start at the summary. Click any source chip to jump to the moment it came from. That round trip is the product, everything else on this page is an argument for it.
Open full screen in Figma ↗The wireframes that led to the architecture call
Same screen, same chrome — one structural element changed. The captions record what each version taught, not what it looks like.
Before

After

↓ These wireframes became Decision 01 below — where the same choice is shown in final production UI, and the cost of making it is named.
Three calls, the options I rejected, and what each one cost
Progressive AI disclosure — a timing spec, not a principle
AI products fail in one of two directions: they hide what the model can do, or they dump every capability on a first-time user. I rewrote progressive disclosure as what the interface must have proven by which second, and held all four surfaces to it.
Why it mattered beyond the screens: it gave a four-person team a checkable rule for arguments that would otherwise have been taste. "Does this earn its place before the ten-second mark?" settled scope disputes faster than any mockup.
Every stage had a failure. This is the one I removed from each

How I validated it — and what I couldn't
I ran moderated sessions on UserTesting and Lookback with all three segments, iterating between rounds. The fixes that worked all did the same thing: they showed where an answer came from.
The change that mattered most came late: participants who skipped first-run setup were the ones who abandoned after their first AI error. Onboarding wasn't polish — it was where trust was established or lost, and I rebuilt it to teach verification rather than tour features.

You don't have to take my word for any of this
Three things I can point at rather than assert. All publicly checkable, none of them mine to edit.
Built as a system, so one designer could keep pace with four people shipping
The four surfaces share one component library — variants, tokens, handoff-ready. That's the only reason a solo designer kept pace with a founding team's roadmap: a new surface cost composition, not redesign.
The system outlived my engagement. The team kept building on the library after I left, without another designer on staff — the strongest evidence I have that it was built as infrastructure rather than as my own working file.
Three calls I made, and the pushback I took for them
On a four-person team there is no design org to escalate to. I made these calls, gave the founders the tradeoff, and owned what followed.
What didn't move, what did, and what changed beyond the product
What didn’t move: verification rate, the metric I argued mattered most, was never instrumented. Users trusted visible sources in testing. I can’t show it changed retention.
What moved: four months from first interview to launch. After I left, the founders reported 7,000+ sign-ups across five industries, also cited on VeedoAI’s public ToolMage listing.
Beyond the product: “out-design, not out-model” became how the founders described the company. The design strategy became the business strategy.

What I'd do differently
Before you ask in the interview
Sole product designer on a four-person founding team, for four months. Director title, but an IC role with no reports: I owned research, product design, brand and the design system.
The 7,000+ is company reported and listed publicly on ToolMage. I didn’t have analytics access, so I don’t claim it as mine. The 70% came from moderated sessions (n = 27), not an A/B test, and I say so on the page.
Showing the AI’s limits instead of hiding them. The CEO wanted to show off every capability, and Growth wanted a shorter onboarding. I held my ground, and the cost was a product that demos smaller than it is.
I assumed the AI would sometimes be wrong. Every answer links to the exact moment it came from, so users can check it in one click, and legal teams get more checking than creators do.
People don’t distrust AI. They distrust AI they can’t check. If your users act on what the model tells them, show them where every answer came from.
This page is the argument. Here’s what I’d walk you through live.

I had the pleasure of working with Olha during our time together at VeedoAI, where she served as Director of Product and Brand Design. From day one, Olha brought a rare combination of creative vision, design excellence, and strategic thinking that had a transformative impact on our product and brand.
Ready To Start?
Book a free 30-minute discovery call
Tell me what you're building.
I'll tell you how I can help and exactly what it will cost.
Currently taking new clients · Typical start: 1–2 weeks from contract
