Refine is a React-based enterprise admin framework (open-core, used by 40,000+ organizations). Coconala — Japan's largest freelance platform — rebuilt their entire legal consultation admin panel on Refine and published the full engineering account on Zenn. That is not a side project: it is a Japanese unicorn using Refine in production and publishing about it publicly. Below is what stands between that adoption signal and Refine capturing more of the Japanese market.
Coconala, Japan's largest freelance platform (listed on TSE, 3 million+ users), rebuilt their legal consultation management admin panel using Refine and published a detailed engineering article on Zenn. The article describes choosing Refine over alternatives, implementation decisions, and 6 months of production usage. It is public, detailed, and signed by Coconala's engineering team.
zenn.dev/coconala/articles/58553170d35593 — 「Refineでコナラ法律相談管理画面を作り直した話」Coconala is the kind of Japanese reference customer that closes enterprise deals. A Japanese engineer evaluating admin frameworks will search Zenn and find this article — but then arrive at a Refine site with no Japanese content and no acknowledgment that this category of Japanese adoption exists. The conversion signal is already there; Refine is not positioned to capture the next wave of Japanese teams who follow Coconala's lead.
A Japanese case study page (even a translated version of the Zenn article, with Coconala's permission) and a Japanese-language landing page for the enterprise/admin use case. This converts a public proof point that already exists into an official funnel entry for Japanese teams.
The refine.dev site and its documentation are English-only. No Japanese locale exists in the product, and no Japanese translation of the documentation exists. Despite real Japanese production adoption (Coconala), Refine has made no investment in any Japanese-language surface.
refine.dev (lang="en", no language switcher confirmed)Refine is a framework — the engineering team using it reads English. But when a Japanese company wants to expand usage beyond the initial integration team or needs to onboard new engineers, the lack of Japanese documentation becomes a barrier. In Japanese enterprise contexts, tools with Japanese documentation signal organizational maturity.
Japanese-language documentation for the most-used features (data providers, CRUD views, auth). The Coconala article already describes the real-world Japanese use case — that is a starting point for what Japanese teams actually need.
refine.dev has Terms of Service and Privacy Policy, but no 特商法に基づく表記. This is directly relevant for Refine's paid Cloud, Team, and Enterprise tiers.
refine.dev/enterprise (Enterprise/Team/Pro tiers — no 特商法 in footer)The Coconala usage is on the open-source core. But if Coconala or a similar Japanese company wants to evaluate Refine Cloud or Enterprise, the procurement team will look for the 特商法 page. Its absence blocks the conversation at the contract stage specifically — not at the technical evaluation stage, but after the engineering team has already decided they want it.
A 特商法に基づく表記 page covering the paid products. Standard template. < 1 day.
Refine Cloud and Team pricing is listed in USD. No JPY display is available. Enterprise pricing is custom, but the reference frame is USD.
For a listed Japanese company like Coconala considering a paid Refine tier, a USD-denominated contract requires additional approvals compared to a JPY contract. The technical team wants the product; procurement introduces the currency friction. JPY pricing is the difference between procurement rubber-stamping an approval and asking questions.
JPY display pricing. For Enterprise, a JPY invoicing option. Configuration-level fix.
No Japanese-language Refine page exists on refine.dev, so queries like 「React 管理画面 フレームワーク」 or 「admin panel OSS」 return no Refine results from the official site. The Coconala Zenn article appears in search results, but it links to an English product — there is no Japanese landing page to absorb that traffic.
A Japanese engineering team evaluating options for an internal admin tool will search in Japanese. Refine is absent from those results. The teams that find Refine in this context find it via the Coconala article — a single community-created proof point doing the discovery work that Refine's own site should be doing.
A Japanese landing page for the admin framework use case, ideally referencing the Coconala production example. Short pages with specific use-case framing rank better for these queries than translated marketing copy.
Five signal dimensions, each 0–20. Verified against the live site on 2026-06-20:
| 1. Japanese marketing funnel | 2 / 20 |
| 2. Legal / trust (特商法) | 0 / 20 |
| 3. JPY billing / payment | 0 / 20 |
| 4. JP search visibility | 3 / 20 |
| 5. Product locale / IME / UX | 12 / 20 |
Dimension 4 scores slightly higher than 0 because the Coconala Zenn article creates some organic JP search presence for Refine, even though it is community-created not official. Dimension 5 is penalized because Refine, as a framework, has no JP locale at all — the product doesn't speak Japanese even partially.
This map is the free slice. The full Japan-readiness audit covers the same gaps end-to-end, with specific copy, the 特商法 fields filled in, a ranked impact list, and a concrete action plan — delivered as a paid audit.
Data verified 2026-06-20 against refine.dev, refine.dev/enterprise, and Coconala Zenn article. If something here is wrong or you'd like this page removed: hello@glovrex.com.