Progressing together
Foresight is gathering the people who measure themselves against more than the quarter — people willing to contribute to the betterment of business generally, rather than hold profit and knowledge inside one company.
The pattern it stands against is ordinary and expensive: a company solves something hard, keeps the answer, and a dozen others spend the same year solving it again. Everyone protects a margin, and the whole trade moves slower than any one of them wanted.
Hoarded knowledge compounds for one. Shared knowledge compounds for everyone.
What that means in practice
It means publishing the method instead of implying there is a trick to it. Answering the question a competitor asks. Sacrifice occasionally, forward-thinking as a habit, and innovation expected from everyone in the room rather than from a department that owns it.
Nothing here requires anyone to stop running a business. Shared knowledge and a working balance sheet have never actually been at odds — the belief that they are is what keeps this industry repeating each other's mistakes in private.
What Foresight puts in
Knowledge, expertise, connections and resources, applied to that end rather than held back for advantage. Concretely: the build discipline written out in full on the services page, the honest-refusal standard the tools are held to, introductions between people who should be talking, and time.
Foresight is one person, so the resources are finite and the promises stay small enough to keep. What scales is the method — and method costs nothing to hand over.
The 52 Meal Bank platform
Harvest is the software behind a church food shelf: a web app at 52mealbank.org that handles provision with dignity, so people collecting food are treated as people and volunteers can see what the shelf actually holds. Its mark is a woven kete with a rising frond, in kōwhai gold.
It is built and maintained to the same standard as everything else Foresight ships — versioned, asserted, and fixed when a volunteer says something is wrong. It is part of the work, not here to make the rest of the site look generous.
Software that keeps a shelf stocked and a queue dignified is the same craft as software that keeps a part number honest — pointed somewhere it matters more.
Who this is for
Individuals and organizations already doing some version of this who would rather not do it alone. Manufacturers willing to share what a process actually cost. Engineers who publish the fix. People building for their communities who need a hand with the software half.
It is not a peer group defined by size or sector. The only real filter is whether someone would still hand over a hard-won method knowing a competitor might read it — and enough people answer yes to make the gathering worth doing.
How to start
There is no membership and no form beyond the one below. Send a note describing what you are working on and what you would be willing to share. If the fit is there, the conversation continues. If it is not, you will be told plainly.
Bring a problem, a proven method, or an hour. All three are the same currency here.
This is not the charitable wing of a software company. It is the same conviction that produces the build discipline, the honest refusals and the published method — pointed outward instead of inward.