SALES DASHBOARDS · セールス ダッシュボード

Japanese sales dashboards need Japanese-language KPI labels, an April-to-March fiscal year configuration, and activity metrics that reflect the Japanese sales process — not a US-designed dashboard translated into Japanese

The majority of CRM dashboards deployed at Japanese businesses are configured by the same implementation partners who serve the US and European markets. The fiscal year starts in January. The KPI labels are in English. The activity metrics track call volume and email cadence, which are secondary to the meeting cadence and internal approval cycle that actually drives Japanese B2B sales velocity. A dashboard that does not reflect how Japanese businesses sell does not get used. The sales team glances at it in the weekly meeting and then continues tracking progress on a spreadsheet because the spreadsheet was built for the Japanese process. We configure and build sales dashboards for Japanese businesses that reflect the April-to-March fiscal year, use Japanese-language field labels and titles where required, and include the activity metrics that matter in a Japanese B2B sales environment.

Request a Dashboard Build → View the evidence →
This is for you if

This is for Nepali business owners and sales managers who:

Check booking and revenue numbers by asking a team member, then wait for them to count

Run end-of-month reports by having someone copy figures from multiple sources into a spreadsheet

Have no single place that shows enquiries, conversion rates, revenue, and team activity together

Do not know what percentage of enquiries become actual bookings, or where most leads drop off

Cannot tell, without asking, how many calls or follow-up messages their sales team made last week

This applies to education businesses, real estate firms, travel and hospitality operators, healthcare providers, and any Nepal-based service business where enquiry volume and conversion rate directly determine monthly revenue.

What's broken

Problems We Solve

Salesforce dashboards using English KPI names for a Japanese team

A Japanese sales team reviewing dashboards with English field names such as "Amount", "Stage", and "Close Date" is not using those dashboards as their primary reference. This is not a preference issue. It is a comprehension and adoption issue. When a field label does not match the term a salesperson uses in their daily work, the dashboard becomes something they consult once a week in a meeting rather than something they update and rely on. Salesforce supports Japanese-language field labels and dashboard titles. The configuration is available but requires deliberate setup, including translation of field labels, dashboard component titles, and list view column headers. Most implementations skip this because the implementation partner is working in English and the Japanese team has not formally escalated it as a requirement. We configure Salesforce and HubSpot environments with Japanese-language field labels, dashboard titles, and report column headers where required, and we validate the output with Japanese-speaking reviewers before delivery.

Fiscal year set to January-December instead of April-March

The Japanese financial year (会計年度) runs from April to March. Most Japanese businesses, including the overwhelming majority of listed companies and many SMBs, close their books on 31 March. Salesforce and HubSpot default to a January-to-December financial year. The consequence is not subtle. Year-to-date quota attainment calculated against a January-December year in a company whose quota was set against an April-March year is wrong from the first day of April. A sales manager comparing this year's performance against last year's is comparing misaligned periods. Pipeline coverage ratios calculated at year-end in February or March are compared against a quota that still has one month to run. We configure the fiscal year setting in Salesforce and HubSpot to April-March, rebuild the affected standard reports, and verify that YTD, quarter-to-date, and year-over-year comparisons are all calculating against the correct boundaries.

No Rakuten or Yahoo Shopping revenue visible alongside DTC CRM data

Japanese brands selling on both direct-to-consumer channels (tracked via Shopify or WooCommerce, connected to a CRM) and marketplace channels (Rakuten Ichiba, Yahoo Shopping) have two separate revenue streams with no consolidated view. The CRM sees the DTC channel. Rakuten and Yahoo Shopping report separately in their own management consoles. Management sees only the CRM channel's contribution and assumes it represents total revenue. This is not a trivial gap. For many Japanese consumer brands, Rakuten and Yahoo Shopping together account for 40 to 70 percent of total revenue. A sales dashboard that excludes them is not a sales dashboard; it is a partial channel report. We build Looker Studio dashboards that pull DTC CRM data alongside Rakuten and Yahoo Shopping exports (via Google Sheets or automated connectors where available) to produce a consolidated revenue view across all sales channels.

Meeting and ringi activity metrics not in the dashboard

Japanese B2B sales velocity is not measured the same way it is in a US or European sales environment. The number of cold calls made or emails sent is a minor indicator. The metrics that actually predict deal progression in a Japanese enterprise sales cycle are: number of meetings held with the prospect (including how senior the attendees were), whether an internal approval process (稟議, ringi) has been initiated, and whether a formal proposal has been submitted and received by the correct approver. A standard Salesforce or HubSpot activity dashboard measuring call count and email open rate is not measuring the right things. The result is a dashboard that cannot tell a sales director whether a deal is genuinely progressing or stalled behind an internal approval that may take three months. We configure custom activity object fields and dashboard components in Salesforce and HubSpot to track meeting count and seniority, ringi initiation status, and proposal submission stage, producing activity reports that reflect the actual progression indicators in Japanese enterprise sales.

What we engineer

What we build for Nepali businesses

Looker Studio dashboard builds

pulling data from Google Sheets, Google Analytics, Facebook Ads, Google Ads, and CRM connectors available at no cost

Conversion funnel reporting

showing the drop-off rate at each stage from first enquiry to closed booking

Revenue tracking

by week and month, with comparison to the previous period

Lead source attribution

showing which channel — organic search, Facebook, Google, referral, direct — is producing the highest volume and best conversion rate

Team activity reporting

showing calls made, messages sent, and follow-up completions per team member

GoHighLevel and HubSpot Free reporting configuration

for businesses that have a basic CRM but have not set up reporting inside it

Shareable dashboard links

that the business owner can open from any device without logging into four separate tools

Request a Dashboard Build →
What changes

What a Nepali business looks like after a dashboard is built

Before
After
Before Revenue data sits in the accounting system. Enquiry data sits in WhatsApp. Booking data sits in a Google Sheet. Ad performance data sits in Facebook Ads Manager and Google Ads. These four sources are never combined into a single view. When the business owner wants to understand performance, they get a fragmented picture from four separate systems, none of which talk to each other. Pulling a meaningful weekly or monthly picture requires manual effort every time, and the picture is never complete because one person controls each source.
After Reporting time drops to zero — no more manual monthly compilation; the dashboard is always current
Before Someone on the team spends two to four hours each month copying numbers from multiple sources into a reporting spreadsheet. By the time the report is shared with the business owner or management team, the numbers are already a week or more out of date. Decisions made from that report are based on a lagging snapshot, not current reality. A Looker Studio dashboard connected directly to Google Sheets, Google Analytics, and basic CRM sources produces the same report in real time, with zero manual compilation effort.
After Conversion rate becomes visible — for the first time, the business knows the actual enquiry-to-booking rate and can set a realistic improvement target
Before The business does not know what percentage of enquiries become quotes. It does not know what percentage of quotes become bookings. It does not know where in the process most leads stop progressing. Without funnel visibility, there is no data-supported answer to the most important question in sales: which step in the process, if improved, would have the largest impact on revenue? Investing in more lead generation when the conversion rate between quote and booking is 20 percent is a much lower-leverage decision than fixing the conversion rate first.
After Lead source data informs ad spend decisions — when the dashboard shows that Facebook Ads produce twice the volume but half the conversion rate of Google Ads, the budget allocation decision becomes straightforward
Before The business owner has no visibility into how many calls or follow-up messages each team member made in the past week. Performance management relies on subjective impressions and the volume of visible WhatsApp activity. There is no report showing which salesperson is most active, which has the highest conversion rate, or which is sitting on a high number of stale leads. Activity data is the leading indicator of revenue. Without it, the only performance signal available is the lagging result: revenue at the end of the month.
After Team activity becomes a manageable metric — activity data turns a subjective performance conversation into a specific one
How it works

How we build a Nepali business dashboard

  1. 01

    Data source audit

    Week 1

    We map every data source the business currently uses: the Google Sheet tracking bookings, the CRM or GoHighLevel account, the Google Analytics setup, the Facebook Ads account, and the Google Ads account. We identify which sources have reliable, consistent data and which need cleaning or restructuring before they can be used in a dashboard.

  2. 02

    KPI definition

    Week 1

    We work with the business owner to define the four to eight numbers that matter most for their specific business. For most Nepali businesses this is: total enquiries by source, enquiry-to-booking conversion rate, monthly revenue vs target, and team activity by member. We confirm the definitions before building.

  3. 03

    Data connection and structure

    Week 2

    We connect each data source to Looker Studio using available free connectors. Where a direct connector does not exist, we set up a Google Sheets structure that the team updates and that feeds the dashboard automatically. We clean any data quality issues at this stage.

  4. 04

    Dashboard build

    Week 2-3

    We build the dashboard in Looker Studio with the agreed KPIs, conversion funnel view, lead source breakdown, and team activity report. We configure date range controls so the business owner can view any period without changing the underlying data.

  5. 05

    Handover and training

    Week 3

    We share the dashboard link, walk the business owner and relevant team members through each section, and document the data sources connected. We confirm the team can update data sources without our involvement.

Request a Dashboard Build →
Common questions

FAQs

How do I configure Japanese-language field labels and dashboard titles in Salesforce?

Salesforce supports translated field labels through the Translation Workbench feature, which is available in Enterprise edition and above. To configure Japanese-language labels, you enable the Translation Workbench in Setup, add Japanese as a supported language, and then translate each field label, picklist value, and dashboard component title individually. The Translation Workbench covers standard and custom fields, list view column headers, report column headers, and dashboard component titles. Users with their Salesforce language preference set to Japanese will see the translated labels automatically. The most common gap is that custom fields added after the initial translation setup are left in English, so a periodic review of untranslated fields is necessary.

How do I set the Japanese fiscal year (April to March) in Salesforce or HubSpot reporting?

In Salesforce, the fiscal year is configured in Setup under Company Information, where you can set the fiscal year start month to April. Salesforce offers both a standard fiscal year (any starting month) and a custom fiscal year (non-standard quarter lengths). For most Japanese businesses, setting April as the fiscal year start month in the standard configuration is sufficient. In HubSpot, the fiscal year start is set in Account Settings under Fiscal Year, available in Sales Hub Professional and above. Once set, HubSpot's built-in date range filters such as "this fiscal year" and "last fiscal year" will use April to March. Both platforms require that existing saved reports be reviewed after the fiscal year change, as date filters referencing "this year" will shift to the new boundary.

How do I build a Looker Studio dashboard combining Rakuten and DTC sales data for a Japanese brand?

Looker Studio does not have a native Rakuten connector. The most reliable approach is to export Rakuten Ichiba sales data from the RMS (Rakuten Merchant Server) as a CSV on a regular schedule, import it into Google Sheets, and connect that Google Sheet to Looker Studio as a data source. DTC data from Shopify connects to Looker Studio via the official Shopify connector or a third-party connector. Yahoo Shopping data follows a similar export-to-Sheets approach. The build involves creating a blended data source in Looker Studio that aligns the date dimensions and revenue fields across the three sources, applies consistent currency formatting, and allows filtering by channel. The main ongoing maintenance requirement is ensuring the Rakuten and Yahoo Shopping export schedules remain consistent.

How do I add ringi status and meeting activity metrics to a Salesforce dashboard for a Japanese sales team?

Ringi status and meeting seniority level are not standard Salesforce fields. The configuration requires creating custom fields on the Opportunity or Activity object: a picklist field for ringi stage (not initiated, initiated, approved, rejected), a number field for meeting count, and a picklist or text field for the seniority level of the most recent prospect meeting attendee. These fields are then added to opportunity page layouts so salespeople can update them, and they are added as columns in opportunity list views and report types. Dashboard components showing ringi stage distribution across the pipeline and meeting count by deal stage then give sales leadership the activity metrics that reflect actual Japanese B2B sales progression.

What sales reporting tool is most commonly used by Japanese enterprises — Salesforce or a domestic tool?

Salesforce is the dominant CRM in large Japanese enterprises, with significant market share across financial services, manufacturing, and professional services. For SMBs, Kintone (by Cybozu) and HubSpot are more common, and some businesses continue using domestic tools such as Sales Force Assistant by NI Consulting or eセールスマネージャー by Softbrain. Power BI is the most widely used dashboard tool for management reporting in Japanese enterprises, partly because Microsoft's Japanese-language support and Japanese localisation have been mature for longer than competing tools. For businesses that are already on Salesforce, Salesforce's native dashboards combined with Tableau (which Salesforce owns) are the most common enterprise-grade reporting stack.

Our team

The people behind the work

Not a black box. Real specialists you can call, with their names on the work.

Niraj Raut

Niraj Raut

Founder — Ecommerce SEO
Keshab Joshi

Keshab Joshi

PPC Expert
Hawrry Bhattarai

Hawrry Bhattarai

Google Ads Expert
Arogya Rijal

Arogya Rijal

SaaS SEO Expert
About Us →
Start here

Ready to see your business numbers in one place?

Most Nepali businesses already have the data — it is just in four separate places and nobody has combined it. A Looker Studio dashboard does not require new software, does not require changing how your team works, and does not require technical knowledge to use once it is built. If you want to stop asking team members what the numbers are and start seeing them directly, we can map your current data sources and tell you exactly what a dashboard would show.

Request a Dashboard Build →