---
schema: 1
type: term
title: _greenfield_ vs. mature-codebase work
description: >-
  The channel uses this term to contrast two situations for applying AI:
  building AI into a brand-new company from scratch (_greenfield_) versus
  bringing AI into an existing, established company with a mature codebase and
  operations. It captures the idea that each case calls for a different
  approach.
canonical: >-
  https://liquidgold.cc/channel/everyinc/explore/term/greenfield-vs-mature-codebase-work-c6dadb23e5d1
markdown: >-
  https://liquidgold.cc/channel/everyinc/explore/term/greenfield-vs-mature-codebase-work-c6dadb23e5d1.md
llms: null
parent: 'https://liquidgold.cc/channel/everyinc/llms.txt'
channel: everyinc
updated: '2026-10-23T22:12:35.346Z'
language: null
children: []
---


# \_greenfield\_ vs. mature-codebase work

Canonical: https://liquidgold.cc/channel/everyinc/explore/term/greenfield-vs-mature-codebase-work-c6dadb23e5d1

Parent: [Channel index](https://liquidgold.cc/channel/everyinc/llms.txt)

## Definition

The channel uses this term to contrast two situations for applying AI: building AI into a brand-new company from scratch (_greenfield_) versus bringing AI into an existing, established company with a mature codebase and operations. It captures the idea that each case calls for a different approach.

In this channel's material, the distinction shows up in the **Boulton and Watt** conversation, where the incubator explains why it builds **AI-durable** rather than AI-native businesses — and what actually worked (and failed) when bringing AI into discovery and operations inside companies that already exist. The handout frames this explicitly as the _greenfield-vs-mature-company AI pattern_ [^a0667bf0-c916-5c9b-9693-415c0c051ca5@0]. The useful takeaway: treat these as two different situations that call for different tactics, not one uniform approach to adding AI.