✨ This website is created and maintained by Neo, our coding nim β€” powered by its AI agent Claude πŸ€– and its person Cederik πŸ™‚, our founder.
🌳 Nimsforest
The Organization Organism

From organization
to organism

The bigger you get, the more of your week goes to keeping everyone in sync. An organism doesn't need that β€” it senses, decides and acts as one.

Nimsforest connects the systems you already run on, turns everything happening in them into one shared picture, and lets your people β€” with their AI agents β€” act on it. Nothing to migrate, nothing new to learn.

Four weeks to something real Β· One team to start Β· Nothing to migrate
Start with one team Β· end up organization-wide
πŸ’§ πŸ’§ πŸ‚ πŸ‚
πŸ’§
Your tools keep reporting
spreadsheets Β· drive Β· inbox Β· crm
🌊
It all flows into one river
no dashboards to check
🌳
The forest makes sense of it
one shared language
✨
Your nims act on it
people Β· agents Β· treehouses
πŸ’§ drops🌊 riverπŸ‚ leavesπŸƒ wind✨ nims
The science behind it
01
Optimizing the speed of an organization is defined by its waiting β€” in transport, goods spend most of their time standing still, waiting to be processed.
02
Left alone, AI will hit the number and miss the point. People decide what success means.
Read the whitepaper β†’

The people who know what works don't shape strategy. The people who shape strategy don't know what works.

Every tool picks a side. Project management serves the doers. Strategy platforms serve the thinkers. The gap gets papered over by meetings, reports and coordination overhead that exists only because the organization cannot sense itself.

Whole-organism care

Nimsforest tends to the whole

The hand knows what the brain is thinking. The brain knows what the hand is touching. The nervous system between them grows smarter every day.

You don't start with a strategy. You start with your people β€” and the work they're already doing. Nimsforest observes, maps what is actually happening, and finds value creation nobody documented.

πŸƒ

For the doers

Strategic context, for the first time. Your work connects visibly to goals, focus areas, mission. You understand why it matters.

✨

For the strategists

Execution reality, for the first time. Not a quarterly report β€” a living picture of what is happening, right now.

Productized sprint

Growth Engine Sprint

Your marketing runs across several channels. Each consultant optimises their own. Who coordinates across all of them to reach the right people?

Refined personas from real data and team expertise
Content strategy aligned to qualified leads
Cross-channel budget allocation insights
Productized sprint

Strategy Activation Sprint

Your strategy lives in a slide deck. Your people are busy β€” but busy doing what? Everyone becomes part of Napoleon, the strategic nim.

Unaligned effort revealed and redirected
Weekly alignment reports that surface drift early
Works with EOS, OKRs, Scaling Up or your own rhythm
Autonomization, not automation

Nimsforest doesn't optimize your process. It helps your organization evolve.

Automation makes your current process faster β€” a bet on the present. Autonomization is different: the system learns when a process is ready to run itself, and shifts human attention to where being human matters.

01
Operating processes
Where most small teams spend their week
02
Making decisions
Once the routine work runs itself
03
Shaping strategy
Where owners actually want to be

A forest, not a factory

An ecosystem that self-organizes, senses its environment and grows more resilient over time. Here is how it actually works.

πŸ’§

The drops

Every outside system β€” your inbox, your shop, your bookkeeping β€” keeps reporting what it sees. Each of those is a drop.

🌊

The river

The drops all flow into one stream instead of a dozen dashboards. One current, running through your company.

🌳

The forest

Everything you already run on, standing together as one place. It reads the river and works out what each drop actually means.

πŸ‚

The leaves

What the river turns into once it is understood. An order placed, a lead replying, a promise made β€” in language the whole forest shares. The wind carries them to whoever should act. πŸƒ

✨

The nims

Your people and their AI counterparts. They catch the leaves, decide what to do, and let new leaves go β€” leaving the forest better than they found it.

🏑

The treehouses

Work that no longer needs judgment. A treehouse does the same job the same way every time β€” reliably, cheaply, without anyone thinking about it.

How it works

Nothing to migrate. Nobody to fire.

Nothing gets ripped out and nobody gets replaced. Your systems each say things their own way; the river carries all of it in, the forest turns it into one shared language, and the wind carries those leaves to whoever should act β€” people first.

See which tools connect
HubSpot
dealstage β†’ "Closed Won"
πŸ’§
Basecamp
todo #418 completed βœ“
πŸ’§
Teams
"ok shipping it today πŸ‘"
πŸ’§
Exact
INV-4471 Β· status PAID
πŸ’§
🌊 river
🌳
πŸƒ wind
πŸ‚
πŸ‚ order.placed
πŸ‚
πŸ‚ customer.contacted
πŸ‚
πŸ‚ work.completed
πŸ‚
πŸ‚ invoice.paid
πŸƒ carried to whoever should act
πŸ‚
✨
Napoleon strategizes
πŸ™‚
Amy weighs the trade-off
πŸ€–
Agent drafts the brief
πŸ‚
✨
Nectar sells
πŸ™‚
Tom picks up the warm ones
🏑
Treehouse sends the quote
πŸ‚
✨
Nimble talks to customers
πŸ™‚
Sara handles the delicate reply
πŸ€–
Agent answers the rest
πŸ’§ sources🌊 river🌳 forestπŸ‚ leavesπŸƒ wind✨ nims🏑 treehouses
πŸƒ
Nothing in the forest waits on anything else. No handover, no status meeting, no approval queue holding the next step. That is a design decision, not a feature β€” and it is why the forest keeps moving while you sleep.
Grassroots, not rollout

You don't plant the whole forest at once

This is not a company-wide AI rollout β€” no all-staff licence, no assistant bolted onto every desk in the hope something sticks. Nobody has to agree on everything first: start in the corner that hurts most, with the handful of systems that corner already uses. Elsewhere in the company another team can plant their own at the same time β€” and where two forests touch, they start sharing leaves.

🌱

Start in one corner

One team, a few sources, four weeks. Small enough that nobody needs permission from everybody.

🌱 🌱

Plant in parallel

Sales can plant while operations does. No waiting for a company-wide decision, no big-bang migration.

🌳 🌳

Grow toward each other

When two forests meet they keep their own rhythm β€” and leaves start flowing both ways. Groups of 1–100 people, as many as your company needs.

What it costs

One price to plant the forest. Then a small yearly fee to keep it alive β€” and you choose how the thinking gets paid for.

Step one Β· the sprint
€5,000
once

Four weeks of hands-on work, plus your first year on the platform and all the AI thinking the sprint needs. Nothing else to buy.

Setup β€” connecting your sources, configuring your nims€3,000
Platform, first year€1,000
AI credits for the sprint€1,000
Step two Β· every year after
€1,000
/ year

The platform fee. Your nims keep running, keep coordinating, keep learning. That is the whole recurring bill.

✨
You choose who handles the AI
Connect the model subscriptions your team already pays for and the nims use those β€” platform fee and nothing more. Or let us manage it: we follow where the models are going and put the right one on the right task, so you never have to.
Optional Β· or let us handle the AI

One bill, no model shopping

If you would rather not manage AI subscriptions yourself, pick a tier and we cover the thinking. Sits on top of the platform fee. Nothing here is a hard limit β€” every extra source, ceremony or nim is more for the forest to read and interpret, and that is what drives your AI usage. The numbers below are what a tier comfortably carries.

🌱 Seed
πŸƒ Growth
🌳 Forest
✨ Tailored
AI credits
€50/mo
€100/mo
€200/mo
let's talk
Sources, comfortably
around 4
around 8
around 20
whatever your forest needs
Daily ceremonies
around 2
around 4
around 10
whatever your forest needs
Nims
around 2
around 5
around 15
whatever your forest needs
πŸƒ
And usage goes down over time, not up
More parts mean more to interpret β€” but only at first. The longer the forest runs, the more it recognises without re-thinking: work that used to need thinking starts running on memory, or gets handed off to a plain automation with no AI involved at all. Most teams end up moving down a tier, not up.

All prices exclude VAT. Guidance, not caps β€” grow past a tier and we simply move you up together.

πŸ’§πŸŒ³πŸƒβœ¨

It starts with your people

The forest grows from there.

Productized sprint Β· πŸƒ

Growth Engine Sprint

Your marketing runs across multiple channels. Each consultant optimises their own. But who coordinates across all of them to make sure you reach the right people?

Start this sprint
Four weeks, four movements
01

Connect & organise

Your channels, tools and reporting in one living picture.

02

Learn & analyse

What actually brings qualified leads β€” not what looks busy.

03

Recommend & align

Concrete briefs so every consultant pulls the same direction.

04

Autonomise & hand over

The nims keep running the rhythm after we leave.

What you get

πŸƒRefined personas from real data and team expertise
πŸƒContent strategy aligned to qualified leads
πŸƒConcrete consultant alignment briefs
πŸƒCross-channel budget allocation insights

What stays after

✨Nims keep learning autonomously
✨Daily ceremonies run without intervention
✨No additional consultancy costs
✨Your forest gets smarter every week
🌳 πŸƒ ✨

Ready to coordinate the whole engine?

Plant your forest
Productized sprint · ✨

Strategy Activation Sprint

Your strategy lives in a slide deck. Your people are busy β€” but busy doing what? Everyone becomes part of Napoleon, the strategic nim that bridges strategy and execution.

Start this sprint
Four weeks, four movements
01

Plant the forest

Your people, roles and rhythm β€” mapped as they really are.

02

Connect the work

Every task finds the goal it actually serves.

03

Activate alignment

Drift surfaces weekly, while it is still cheap to fix.

04

Autonomise & hand over

Napoleon checks alignment continuously, on its own.

What you get

πŸƒYou become part of Napoleon, the strategic nim
πŸƒUnaligned effort revealed β€” redirected to what moves the needle
πŸƒWeekly alignment reports that surface drift early
πŸƒWorks with EOS, OKRs, Scaling Up or your own rhythm

What stays after

✨Napoleon checks alignment continuously
✨The vector sum of your organisation increases
✨Strategy becomes a living force, not a document
✨Your forest gets smarter every week
🌳 πŸƒ ✨

Make the strategy a living force

Plant your forest
Integrations

Roots into the tools
you already use

Nimsforest doesn't ask your team to move house. It grows roots into the systems where the work already happens, and senses from there.

Conversation

Chat & email

Where decisions actually get made. Nims listen for commitments, not gossip.

Work

Tasks & projects

Boards, backlogs and to-do lists become visible effort, mapped to goals.

Demand

CRM & pipeline

Which effort turns into qualified conversations, and which quietly doesn't.

Reach

Channels & ads

Spend, content and audience data across every channel in one view.

Truth

Finance & invoicing

The numbers that decide whether the forest is actually growing.

Memory

Docs & drives

Everything written down once and never found again β€” now searchable context.

Nothing to migrate. Nobody to fire.

If you run a 12-person company on a spreadsheet, a shared inbox and one project tool β€” that is a perfectly good forest floor to start from. Nothing gets ripped out and nobody gets replaced.

Talk to us about your stack
Don't see your tool?

Most systems can report what they see in some form β€” that is all the forest needs. If yours can't, we start with the ones that can and come back to it.

HubSpot
dealstage β†’ "Closed Won"
πŸ’§
Basecamp
todo #418 completed βœ“
πŸ’§
Teams
"ok shipping it today πŸ‘"
πŸ’§
Exact
INV-4471 Β· status PAID
πŸ’§
🌊 river
🌳
πŸƒ wind
πŸ‚
πŸ‚ order.placed
πŸ‚
πŸ‚ customer.contacted
πŸ‚
πŸ‚ work.completed
πŸ‚
πŸ‚ invoice.paid
πŸƒ carried to whoever should act
πŸ‚
✨
Napoleon strategizes
πŸ™‚
Amy weighs the trade-off
πŸ€–
Agent drafts the brief
πŸ‚
✨
Nectar sells
πŸ™‚
Tom picks up the warm ones
🏑
Treehouse sends the quote
πŸ‚
✨
Nimble talks to customers
πŸ™‚
Sara handles the delicate reply
πŸ€–
Agent answers the rest
πŸ’§ sources🌊 river🌳 forestπŸ‚ leavesπŸƒ wind✨ nims🏑 treehouses
Whitepaper Β· July 2026

Operating at the limits

Everything else on this site is the plain-language version. This is the reasoning underneath it.

An organization is a social construct for achieving goals. Once compute does the pursuing, two permanent laws take over β€” one on the goals, one on the speed.

Neither law can be broken. Most systems ignore one or both and pay for it in silent drift or wasted scale. Nimsforest is engineered to run as close to both frontiers as physics and judgment allow. This is the reasoning behind the forest.

Read the full paper (PDF, 9 pages) Nimsforest BV Β· nimsforest.com
In this paper
01 Two laws, two different kinds of limit
02 The architecture: transport and truth
03 Every hazard, cornered
04 What this system does not claim
05 Residual risks, stated plainly
06 Conclusion: running at both frontiers
The machine pursues. The human defines.
9 pages Β· ~20 min read
The two laws

Two limits, different in kind

Goodhart's law

The limit on goals

When a measure becomes a target it stops being a good measure. Every KPI is a lossy compression of a richer purpose, and an optimizer exploits precisely what was lost β€” because that divergence is free reward. No metric can detect its own divergence.

A definitional limit. Not measurable from inside the system β€” so a machine is actively dangerous here. It needs judgment from outside the metric.
Amdahl's law

The limit on speed

A computation's maximum speedup is set by its sequential fraction. If five percent of the work is a dependency chain, infinite hardware buys you at most twenty times. Parallel throughput scales almost without bound; the critical path does not.

A mechanical limit. Measurable, and approaching it is unambiguously good β€” exactly the kind of thing a machine should drive toward automatically.
✨
So the design puts the machine where more optimization is always better β€” pursuit β€” and human judgment where more optimization is a hazard β€” definition. The machine pursues. The human defines and audits. That single placement is the whole architecture in one sentence.
In practice  For a twenty-person company: you get faster by removing waiting, and you stay honest by keeping people in charge of what counts.
The architecture, in forest words

Every part of the metaphor is a real mechanism

The forest language on the rest of this site is not decoration. Each word maps to a specific engineering decision.

πŸ’§
Drops
Events from the outside world, captured reliably at the boundary. The unreliable exterior gets recorded; the interior stays light.
🌊
The river
Events as pure signal β€” fire and forget, nothing waits on anything. A dropped event is a dropped frame, superseded by the next one, never a corrupted world.
🌳
The forest
Truth held separately from signal, one invariant per key. The only sequential step anywhere is a single compare-and-swap β€” the permanent tax compressed to its practical floor.
πŸ‚
The leaves & the codex
A governed vocabulary. Agents can get arbitrarily clever about when they speak, but only in words that exist β€” so the set of possible cause-and-effect edges stays finite and reviewable.
🏑
The treehouses
Deterministic workers. They don't decide, they execute: same input, same action, every time. The analyzable substrate.
✨
The nims
Deciding workers, human and digital. They may read the world for context but never write it β€” so deciding can never silently deepen the chain of causes. Only deliberate emission can.
Every hazard, cornered

Nothing abolished, everything pinned

Each hazard that theory says must exist somewhere is pushed into the smallest, most inspectable place it can occupy.

Hazard
Where it is cornered
Lost messages
Truth lives in the store; events are only hints. A drop costs one tick of staleness, corrected on the next read.
Barriers and joins
Structurally impossible β€” no worker waits on another, so the classic fan-in stall cannot be built.
Torn state
One invariant per key. The sole sequential primitive is a per-key compare-and-swap.
Runaway decisions
Decisions read, never write. A read is a causal dead end; only emission extends the graph.
Emergent cascades
The codex makes possible edges finite and reviewable; loops are statically detectable cycles.
Amdahl residue
Made the optimization target itself: fewer words, fewer hops, fewer tokens β€” continuously self-minimized.
Goodhart drift
A human–machine seam owns the translation from purpose to KPI and audits it against reality, outside the fast loop.
Stated plainly

What this does not claim

Precision here is not modesty. Systems that claim to beat these limits are the systems that quietly violate them.

Amdahl is approached, not beaten

The serial residue is compressed and then continuously reduced toward its floor β€” the way a good engine rides thermodynamics. Not past the bound; wasting as little as possible against it.

Goodhart is guarded, not solved

The gap between metric and purpose still opens. Judgment is stationed exactly where it opens, so divergence is noticed and corrected faster than it compounds.

Emergence is bounded, not eliminated

The codex bounds what can happen, not what will. Long reaction chains stay possible β€” so cascade length is measured and minimized, not assumed away.

Residual risks
The rubber stamp
If the machine proposes faster than the human can genuinely evaluate, judging degrades into approving β€” and Goodhart protection silently becomes zero while looking intact.
KPI staleness
Without a deliberate cadence for re-grading the KPIs themselves, the system converges confidently on yesterday's purpose.
Proxy incompleteness
Anything not encoded β€” trust, resilience in rare states, restraint β€” exerts zero force on the optimizer. The dangerous KPIs are rarely wrong; they are incomplete.
πŸ’§πŸŒ³πŸƒβœ¨

The machine pursues. The human defines.

Running an organization at both frontiers at once β€” not past them, which is impossible, but against them, with nothing wasted in between.

Which is a long way of saying something simple: let the forest do the waiting, the fetching and the remembering β€” and keep the judgment where it belongs, with your people.

🌳 πŸƒ ✨

Plant your forest

Tell us a little about your company. We'll come back within two working days with what a first sprint would look like for you β€” no slide deck, no procurement dance.

🌳
We start where you are
Your current tools stay. Nothing gets migrated.
πŸƒ
Four weeks to something real
A sprint, not an open-ended engagement.
✨
It keeps working after we go
Your nims run the rhythm without us.
🌳 πŸƒ ✨

Your forest is planted

We'll be in touch within two working days.

Get started
How many people?
Which sprint interests you?

No card needed. We reply personally, within two working days.