Seven doors, walked all the way through.

The entry

A chef-owner running a small West Texas restaurant group reaches out after a rough season — unreliable deliveries, produce arriving tired after long hauls, margins squeezed. They don't want a garden; they want supply they control, and a farm-to-table story guests can actually see.

The discovery

What are your top ten highest-volume, highest-margin produce items? Weekly covers by season? Current food cost and spoilage? Do you hold water rights, and what's your source? Who on your team could tend a farm — or do we train someone? What's the capital envelope, and can we phase it?

The data

We map the site's brutal constraint first — water — alongside soil, sun, wind, and existing infrastructure, then translate the menu into a crop demand table: what the kitchen actually uses, when, and how much. Design is driven by that demand, not by what's pretty.

The preliminary design

Water-first: catchment, storage, and efficient drip. Production beds sized precisely to the menu, season extension for the shoulder months, a simple wash-pack station, and sensors feeding a monitoring dashboard. The farm is engineered to feed the kitchen on schedule.

The iteration

The chef wants triple the herbs and specialty greens, less ornamental hardscape, and the capital spread across two years. We resize the beds, cut the hardscape, and phase the build so cash flow breathes.

The adaptability

Midway, they see the marketing gold and ask for a small on-farm dinner space — we fold in an events flow and booking so the farm becomes a revenue-generating venue too.

The rendered outcome

A tight, water-smart production farm humming beside the restaurant — beds keyed to the menu, a wash-pack shed, a long communal table under shade for farm dinners, and a dashboard on the chef's phone showing what's ready to harvest. The story writes itself: this is ours.

The entry

A young couple with two small kids just bought a modest place on an acre. They're excited and a little overwhelmed — they want to grow real food, be more self-reliant, and raise their kids close to the land, but they're on a budget and don't have the skills yet.

The discovery

How does your family actually eat and cook? How many hours a week can you realistically put in? What's your skill level today — honestly? What are your three non-negotiables versus your someday dreams? Would you rather we build it, or teach you to build it?

The data

On a small site every foot counts, so we map sun and shade, water flow, soil, house position, and the microclimates — the warm south wall, the soggy corner — and line them up against the family's real cooking habits.

The preliminary design

A kitchen garden by the door, a starter food forest, a few chickens, rain catchment, a small greenhouse, and a dedicated kids' bed — all designed to be installed in affordable phases, much of it DIY with our guidance.

The iteration

They want chickens this spring and can defer the greenhouse a year; they ask for a bigger kids' zone. We reorder the phases, pull the greenhouse to Phase 3, and expand the children's garden.

The adaptability

This is a teaching-heavy engagement: light build from us, heavy training, plus a system bible and the app so a busy family can confidently run it themselves — and modularly, we trim elements to hit their number without losing the vision.

The rendered outcome

A beautiful, productive little homestead a family can actually manage — herbs and greens steps from the kitchen, fruit trees getting established, hens the kids love, and a phone app nudging "water the north bed" and "harvest lettuce this week." They're feeding themselves and learning as they go.

The entry

An extended family — three generations, a family office involved — is planning a shared compound: several homes for grown siblings and aging parents, with real food and water sovereignty, comprehensive food forests, and a place built to be inherited and stewarded for decades.

The discovery

Who lives where, and what's shared versus private? Water rights, wells, and watershed? Energy goals? How will the family govern and maintain shared systems — and who manages them day to day? What's the multi-year budget and build sequence? What does "legacy" mean to you in concrete terms?

The data

A large site demands real analysis: watershed and topography mapping, zone planning, road and utility infrastructure, and careful home-site selection across multiple microclimates — organized into a master plan the whole family can read.

The preliminary design

A comprehensive master plan: home sites with private kitchen gardens, expansive shared food forests, production gardens, integrated water systems — ponds, swales, storage — animal systems, compost centers, greenhouses, on-site energy, and a shared kitchen and gathering barn.

The iteration

The family debates shared versus private growing space, and whether to add an event venue for gatherings and income. We adjust the master plan, define shared-vs-private clearly, and phase the build home site by home site over several years.

The adaptability

We design a governance and maintenance plan for the family's shared resources, train a dedicated on-site manager, and deploy estate-wide monitoring so the whole system is legible from one dashboard.

The rendered outcome

A comprehensive regenerative estate — homes nestled into their best microclimates, food forests knitting the property together, ponds and swales holding water through dry spells, a gathering barn at the heart, and a trained manager keeping it all running. A place that feeds three generations and grows more valuable every year.

The entry

A city school wants a production garden woven into campus life — with an outdoor kitchen-class element right where the gardens are, so children grow food and then cook and eat it as part of learning. The driver isn't yield; it's food literacy, wonder, and community.

The discovery

What ages, and how does this map to your curriculum? How much space, and what are the sun, water, and safety constraints? Which staff will run it, and what's their capacity? How do we handle the summer break against the school calendar? Is there a fundraising story to support?

The data

An urban site analysis: available space, sun and shade, water access, safe materials and sightlines, proximity between the garden and the kitchen-class area — all aligned to the rhythm of the school year.

The preliminary design

Kid-scaled production beds, sensory and learning zones, and an outdoor kitchen-classroom set among the gardens, with a curriculum-linked planting calendar and a clean harvest-to-kitchen flow — everything safe, durable, and legible to a six-year-old.

The iteration

Teachers ask for more hands-on beds, a composting lesson loop, tighter alignment to the school calendar, and a realistic summer maintenance plan. We add the compost lesson, shift plantings to harvest during term, and design a light summer-care schedule.

The adaptability

We build for kids' scale and safety, integrate the kitchen-class element, and hand over a simple teacher-facing bible and app plus staff training — with the program documented for the school's community and fundraising.

The rendered outcome

A living outdoor classroom: raised beds full of things kids planted, a shaded cooking-and-eating space beside them, a compost corner that's part of the lesson, and children carrying their own harvest ten feet to the pan. A program the school can run and be proud to show off.

The entry

A remote-working couple left a major city — rattled by supply shocks, cost of living, and how fragile everything felt — and bought rural acreage. They want real self-reliance and to be prepared, but they also want beauty and comfort. This is a life they're building, not a bunker.

The discovery

What are you moving toward, and what are you moving away from? How self-reliant do you want to be — fully off-grid, or resilient-but-connected? What are your non-negotiable infrastructure needs — power, water, internet? How much do you want to do yourselves versus have run for you? What does a good day here actually look like?

The data

A rural site analysis: water sources and rights, off-grid feasibility — solar, well, septic — road access, soil, sun, wildfire and flood exposure, and connectivity — organized against how independent they truly want to be.

The preliminary design

Water security first — well, catchment, storage, filtration — then food: gardens, food forest, a few animals. Then energy: solar with backup, around a resilient, comfortable homestead core — designed so it's a beautiful life, not a survivalist compound.

The iteration

They want it warmer and less "prepper," reliable internet prioritized, and a guest cabin for visiting family. We soften the aesthetic, sequence the infrastructure first, and add the cabin.

The adaptability

We land on resilient-but-connected rather than fully off-grid, deploy monitoring so they can travel and have the systems report in, and train them so their independence grows season over season — with modular room to expand as confidence does.

The rendered outcome

A beautiful, self-reliant rural property — water and solar secured, orchard and gardens producing, a warm main house and a guest cabin, and a phone that shows the systems humming even while they're away. Independence, without isolation.

The entry

An investor or family office sees regenerative food systems as an appreciating, income-producing asset and a food-security thesis. They have raw or underused land and want it turned into something productive, valuable, and ideally leaseable or brandable. This conversation is less about feeling and more about the spreadsheet.

The discovery

What's your thesis and hold period? Income now, appreciation, or both? Will you operate it, lease it, or hire management? Risk tolerance and capital envelope? Exit — sell, lease, or generational hold? Any brand or impact goals riding alongside the return?

The data

Financial-first: we pair the site analysis — water, soil, production capacity — with a pro forma: yields, revenue lines, capex, and operating costs. Here, the design serves the model rather than the other way around.

The preliminary design

A production system sized for ROI — high-value crops, efficient infrastructure, and diversified revenue: wholesale, CSA, events, agritourism — with a management and monitoring layer so it runs without the investor in the weeds.

The iteration

They want faster payback and lower opex. We shift the crop mix toward quicker-return, high-margin lines, automate more with sensors, and phase the capex to protect cash flow.

The adaptability

We can operate it, train a manager, or set it up to lease — and the software stack plus the system bible make it a legible, transferable asset, which means a cleaner sale or handoff down the line.

The rendered outcome

A productive, income-generating regenerative asset — diversified revenue, low-drama operations via monitoring, documented top to bottom so it's sellable or leaseable, on appreciating land with a real story. A thesis made tangible.

The entry

An eco-resort, boutique hotel, farm-stay, or wellness retreat wants an on-site regenerative garden and food system that guests can feel — elevating farm-to-table dining, garden experiences, and the whole property's story, while genuinely supporting the kitchen.

The discovery

What experience are you selling, and how does food and nature fit it? What does the kitchen need on-site versus sourced? Should guests participate — tours, harvests, classes? What are your occupancy and seasonality patterns? Who maintains it — your grounds team or ours?

The data

Site plus experience mapping: sun, water, and soil alongside the guest journey — sightlines, walking paths, the dining terrace, where a guest should pause — with production aligned to both the menu and the property's aesthetic standard.

The preliminary design

Beautiful, productive gardens and food forest woven into the guest experience — a chef's garden feeding the restaurant, sensory and gathering spaces, water features, and optional programming: tours, harvest dinners, workshops — all held to a resort-grade aesthetic.

The iteration

The operator wants more signature, shareable moments and a marquee harvest-dinner offering. We heighten the beauty, add a feature water element, and stand up a farm-dinner venue with an events and booking flow.

The adaptability

We match their maintenance model — train the grounds team or maintain it ourselves — design around occupancy seasonality, and run the content engine that actually sells the experience.

The rendered outcome

A gorgeous, productive property guests remember — a chef's garden feeding the restaurant, paths wandering through food forest and water features, harvest dinners under the stars, and a story that fills rooms. Beauty that also produces.