The "Lost After Launch" Problem That Comes From KPI-Free Commissioning
When commissioning a website build or renewal, most clients center their discussions around design, features, and page structure. Yet the most important question often gets pushed back: "What does success look like for this site — and how much of it counts as success?"
Launching into a build without defining KPIs (Key Performance Indicators) creates two problems after the site goes live. First, there is no way to measure effectiveness. Without numbers to compare before and after, there is no basis for investment decisions or continuous improvement. Second, decisions become impossible. When the question arises of whether to change page content or invest in advertising, there is no reference figure to guide the answer.
A typical failure case: a small manufacturer invested 1.5 million yen in a corporate site renewal. Three months after launch, the development company reported that "access numbers increased." But the business owner was left with a vague "so what?" feeling. Inquiry counts had not changed. Recruitment applications had not increased. Because there was no benchmark to judge the renewal as a success or failure, the decision of whether to take additional action was stuck for six months.
The root cause is simple: KPIs were never designed before the build. The development company built exactly what was requested. The client was satisfied with the appearance. But because there was no numerical definition of what the site was for, there was no axis for evaluating outcomes.
KPI design is the client's job, not the development company's. The development company is the expert in how to build — but deciding what to achieve is the client's responsibility. Completing KPI design before issuing the commission is what determines the overall quality of the project.
The Difference Between KGI and KPI: Understanding Goal Hierarchy
Before designing KPIs, it is important to clarify the difference between KGI (Key Goal Indicator) and KPI. Confusing these two and pressing ahead creates a cluster of metrics that can be measured but do not drive action.
KGI (Key Goal Indicator) is the final business goal you want to achieve. In a website context, examples include "120 new inquiries per year," "10 million yen annual e-commerce sales," or "50 recruitment applications per year." KGI is the business goal itself and includes factors that a website alone cannot control — sales capability, product quality, market conditions.
KPI (Key Performance Indicator) measures the intermediate state on the path to reaching the KGI. It tracks, quantitatively, the portion of the process toward the KGI that the site can contribute to. For a KGI of "120 annual inquiries," KPIs might be intermediate metrics such as "5,000 monthly site sessions," "3% inquiry page reach rate," and "20% form submission completion rate."
In practice, it is also valuable to design leading indicators — early signals that can detect problems before KPIs deteriorate. Examples include specific keyword search rankings, bounce rate, and dwell time. Designing with a three-layer structure of leading indicators → KPIs → KGI enables rapid identification of where problems are occurring.
A three-layer design example:
| Layer | Metric Name | Target Example | |---|---|---| | KGI | Annual new inquiries | 120 | | KPI | Monthly sessions | 5,000 | | KPI | Inquiry page reach rate | 3% | | KPI | Form submission completion rate | 20% | | Leading indicator | Primary keyword ranking | Top 10 | | Leading indicator | Bounce rate | Under 60% |
This structure makes it possible to judge from the numbers whether a "no increase in inquiries" problem stems from insufficient traffic, visitors arriving but bouncing, or drop-off at the form.
The typical mistake of confusing KGI and KPI is "treating the KGI as a KPI." Tracking "increase inquiry count" as a KPI on a weekly basis does not connect to actionable improvement. KPIs need to be broken down to the granularity where they become a handle for improvement.
The Practical Process for Web KPI Design: What to Confirm Before Commissioning
The KPI design process follows the sequence: confirm the KGI → build the KPI tree → confirm measurement methods. Respecting this order matters. Starting from measurement methods leads to distorted KPI design that chases only what is easy to measure.
Step 1: Back-calculate the KGI from business goals
Begin by identifying the business goal the website should ultimately contribute to. The specificity needed is not "increase sales" but "increase orders from new inquiries by five per month by the end of this fiscal year."
The question for setting the KGI is: "If we spend one million yen on this site, what would need to be different twelve months from now for the investment to have succeeded?" If you cannot answer this, the groundwork for setting a KGI is not yet in place.
Step 2: Break down the KGI into a KPI tree
If the KGI is "increase monthly inquiries by ten," work backwards from the goal to map the process.
10 monthly inquiries
↑ Form submission completion rate 20%
↑ Inquiry page reach 50 per month
↑ Service page visitors 500 per month
↑ Monthly sessions 3,000
↑ Search traffic / paid traffic / social traffic
Breaking down the top-level goal this way naturally produces the KPIs that need to be achieved and the target values for each metric.
Step 3: Confirm measurement methods
For each KPI, decide "which tool, by whom, and when" it will be checked. Standard web measurement uses Google Analytics 4 (GA4), but if it is not set up, the setup needs to be included in the build brief.
A KPI without a confirmed measurement method is an unmeasurable KPI — there is no value in setting it. "Improving brand awareness," for example, is an important goal, but it cannot function as a KPI until you decide which number to measure it with.
Step 4: Measure the current state (baseline)
Without recording current values before the build, there is no basis for comparing the improvement effect. If you have an existing site, make sure to capture and record pre-build monthly sessions, inquiry counts, and bounce rate before development begins.
Common KPI Design Traps and How to Avoid Them
Typical failure patterns that recur in KPI design are outlined below. Knowing them in advance prevents failure at the design stage.
Trap 1: The "session count only" vanity metric problem
Access numbers (sessions, page views) are easy to measure, so they get adopted as KPIs. But session count only shows that people came to the site. It does not directly correlate with whether they inquire or purchase.
A site with one million monthly page views contributes nothing to business goals if inquiries are zero. Conversely, one thousand monthly sessions with twenty inquiries directly connects to KGI achievement. Session count should be treated as a leading indicator rather than a KPI, with conversion rate and inquiry count at the center of the KPIs.
Trap 2: Too many KPIs
"Everything matters so everything becomes a KPI" does not work. When there are more than ten KPIs, it becomes impossible to decide what to improve first. Narrow KPIs down to the three to five that must absolutely be tracked. Manage the rest separately as reference metrics.
Trap 3: KPIs that do not drive improvement actions
Calling qualitative goals like "improve UX" or "strengthen credibility" KPIs is meaningless without a measurement value. What should be set as a KPI is "a metric where a change in the number makes the next action clear." For example, "if form completion rate falls below 10%, reduce the number of form fields" — a KPI only functions as one when the metric and the action are tied together.
Trap 4: Goals without achievement criteria
Many cases involve setting only the direction — "increase inquiry count" — without a specific numerical target. This creates a state where it is impossible to judge whether progress has been made. KPIs must always have a target value and a measurement period. The preferred format is something like: "Monthly inquiry count: 10 (current: 3), target to be achieved in 6 months."
KPIs that exist only in the designer's head do not function. KPIs need to be made explicit as commissioning requirements at the requirement definition stage with the development partner.
Example RFP language
Include KPIs explicitly in your RFP (Request for Proposal) or briefing document. Here is an example:
[KPI Requirements]
Project business goal (KGI):
- Increase monthly new inquiries from current 3 to 10 within 12 months
KPIs to track:
- Monthly sessions: current 1,500 → target 4,000 (in 6 months)
- Inquiry form reach rate: current 1.2% → target 3.0%
- Form submission completion rate: current 15% → target 25%
Measurement tool: Google Analytics 4 (setup and configuration to be included in proposal)
Reporting frequency: Monthly reports to be provided for 6 months after launch
Including KPIs in this format in the brief causes the development company to frame their proposal around "does this design or feature choice contribute to hitting the KPIs?" Without explicit KPIs, the development company defaults to maximizing visual completeness.
KPI confirmation when evaluating proposals
When receiving proposals from multiple development companies, create an opportunity for each to explain how their proposed design and features contribute to hitting the KPIs. A development company that cannot describe the pathway to KPI achievement likely has not understood the client's business goals.
Post-launch KPI review cycle
KPI design is not a one-time activity before the build — it needs regular review after launch too. Incorporating a cycle of "re-evaluate whether targets are realistic three months after launch" and "update KGI to reflect new market conditions" into the development contract or maintenance arrangement is the ideal approach.
The important thing is not just setting KPIs but building a system that keeps them functioning continuously as an operational compass. Finding a partner who can think through "how do we achieve these KPIs" together from the vendor selection stage is what determines whether a website investment succeeds.
References
(2024). Google Analytics 4 Help — About Conversions
(2024). Google Marketing Platform — Google Analytics Official Site
(2024). Ministry of Internal Affairs and Communications — 2024 White Paper on Information and Communications in Japan
(2023). Web Tan Forum — Practical KPI Design and Web Analytics