This case study highlights how the KPI Scope Builder applies decision-first systems thinking to KPI planning before analytics or CRM implementation.

The KPI Scope Builder is a low-code web application prototype designed to help teams clarify what they are trying to decide before analytics dashboards, reports, or CRM implementations are built.

It provides a guided, repeatable workflow for defining business objectives, selecting meaningful KPIs, assigning ownership, and identifying data sources. By introducing a structured pre-analytics planning layer, the tool helps prevent misaligned metrics, reporting sprawl, and wasted development effort.

Organizations often jump straight into dashboards or tooling without clearly defining:

What decision the data is meant to support

Who owns each metric

How KPIs will actually be used

This leads to inconsistent reporting, unclear accountability, and analytics that don’t drive action.

The KPI Scope Builder solves this by formalizing KPI scoping before analytics work begins, aligning stakeholders around a shared definition of success.

Built with: Lovable (low-code web development platform)

Development Style: Low-code, visual drag-and-drop with relational logic modeling

Guided project setup (objective, business area, cadence)

Custom KPI creation with definition, owner, and data source

Suggested KPI templates by category (e.g., Acquisition, Engagement, Performance)

Validation rules to enforce clarity and prioritization

Auto-generated summary for review or export

Finalization workflow to lock scope and prevent drift

Printable PDF output for stakeholder alignment

Project Title: Q4 Marketing Roll-up Objective: Align on which marketing KPIs should be tracked and reviewed to evaluate campaign effectiveness and inform next-quarter strategy.

Website Traffic Growth Month-over-month increase in website visitors Source: Google Analytics

Content Conversion Rate Percentage of content viewers taking desired actions Source: Analytics, CMS

Cost Per Lead (CPL) Total marketing spend ÷ leads generated Source: Ad Platforms, Analytics

Social Media Engagement Total likes, shares, and comments across platforms Source: Social Media Tools

Return on Ad Spend (ROAS) Revenue generated per advertising dollar Source: Google Ads

Each KPI includes a clear definition, owner, and data source, ensuring shared understanding before any dashboards are built.

This project followed an iterative, human-centered systems design approach:

Defined user needs and decision context

Modeled relational entities and validation rules

Built and tested MVP workflows

Refined UI clarity and reporting flow through iteration

Each cycle improved usability, scope discipline, and alignment.

Completion: ~70% functional prototype

Core features built: Project creation, KPI selection, validation, inline editing, export

Next steps: Multi-user access, role-based permissions, BI tool integrations

Role-based access and multi-user collaboration

Live data integrations (Salesforce, GA4, HubSpot)

Dynamic handoff to dashboards or reporting tools

Expanded KPI libraries by function or industry

Validation prompts for incomplete ownership or data sources

While this project is presented as a systems and decision-scoping case study, the prototype demonstrates how scoped KPI frameworks can be directly implemented into low-code products, internal tools, or client-facing dashboards.

This project strengthened my ability to translate ambiguous business needs into structured systems and decision frameworks. It reinforced the importance of scoping and alignment as foundational steps in analytics, CRM, and digital transformation work.

© 2025 Amy Frank. All rights reserved.

This project is shared for portfolio and demonstration purposes. Concepts and documentation may not be reused for commercial or derivative purposes without permission.