I help developer-first startups get real adoption

Most early-stage products don’t fail because of bad engineering.

They fail because:

  • Developers don’t understand the product
  • Onboarding is confusing
  • Documentation is weak
  • Positioning is unclear

I work with small teams (<20 people) to fix that.

What I do

I operate at the intersection of DevRel, product, and engineering.

My focus is simple:

turn ‘we built something’ into ‘developers actually use it’

Core areas:

  • Developer onboarding & activation
  • Documentation & technical writing
  • Developer experience (DX)
  • Product feedback loops
  • Technical positioning & messaging

How I work

I advise part-time with a small number of startups.

  • 10–20 hours per week
  • Async-first (minimal meetings)
  • Direct collaboration with founders

Best fit:

  • Developer tools, APIs, infrastructure, or technical products
  • Strong engineering, weak adoption
  • Early-stage teams (pre-seed to Series A)

Pricing

  • Monthly Retainer
  • Starter Engagement
  • Hourly

Ongoing support for early-stage teams that need consistent progress.

Best for:

  • Teams with an existing product
  • Ongoing developer adoption challenges
  • Founders who want a long-term partner

Includes:

  • Developer onboarding improvements
  • Documentation and technical writing
  • DevRel and developer GTM support
  • Product feedback and iteration loops

Most clients work with me on this model.

A short, focused engagement to identify and fix key bottlenecks.

Best for:

  • Early-stage products
  • Pre-launch or low traction
  • Founders who want quick, actionable insights

Includes:

  • Developer onboarding audit
  • Documentation review and fixes
  • Clear recommendations for improvement

Used only for clearly scoped or short-term work.

Best for:

  • Small, well-defined tasks
  • Overflow work
  • One-off technical support

Limited availability. Most work is done via retainers.

I typically work with 1–3 companies at a time to maintain focus and impact.

Background

I started in Python, automation, and web scraping, then expanded into APIs, data systems, and infrastructure.

Over time, I moved closer to:

  • product thinking
  • developer experience
  • go-to-market for technical products

I’ve worked on:

  • MVPs and internal tools
  • data pipelines and analytics
  • developer-facing systems

Today, I focus on early-stage adoption problems, not just building features.

Tech Stack (when needed)

I stay hands-on when useful, but only where it drives outcomes.

  • Python (core)
  • FastAPI, Flask, Node.js
  • Vue / Nuxt, Hugo
  • PostgreSQL, SQLite, BigQuery
  • Cloudflare, Firebase, VPS/NGINX

Philosophy

Keep things simple.

Most startups don’t need:

  • complex systems
  • perfect architecture

They need:

  • clarity
  • usability
  • feedback loops

I focus on shipping fast, learning quickly, and improving what matters.

Work with me

If you’re building a developer-first product and struggling with adoption, I can help.

Reach out via LinkedIn