Optimal foraging for startups, distributed systems, privacy and cryptographic organisations

Complex technology, turned into a business model.

Technical and market work from one team. We read your architecture, pick the segment worth entering, and build the funnel that feeds it. You pay per milestone, not per hour.

  • 3 at a time

    At most three engagements run at once, so yours gets priority

  • Both halves

    Solution architecture and go to market from one team

  • 25+ years

    Combined experience in privacy, cryptography and decentralized systems

  • No hype

    No airdrops, no KOL buys, no engagement farming

Optimal foraging theory, applied to startups

Nature has been solving this problem for a hundred million years, with a much faster feedback loop than yours. A model from behavioral ecology describes the go to market problem of a deep technology company better than any funnel diagram does.

Start with how reality works. An animal gains energy by finding food and spends energy searching for it and catching it. The animal that survives is not the one that finds the richest patch. It is the one that knows when a patch has stopped paying, and moves.

To maximize fitness, an animal adopts a foraging strategy that provides the most benefit for the lowest cost, maximizing the net energy gained. Optimal foraging theory

You have the same problem with a much worse feedback loop. A segment looks rich, the team settles in, and three years later the cryptography is excellent, the integrations are half finished, and nobody ever priced what entering that patch would cost. That is not bad luck. That is what happens when the cost of the search is never written down.

Charnov's marginal value theorem gives you the rule. Leave a patch when its rate of return falls to the average rate of the whole environment, including the cost of travelling to the next one. Read it in both directions, because the second direction is where good teams go wrong: the harder the next patch is to find, the longer it is rational to stay in this one. The chart is that rule, and the two ways people miss it.

Then look at the incentives, which is where these relationships are actually decided. An hourly agency is paid for residence time, so it has no reason to tell you a patch is empty. We price per milestone, so our incentive points where yours does: reach the decision point, take the decision, and move.

This is your last three years. Search cost is how long it takes to get a real conversation in a new segment.

medium

Research, intros, credibility and dead ends before the next segment produces anything. When search is expensive, staying longer is the rational choice rather than the lazy one.

medium

A shallow segment gives up its learnings immediately and then flattens. A deep one keeps paying for longer.

Move the controls and watch the moment to leave move with them.
  • Validated progress in the segment
  • Best achievable rate
  • Entering the segment

Work that converts, not work that trends

Most agencies arrive with a playbook and fit your protocol into it. When the product is a mixnet, an encrypted transport or a proving system, the playbook is the problem. We write the strategy from your architecture, because we can read your architecture.

What we do not sell

This is not squeamishness. These tactics measure beautifully and convert badly, and when your users chose you for trust, they cost you the thing you were selling.

  • Airdrops and points farming. Rented users who leave the week the emissions stop, and a metrics baseline you can never read honestly again.
  • KOL packages and paid threads. Impressions from accounts your actual buyers already discount.
  • Engagement farming. Followers are not a pipeline. A privacy protocol does not get adopted because a thread did numbers.
  • Ghostwritten claims. If a property is not true in the code, we will not write it. Over-claiming on privacy is a security incident waiting for a journalist.
  • Vanity dashboards. Reach reporting with no line back to a signed integration or a retained user.

What we hold ourselves to

Every milestone is written against something on this list, so acceptance is a fact instead of an argument about whether we did a good job.

  • Qualified conversations with people who match the thesis, logged with what they said, not just that they showed up.
  • Design partners who commit engineering time, which is the only interest signal that costs the other side something.
  • Integration commitments, dated, with the technical blockers named.
  • Retention after the incentive ends, measured deliberately rather than discovered later.
  • Cost per validated learning. The foraging metric: what did this milestone buy, and is the rate still worth the residence time.

Two halves of the same job

Buy technical work and market work separately and they fail separately. The positioning has to survive the architecture, and the architecture has to be explainable to whoever signs. We do both, which is the only way to hold each one to the other.

Technical

Architecture and technical strategy

For teams whose hardest constraints are cryptographic, distributed or regulatory

  • Technology and architecture review
  • Technical onboarding and documentation testing
  • Feature work from client discovery
  • Product backlog prioritisation
  • Technical and business incentive optimisation
  • Privacy and trust positioning review
  • Specifications: protocol, product, bounty, grant and integration

Cadence One to four weeks per milestone

Pricing Scope and fee fixed before anything starts

Not A formal cryptographic or smart contract audit. We will say so and point you at someone who does that work.

Market

Product market fit and demand

For teams with real technology and no repeatable way to put it in front of a buyer

  • PMF discovery: segment mapping, interviews, and a ranked list of patches worth entering
  • Positioning and message testing against the segments that survived the ranking
  • Technical narrative
  • Funnel design from first touch to signed integration
  • Event and program design
  • Launch execution alongside your team

Cadence Two to six weeks per milestone

Pricing Scope and fee fixed before anything starts

Not A team shopping a KOL package, or a retainer against vague strategy.

Flagship engagement

The product market fit rescue

For teams three years in who still cannot name the buyer in one sentence

  1. Patch survey

    Interview candidate segments and rank them by cost of entry.

  2. Entry test

    One segment, one narrative, one funnel. Demand appears or it does not.

  3. Scale or leave

    Build the motion and hand it over, or test the next candidate.

Commitment Stage by stage. Stop after any stage and keep the work.

Not Pre-architecture vapor. The machine has to exist before we price a market for it.

Anonymized, because most of it is not ours to publish

Teams working on anonymity systems tend not to want a case study with their name on it, and we would rather keep that trust than win an argument with a logo. Names and references come on request, under NDA where it matters. The shape of the work is the part worth showing anyway.

References on request

We do not publish client names or the people on the bench. Once we are in a sales conversation or writing a scope, we name who would do the work and put you in front of a reference who has worked with them. Ask for it when you write. It is the part of the proof that does not belong on a public page.

Work runs under a written scope. If the product is regulated or there is a token involved, bring legal and compliance in early. You will want them anyway. We are not a law firm and we will not write communications that are securities promotions. We can introduce you to lawyers who do that work, and if the scope needs it we put a credible lawyer on the team under the same milestone terms.

Ask for a reference

A quantum resistant mix network

  • Post-quantum
  • Mixnet
  • Campaign
  • Token
  • BD
Context
A cryptography team running a working post-quantum mix network with years of research behind it. Deep technology, a still-present community, almost no market surface. Foundation, council and contributors were unclear on who did what, and the public story left the protocol looking inactive.
Missing
A field test of adoption, a treasury plan that did not depend on selling into weakness, and proof that business work produced revenue rather than just spending the treasury. External interest in the tech existed. Trust and packaging did not.
Milestones
  1. Stakeholder, investor and user research across foundation, council, node runners and early backers
  2. Treasury and token analysis, with a liquidity plan sized to cover operating costs without forced selling
  3. Revenue designs around the API surface, plus brand and website direction
  4. Two field campaigns during a major ecosystem week: an in-person hackathon and a cryptographic quest
  5. Business development that opened paid integration conversations
Result
Two new clients requested paid integrations. The campaigns ran for a fixed window against a baseline measured before they started, and the momentum they created held for two months after spend ended instead of collapsing with it.
Counsel
A token was involved, so the rule applies: we are not a law firm and we do not write communications that are securities promotions. We connect you with lawyers who do that work, and when the scope needs it, we put a credible lawyer on the team under the same milestone terms.

An encrypted peer to peer network

  • P2P
  • Technical writing
  • Launch
  • Campaign
Context
A privacy-first peer to peer stack launching a new umbrella of products into an already crowded ecosystem.
Missing
Engineering could explain the system to other engineers. Nothing translated it for the funders, integrators and press who decide whether a protocol exists in public.
Milestones
  1. Technical writing across the core product surfaces
  2. Launch event designed and run during the ecosystem's largest week
  3. Campaign built around the launch, then generalized so other teams could reuse it
Result
The campaign format was adopted across every business unit in the organization.

A privacy research collective

  • Ecosystem data
  • Audit design
  • Fundraising
  • Events
Context
An open collective mapping the privacy landscape, run largely by volunteer contributors across time zones.
Missing
Genuine data and genuine credibility, but no product built on either, and no funding line to keep the contributors working.
Milestones
  1. Ecosystem explorer built, along with the scoring method underneath it
  2. Repeatable privacy audit service designed on top of that method
  3. Fundraising and the contributor process run to pay for both
Result
Over thirty thousand euro raised, a distributed contributor base shipping to schedule, and an audit service that outlived the grant that funded it.

A privacy first property platform

  • Zero to one
  • MVP
  • Regulated market
  • Revenue
Context
A regulated market where every incumbent treats personal data as inventory, and where the buyers had never been offered an alternative.
Missing
Everything. This one was a founding rather than an engagement.
Milestones
  1. Privacy and security workflows designed before the product was built
  2. MVP shipped to the narrowest segment that would pay for it
  3. Front end and funnel built around the first paying cohort
Result
Over twenty thousand euro of revenue in the first four months, from a standing start.
Consistently delivered high quality work during our time spent working together on various projects, as well as when winning prizes in a multitude of hackathons during which the team's skillset was invaluable in securing all of our team's wins.
E. N., Senior Smart Contract Engineer
Just amazing, clear and great event.
R. G., attendee at a protocol launch event we ran

Milestones, not hours

We agree what done looks like, cut it into pieces, and you pay against delivery. Hourly billing pays an agency to sit in a patch that stopped producing. We would rather be paid for the decision than for the residence time.

  1. Diagnose and plan

    An initial 30 minute introduction, then a one week paid diagnostic that ends in an initial plan. You can stop after it and keep the plan.

  2. Slice it

    Milestones with written acceptance criteria. Each one small enough that you can stop after it without stranding the work or the people doing it.

  3. Fix the price

    Scope and fee are agreed before anything starts. No hourly drift, no surprise invoice, and no reason on our side to make the work take longer.

  4. Deliver and hand over

    You get artifacts your team can run without us. When the work needs a sharper specialist than we are, we say so and bring one in on the same terms.

  5. Decide

    Continue, re-scope, or leave the patch. Leaving is a legitimate outcome, and if the rate of return says so, we will be the ones to say it first.

Team skillset

Two partners set the scope, then pick the people. Everyone else comes from a bench of specialists we bring in when the work needs them. This is an example of a bench that sat on one client scope.

Partners

  • Business partner Solution architecture, communications, oversight
  • Technical partner Core engineering, CTO

Bench, per scope

  • Marketing and events CMO level
  • Data science Data pipelines and APIs
  • Art direction Brand, web and event identity
  • Consulting Procurement and operations

Who shows up, and how much of them

At most three engagements at a time. That is a promise of priority: the people on your work are not split across a dozen accounts, and when you need an answer, the partner who scoped it gives it.

Names come with references. We do not publish the partners or the bench on this page. Once we are in a sales conversation or writing a scope, we name who would sit on your work and put you in front of someone they have worked for.

Costs outside the work are scoped separately. Media, events and travel are priced on their own line. They are never hidden inside a strategy fee.

The first paid milestone

The one week diagnostic

It starts after an initial 30 minute introduction, and only if that conversation shows a problem we can work on. The week produces an initial plan that identifies what is actually blocking you and sets out the milestones that get you past it. A plan built on the real problem costs far less than executing the wrong brief well.

Interviews

Your team first, then the people whose decisions matter: users, integrators, partners or buyers, wherever the answer is most likely to be.

Research

A read of everything you can share: architecture, docs, repo, data, past campaigns. Then the market around it, and what entering each segment would cost.

Initial plan

A written report: what is actually blocking you, the segments worth testing, and a first set of milestones with acceptance criteria and a price.

Price From EUR 1,500. The final fee reflects the technical complexity of your system and the depth of documentation and access you can provide.

Your exit You can stop after the week. The plan, report and analysis are yours to keep and use.

Outside it Media, events and travel are scoped and priced separately.

Start with the problem, not the package

Pick the closest thing below so the subject line is useful, then tell us what is actually going wrong. Be blunt about it. If we are the wrong people for the job, we will say so in the first reply and point you at someone better.

Fastest: Signal. Message us there and we will set up the initial 30 minute introduction. Prefer email? Pick the closest fit on the right and your email app opens with starter text you can edit. If it does not open, use Copy message text and paste it into your own client.

Message us on Signal
Signal
m_f.27
Email
mf@foragers.io
Elsewhere
GitHub: DeBelg (business partner) Tranquil-Flow (technical partner)

Nothing is submitted to us from this page. It only prepares a draft in your own email client.

Open email draft