Skip to main content
Account

Partnerships

Build the developer journey your product needs.

I work hands-on with your product to show engineers what it can do, find where they get stuck and help them be successful from dev to prod.

Partnership
$15,000 a quarter

Watch me try a new tool live

One partnership, built around your users

We agree a quarterly plan for the work your product needs. Adoption reviews are part of that plan, alongside practical content and support for your users.

Send the partnership brief to your team

Partnership

$15,000 a quarter

Three months at $15,000. Discounted pricing starts at six months: $24,000 for six months, billed $12,000 a quarter, or $40,000 for a 12-month contract, billed $10,000 a quarter.

Work with me across Awareness, Adoption, and Support. Each quarter has a focused plan built around what your users and your team need.

  • An agreed delivery plan with named outputs, dates and review rounds
  • Monthly 60-minute working sessions with written recaps
  • Questions and feedback in Slack Connect, with response times agreed in the scope
  • A quarterly read-out and one-page summary of the work, findings, measured changes and next priorities

The plan sets how much work we do in each area. We agree the scope before you commit.

Ask about a partnership

An example quarter

A review and a practical build around one agreed developer workflow. Your statement of work fixes the deliverables, dates and review rounds.

  • An adoption review of one agreed developer workflow, with evidence and ranked fixes
  • One live session or recorded build on that workflow, with a runnable example repository
  • Three monthly 60-minute working sessions with written recaps
  • A retest of the reviewed workflow and a quarterly read-out after your team makes changes

Awareness, Adoption, and Support

We choose the work that helps your engineers next, from discovering the product to succeeding with it in production.

  • Awareness

    Get engineers interested

    Show engineers what your product can do through real problems and honest technical work.

    • Practical builds and live sessions
    • Walkthroughs, runnable examples and reusable clips
  • Adoption

    Help engineers get to production

    Work through the experience from a first try to production and find what gets in the way.

    • Hands-on reviews of agreed developer workflows
    • Reproducible findings, ranked fixes and scoped retests
  • Support

    Help users succeed over time

    Bring in experienced engineering help for the education and answers your users need next.

    • Docs, guides, runnable examples and community Q&A
    • Office hours, talks, conference workshops and customer education

Agree what success looks like

Before we start, we agree what you want engineers to be able to do, the starting point and how we'll assess the work.

We choose useful measures and agree who provides the data. At the read-out, you get the findings, what changed and recommended next steps.

  • Awareness: relevant reach, engaged viewing, tagged referrals and use of published examples where measurable. Organic performance and paid amplification are reported separately.
  • Adoption: reproducible obstacles and ranked fixes. If a retest is included, we check the agreed workflow again after your team makes changes.
  • Support: questions addressed, use of learning materials, participation and recurring problems, using the evidence available for the agreed work.

Activation and retention need product data from your team. We report observed changes and the limits of the evidence. An expert review does not replace research with your users, and results are not guaranteed.

Teams I've worked with

  • ControlPlane
  • Datum Cloud
  • Fermyon
  • Guidepad
  • Heroku
  • Microsoft Azure
  • ngrok
  • Spectro Cloud
  • Teleport
  • WunderGraph
  • Zitadel
As a builder, watching someone use your product in real time is one of the most useful things you can do.
Solomon Hykes, Co-Founder of Docker & Dagger

What partners say

  • On advisory work: positioning and demos

    His deep expertise in the cloud native landscape has helped us refine our product positioning, create compelling demo videos, and confidently navigate the market.
    Reggie Wilkerson Co-Founder & CEO at Guidepad
  • On David's public walkthrough of WunderGraph on Rawkode Live

    It was great to see him explore WunderGraph for the first time, especially to see the excitement when we were combining APIs, first with GraphQL and then with TypeScript.
    Jens Neuse CEO & Co-Founder of WunderGraph
  • On Advent of Spin, built for Fermyon

    We've seen notable results in developers joining our community and using our services.
    Mikkel Mørk Hegnhøj Head of DevRel at Fermyon

Teams I work best with

  • You build developer tools: infrastructure tools, Kubernetes and cloud native projects, cloud platforms or AI infrastructure.
  • An engineer can install or sign up for your product and try it, including open-source projects installed from GitHub or Helm.
  • Any size of company, from a first open-source release to a public company.
  • You have a clear priority for your users and someone who can provide access, check technical accuracy and help act on the findings.

Bespoke projects

A specific piece of work, with a clear scope and a price agreed before we start.

Bespoke project

Quoted to scope

For an event, a particular piece of technical work or a project that needs its own scope.

  • Event interviews, technical hosting, live builds, panels and workshops
  • Commissioned docs, technical content or training
  • A specific community or education project

We agree preparation, production, access, travel, editing, publication channels and reuse rights where relevant.

Discuss a project

Community challenges

Give engineers a reason to build, experiment and share what they learn.

Community challenge series

From $15,000

A hands-on challenge series built around your product, like Advent of Spin for Fermyon, that gets engineers building and sharing what they make.

Ask about a challenge series

Simple terms

  • Agreed before we start We agree the priorities, deliverables, dates and review rounds in writing. Bespoke projects and community challenges are scoped separately.
  • Partnership renewal Start with three months at $15,000. Discounted pricing requires a commitment of six months or longer. Nothing renews automatically.
  • You keep the work You own the reports and the read-outs. Example repositories are licensed Apache 2.0, so you can use, change and ship them.

Independent public work

Your team helps set the scope and checks technical accuracy. What I publish about the product reflects my experience of using it.

  • We agree the scope. We agree the audience and the work before starting. For public content, I choose a real use case and show what happens when I build it.
  • My conclusions stay independent. You can correct facts before publication. My conclusions stay in, including limitations and problems I find.
  • Paid work is labelled. Public work you pay for is clearly labelled. Payment doesn't guarantee viewers, leads or a recommendation.

Questions

Something else? Email david@rawkode.academy

Where should we start?

Start with the developer workflow you want to improve. We agree the work across Awareness, Adoption, and Support for one partnership. Bespoke projects and community challenges are scoped separately. If you only want to fund free education, see Support Our Work.

Does the partnership cover all three areas?

Awareness, Adoption, and Support describe the work we can do together. Each quarter has agreed priorities and outputs, based on what your users and team need most. We review that plan together as the work progresses.

What does Support cover?

Docs, runnable examples, community participation, technical Q&A, public speaking, conference workshops, customer education and office hours. We choose the work your users need and agree its scope and frequency.

Can we commission event content or a specific project?

Yes. Bespoke projects can include technical hosting, interviews, live builds, workshops or a defined piece of content. We agree preparation, production, travel, publication channels and reuse rights before quoting.

How much of our engineers' time does it take?

I need access to the product, someone who knows your users and someone to check technical accuracy. We agree preparation and review time with the scope. Partnership working sessions are monthly and last 60 minutes.

How do you account for different levels of experience?

I bring an experienced engineer's perspective. We define the intended users and what they should need to know, then compare the findings with your user feedback and support questions. An expert review complements evidence from real users.

Who on our side should own it?

Choose someone who can set priorities and get the right people involved. That's often marketing or DevRel for awareness, product or developer experience for adoption, and community, customer success or DevRel for support.

Do open-source maintainers have to pay to come on Rawkode Live?

Editorial guest sessions with open-source maintainers remain free. Partnerships pay for agreed engineering, content and community work around your product.

Not Ready Yet?

Support free learning now

Want to back practical developer education without planning product work together? Support Our Work gives your company clear recognition while the Academy's editorial conclusions stay independent.

Explore Support Our Work

What are you building?

Tell me about your product, who uses it and what you want to help them do. I read every enquiry and reply with a recommendation for how we could work together.

Loading enquiry form...

You can email me directly instead.

Partnership $15,000 a quarter

Ask about a partnership