Bratha

Part 5.0 — Goals and Structure (How Companies Decide Who Does What)

15 min read

This is Part 11 of 13 in the Capabilities and Competency series. You can now read the engine, the numbers, the map, the four jobs, where value lives, what power keeps it, and how stage shifts the constraint. This article connects all of that to the people inside the business who actually own each piece. How a company cascades a big goal into specific numbers, who owns which number, and why finding the owner of the number you can move is exactly how you find your buyer. This is the article that turns lens-into-skill-into-sale.

Table of Contents

Why this is the article that makes the rest usable

Without this article, the lenses in Parts 2-4 leave you with a diagnosis (“the constraint is X, the skill that fixes it is Y”) and no next step. You can’t sell a skill to a business; you can sell it to a person inside a business who is responsible for the number the skill moves. The map of who owns what is the bridge from "this business needs the skill" to "this specific person will pay for the skill." Without the bridge, the diagnosis is academic.

Why goals and structure matter for you, the seller

A business is not a customer. People inside a business are customers, and only some of them have the authority and budget to buy what you offer.

This sounds obvious; it isn’t. Most people pitching capabilities (a freelance designer, a consultant, an internal hire applying for a role, a junior trying to make a case for a new project) pitch to “the company” rather than to “the specific person whose number this would move.” The pitch lands soft, because no one specific is sure they should care.

The fix is structural. Every company has organised itself, formally or informally, around a set of numbers, and assigned each number to a specific human. The number you can move belongs to someone. Find that person; pitch to them; the conversion rate of your pitch goes up by an order of magnitude.

This is the move that turns the lenses in Parts 2-4 from analytical to operational. You read the bottleneck (Part 2.0); you find the number that bottleneck shows up in (e.g. churn rate, CAC, LTV, manufacturing throughput); you find the person whose job it is to move that number; you propose how your skill helps them move it. The whole series collapses into a single sentence: read the constraint, find the owner of the metric, pitch to them.

How companies cascade goals (OKRs and KPIs, in plain words)

Most companies of any meaningful size use some version of goal cascading: a big company-wide goal is broken into smaller department goals, which are broken into smaller team goals, which are broken into individual goals. At the bottom, every person knows what they’re trying to do this quarter; at the top, the company knows that if everyone does their bottom-level work, the top-level number moves.

The two dominant frameworks for doing this are KPIs and OKRs.

KPIs (Key Performance Indicators). A KPI is a measurable number the company has decided is important enough to track every period. Revenue, gross margin, customer count, average order value, churn rate, net promoter score, employee retention. The KPI is the what. Each KPI has an owner (the person responsible for moving it).

KPIs are the closest thing a business has to a public scoreboard. If you can read the KPIs, you can read the business's priorities and identify which numbers are healthy, which are sick, and which need attention.

OKRs (Objectives and Key Results). Popularised by Google (originally from Intel), OKRs are a more ambitious framing. An Objective is a qualitative goal (“become the leading provider of X in Malaysia”). The Key Results are the specific measurable outcomes that, if hit, would mean the Objective was achieved (e.g., “reach RM 50M ARR,” “hit 60% market share among the 50 largest Malaysian SMEs,” “achieve NPS of 60+”). OKRs are usually set quarterly or annually.

The mechanism: leadership sets company-level OKRs. Department heads set department-level OKRs that cascade from the company ones (the marketing team’s OKRs should plausibly contribute to a company OKR; otherwise, why have them?). Teams cascade further. Individual contributors get their goals from team goals.

In practice, most companies do this imperfectly. The cascading often breaks (department goals that don’t actually map to company goals; individual goals that nobody can trace back to anything important). But even an imperfectly cascaded business has a map of who owns what, and that map is what you need.

The fundamental insight for a seller: at any given quarter, every important number in the business is on someone's OKR or KPI scorecard. That someone is the buyer for any work that moves that number. You don't have to convince them the number matters; their job is already to move it. You just have to convince them you can help.

Who owns which number (the buyer map)

Here is the practical map. Most companies, formal or informal, have some version of this:

Profit. Owned by the CEO / founder. The CEO is the only person whose job is the whole bottom line. Everyone else owns a piece of the input chain.

Revenue. Owned by the CRO / VP of Sales / VP of Revenue / Head of Sales. In some companies, “revenue” is split into multiple numbers (new business revenue vs. expansion revenue vs. retention revenue), each with a different owner.

Customer acquisition and brand. Owned by the CMO / VP of Marketing / Head of Growth. The boundary between “marketing” and “sales” is fuzzy and varies by company; in B2B SaaS, marketing usually owns lead generation and sales owns closing, but in consumer the marketing function usually owns the whole top-of-funnel.

Product. Owned by the CPO / VP of Product / Head of Product. Specifically: what the product does, what gets built, the product roadmap. In smaller companies, the founder often plays this role.

Engineering. Owned by the CTO / VP of Engineering / Head of Engineering. The technical capability of the business: what can be built and how reliably.

Cost-to-serve and operational efficiency. Owned by the COO / VP of Operations / Head of Operations. Manufacturing, supply chain, customer service costs, internal process. The keep-half (Part 3.0) on the operations side.

Cash and capital. Owned by the CFO / VP of Finance / Head of Finance. Cash flow, profitability, fundraising, allocation of capital. The keep-half on the financial side.

People and culture. Owned by the CPO (Chief People Officer) / VP of People / Head of HR / CHRO. Hiring, retention, performance, comp, culture. The leverage layer from Part 2.3.

Strategy and corporate development. Owned by the Chief Strategy Officer / VP of Strategy / Head of Corp Dev, when it exists; otherwise by the CEO. Long-horizon decisions about which markets, which acquisitions, which new lines of business.

This is the map. Inside each top-level owner, there's a sub-map (a CMO has a head of paid acquisition, a head of content, a head of brand, a head of lifecycle; each of those owns a sub-number). The map fractals downward until you reach individual contributors.

The founder owns profit, but rarely buys at that level

A subtle but important point: although the founder/CEO owns profit, most purchasing of capability-as-a-service doesn’t happen at the profit level. The CEO buys at the level of strategy and people, but the work that moves specific KPIs is bought by the people who own those KPIs.

This matters for sellers. A common mistake is pitching to the CEO when the work is operational, or pitching to the VP-level when the work is strategic. The mismatch makes the pitch land soft.

A few practical reads:

  • Strategy and big-bet hires: the CEO or board buys these. A new VP of Engineering hire, a strategic partnership, a market-entry decision.
  • Department-level programs: the C-suite head buys these. A new performance-marketing agency, a new sales methodology, a new finance system.
  • Specific projects inside a department: team leads and managers buy these. A specific CRO project, a specific content campaign, a specific process improvement.
  • Individual tools and small contracts: individual contributors and team leads buy these. Software subscriptions under a certain threshold, freelancer engagements, ad-hoc consulting.

If you’re a senior consultant pitching strategic work, the CEO and board are the buyers. If you’re a mid-level specialist pitching a department-level project, the C-suite head is the buyer. If you’re a freelancer pitching a specific project, the team lead is the buyer.

Knowing which level to pitch is half the battle. Pitching the right work to the wrong level wastes everyone's time, including yours.

The C-suite map

Most growing companies converge on roughly the same C-suite as they scale:

  • CEO — the whole business; the buyer for big-strategy and senior-people decisions.
  • CFO — finance, accounting, capital; the buyer for finance tools, audit, banking, and cost-engineering work that touches the books.
  • CMO — marketing and brand; the buyer for acquisition, brand, content, and brand-touching CRO work.
  • CRO / VP Sales — sales and revenue; the buyer for sales process tools, sales training, RevOps, sales-touching CRM.
  • COO — operations and execution; the buyer for ops consulting, process design, automation, and supply chain work.
  • CTO — engineering and technology; the buyer for technical infrastructure, engineering tools, and dev process improvements.
  • CPO (Product) — product strategy; the buyer for product research, design, and product-side analytics.
  • CHRO / CPO (People) — people; the buyer for hiring tools, comp benchmarking, performance management, and culture work.

The C-suite is also where political resistance to outside help tends to live, because each C-suite member is defending their department’s budget and authority. The seller who positions their work as "helping you hit your KPI" lands; the seller who positions it as "fixing what's wrong" gets walked out, even when they're right about what's wrong.

Department heads and the operating layer

Below the C-suite is the operating layer: heads of department, senior managers, team leads. This is where most specific capability work gets bought, because:

  • The C-suite is too busy to manage individual projects.
  • The operating layer has enough budget for project-level work but doesn’t need to escalate to the C-suite.
  • The operating layer feels the bottleneck directly (the head of growth knows the funnel is leaking; the head of operations knows the supplier is unreliable).

If you’re early in your career or pitching a specific capability, this layer is usually the right buyer. They have the authority and the felt pain. A pitch to "the head of growth at a Series B SaaS startup," tailored to a specific gap in their funnel, lands much harder than a pitch to "the CEO" of the same company at the same time.

The operating layer is also where most internal moves happen. If you’re an employee proposing a new project, the relevant operating-layer person (your manager’s manager, usually) is the decision-maker.

How to find the buyer from the outside

A practical workflow:

  1. Identify the metric you can move. From Parts 2-4: what specific number does your skill improve? Be specific. “Marketing” isn’t a metric. “Conversion rate from trial to paid” is.
  2. Identify which department owns that metric. Conversion rate from trial to paid usually lives with growth or product, depending on the company. Lead generation lives with marketing. Customer churn lives with customer success or product. Cost per shipment lives with operations.
  3. Find the head of that department. LinkedIn, the company’s About page, public press, news coverage. In smaller companies (under 50 people), this is usually a direct LinkedIn search. In larger ones, the org chart is harder to read but inferrable.
  4. Find the second-degree connection if possible. A warm intro from someone in their network multiplies your conversion rate. Cold outreach works (especially with a sharp, specific pitch), but warm is better.
  5. Pitch the metric and the move, not your skill. “I help SaaS companies improve trial-to-paid conversion” beats “I do CRO.” Even better: “I noticed [specific public signal about the company’s funnel] and have a hypothesis about how to fix it; happy to share.”

The targeting work (which metric, which department, which person) is what separates an effective pitch from a generic one. Most people skip the targeting and pitch the skill in the abstract. The skill in the abstract has no buyer.

Where the buyer-map lens breaks

Three real limits.

One: the map is cleaner than reality. Real org charts are messy. People wear multiple hats. The “head of growth” might also informally own the brand. The “VP of Operations” might also be doing finance work because there’s no CFO yet. Treat the map as a starting point, then ask, and revise.

Two: in very small companies (under 10 people), the founder owns everything. All metrics, all decisions, all purchasing. The map collapses into one person. Pitches in that context are direct-to-founder, and the founder’s filter is “does this help me run this business?” not “does this match a department’s KPI?”

Three: large companies have a procurement layer. At companies over a few hundred people, even when you’ve identified and convinced the right operating-layer buyer, the purchase has to clear procurement, legal, and sometimes IT review. The buyer’s authority is constrained by the company’s processes. The seller in that context has to factor in not just "who decides" but "how does this get bought." That's a different skill and worth knowing if you sell into enterprise.

Minor edge: in highly cross-functional projects (something that spans growth, product, and engineering), no one person fully owns the relevant metric, and selling requires building consensus across multiple buyers. This is enterprise-sales work and has its own playbook.

Part 5.0 takeaways

Key concepts to internalise

  • Every important number in a business is owned by a specific person. Find that person; pitch to them.
  • OKRs and KPIs are the formal map of who owns what. If you can read them, you can identify priorities and weaknesses.
  • The buyer for your capability is the owner of the metric you move. Not “the company”; not “the CEO” (usually); the person whose quarterly goal is the thing your skill improves.
  • Pitch at the right level. Strategic work → CEO/board. Department-level programs → C-suite head. Specific projects → team lead.
  • The operating layer (department heads, senior managers) is where most specific capability work gets bought.
  • Targeting the right buyer beats refining the skill. Most people skip the targeting and pitch in the abstract; the abstract has no buyer.

Your weekly task

The recurring closing move, refined.

  1. For your case business, identify the specific metric your candidate skill would move. Be precise. Not “marketing”; “trial-to-paid conversion rate” or “lead-to-MQL conversion rate.”
  2. Identify which department owns that metric. And, if you can, which sub-role within the department.
  3. Find the actual person who owns it. LinkedIn, the company’s About page. Name them.
  4. Draft a one-sentence pitch tailored to them. “Hi [Name], I noticed [specific signal about their metric] and have an idea about how to move it; happy to share.” The signal can be public-facing (slow site, bad page, weak email sequence) or industry-pattern-based (companies at this stage usually struggle with X).
  5. Compare your pitch to “I do [skill].” Notice the difference. The first is targeted; the second is generic. The first converts; the second doesn’t.

Up next

You now have every piece of the chain. Part 6.0 — From a Business to the Exact Skill runs the whole chain live on a real Malaysian example, start to finish. Reading the stage, finding the constraint, locating the weak number, naming the skill, naming the buyer. By the end of that article, you’ll have walked the chain with one business; by the end of Part 6.1, you’ll have walked it with yourself.

Disclaimer

Business literacy education, not consulting or sales advice. Real org charts are messier than the map here suggests; specific company structures vary widely. The KPI / OKR conventions described are widespread but not universal; some companies use different frameworks or none at all.

Sources & references

The OKR framework was popularised by John Doerr’s Measure What Matters (2018), which documents Andy Grove’s original Intel implementation and its later spread through Google and elsewhere. The KPI tradition is older and broader; standard references include Robert Kaplan and David Norton’s Balanced Scorecard (1996) and the broader managerial accounting literature. The buyer-map framing (matching the seller to the metric-owner) draws on enterprise sales methodology, particularly Mike Bosworth’s Solution Selling (1995) and the more recent challenger-sale tradition (Matthew Dixon and Brent Adamson, The Challenger Sale, 2011). The “pitch the metric, not the skill” advice is a synthesis of decades of sales-effectiveness research compressed into a sentence.

Graph View

Backlinks