Strategic product and technology consultancy

What got the product this far is rarely what takes it further.

Four paths. For startups: take a proof of concept to its first external customer, or unblock a product that already sells but has stopped scaling. For established companies: organise a portfolio that grew without product management, or set up a lab for new products. In all of them: scope with explicit criteria, evidence instead of conviction, and deliverables that stay with your team when the contract ends.

Where you come in

In consultancy I lead: I decide scope, architecture and cadence with you, and I'm accountable for delivery. If what you need is a sparring partner to decide for yourself, the format is executive mentoring.

For startups
Path A · 6-month engagement

From proof of concept to first customer

For startups with funding and a working proof of concept that now need something an external customer will buy and use without anyone on the inside running it behind the scenes.

PoC: doneOne user: yourselves. Controlled environment.
MVP: targetFirst external customer, end-to-end flow without help.
ProductMulti-tenant, billing, SLA, GDPR, sales material.
  • Scope before code. Every cut is recorded: when someone questions it in month six, the reason is written down.
  • Architecture that can handle the second customer. Multi-tenancy, isolation and cost per run are decided now.
  • A team that leaves stronger than it came in. The stated goal is for the team to sustain the product without me.
Path B · diagnosis and delivery

Unblocking the product that already sells

For startups with a product in the market and revenue coming in, where every new customer costs more than it should, because what was built proved the idea but wasn't designed to sustain it.

  • The bottleneck is rarely where it hurts. Diagnosis first: architecture, cost per run, cadence and team. Only then the plan, costed.
  • Cost per run is a product metric, not an infrastructure one. In an AI product it sets price, margin and, ultimately, whether the business adds up.
  • Technical debt with a deadline and a price. What to rebuild now, what to defer knowingly, and what will never be worth rebuilding.

The first cycle starts with a deep dive into what exists, already inside the engagement that will deliver it. If what you want is an independent assessment before hiring anyone, that's a different service: technical due diligence.

For established companies
Path C · diagnosis and leadership over 7 to 9 months

Product management for a portfolio that grew without it

For companies with products in the market for years, where knowledge has concentrated in a few people, deadlines slip and every customer runs a different version, and the whole team depends on people who no longer have time.

DiagnosisMonth 1. The portfolio in data, not opinion.
PilotMonths 2 to 4. One product, one owner, rituals running.
ExpansionMonths 5 to 7. The other product families.
  • A portfolio backed by data. Products, customers, versions, revenue and churn cross-checked before any decision.
  • Decision rights before rituals. Who owns each product, who looks after the shared core and what goes up to the committee.
  • AI to get knowledge out of a few people's heads. What only three people know becomes documentation the team uses.

It starts with a four-week diagnosis at a fixed price. If the leadership phase is commissioned afterwards, it counts as the first month.

Path D · 90-day cycle

An experimentation lab to design new products

For companies where good ideas are born in operations and die there, because they compete with the day-to-day delivery schedule, and lose. The lab is the system that separates what deserves investment from what deserves to be dropped early, from the charter to the first experiment with a decision made.

  • A funnel, not a suggestion box. Every idea comes in the same way, with entry, progression and discard criteria.
  • Evidence, not prototypes. A stated hypothesis, a short deadline, a binary result.
  • A portfolio that defends itself with numbers. Cost, hypothesis and indicator from day one.

Twenty-one years at CESAR, one of Brazil's leading innovation centres, where the experimentation lab is the way of working, not a novelty. It doesn't require hiring a new team: it requires steering a small group, with method, cadence and someone senior sitting beside the people who decide.

What stays with you

Transferable deliverables, not meeting minutes.

Product decisions

Competitive analysis, scope with recorded cut criteria, costed technical roadmap.

Engineering

Target architecture documented and implemented, CI pipeline, coding and review standards.

Team and operations

In-house technical leadership developed, cadence and decision rituals working, operations runbook.

How we measure whether it's working

Two separate columns from kick-off. If the product doesn't sell, the cause can be technical or commercial, and we'll only know which if both are measured.

On my side

Milestones delivered on time, flow working without manual intervention, test coverage and stability, cost per run under the ceiling, the team's technical autonomy.

On your side

Customers in pilot and conversion to contract, willingness to pay validated in a real proposal, recurring revenue, acquisition and support costs.

An experiment that dies in three weeks with a clear decision is a success. One that survives six months without metrics is exactly the cost we're tackling.

What I need from you

It's not a request for comfort: it's what separates leadership that delivers from leadership that is merely accountable for a result it doesn't control. These conditions go into the contract.

Team in place before kick-off

Roles filled and dedicated. A shared calendar doesn't count as a filled role.

A product owner on your side

Someone with the authority to decide scope and speak for the customer.

Access to whoever signs off the investment

A monthly meeting with whoever signs. A decision stuck for two weeks costs a whole cycle.

Technical leadership without line management

I decide stack, architecture and scope. Formal management of the team stays with you.

Start with an alignment conversation

Sixty minutes to choose the format, agree the scope of the first cycle and validate the team set-up. No generic proposal before that.

Message on WhatsAppcontato@nagelveras.com

I reply within 8 working hours.