u/Top_Pomelo7996

I’m doing early customer discovery for a developer infrastructure product and am looking to speak with founders, engineers or investors at API/SDK companies.

I’m particularly interested in companies that have dealt with v1 → v2 migrations, major SDK releases, endpoint deprecations, authentication changes, or shutting down legacy versions.

For some background, I do research at Harvard, Stanford, and Brown, and my cofounder is a Columbia CS major.

The goal is to validate the problem, understand how painful these migrations actually are for providers, and talk to people who have experienced this firsthand.

I’m doing early customer discovery for a developer infrastructure product and am looking to speak with founders, engineers or investors at API/SDK companies.

I’m particularly interested in companies that have dealt with v1 → v2 migrations, major SDK releases, endpoint deprecations, authentication changes, or shutting down legacy versions.

For some background, I do research at Harvard, Stanford, and Brown, and my cofounder is a Columbia CS major.

The goal is to validate the problem, understand how painful these migrations actually are for providers, and talk to people who have experienced this firsthand.

I’m doing early customer discovery for a developer infrastructure product and am looking to speak with founders, engineers or investors at API/SDK companies.

I’m particularly interested in companies that have dealt with v1 → v2 migrations, major SDK releases, endpoint deprecations, authentication changes, or shutting down legacy versions.

For some background, I do research at Harvard, Stanford, and Brown, and my cofounder is a Columbia CS major.

The goal is to validate the problem, understand how painful these migrations actually are for providers, and talk to people who have experienced this firsthand.

I’m doing early customer discovery for a developer infrastructure product and am looking to speak with founders, engineers or investors at API/SDK companies.

I’m particularly interested in companies that have dealt with v1 → v2 migrations, major SDK releases, endpoint deprecations, authentication changes, or shutting down legacy versions.

For some background, I do research at Harvard, Stanford, and Brown, and my cofounder is a Columbia CS major.

The goal is to validate the problem, understand how painful these migrations actually are for providers, and talk to people who have experienced this firsthand.

I’m doing early customer discovery for a developer infrastructure product and am looking to speak with founders, engineers or investors at API/SDK companies.

I’m particularly interested in companies that have dealt with v1 → v2 migrations, major SDK releases, endpoint deprecations, authentication changes, or shutting down legacy versions.

For some background, I do research at Harvard, Stanford, and Brown, and my cofounder is a Columbia CS major.

The goal is to validate the problem, understand how painful these migrations actually are for providers, and talk to people who have experienced this firsthand.

I’m doing early customer discovery for a developer infrastructure product and am looking to speak with founders, engineers or investors at API/SDK companies.

I’m particularly interested in companies that have dealt with v1 → v2 migrations, major SDK releases, endpoint deprecations, authentication changes, or shutting down legacy versions.

For some background, I do research at Harvard, Stanford, and Brown, and my cofounder is a Columbia CS major.

The goal is to validate the problem, understand how painful these migrations actually are for providers, and talk to people who have experienced this firsthand.

I’m doing early customer discovery for a developer infrastructure product and am looking to speak with founders, engineers or investors at API/SDK companies.

I’m particularly interested in companies that have dealt with v1 → v2 migrations, major SDK releases, endpoint deprecations, authentication changes, or shutting down legacy versions.

For some background, I do research at Harvard, Stanford, and Brown, and my cofounder is a Columbia CS major.

The goal is to validate the problem, understand how painful these migrations actually are for providers, and talk to people who have experienced this firsthand.

I’m talking with API and SDK companies about a problem I’m curious about:

You ship a new version, document the breaking changes, maybe write a migration guide or codemod, and then have to wait for customers to actually migrate.

Some upgrade immediately. Others stay on the old version for months, open support tickets, or only migrate when the old version is about to be shut down.

We’re building a tool where the entire process could eventually become something close to one click for the API company.

If you work at a company that maintains a public API or SDK, I’d love to know:

• How hard is it to get customers off deprecated versions?
• Does your engineering/support team spend meaningful time helping customers migrate?
• Have you ever delayed a breaking change because migrating customers would be too painful?
• If you could make a migration across your customer base essentially one click, would that actually matter to you?

Especially interested in hearing from smaller API-first companies that have gone through a v1 → v2, major SDK release, endpoint deprecation, auth change, or similar migration.

Happy to chat privately too.

I’m talking with API and SDK companies about a problem I’m curious about:

You ship a new version, document the breaking changes, maybe write a migration guide or codemod, and then have to wait for customers to actually migrate.

Some upgrade immediately. Others stay on the old version for months, open support tickets, or only migrate when the old version is about to be shut down.

We’re building a tool where the entire process could eventually become something close to one click for the API company.

If you work at a company that maintains a public API or SDK, I’d love to know:

• How hard is it to get customers off deprecated versions?
• Does your engineering/support team spend meaningful time helping customers migrate?
• Have you ever delayed a breaking change because migrating customers would be too painful?
• If you could make a migration across your customer base essentially one click, would that actually matter to you?

Especially interested in hearing from smaller API-first companies that have gone through a v1 → v2, major SDK release, endpoint deprecation, auth change, or similar migration.

Happy to chat privately too.

I’m talking with API and SDK companies about a problem I’m curious about:

You ship a new version, document the breaking changes, maybe write a migration guide or codemod, and then have to wait for customers to actually migrate.

Some upgrade immediately. Others stay on the old version for months, open support tickets, or only migrate when the old version is about to be shut down.

We’re building a tool where the entire process could eventually become something close to one click for the API company.

If you work at a company that maintains a public API or SDK, I’d love to know:

• How hard is it to get customers off deprecated versions?
• Does your engineering/support team spend meaningful time helping customers migrate?
• Have you ever delayed a breaking change because migrating customers would be too painful?
• If you could make a migration across your customer base essentially one click, would that actually matter to you?

Especially interested in hearing from smaller API-first companies that have gone through a v1 → v2, major SDK release, endpoint deprecation, auth change, or similar migration.

Happy to chat privately too.

I’m talking with API and SDK companies about a problem I’m curious about:

You ship a new version, document the breaking changes, maybe write a migration guide or codemod, and then have to wait for customers to actually migrate.

Some upgrade immediately. Others stay on the old version for months, open support tickets, or only migrate when the old version is about to be shut down.

We’re building a tool where the entire process could eventually become something close to one click for the API company.

If you work at a company that maintains a public API or SDK, I’d love to know:

• How hard is it to get customers off deprecated versions?
• Does your engineering/support team spend meaningful time helping customers migrate?
• Have you ever delayed a breaking change because migrating customers would be too painful?
• If you could make a migration across your customer base essentially one click, would that actually matter to you?

Especially interested in hearing from smaller API-first companies that have gone through a v1 → v2, major SDK release, endpoint deprecation, auth change, or similar migration.

Happy to chat privately too.