Gibier utilization intelligence
Inspect the official source ledger, calculated gaps, method notes, and interactive view built from MAFF's public data.
Open the public intelligence mapRestaurant services
Good sourcing is not just finding something rare. The product has to arrive, fit the kitchen, make sense on the menu, and be easy for staff to explain.
Typical engagement path
1
Understand the restaurant, menu, audience, sourcing problem, and current web/search gaps.
2
Map possible producers, regions, products, limits, and the questions to ask first.
3
Check season, volume, samples, communication, documents, ordering, and follow-up.
4
Create chef notes, menu language, buyer materials, web/search updates, and a follow-up record the team can keep using.
What we check before recommending a lead
Product context
Where it comes from, who makes it, how it is produced, when it is available, and what can be said plainly.
Restaurant fit
Menu use, prep, storage, portions, staff explanation, and whether the product earns its place.
Ordering path
Samples, lead time, minimums where known, paperwork, communication, payment/admin friction, and who follows up.
Public story
What the menu, website, Google profile, and search pages can say without stretching the truth.
What this does not promise
Wild Food Japan does not guarantee availability, pricing, logistics, permits, exclusivity, or supplier acceptance. The point is to find out what is worth pursuing before the restaurant spends time, menu space, or staff attention on it.
Practical outputs
The story only matters if the team can use it.
Source map
A short map of possible producers, regions, products, limits, and the checks needed before contact or menu planning.
Chef notes
Brief notes on use cases, sample questions, prep, and language staff can repeat.
Relationship notes
Contacts, message history, availability checks, documents, admin issues, and follow-up tasks kept in one place.
Menu differentiation
Domestic products with a clear reason to be there: source, season, import alternative, or a story staff can explain.
Web and search
Website, Google Business, local search, content, photos, and public copy that make the sourcing visible.
Ongoing support
For teams that need research, relationship management, web/content support, and cleanup over time, not a one-time list.
Public work, open to inspection
See how the research is structured before you inquire.
These are public research and editorial examples—not client testimonials or outcome claims. They show how sources, limits, route questions, and next actions are organized.
Source-led decision note
See a working example that separates the short answer, cited evidence, operational interpretation, and known constraints.
Read the cited briefingField context and related work
Review the operator background, public projects, field images, and the boundaries used when handling sourcing relationships.
Review the field backgroundIllustrative working-memo structure
Decision to make → verified facts and source URLs → unknowns and boundaries → next check, owner, and follow-up.
This is a sample structure, not a client document.
Have a real sourcing question?
Send a free inquiry if you need to check fit. Choose the paid working session when you already have one concrete decision to work through.