Cam IncollFieldwalker is a permaculture design tool built around the idea that the design process — observe, reflect, iterate — matters more than any single map you produce. It's a tool for thinking through a site, not just drawing one.
I built Fieldwalker because I kept hitting the same wall. I'd done my PDC. I understood the principles. I could read a landscape, think in systems, see the patterns. But when it came to actually producing a design — turning all that understanding into something I could hand to a contractor, pin to the shed wall, or present to a client — the workflow fell apart.
Not because the thinking was hard. Because the mechanics were.
The gap nobody talks about
Permaculture Design Certificates are brilliant at what they do. They teach you to observe. To think about water before anything else. To design from patterns to details. To stack functions, to value the edge, to understand that every element in a system should serve multiple purposes.
What they don't teach is how to turn all of that into a professional design document.
How do you create a base map? Most people screenshot Google Maps and print it out. How do you get contour lines onto that map? Most people either skip contours entirely or spend days learning GIS software. How do you iterate on a design when each version means starting from scratch on a fresh printout?
This is the gap. Not in knowledge — PDC graduates have plenty of that. In workflow. In the practical mechanics of going from observation to design to document to iteration.
Why the process matters
A permaculture design isn't a deliverable. It's not something you produce once and hand over. It's a snapshot of your understanding at a particular point in time.
You observe the land in winter, and you see where the water sits. You come back in summer, and you see where the sun falls. You design based on what you've learned, and then you observe again — did the swale catch the water where you expected? Is the orchard getting the morning sun you planned for?
The design evolves because your understanding evolves. That's the whole point of observe, reflect, iterate. The map is a tool for thinking, not the end product.
But if every iteration takes hours of redrawing, the iteration stops. If creating the base map is a full afternoon's work, you do it once and then you're locked in. The overhead of the mechanics kills the very process that makes permaculture design powerful.
What a design tool should actually do
So I asked a simple question: what if the mechanical parts were fast?
What if you could type an address and have an aerial image of the site in seconds, not hours? What if contour lines appeared automatically from elevation data, instead of requiring a GIS degree? What if AI could identify the existing trees, buildings, and vegetation on the site, so you didn't spend your first hour tracing?
That's what Fieldwalker does. It handles the mechanics so you can focus on the design thinking.
The base map takes seconds. Contour lines are generated automatically. Feature detection identifies what's already on the site. And then you design — placing swales, laying out zones, planning garden beds, running fence lines — using symbols drawn in the visual language permaculture designers already know from their training.
When you want to try a different approach, you iterate. Move the swale. Adjust the paddock boundaries. Try the orchard on the north-facing slope instead. The speed of the tool matches the speed of your thinking.
Who this is for
If you've done your PDC and you're staring at your own property thinking where do I start? — this is for you.
If you want to take on your first paid design client but you're not sure how to produce a professional document — this is for you.
If you're managing a farm and you want a working reference map that evolves as your understanding deepens — this is for you.
The process is the same in each case. Observe the land. Understand the contours, the water, the sun, the existing features. Design from that understanding. Come back next season and refine. The map is the thinking tool that makes that cycle possible.
Fieldwalker is built to support that cycle — fast enough to keep up with your thinking, detailed enough to produce professional work, and grounded in the design language and principles that permaculture practitioners already use.
Because the process really is more important than the output. And a good tool should make the process easier, not harder.