FILED FROM DUBLIN — The Bulletin's reading list and directory entries have, for the last three issues, been concentrated on the named winners of the autonomy-layer category. The framing is useful but incomplete. The real commercial story of the next eighteen months will be a long tail of working platforms — Buildship, Pipedream, Tray, Make, the broader workflow-and-integration-automation cohort — that are quietly absorbing the field's adjacent commercial value.

This piece is the working field guide.

The category, in shape

The Bulletin's working term for this category is "Web4-adjacent." The platforms in the category are not autonomy-layer-native. They are workflow-automation, integration-substrate, or low-code platforms that have been extended with agentic primitives over the last twelve to eighteen months. The structural pattern is consistent across the cohort: existing user base, existing integration substrate, agentic primitives added as first-class capabilities, commercial growth that is steady rather than exponential.

The trade-press framing has tended to dismiss this cohort as legacy. The Bulletin's editorial position is that the framing is wrong. The platforms in the cohort have, taken together, a larger user base and a more diverse customer footprint than the named autonomy-layer winners; they are quietly absorbing the long-tail commercial demand for autonomy-layer capability that the autonomy-layer-native products are not positioned to serve.

Buildship

Buildship is the working example of the cohort's structural posture. The product is a low-code application builder that has added agentic primitives — LLM nodes, multi-agent workflows, structured-output handling — as first-class capabilities over 2025. The user base is heavy on independent builders, small agencies, and the long tail of small-team operators who need to ship agentic functionality without building a custom application stack.

The commercial story is less aggressive than the autonomy-layer-native cohort's but more durable. Buildship's revenue trajectory is, by our reading of the public signals, steady mid-single-digit-percentage monthly growth — the kind of trajectory that compounds into a meaningful business without producing the headline-driving funding rounds the trade press tends to cover. The user base has grown roughly threefold over 2025. The platform's enterprise tier, launched in late 2025, has begun to attract the mid-market customers who would otherwise be priced into the autonomy-layer-native products.

Pipedream

Pipedream is the developer-friendlier corner of the cohort. The product is, in its mature form, a serverless workflow platform with first-class support for arbitrary code execution. The 2025 evolution of the product has added the same agentic primitives — LLM nodes, multi-agent orchestration, structured outputs — and has positioned the product around the developer audience that wants the workflow-automation surface but is comfortable writing custom logic at the node level.

The structural advantage of this posture is that the platform absorbs the developer audience that finds the no-code workflow-automation tools too constrained and the autonomy-layer-native frameworks too opinionated. The user base is, by our reading, the most senior of any platform in the cohort; the customer base is, correspondingly, weighted toward technical teams and engineering organizations rather than ops or marketing teams.

Pipedream is the platform the Bulletin has been most interested in over the last quarter. The combination of developer-friendly workflow surface and agentic-primitive support is the structural shape we think will produce the most durable commercial businesses in the autonomy-adjacent category.

Make and Tray

Make and Tray are the established workflow-automation incumbents in the cohort. Both companies have added agentic primitives over 2025; both companies have user bases in the millions; both companies have commercial businesses that are mature, profitable, and unusually durable for the category.

The structural lesson the Bulletin keeps returning to is that the incumbents are absorbing the autonomy-layer transition more cleanly than the venture-press framing has acknowledged. The user base is sticky. The integration substrate is deep. The agentic primitives are usable. The transition is gradual but it is happening, and the commercial outcome is that the incumbents are growing their addressable market without giving up their existing customer base.

The autonomy-layer-native cohort competes with the incumbents at the new-customer margin. The incumbents do not have to win the new-customer margin to stay relevant; they have to retain their existing customers as those customers absorb agentic capability. This is, structurally, a meaningfully easier problem.

What this means for the category

The Bulletin's editorial position is that the trade-press framing of the autonomy-layer category is incomplete in three specific ways.

The first is that the cohort of Web4-adjacent platforms is larger and more commercially mature than the framing has acknowledged. The long tail of workflow-automation, integration-substrate, and low-code platforms is, in aggregate, the larger commercial story for the next eighteen months.

The second is that the structural advantage of the cohort is the existing user base and integration substrate. The named autonomy-layer winners have to teach the mental model and build the integrations. The Web4-adjacent platforms inherit both halves and add the agentic substrate on top. The structural advantage is, in our reading, more durable than the venture-press framing has assumed.

The third is that the competitive dynamics will resolve at the user-population margin rather than at the product-capability margin. The autonomy-layer-native cohort and the Web4-adjacent cohort serve different user populations, with different mental models, different commercial expectations, and different integration requirements. The two cohorts are less directly competitive than the venture press has framed them.

What we are watching

Three things specifically.

The first is whether the Web4-adjacent cohort sustains its current commercial trajectory. The cohort's growth is steady but not headline-driving; if the trajectory holds, the commercial story compounds into a meaningful slice of the category. If the trajectory slips, the cohort's role consolidates around the incumbents and the smaller players exit.

The second is whether any of the cohort's smaller platforms — Buildship, Pipedream, the long tail of similar products — raises a round at the kind of scale that would force the trade press to update its framing. The base-rate behavior is that the smaller players get acquired by the incumbents before reaching that scale. If any of them stays independent and raises at scale, the venture-press framing of the category shifts.

The third is whether the autonomy-layer-native cohort starts shipping product capability that competes directly with the Web4-adjacent cohort's strengths — depth of integration, sticky existing user base, mature commercial models. The base-rate behavior is that the new-cohort cannot replicate the old-cohort's structural advantages on a useful timeline. If any of the autonomy-layer-native players manages to, the competitive dynamics change.

The Bulletin's editorial position is that the long tail of Web4-adjacent platforms is the part of the category that the directory will continue to expand into over the next two issues. The named winners will get coverage. The quiet successes will get directory entries.