MarcusRibeiro

For funded teams with a launch, go-to-market or partnership decision

Find the problems in the plan before you pay for them.

I pressure test launch, go-to-market and partnership plans before the budget is committed. My background is in crypto, fintech and emerging technology.

Request a plan review Read what I’m writing
$1.3Mannual growth budget managed across 30+ portfolio companies
~$400Kcut from the projected annual plan after reviewing roughly six months of agency and KOL activity
200 → 2,500+helped move NEARCon registrations in approximately six weeks, without paid acquisition

Before you approve anything

Four questions the plan needs to answer.

01

Who needs to care, and what problem are they already trying to solve?

02

What do they need to do for the launch, campaign or partnership to count as a win?

03

Will the positioning, channels and product journey get them to that result?

04

Who owns each step, and what tells you to keep going, change course or stop?

Launch & Adoption Decision Review

Give me five days before you approve the plan.

You give me the target audience, positioning, launch or growth plan, product journey, partner commitments, vendor proposals and available data. I test whether they add up to the result you need.

Fixed fee
$3,500
Turnaround
Five working days
Scope
One live initiative

I’m paid for the decision, not the size of the campaign. If I think you should cancel the spend, I’ll say it.

See exactly what you get

Background

Seven years in crypto. Five years at NEAR Protocol. Hundreds of founders.

I worked with founders from the first conversation through funding, onboarding, launch and post-launch. I also managed portfolio work across agencies, KOLs, partnerships, regional teams and a $1.3M annual growth budget.

Before crypto, I worked in customer relationships and financial-product sales at Bank of America and Merrill Edge. The products change. The basic questions don’t: who needs this, why should they care and can the plan get them there?

How I work with teams ↗

What I’m writing about

I had a computer in 1996. I’ve spent the last seven years working in crypto. Some of this feels very familiar.

I write about what survived the dot-com crash, what crypto teams keep getting wrong and the launches, budgets and founder problems I saw up close at NEAR.