Hi, I'm Sandeep

Helping scaling startups turn growth into repeatable execution

I embed with scaling startups and build the systems that make growth hold — partner programs, ops structures, GTM motions. Hands-on, until it runs.

Explore working together See my work
About

From strategy to execution —
where scaling usually breaks

Most companies don't stall because of bad ideas. They stall when growth outpaces the systems holding it together.

Over 8+ years across Web3, climate tech, and global standards work — from building Berlin's blockchain ecosystem to aligning three standards bodies during COVID — I've seen the same pattern: growth compounds when execution is owned and systems are clear. That's what I build. Embedded with your team, hands-on until it holds.

Based in Berlin. Working globally.
8+
Years of experience
1.5K+
Community members built
100+
Events organized
3
Continents impacted

Selected collaborations

Logos represent a mix of leadership roles, ecosystem contributions, and partnership work.

Affinidi
BerChain
Linux Foundation Public Health
W3C
Decentralized Identity Foundation
Affinidi
BerChain
Linux Foundation Public Health
W3C
Decentralized Identity Foundation
Fit Check

Let's see if we're a match

I thrive when

  • ✓
    You have product–market fit and are entering a scaling phase.
  • ✓
    Growth is happening, but execution isn't compounding.
  • ✓
    Partnerships, initiatives, or teams feel disconnected.
  • ✓
    You want structure without slowing down.

I'm not the right fit when

  • ✗ You're still validating the core problem.
  • ✗ You want strategy decks without ownership.
  • ✗ You need heavy hand-holding or long approval cycles.

What you get

A systems thinker who owns execution — bringing clarity, structure, and momentum when scaling gets messy.

Open to Selected Roles

Open to full-time roles in operations, ecosystem, partnerships, or strategy & execution at growth-stage companies. If you're a founder or hiring manager, reach out.

Services

How I help scaling teams execute

I typically help in three ways:

1. Execution & Operations

When growth accelerates, priorities blur. I build the operating structures that fix it — roadmaps, ownership models, decision frameworks that teams actually use.

Typical outcomes:

  • → Clear priorities and execution rhythm
  • → Fewer stalled initiatives
  • → Alignment across founders, teams, and stakeholders

Available for: project-based work, fractional leadership, or embedded roles.

2. Partnerships & Ecosystem Building

At scale, partnerships stop being opportunistic and start needing structure. I design and execute partnership and ecosystem frameworks that support real business goals — not vanity logos.

Typical outcomes:

  • → Partnerships that open new markets
  • → Ecosystems that support GTM and adoption
  • → Reduced coordination overhead

Available for: consulting engagements or ownership of partnership initiatives.

3. Complex Projects, Ambiguity & Design Thinking

Some initiatives don't fit neatly into any existing team — especially at scale. I step in, create clarity fast, and move teams from discussion to decisions using design thinking.

Typical outcomes:

  • → Ambiguity turned into actionable plans
  • → Faster decision-making and team alignment
  • → Momentum on initiatives that were previously stuck

Available for: project ownership, design thinking facilitation, or short-term embedded support.

If you're unsure which bucket your situation fits into, that's usually a good sign we should talk.

Explore working together
Portfolio

Selected work

Community Building Web3 Long-term Sustainability Ecosystem Operations

Berlin Blockchain Guide

→ BerChain

1,500+
Members
100+
Events
6
Years

Context

Berlin's blockchain scene in 2018 was fragmented: many actors, little coordination, and no shared infrastructure. Momentum existed, but it wasn't compounding.

The challenge

This wasn't a community problem — it was an execution and systems problem. Events happened, conversations started, but nothing connected or sustained itself.

My role

I helped turn an informal network into a durable ecosystem — designing governance and operating structures that could scale, building partnership frameworks across startups, corporates, and public institutions, and using design thinking to align diverse stakeholders around what members actually needed.

What changed

BerChain grew from an informal network into Berlin's primary blockchain ecosystem — 1,500+ members, 100+ events over 6 years, and €100K+ in annual revenue sustained by 20+ corporate sponsors. With €300K+ in budget managed through structured governance, it became the reference network for blockchain and Web3 innovation across the DACH region. Ad-hoc momentum became compounding infrastructure.

Why this matters

Community without infrastructure is just noise. BerChain stayed relevant for 6 years because it was built on governance and repeatable systems — not enthusiasm. What looked like a community problem was always a systems problem. That distinction is what made it durable.

Read the original guide Visit BerChain
Partnerships Standards Bodies Crisis Response Systems-Level Impact

COVID-19 Credentials Initiative

Linux Foundation

1,000+
Labs
3
Standards Bodies

Context

At the height of the pandemic, borders were closed and vaccine certificates varied wildly across countries. Reopening travel wasn't a technology problem alone — it was a coordination problem across governments, standards bodies, labs, airlines, and technology providers.

The challenge

More than 20 credential formats existed, with no interoperability. Stakeholders had conflicting incentives, timelines, and constraints. Decisions had to be made quickly, with global consequences.

My role

I led partnership efforts and represented Affinidi across key standards bodies, including Linux Foundation Public Health, W3C, and the Decentralized Identity Foundation — aligning diverse stakeholders around shared outcomes, using design thinking to keep discussions grounded in real‑world use cases, and translating ecosystem influence into concrete execution paths.

What changed

20+ competing credential formats were aligned into a single interoperability framework, ratified across Linux Foundation Public Health, W3C, and the Decentralized Identity Foundation. The resulting whitepaper became a reference standard for verifiable health credentials across a network of 1,000+ labs and healthcare providers. A fragmented standards landscape became a unified technical and policy baseline — shipped under pandemic timeline pressure.

Why this matters

Aligning 3 major standards bodies around one framework — under real deadline pressure — required the same skills as any multi-stakeholder ecosystem build: clear value framing, incentive alignment, and relentless focus on a shared outcome. The credential format problem wasn't technical. It was a partnership and coordination problem. That's what made it solvable.

Read the whitepaper Affinidi LFPH
FAQ

Common questions

Everything you need to know before reaching out.

What does an ecosystem and partnership architect do?
An ecosystem architect designs and operates the network of relationships — partners, communities, integrations, distribution channels — that make a technology or product spread at scale. Rather than closing individual deals, the work focuses on building repeatable systems: partner programs, enablement frameworks, community infrastructure, and GTM motions that compound over time. The role sits at the intersection of strategy and operations — not just designing the ecosystem, but building the engine that runs it.
What is GTM ecosystem strategy, and why do startups need it?
A GTM ecosystem strategy uses partners, communities, and third-party networks as primary distribution channels — instead of relying solely on direct sales. For startups past product-market fit, it's often the difference between hitting a growth ceiling and scaling efficiently. At Affinidi, an ecosystem-first approach generated over €2M in partnership pipeline and contributed to 200% revenue growth, with 30% of inbound product trials coming directly from community. The key is building the ecosystem before you need it, not after direct sales has stalled.
What's the difference between ecosystem strategy and business development?
Business development focuses on closing specific partnerships or deals — one at a time. Ecosystem strategy is about building the system that makes partnerships self-reinforcing. BD is a transaction; ecosystem strategy is infrastructure. In practice, this means designing tiered partner programs, creating enablement resources that let partners sell independently, building communities that generate referrals, and aligning partner incentives with product growth. The goal is a network where each new partner makes the next one easier to recruit.
What types of companies do you work with?
Companies that have cleared product-market fit and are hitting a scaling problem — typically 20-200 people, Series A to C, with a technical product that needs a broader adoption network. Industries I've worked in: SaaS (identity, developer tools), climate tech, Web3, and sustainability. I'm based in Berlin but have operated across 60+ countries. The common thread isn't industry — it's the moment: when founder-led everything stops working and you need someone to build the partnership and operational layer.
What results can I expect?
Recent results include: €2M+ partnership pipeline at Affinidi contributing to 200% revenue growth; a 1,000+ developer community built from zero with 40% activation improvement; 15+ partnerships and €150K+ in sponsorships for Blockchain4Good Summit with 1,500+ attendees; and a 65% increase in qualified referrals through partner enablement programs. Engagements run 3-6 months with clear milestones and defined success criteria agreed upfront.
How does a typical engagement work?
Most engagements start with a 2-4 week diagnostic: identifying where growth is stalling, what partnership or operational gaps are the root cause, and what the 90-day priority should be. From there, engagements are either project-based (a specific build like a partner program or GTM playbook) or fractional (embedded 2-3 days per week as part of the leadership team). Typical length: 3-6 months. The goal is always to build something that runs without ongoing dependence.
Contact

Let's build
something together

If you're navigating a scaling phase and want to explore working together, I'd love to hear what you're working on. Let's figure out if there's a fit.

hello@sandeepbajjuri.com
Berlin, Germany — Working globally

✦ Open to speaking engagements and guest lectures