Research & discovery for technology-led companies and the teams that build or back them

Research for hard decisions about products and technology.

I investigate the market, the technology and the way the work actually happens. You get a clear recommendation, the evidence behind it, and a practical scope and requirements your team or vendor can act on.

When this is useful

When a decision needs research, not another meeting.

The work starts when a decision matters, but the problem is still defined differently by everyone in the room.

01

The budget exists. The decision does not.

I turn assumptions, disagreements and constraints scattered across meetings into a clear question, options and decision criteria. If the project moves forward, I translate the decision into implementation requirements.

02

Everyone sees a problem. Nobody agrees what it is.

Interviews and process analysis expose the actual conflict before a team builds a compromise nobody needs.

03

Every vendor sounds convincing.

Claims need to be translated into measurable criteria, tested where possible and compared against the real use case.

04

A new market looks promising. The evidence is fragmented.

I combine desk research with expert or customer interviews to produce a recommendation, including reasons not to proceed.

The work

Three ways to move from uncertainty to action — with research.

Each engagement starts with the business question and ends with a decision, an assessment or working requirements. The methods fit the question, not the other way around.

Core offer1–2 weeks · fixed scope

Decision & Discovery Sprint

For an important initiative with an open question, unclear boundaries or requirements that have not yet been written down.

01

The decision question and the problem behind it

02

Options and the criteria for choosing between them

03

A recommendation and the evidence behind it

04

Solution boundaries and prioritized requirements for the first version

05

Risks, assumptions and unresolved unknowns

06

Clear next steps for your team or vendor

Typical inputs: stakeholder interviews, workflow analysis, market and solution research, technical review and targeted experiments.

Ask about this format ↗
Focused project

Technical & Market Assessment

Independent evaluation of a technology, vendor, partner, investment or emerging market.

  • Technology, architecture and implementation approaches
  • Market, competitors and alternative approaches
  • Technical-claim verification and practical constraints
  • Evaluation criteria and vendor or partner comparison
  • Recommendation, limits and the next useful test
Ask about this format ↗
Ongoing or on demand

Fractional Discovery Lead

Senior research and decision support for a few days a month, or for a complex cross-functional question that does not fit an existing role.

  • Continued stakeholder and customer interviews
  • Requirements kept current
  • Business, vendor and engineering alignment
  • Executive decision support and special cross-functional projects
  • White-label delivery for agencies
Ask about this format ↗

Who usually buys this

01

Technology-led companies and product teams

CEOs, COOs, product and operations leads committing budget to a new digital initiative.

02

Software & automation agencies

Agencies that need a senior discovery partner to interview the client and define the work before scoping and pricing it. White-label is welcome.

03

Investors and strategy teams

Independent technical and market research before a commitment to a company, vendor or emerging theme.

Selected projects

What the work looked like in practice.

Client work is anonymised where required. These summaries show the starting question, the research and what changed. The profile includes work you can read in full.

Venture strategyPayments / fintech

Broadened an investment lens beyond one ecosystem.

Context
Deal sourcing was centered on affiliation with a single blockchain ecosystem.
Work
Mapped payments and cross-border themes, screened 100+ startups and conducted 30+ interviews with founders.
Result
Helped the CEO shift sourcing toward the problem solved and value created, including opportunities beyond crypto.
Technical evaluationConfidential deliverable

Turned a vague competition into measurable criteria.

Context
Several swap-routing solutions on TON had to be compared despite a new architecture and inconsistent claims.
Work
Learned the transaction model, defined speed and cost metrics, designed the benchmark and ran comparative tests.
Result
The resulting report became the evidence used by the jury to inform ecosystem-funding decisions.
Research to launchRegulated financial product

Research that ended in an operating business.

Context
A team wanted to launch a cryptocurrency exchange but had not chosen a jurisdiction, product scope or operating model.
Work
Compared jurisdictions and licensing requirements, shaped the product and business plan, budget, timeline and local leadership search.
Result
A company was established, obtained a cryptocurrency license and launched the business.

How I work

Research built for your specific question.

I choose the depth and methods the decision requires. The result is concise, usable and clear about what is known, inferred and still unproven.

01

Frame the decision

What needs to be decided, who will decide it, by when, and what changes with the answer?

02

Investigate what matters

Technologies, implementation approaches, market, documents, interviews and the smallest useful experiment.

03

Turn the answer into action

A recommendation with alternatives, solution boundaries, requirements, risks and next actions.

Research depth · technical judgment

Experience that connects strategy, the market and the code.

I have advised the CEO of a venture fund, led product and engineering as a CTO, built software and assessed early-stage companies and complex systems. That range lets me test strategy against what is feasible in practice and turn research into something both leaders and delivery teams can use.

  • Venture research: markets, founder interviews, technical and commercial assessment
  • Product leadership: CTO work, early-stage products, requirements and cross-functional delivery
  • Engineering: software development, architecture, documentation and hands-on testing
  • Domains: fintech, payments, AI products and blockchain infrastructure
Experience & publications →

Questions

How the work starts.

How do we start?

We start with a short call to define the decision, the stakes and what is already known. If the question is bounded, I propose a one-to-two-week Decision & Discovery Sprint with a clear outcome and fee. If another format fits better, I will say so.

We already have developers or an agency. Where do you fit?

Before implementation or alongside its earliest stage: clarifying the problem, interviewing stakeholders, comparing options and producing requirements. I can work directly with your delivery team or white-label inside an agency engagement.

Can you help us decide whether we need AI?

Yes. I start with the problem AI is expected to solve and compare it with simpler options. If AI is the right fit, I identify a useful pilot and define how success will be measured. If it is not, I recommend the simpler system.

What if the evidence does not support our preferred answer?

The conclusion will say so. I distinguish observed facts, supported inferences and unresolved unknowns, then name what evidence or experiment would change the decision.

Do you write code?

I have a software-engineering background, can read code and test technical claims, and build my own products. I use that depth to improve discovery and assessment work; I do not take staff-augmentation engineering roles.

Contact

Tell me what you’re trying to decide.

Three sentences are enough, but the full context is welcome: what you are trying to decide, what is unclear, what depends on the answer and your deadline. I reply within one working day.

FormSubmit delivers your message to my email. Google Analytics never receives the message or contact details entered here.