Inquiry contact. Use contact@leefan.co.jp. No form, scheduling link, or external tracker is used on this page.

Contact

There are three real ways to reach the operator behind Leefan Reports. Each one is read by the same person. None of them is read faster than the others, so pick the one that fits what you actually want to say.

If you have not read the /about page yet, that is a better first stop than this page. /about names the operator and states what the practice does and does not do today; this page is just routing.

1. The three surfaces

If you want to…	Use this surface	Read by	Typical response window
Discuss a paid engagement, ask about scope, or request a discovery call	`contact@leefan.co.jp`	The operator named on /about.	Two business days.
File a correction, a replication note, or a benchmark disagreement on a specific library page	`contact@leefan.co.jp (subject: correction or replication)` with the `correction` or `replication` template	The same operator.	Two business days, or a short “won’t address — here is why” note.
Press / podcast / conference / community invitation	`contact@leefan.co.jp`	The same operator.	Five business days. We are slower on these on purpose.

There is no scheduling-link dropped on this page. A discovery call is scheduled by reply from contact@leefan.co.jp, after the operator has read the request.

2. What to put in an inquiry (one paragraph each, max)

What kind of operation you run: rough scale, tooling, who is doing the work today.
The specific question or problem: the bug you are looking at, the audit you want, the methodology piece you want help applying. Specificity beats breadth.
The shape of help you are imagining: hourly review, fixed-scope audit, longer engagement. We will tell you honestly if that shape is wrong for the problem.
Any constraints we should know up front: NDA, language, time-zone, regulatory environment.

We do not need a written brief, a deck, or pre-call homework. A four-paragraph email is plenty.

What we explicitly do not ask for at inquiry time:

Budget. We will quote against the work; you can disagree with the quote.
A list of competing operators you are also evaluating. Not our business.
A signed NDA before the first reply. We will sign one before the call if your inquiry touches confidential material.

3. What to put in a companion-repo issue

correction — “I think a claim on this page is wrong.” Include the page URL, the specific sentence or table cell, and what you think is correct.
replication — “I reran a benchmark and got a different result.” Include the page URL, the benchmark inputs you used, the run logs, and the result you got.

We do not accept pull requests for new pages, new vendor comparisons, or new diagnostics at v1. If you have a comparison you think should exist, send it as an inquiry.

4. What this page is not

No live chat widget. No persistent floating button on any page.
No contact form.
No “book a 15-minute call” calendar.
No waitlist. No “limited availability”. No “next cohort”.
No NPS / “rate this site” prompt.
No autoresponder beyond a single confirmation line.

5. Response cadence (the part we will not negotiate down)

Two business days for contact@leefan.co.jp. “Business day” means Tokyo time, Monday–Friday excluding JP national holidays. A reply that lands later than two business days is a defect.
Two business days for issues. A “won’t address — here is why” reply counts as a real reply; an empty queue is what we owe you, not a closed ticket.
Five business days for press / podcast / community notes. Press / podcast / community contacts are batched for efficiency; this is the honest cadence.

If you have not heard from us inside the window, the reason is one of: (a) the message landed in spam; (b) the operator is offline; (c) we have failed to keep our own SLA. There is no fourth reason.

6. What language we reply in

Inquiries in Japanese are answered in Japanese. Inquiries in English are answered in English. We do not run automatic translation on inbound messages.

7. What the operator will not do via this contact surface

Sign an affiliate agreement “so we can list each other”. The site has no affiliate links and is not joining a reciprocal-promotion program.
Accept paid placement in a sponsored newsletter / podcast / listicle.
Ghost-write a methodology page under your brand.
Give a 30-minute “free” consult on your specific pSEO problem. That is what a paid engagement is for.
Remove a page because a vendor disagrees with the take. Substantive corrections, yes; vendor takedown requests, no.