From Yakitori to Web3: A Practical DX Playbook for Local Governments

Okamu's Ideas
From Yakitori to Web3: A Practical DX Playbook for Local Governments

どうも〜おかむーです!

  • Small towns need digital transformation that actually connects with people, not just systems.
  • Local governments can attract remote talent and boost the economy (Fukuoka saw ¥140M in one program) by combining DX, APIs, and community design.
  • My proposal: a low-cost, open, people-centered platform that leverages MyNumber APIs, local events, and AI-driven creator tools.

結論

Local governments should run a pragmatic, open DX program that: 1) opens usable APIs (MyNumber/PMH where possible), 2) builds community-first services (marketplace + events), and 3) uses lightweight AI/Web3 tools to onboard citizens and remote workers. 要するに、技術で行政を固めるのではなく、人と接続するためにDXを使う、ということです。

本文

I grew up in my dad's yakitori shop "Hodohodo" in Fukuoka — I was the signboard kid, serving customers and learning that people are everything. At Kyushu Institute of Technology I ran the startup circle P&D, and that taught me how to motivate volunteers without money. After graduating I joined Kayac immediately as an iOS/backend engineer, then went freelance and eventually founded no plan inc. in 2019 and NoGears in 2025. Along the way I built things like GawainAI and ReCone, and even a tiny dating app "5 hours only Cinderella Time" that led two friends to get married — real proof that product design can change lives.

Now look at the challenge local governments face: this is DX season, and it isn't just about replacing paper with PDFs. Digital nomad initiatives are already showing measurable returns — Fukuoka reported about ¥140,000,000 in economic effect from attracting remote workers (see Colive Fukuoka 2025 program). At the same time, the MyNumber portal APIs and related services are expanding (the government notes ~197 services using MyNa APIs), but municipalities struggle to turn those building blocks into citizen-facing value.

From my failures (like the wedding app that failed at the moment-of-use) and successes (ReCone onboarding mainstream fans to NFTs, choosing debt financing to keep control, and making AI tools that automate creative promos), I learned three practical rules:

1) Start with a real human moment. In the yakitori shop we didn't digitize the menu — we made conversation. Local DX should start with community moments: festivals, markets, daycare pickup, tax filing night.

2) Use open, composable APIs. The central MyNumber/PMH APIs are infrastructure — municipalities should wrap them into simple SDKs and low-code templates so small vendors and civic hackers can build services quickly.

3) Incentivize creators and remote talent. Run short, reward-driven contests (hackathons, creator residencies) that use Web3 badges or small grants; creators can use tools like GawainAI to produce promotional vertical videos at scale.

Concretely: a pilot "Local Life SDK" for a city that includes MyNa-backed identity flows, an events marketplace, and a creator toolkit. Pair that with monthly IRL events (market + co-working + tasting — yes, like my dad's shop vibe) to convert visitors into longer stays. Fund it with modest debt or sponsorships — I've done the debt route before at no plan inc. and it preserves mission.

まとめ

  • People-first DX beats paperwork-first DX.
  • Combine national APIs (MyNumber/PMH), local community design, and lightweight AI/Web3 tools.
  • Pilot with measurable KPIs: economic impact, residency nights, service adoption.

おかむーから一言

I want to see towns where tech brings people closer, not drives them away. Let's build DX that smells a bit like yakitori, tastes like local wine, and actually helps people live better.