The Problem

Before you commit

You have something worth pursuing — but you're not sure what's actually feasible, which direction to take, or how to explain it to the people who need to fund or build it. That uncertainty is expensive. Most of the costliest mistakes happen before anyone writes a line of code.

You have something valuable but no clear path forward

Maybe it's research that could become a product. Maybe it's a product idea that could become a company. Maybe it's a technical direction that could transform what you're already doing. But right now it's stuck — because nobody has done the work of figuring out whether it's feasible, how to structure it, and what to do next.

The question isn't clear yet

The hardest challenges don't arrive as well-defined briefs. They arrive as a hunch, a contradiction, or a vague sense that something isn't right. Committing resources before the real question is understood is where the most expensive mistakes are made — and most advisors won't engage until you've already figured out what to ask.

Who I Work With

Who this
is for

Founders with domain expertise

You know your market and your problem. What you need is someone who can evaluate the technical dimension — what's buildable, what isn't — and make that direction legible to the people who need to fund or build it.

Organisations exploring a new direction

You have an ambitious bet — a new product, a new capability, an R&D investment — but no clear map for it. You need someone to assess feasibility and structure the work before your team commits to building.

Creative & research-driven industries

You work in a domain where technical rigour and human experience both matter — music, media, health, or the space where they converge. You need someone who won't flatten one to serve the other.

I also work with research teams bringing academic work into applied practice, and with any organisation that needs an independent perspective on a complex technical decision.

How I Work

Start here

Clarity brief

You have an idea, a direction, or a research question you can't answer internally. In 1–2 weeks, I'll turn that ambiguity into a clear, written assessment you can act on.

What I do

Go deep on your specific situation

I start by listening — not just to what you're asking, but to what's underneath it. Often the question you came in with isn't the one that actually needs answering. I investigate your particular constraints, talk to the people involved, examine what's been tried, and form a judgment about what's technically feasible, what's worth pursuing, and what isn't — drawing on experience shipping products through exactly this kind of ambiguity.

What you get

A written report with a clear direction

A document you can hand to your engineers, your investors, or your co-founder. It covers what's buildable, what isn't, which path I'd recommend and why, and what the next concrete steps look like. Not a survey of options — a grounded recommendation from someone who's done this work before, with the reasoning laid out so you can challenge it.

Timeline 1–2 weeks, depending on complexity
Deliverable Written assessment with findings, feasibility analysis, and recommended direction
Discuss your project

When the work continues

Some projects end with the brief — you have your answer and you move forward. Others open up a next phase. Two ways engagements typically grow:

Translate

From findings to framework

Turn the brief's findings into something your team can build from and your stakeholders can act on — a structured white paper, a system architecture, a strategy document that holds up under scrutiny.

White paper · Architecture doc · Strategy brief

Guide

Ongoing direction

Fractional advisory as your team builds. I stay involved at a sustainable pace — reviewing decisions, maintaining alignment between strategy and execution, translating across technical and non-technical stakeholders.

Decision review · Stakeholder alignment · Advisory

Selected Work

Research in practice

01

Proprietary FPGA DAC

Algorithm Research  ·  Technical Architecture  ·  Specialist Direction

Schiit Audio needed a proprietary FPGA DAC algorithm but had no internal expertise in the domain. I was the sole knowledge bridge — from the initial research through algorithm design, technical architecture, and specialist direction of the implementation. The result: FPGA-quality digital-to-analog conversion at a price point the market had never seen below $2,000, now adopted across their product line.

Shipped · Adopted across the Schiit Audio product line

View work
02

Brand–Artist Matching

Research  ·  Product Strategy  ·  Framework Design

Turned a vague instinct — "which artist fits this brand?" — into a structured, explainable matching framework. Covers quantitative and qualitative dimensions, conflicting trade-offs, and a staged pipeline built for brand-side decision-making.

Working prototype · In investment stage

View work
03

AI for Music Creation

Independent Research  ·  Market Analysis  ·  Strategic Vision

An independent opportunity analysis identifying a structural gap in music creation tools before the market recognised it. The tension it named remains largely unresolved — most tools built since have addressed the technical layer, not the semantic and collaborative one.

Cornell Tech Runway shortlisted · 2021

View work

Background

The foundation behind the work

Education
PhD, Media Arts & Technology — UC Santa Barbara.
MS, Computer Science — George Washington University.
BS, Computer Science — University of Belgrade.
Research
Peer-reviewed publications in top-tier venues, including the International Journal of Human-Computer Studies. Work cited across human-computer interaction, music information retrieval, and data visualization.
Applied work
Over a decade at the intersection of research, product strategy, and system design — including the work shown above.

Get in Touch

Ivana Benci

Ivana Benci

Research & Technical
Strategy Consulting

Let's talk

If you have a problem that's hard to frame, a technical direction that needs mapping, or a research question that hasn't found its answer yet — I'd like to hear about it.