Edgerunners
Our approach

We don't start with technology. We start with where value is created.

Most technology projects fail quietly. Nothing crashes. The system ships, the dashboard goes live, and six months later nobody can say what changed in the business.

Edgerunners works the other way round. Before we write a line of code, we work out what kind of value you need, what kind of business has to carry it, and which numbers will prove it worked. The technology comes after that and follows from it.

See how we workStart a conversation

01 — Value Creation Strategy

Name the value first. Then engineer for it.

"We need an app," "we need AI" and "we need a dashboard" are all solutions. We push back to the question underneath: what should be different in your P&L, your operations or your risk profile once this is done? The answer puts the project into one of five value archetypes, and each archetype has its own logic, its own tools and its own definition of success.

Primary archetypes

  • Operational Optimization

    Do more with what you already have. Lower cost, higher throughput, less waste, better asset use. We map exactly which operational levers move your bottom line, and by how much.

    Tools

    • Value Driver Tree
    • KPI Tree
    • Bottleneck Analysis

  • Revenue Growth

    Grow the top line on purpose. New customers, new markets, higher conversion, longer lifetime value. We build growth around the drivers that actually compound, not around feature lists.

    Tools

    • Growth Strategy
    • Revenue Model
    • Revenue Driver Tree

Complementary archetypes

  • Business Model Innovation

    Change how you make money, not only how much. New revenue streams, platform plays, subscription and service models, with the unit economics checked before anything is built.

    Tools

    • Business Model Canvas
    • Unit Economics

  • Risk & Resilience

    Protect the value you've already created. Compliance, operational continuity, data integrity and control. These systems earn their keep by making sure things don't happen.

    Tools

    • Risk Assessment
    • Control Framework

  • Capability & Experience

    Build what you can't do today. New capabilities for your teams and better experiences for your customers, mapped from the journey down to the systems that have to support it.

    Tools

    • Capability Mapping
    • Customer Journey Mapping

Value Driver Tree

Why a Value Driver Tree, and not another dashboard

You've probably seen plenty of dashboards already: Google Analytics, a BI tool, a monthly KPI deck. They look great and they report everything. Even so, when it's time to decide something, the decision still gets made on gut feel.

The reason is simple: a dashboard tells you what happened. It doesn't tell you why, or which lever to pull next. Forty KPIs on one screen, with no structure linking them to profit, add up to noise.

A Value Driver Tree is the structure that's missing. It starts from the outcome you care about (margin, cash, cost per ton, revenue per customer) and breaks it down, mathematically, into the operational drivers that produce it, all the way to the metrics your teams can actually move.

DashboardWhat happened

Forty KPIs, no structure, no next step.

Value Driver TreeWhy, and what next
  • EBITDA margin
  • Revenue
  • Throughput
  • Ore recovery rate
  • Cost per ton
  • Equipment uptime+4% → ?
  • Dilution rate
  • Energy per ton

One outcome, traced to the levers your teams can move.

With that tree in place, three things change:

  1. Every KPI has a reason to exist.

    If a metric doesn't connect to value, it comes off the screen.

  2. You can simulate before you invest.

    For example: "if we improve equipment uptime by 4%, what happens to cost per ton?" You get an answer in seconds, not after a quarter.

  3. Prioritization becomes arithmetic.

    You see which three levers carry most of the value and put your budget there.

We don't build dashboards. We build a model of your business, and then we put a screen on it.

A VDT isn't only for cost cutting. We build revenue driver trees for growth engagements too traffic × conversion × basket size × retention. The method stays the same and the drivers change.

Two Paths, One Discipline

Most engagements follow one of two paths. The steps differ, but both end in measurable value.

Path A

Optimization-Driven

The business already exists. Our job is to make it perform better.

  1. Business Understanding: the operating model, processes, organization and where the money actually flows.

  2. Value Driver Mapping: build the Value Driver Tree and find which drivers really move value.

  3. KPI Decomposition: break top-level targets into operational KPIs that are measurable and owned.

  4. Opportunity Identification: find the bottlenecks, inefficiencies and leakage, then size each one.

  5. Solution Engineering: design the fix in software, AI, automation or industrial intelligence.

  6. Impact Measurement: quantify the effect on KPIs and on economic value, and keep tracking it.

In practice: mining

Objective
Increase extraction productivity
Value drivers
Less waste, more accurate extraction, higher mineral recovery
KPIs
Ore Recovery Rate · Dilution Rate · Equipment Utilization · Production Cost per Ton
Solution
AI-based Grade Control · Predictive Analytics · Operational Intelligence
Outcome
Lower extraction cost, higher recovery, stronger margins
Read the case: AI Grade Control in Mining

Path B

Growth & Business Building

The goal isn't to improve something that exists. It's to create a new product, revenue stream or business model.

  1. Business Discovery: what the business is, who owns it, how decisions get made and who has a stake.

  2. Market & Customer Analysis: the target market, real customer needs and buying behavior.

  3. Business Model Assessment: revenue model, channels, competition and unit economics.

  4. Product & Revenue Strategy: design the product around its role in generating revenue.

  5. Solution Architecture: a technical architecture that fits the business and operating model.

  6. Build, Launch & Scale: develop, launch, validate and scale.

In practice

"We need a mobile app." We don't jump into UI/UX and sprints. First we ask:

  • What problem does this solve for the end customer, and is it painful enough to pay for?
  • Who exactly is the end user?
  • Should it be transaction-based or subscription-based?
  • Does it go to market directly as B2C, or through partners as B2B2C?
  • What will actually drive conversion, retention and customer lifetime value?

After that we design and build the product around those dynamics. The result is an app with a business behind it.

02 — Business Context & Engagement Model

The same label doesn't mean the same problem.

A mobile app for a retail company and a grade-control system for a mine are both "B2B projects," yet they share almost nothing: different stakeholders, different risks, a different pace and a different definition of done. We read context along two axes before we decide how to engage.

Axis 1 — Business Relationship

  • B2B

    You sell to buying committees, not to individuals. Your revenue lives in contracts, SLAs and renewals, and one missed delivery can cost you an account. We design for contract control, multi-stakeholder approvals and long sales cycles, so commitments, delivery and billing stay in sync.

    Read more

  • B2C

    Your customer is one tap away from leaving. Acquisition is expensive and loyalty is fragile. We engineer for activation, retention and lifetime value from day one, because downloads alone mean very little.

    Read more

  • B2B2C

    You have to win twice: the partner who distributes you and the consumer who uses you, and their incentives don't always line up. We design products and revenue shares that work for both sides of the channel.

    Read more

  • B2G

    Procurement rules, accountability, long timelines, and systems that must serve everyone. We build for transparency, compliance and data governance without losing usability.

    Read more

Axis 2 — Business Environment

  • Enterprise & Corporate

    Legacy systems, political complexity, and change that has to happen while operations keep running. We focus on transformation, integration and optimization that survives contact with the organization.

  • FamilyOwnershipBusiness

    SME & Family Business

    In a family business, the most important decisions are rarely made in the boardroom. We work with the Three-Circle Model: family, ownership and business overlap, and every stakeholder sits somewhere in those circles. So we know why a "simple" system change can touch trust, succession and authority. We design digitalization and automation that respect how decisions are actually made, and then help professionalize that, gently.

  • Startup & Venture

    Runway is your most important metric and certainty is a luxury. We help you validate before you scale: lean MVPs, real signals, and an architecture that won't need a rewrite when traction arrives.

  • Industrial & Manufacturing

    Here downtime is measured in tons and dollars per hour, and "move fast and break things" isn't an option. We bridge IT and OT, turning sensor data and operational knowledge into Industry 4.0 systems your engineers trust.

    Read more

  • Government & Public Sector

    Scale, accountability and public trust. We deliver digital public services and data governance that are secure, auditable and built to last beyond one administration.

03 — Solution Engineering & Value Realization

From objective to engineered outcome, and proof that it worked.

Once we know the value and the context, we engineer. The engagement isn't finished when the system goes live. It's finished when the value shows up in the numbers.

  1. 01 · Discover

    Discovery & Architecture

    turn business objectives and context into a solution architecture with clear success metrics.

  2. 02 · Build

    Product · Platform · AI · Industrial Systems

    build whatever the problem needs, whether that's a customer product, an internal platform, an AI model or an industrial control system.

  3. 03 · Integrate

    Implementation & Integration

    connect to your existing systems, data and teams, and get people to adopt it.

  4. 04 · Measure

    Measurement, Optimization & Continuous Improvement

    track impact against the KPIs we agreed in step one, then keep improving.

Measurement feeds the next round of discovery.

The Edgerunners Difference

Four commitments behind every engagement.

  • Value before code.

    Every project starts with an economic hypothesis, not a feature list.

  • Context over templates.

    We don't use the same playbook for a family business and a multinational.

  • Models, not dashboards.

    We give you a structure that explains your business. We don't add more charts.

  • Measured outcomes.

    We define success in your numbers, and we stay to see them move.

Let's find where your value is hiding.

Tell us about the outcome you're after, not the technology you think you need. We'll start from there.

Start a conversation