top of page
Ben Tytonovich
2 min read

AI should change how we allocate the R&D budget, including the profile of the people we choose to hire.


I would increasingly allocate that budget toward engineers who combine strong technical judgment with product thinking. People who can understand a customer problem, make architectural decisions and carry a feature through to something a customer can actually use.


These people have always been valuable. As implementation becomes faster, I believe their relative importance grows. A team can produce much more code while still spending most of its time waiting for someone to define the problem, resolve a dependency or decide whether the result is good enough.


Adding more people to that process can also add more coordination.


A few implications for how I would organize an early-stage R&D team:


Give engineers broader ownership. An engineer should understand why a feature exists and take responsibility for its implementation, testing and readiness for review. The work should arrive at a reviewer with the important edge cases already considered.


This still requires independent review and specialist input where appropriate. But there should be a clear owner who carries the feature across these stages, instead of a series of handoffs where each person is responsible for only one small part.


Reconsider the default sprint length. For many well-scoped features, I would aim for a two-day execution cycle. The team should be able to build, review and learn without waiting for the end of a two- or three-week container.


Architecture, migrations and work with substantial dependencies will often require longer cycles. The point is to choose the cycle based on the work. A familiar planning ritual should not become the minimum amount of time it takes to deliver something useful.


Give product a clear monthly coordination role. Shorter cycles create their own problem: a team of capable people can move very quickly in slightly different directions.


Product leaders need to own meaningful monthly milestones and make sure these individual efforts fit together. Which customer outcome are we advancing? What must be ready together? Where does one team’s work depend on another’s? What should we stop building?


That shared direction becomes more important as engineers gain more autonomy.


The budget implication is straightforward. I would be willing to pay more for this combination of product judgment, technical depth and ownership, even if that means hiring fewer people.


The question I would ask before adding another R&D position is how much more independent, customer-relevant progress that hire will make possible.

Ben Tytonovich
2 min read

Founders are familiar with sales cycles. They plan around them, model them in their forecasts, and track them in CRM dashboards. But there’s a second timeline running in parallel that often goes unnoticed: the adoption cycle.


Sales cycles tell you how long it takes to close a deal.

Adoption cycles tell you how often customers are even ready to consider change.

It’s not the same thing.


Not every customer is in market.

Some categories see regular movement—annual tooling refreshes, budget-driven evaluations. Others shift more slowly—one big decision every few years, often tied to leadership changes, compliance shifts, or major infrastructure upgrades.

When a team just rolled out a new system 18 months ago, the bar for switching is higher—regardless of how good your pitch is.


This is especially relevant in brownfield markets, where customers already have a solution in place. It’s not just about proving you’re better; it’s about catching them at the right moment to even consider moving.


Timing matters as much as fit.

In greenfield markets, the challenge is education. In brownfield ones, it’s timing. Even with clear pain, there’s often a window during which adoption is actually possible—driven by budget cycles, roadmap shifts, or external pressure.


Ignoring that timing can lead to a long tail of conversations that never convert—not because the product isn’t relevant, but because the buyer isn’t ready.


A simple shift in approach

Adoption engineering means asking a few slightly different questions upfront:

  • How often do customers in this category adopt or switch?

  • What tends to trigger that adoption?

  • Where are the natural windows for consideration?

  • Are we in a greenfield or a brownfield—and what’s the real cost of entry?

It’s not a replacement for sales thinking. It’s a complement to it. And for teams building into new or replacement categories, it can be the difference between slowly grinding forward… and aligning with momentum that’s already there.

There’s a very important distinction with regards to how we research markets between an exploratory market and a buying one.


An exploratory market = most of the interest among potential customers is focused on researching the subject matter while they’re still in the early stages of understanding how deep the pain actually is within their organization. More often than not, it’s also not just about understanding the pain depth but also what an actual solution architecture might look like and which one would best fit their organization and existing workflows.


A buying market = a more mature landscape where the pain/solution equation is much clearer. Customers are coming to conversations with vendors with ready-made budgets, priorities and at least a rough idea on how their ideal solution may look like.


Obviously, there are many shades of grey between the two - the dynamic here isn't binary.


Founders may struggle, in the beginning, to differentiate between these possible states of the market, since many on the customer side don’t identify themselves clearly as explorers vs. buyers. It’s critical to understand at which phase of the maturity of the buy-side we are currently, as this might indicate whether we’re too early or too late to the ‘party’.

bottom of page