North of Ash

About

North of Ash exists to help people turn difficult problems into practical improvements in how they work and live.

Follow the problem. Build what matters.

Why North of Ash exists

Today, that work takes the form of business strategy, operating design, AI implementation, software development, research, and creative systems. We work across those disciplines because a useful answer often needs more than one of them.

We want the things we build to give people time back, ease everyday burdens, and help them shape their own lives.

Mission

To advance shared flourishing by giving people time back, easing everyday burdens, and making life’s essentials more accessible, so they have greater freedom to be present with the people and pursuits they love.

Vision

A world where less of life is consumed by survival and busywork, leaving more time for health, connection, creativity, laughter and meaningful choice. We build trustworthy tools, services and businesses that help make this possible.

Partnership commitment

We bring curiosity, initiative and care to meaningful work. We seek truth before agreement, explore unconventional possibilities, test what we build, and preserve what we learn. We develop ideas into reliable tools and services that give people more freedom in their everyday lives.

Operating test

Does this give someone time back, ease worry, improve access to essentials, or leave more room for connection and joy? What evidence shows that it helps?

The founder

I founded North of Ash because the problems worth solving rarely stay inside one discipline.

I work across business strategy, software architecture, product design, operational process, pricing, positioning, and AI implementation. I follow the problem far enough that the line between strategy and execution stops being useful.

That range is practical. I build software, design workflows, implement AI systems, study markets, and stay with the work until it functions in the environment where it has to live.

Businesses contain knowledge that software rarely captures well. It lives in experienced judgment, undocumented exceptions, the spreadsheet that quietly runs an operation, and the small adaptations that make the company work.

As AI made more of that knowledge programmable, one question became central:

Who controls a business's knowledge when it becomes software?

That question is central to North of Ash.

Organizations should be able to turn how they operate into software they control. Their processes, judgment, exceptions, and institutional memory should remain theirs.

When something matters, I want to understand the mechanism beneath the abstraction. That has led me across disciplines usually handed to separate specialists and taught me to see how the whole system fits together.

I care about meaning as much as function. Architecture, names, symbols, language, and identity all shape whether a system makes sense to the people who use it.

My standard is evidence over assumption, functioning systems over impressive presentations, and narrow pieces of finished work over sprawling plans.

Technology should give capable people greater control of their judgment, experience, and knowledge.

  • Understand how the business actually works.
  • Find what is valuable but trapped inside people, processes, and disconnected tools.
  • Turn that understanding into durable software.
  • Give the organization control of what was built.
  • And leave behind something more capable than what existed before.

I created North of Ash to do that work at full depth. The aim is practical: understand the business, make that understanding operational, and give people greater control of what they build.

Joe, founder