Minutely 日本@minutely_example
会議の文字起こしから、担当者と期限つきのタスクを自動で抜き出せるようになりました。
日本語の会議にも対応しています。
設定方法はこちら:minutely.example/
Japanese operations for SaaS and AI teams
Send us your English updates. We keep your Japanese website current, publish X posts and articles, and handle first-line Japanese inquiries, within the plan you choose.
If your site is a fit, within three business days: a Japanese headline, subheading and button for your homepage, with an English explanation. No call needed.
Samples for Minutely, a fictional AI meeting-notes app
読まれる議事録を、数分で。
会議の要点・決まったこと・タスクを、Minutelyがまとめます。
無料で試してみる
1ユーザーあたり月額12ドル(年払い)
Minutely 日本@minutely_example
会議の文字起こしから、担当者と期限つきのタスクを自動で抜き出せるようになりました。
日本語の会議にも対応しています。
設定方法はこちら:minutely.example/
請求書払いについて
請求書払いに対応していますか?法人で年払いを検討しています。
はい、年払いのTeamプラン以上で請求書払いに対応しています。お見積もりと請求書の発行は、管理画面の[請求]からお申し込みいただけます。
Approved answer: Help center › Billing
Summary for your teamAsks whether a company can pay by invoice for an annual plan. Answered from the billing docs: invoices are available on annual Team plans and above. No action needed.
Japan monthly report
Minutely · September 2026
Weekly sessions from Japan (GA4)
Mentions in Japanese (X and Google)
What’s included depends on your plan. See Pricing.
Switch between an English homepage, a word-for-word translation and our rewrite. The notes below say what we changed and why.
Ship meeting notes your team actually reads.
Minutely turns every call into a summary, decisions and tasks, in minutes.
$12 per seat / month, billed annually
あなたのチームが実際に読む会議メモを出荷しましょう。
Minutelyは、すべての通話を数分で要約、決定、タスクに変えます。
シートあたり月額12ドル、年間請求
読まれる議事録を、数分で。
会議の要点・決まったこと・タスクを、Minutelyがまとめます。
1ユーザーあたり月額12ドル(年払い)
The English the client sends us. Compare it with the two Japanese versions.
The meaning comes through, but it reads as translated text. Choose Edodana to see what we change and why.
Why each line changed
This is the approval packet you get twice a month. The product is made up.
Japanese post for X
Minutely 日本@minutely_example
会議の文字起こしから、担当者と期限つきのタスクを自動で抜き出せるようになりました。
日本語の会議にも対応しています。
設定方法はこちら:minutely.example/
English summary
Announces that Minutely now pulls tasks out of meeting transcripts, each with an owner and a due date, and that this works for meetings held in Japanese. Links to the setup article on your Japanese blog.
Please confirm
A person on our team replies in Japanese, using the answers you approved at the start. Your team gets a summary in English. Questions the approved answers don’t cover go to you before we answer them, and the customer gets a short note that we are checking.
Example inquiries
InquiryJapanese
請求書払いに対応していますか?法人で年払いを検討しています。
ReplyJapanese
はい、年払いのTeamプラン以上で請求書払いに対応しています。お見積もりと請求書の発行は、管理画面の[請求]からお申し込みいただけます。
To your teamEnglish
Answered
Asks whether a company can pay by invoice for an annual plan. Answered from the billing docs: invoices are available on annual Team plans and above. No action needed.
With Presence and Complete, you get a report like this once a month: numbers from Google Analytics, Search Console and X, what Japanese users asked, mentions of you and up to three competitors, and proposals for next month based on those numbers. Complete adds a written review that answers your questions.
Japan monthly report
Fictional data
Sessions from Japan
4,860
+13% vs August
August: 4,310
Sessions that started on /ja/
62%
+14 pts vs August
August: 48%
Sign-ups from Japan
71
+37% vs August
Sign-up rate 1.46% (August 1.21%)
Impressions on X
52,400
+19% vs August
Engagement rate 3.1% (August 2.8%)
Google Analytics 4 · August and September 2026
| Week | Sessions |
|---|---|
| August W1 | 980 |
| August W2 | 1,020 |
| August W3 | 1,110 |
| August W4 | 1,200 |
| September W1 | 1,090 |
| September W2 | 1,180 (Setup article published, September 9) |
| September W3 | 1,260 |
| September W4 | 1,330 |
The setup article at /ja/blog/tasks went live on September 9. In September it was the second most common entry page for sessions from Japan (880 sessions).
Main entry pages · Google Analytics 4
| Entry page | Sessions | Sign-up rate |
|---|---|---|
| /ja/Japanese home page | 1,560 | 1.9% |
| /ja/blog/tasksSetup article, Sep 9 | 880 | 2.4% |
| /ja/pricingJapanese pricing page | 540 | 1.3% |
| /English home page | 520 | 0.4% |
Visitors from Japan who start on the English home page sign up at 0.4%, about a fifth of the rate on /ja/ (1.9%).
Search Console · country: Japan
| Search term | Clicks | Impressions | CTR | Position |
|---|---|---|---|---|
| 議事録 自動 作成 | 210 | 6,900 | 3.0% | 8.1 |
| 議事録 AI | 180 | 7,400 | 2.4% | 11.3 |
| 会議 文字起こし ツール | 150 | 5,200 | 2.9% | 12.6 |
| minutely 料金 | 120 | 410 | 29.3% | 1.4 |
| 議事録 タスク 抽出 | 95 | 1,900 | 5.0% | 6.8 |
“議事録 AI” has the most impressions of any term but sits on page two (11.3). “minutely 料金” is a brand search: few impressions, a high click rate.
Blog, X and the Japanese site
| Date | Published |
|---|---|
| Sep 9 | How-to article: setting up task extraction/ja/blog/tasks |
| Sep 24 | How-to article: sharing notes with your team/ja/blog/share |
| Sep 1–30 | 10 posts on X@minutely_example |
| Date | Site change |
|---|---|
| Sep 4 | Updated the price table to match the new prices on your English page/ja/pricing |
| Sep 10 | Added a link to the new setup article/ja/ |
| Sep 18 | Fixed a broken link found in the monthly check/ja/faq |
Plan use in September: 2 of 2 articles, 10 of 10 X posts, 3 of up to 4 small updates.
X Analytics · @minutely_example
Japanese posts on X and Japanese Google results, September
| Product | Mentions |
|---|---|
| Competitor A | 120 |
| Competitor B | 64 |
| Minutely | 46 |
| Competitor C | 18 |
Competitor A is mentioned about 2.6 times as often as Minutely.
Helpdesk
| Topics | Inquiries |
|---|---|
| Paying by invoice | 3 |
| Accuracy in Japanese meetings | 2 |
| Where data is stored | 2 |
| SSO | 1 |
| Education pricing | 1 |
Write one of October’s how-to articles about AI meeting notes, the topic people search for as “議事録 AI”.
Add paying by invoice to the Japanese FAQ.
Rewrite the opening of /ja/pricing.
Tell us which ones to go ahead with. Nothing is published until you approve it.
Complete plan · your question this month
Your question
Should we translate the help center next?
Our answer
Not all of it yet. Start with pages on the three topics Japanese users asked about most in September: paying by invoice (3 of 9 inquiries), accuracy in Japanese meetings (2) and where data is stored (2). Japanese pages on these three topics would have covered 7 of the 9 inquiries.
The data storage page needs your answer first: which region stores customer data. We suggest looking at the rest of the help center again after two more months of inquiries.
These pages are outside your plan. If you want us to write them, we will quote them as Flex hours before we start.
Prices in US dollars. Pick one monthly plan and add the Japanese inbox or extra articles if you need them. One-time work, such as Japan Audit or Site Fix, can be ordered on its own, without a plan.
Example: you have no Japanese site yet. You pay $2,900 once for Japan Launch, one page. Presence, at $1,200 a month, starts in the month the new page goes live.
| Care$450 / month | Recommended startPresence$1,200 / month | Complete$2,400 / month | |
|---|---|---|---|
| Good for | Keeping a Japanese site in step with your English one | Starting to talk to Japanese users | Japanese users already writing to you |
| Website | Up to 4 small updates a month and a monthly check of key pages | Same as Care | Same as Care |
| X posts | — | 8 a month | 10 a month |
| Articles | — | 1 a month | 2 a month |
| Japanese Inbox | Optional: 5 a month for +$450 | Optional: 5 a month for +$450 | Included, 10 a month (5 more for +$450) |
| Reporting | Change log | Monthly report and a weekly Slack update | Same as Presence, plus a written monthly review that answers your questions |
Care$450 / month
Recommended start
Presence$1,200 / month
Complete$2,400 / month
| Service | What you get | Time | Price |
|---|---|---|---|
| Japan Audit | Review of three key pages, X and your contact flow, a short comparison with three Japanese competitors, and a 90-day plan. If you start website work (Site Fix or Japan Launch), Presence or Complete within 60 days, the $500 comes off its first invoice. | 5 business days | $500 |
| Site Fix | Up to five existing Japanese pages, checked against your English source, rewritten, implemented and published. | 3–4 weeks | $1,900 |
| Japan Launch, one page | A new Japanese landing page with FAQ and contact form, plus a blog template. | 5–6 weeks | $2,900 |
| Japan Launch, five pages | Home, features, use cases, pricing and FAQ/contact, plus a blog. | 9–10 weeks | $4,900 |
| AI feature | An AI feature on your Japanese site, for example a chat assistant that answers in Japanese from your docs. Fixed price once we agree on the scope. Running costs, such as AI API usage and hosting, and any upkeep are quoted with the build. | Depends on scope | Quote |
Copy & QA: if we can’t publish on your stack, for example a custom Next.js site, we deliver copy ready for your engineers and check the live pages after they ship. Site Fix $1,400, Japan Launch $2,000 (one page) or $3,500 (five pages). Timelines start once we have access and materials.
Your own tool costs are separate, for example a Webflow site plan, a helpdesk seat or note pro.
Every month
$1,200
One-time
$0
Every month
One-time
AI features are quoted separately, once we agree on the scope.
This is an estimate. Before any work starts, we confirm a fixed price in writing.
Send us your site and we reply within one business day. If we can help, within three business days you get a Japanese headline, subheading and button for your homepage, on a one-page English note that shows before and after and explains each change.
We review three key pages, your X account and your contact flow, and agree with you on what to measure over the first 90 days.
We fix your Japanese site or build new pages, preferably under /ja/ on your own CMS.
Twice a month you get an approval packet: Japanese drafts, English summaries, and a list of every claim, number and condition to check. Nothing goes on your site or X until you approve it.
Then the cycle starts again the next month.
Your team owns the domain and every account. We work through delegated access and never ask for passwords.
Already have a Japanese site that works? Go straight to a monthly plan. Needs fixing? Start with Site Fix. Need a new one? Start with Japan Launch. You can also order website work without a monthly plan. If you add one, it starts in the month your website work goes live (for Site Fix, the month the rewritten pages are published), or right away if there is no website work.
Edodana is run by VectorMoon Inc., a software company in Osaka, Japan. VectorMoon develops KnowKnow, an AI that checks business documents against standards and internal rules, and builds software for clients. We read your release notes and docs the way a Japanese user would, and we can also build AI features for your Japanese site, quoted separately.
edo-dana · a merchant house’s branch in Edo
In the Edo period, merchant houses from Kyoto, Osaka and Ise ran branches in Edo, today’s Tokyo, through a trusted manager who reported to the head shop. Edodana works the same way for your company in Japan.
You do. Domains, X, your CMS and your helpdesk stay in your name, and we work through delegated roles. If we stop working together, you keep every page, draft, glossary and log.
Yes. We deliver copy and assets ready for your engineers, then check the live pages after they ship. That is the Copy & QA option under Pricing.
We work inside your helpdesk, such as Intercom, Zendesk or HubSpot, with one seat. Japanese tickets get a JP tag and a reply in Japanese. Anything your team needs to decide comes with an English summary.
Our standard is your own blog. note is a Japanese blogging service. If you use note pro (¥80,000 a month before tax, paid by you) and give us a member role, we publish there too. With a free note account, we deliver the finished post and you publish it.
Yes. Monthly plans run month to month. Give us 30 days’ notice.
We pass them to you with an English summary. We can prepare Japanese answers from material you approve, but the decisions stay with your team.
Send us your website and we reply within one business day. If we can help, within three business days you get a Japanese headline, subheading and main button for your homepage, on a one-page English note that puts before and after side by side and explains each change. No call needed.