Category Archives: Operations

Finance Matters, Operations, Sales Matters

Revenue Leads Expenses

Leave a comment

Most leadership teams know the problem.

They set an annual revenue target, build spending around it, and move forward as if the planned revenue inflow is already on its way. If revenue later develops more slowly than hoped, the organization is forced to pull back, delay hires, cut initiatives, and explain why the original plan no longer holds.

That is not disciplined planning. It is front-loading optimism and dealing with the consequences later.

A better approach is to let revenue lead expenses.

This starts with distinctions that are often blurred: the difference between the revenue goal, the revenue forecast, and the currently authorized level of spending.

The revenue goal is the level of performance the organization intends to produce over the course of the year (with ~75% confidence). It sets direction, expresses ambition, and gives management and the team a target to drive toward. It is, by design, an expression of intent rather than a prediction, and it is set once for the performance period (e.g., a year).

The revenue forecast is management’s best current estimate of what is most likely to materialize based on facts known at the time. It is a high-confidence view (90+%), not an aspiration dressed up as a projection. In practice, teams should be able to articulate the confidence level behind the forecast, explain why it is defensible based on current evidence, and state clearly what must occur for it to materialize. It is established at the beginning of the performance period and updated continuously as new information becomes available.

The authorized expense level follows from the forecast. The organization may appropriately communicate an ambitious plan and budget externally, but it should not authorize spending internally at the full goal level from the outset simply because that is where it intends to end the year. Initial spending should be based on the revenue that management has high confidence will materialize. Spending should remain aligned with the forecast from then on.

A common approach is to spend at the goal level and then cut if triggers are missed. A better approach is for management to begin the year with a forecast-based level of spending. As the year unfolds and predefined triggers are met, the forecast may be revised upward. Each higher forecast then authorizes a higher level of spending.

Done well, this creates an effective operating rhythm. The organization expands deliberately as evidence improves. Spending rises as the facts justify it, with each step grounded in current performance and validated progress.

Note that the revenue leading expenses approach requires clarity about what counts as a trigger. The trigger might be a revenue milestone, a booking threshold, a conversion rate, a renewal event, a signed commitment, or another concrete indicator that the revenue outlook has strengthened. Management should define as part of its plan what justifies moving to a higher forecast and, therefore, a higher spend path.

The accompanying chart illustrates the logic connecting revenue leads to expenses. While the annual revenue goal remains fixed, the initial forecast establishes the baseline spending posture. As specific triggers are met, management adopts updated forecasts. Each revision builds upon the previously authorized path, supporting a higher level of cumulative spending.

This approach reinforces the discipline of aligning spending with current evidence rather than assumptions, helping leadership make decisions based on what is actually unfolding rather than what was originally planned. The discipline is as follows:

  • Plan to the goal. Decide what the organization is trying to produce and what it would take to operate successfully at that level, even though not all of that spending is authorized on day one.
  • Forecast what is most likely. Establish a higher-confidence view of the revenue expected to materialize based on current facts.
  • Let the forecast in force define the current spend level. Authorize spending based on what management currently has high confidence will come in, not simply on what it hopes to produce.
  • Raise authorized spending only as triggers are met and the forecast improves. Expand spending as evidence strengthens and the revenue outlook becomes more secure.

At any point in time, leadership should be able to answer three separate questions:

  • What is the annual revenue goal?
  • What is the current revenue forecast?
  • What level of spending is now authorized based on that forecast?

Those answers should be connected, but they should not be assumed to be the same.

That is what it means to let revenue lead expenses. It is a way to stay ambitious without getting ahead of the facts.

Get Clear, Operations

Before You Build, Get Clear

Leave a comment

Before You Build, Get Clear

AI makes it easier than ever to build, prototype, and automate. It does not make it any less important to think. When the cost of building drops, the cost of building the wrong thing rises. Remember Peter Drucker’s aphorism that ends wtih “… are you doing the right thing?”

That is why a Business System Concept still matters. It helps a team get clear on how the work happens today, what should change and why, which parts of the current process still deserve to exist, and what future-state model is actually worth building toward.

In the latest IntelliVen Insight, we use a simple construction example to illustrate the difference between NOW and NEXT. A descriptive model shows how the organization works today. A normative model defines how it must work to fulfill the mandate. Without both, initiatives multiply but performance does not improve.

Read the full piece here.

Get Clear. Align. Grow.

Governance, Manage to Lead, Operations

Finding the CEO for What Comes Next

Leave a comment

An IntelliVen Insight by Eric Palmer.
AI is not a feature cycle.
It is a reset of SaaS economics.

Eric Palmer, a highly successful Senior Operating Partner with more than 30 years of experience leading private, public, private equity-owned, and venture-backed companies, recently shared what he is seeing across  software businesses.

Eric uses and has contributed to the development of the Manage to Lead Executive Alignment System for Operations and Governance.

His perspective comes from inside boardrooms, executive searches, and portfolio performance reviews. It is direct.

Act 1: What Is Happening Inside PE-Backed SaaS Companies

Across portfolios, three pressures are converging.

Reinvention as AI-first, not AI-augmented

  • Many companies are using AI to optimize what already exists. That feels safe. It preserves roadmaps. It protects org structures.
  • It is not enough.
  • The companies gaining ground are redesigning around AI economics. That requires discontinuous change, not incremental improvement.

Pricing and economic disruption

  • Seat counts are declining. Usage-based economics are rising. AI inclusion without pricing discipline can destroy margin.
  • CFOs want predictability. Customers resist variability. Boards want growth and protection of uFCF.
  • The old SaaS model is under stress.

Bookings uncertainty

  • Buyers are hesitating. Some are delaying category decisions altogether, assuming today’s leaders may not be tomorrow’s.
  • Expansion is harder. Contraction is visible.
  • Incrementalism does not solve this.

Act 2: The CEO This Moment Demands

The traditional SaaS CEO profile is now necessary but insufficient.

Operational excellence. Team building. Customer focus.

All still required.

But the differentiator now is the ability to lead discontinuous change under pressure.

Eric identifies eight characteristics that matter most:

  • Conviction to lead transformation, not manage transition
  • Audacious goals that reorient behavior before the roadmap is complete
  • Ruthless resource reallocation, even mid-cycle
  • Willingness to reconfigure strong legacy leaders
  • AI fluency that reshapes economics, org design, and personal workflow
  • Commercial ownership of the seam between Product and GTM
  • Resilience under sustained, ambiguous pressure
  • Ability to move at board velocity in a PE environment

In his words, some CEOs optimize what is working.

The ones that win are willing to discontinue what is working in order to win what is next.

Eric also points out that AI-first professionals entering the workforce understand the technology. They have urgency. They have ambition.

What most lack are the leadership and management disciplines required to:

  • Align an executive team
  • Govern resource allocation
  • Make hard priority decisions
  • Integrate Product and GTM
  • Drive change across a fully formed organization

Technology fluency alone does not create durable enterprise value.

The missing ingredient is not more AI capability. It is executive alignment around Purpose, priorities, and resource allocation. That is the problem the Manage to Lead Executive Alignment System was built to solve.

AI capability without executive alignment produces motion.
AI capability with alignment produces performance.

The Question for Boards and Investors

  • Are we selecting for transformation or comfort?
  • Is our CEO AI fluent or AI enthusiastic?
  • Can our executive team reallocate resources without waiting for the next planning cycle?
  • Do we have alignment equal to our technical ambition?

The Variable That Determines Value Creation

Valuations are under pressure.

The path back is not cost cutting alone.

It is radical AI-oriented change that:

  • Accelerates productivity and uFCF
  • Increases RPE at unprecedented speed
  • Reinvests gains into top-line expansion

Those that are audacious and aligned will capture disproportionate share.

Some will.

Many will not.

The CEO is the variable.

Read Eric Palmer’s full article:
“Finding the CEO for What Comes Next.”

Operations

Time Horizon Discipline

Leave a comment

Leaders often say:

  • “We don’t have enough time.”
  • “We’re far from our goals.”
  • “Everything feels urgent.”

Most of the time, the issue is not time.

It is a mismatch between the decision and the planning horizon.

Manage to Lead is built on clarity and disciplined change. Time horizon discipline is part of that clarity.

Different Decisions Require Different Clocks

Not every decision should run on the same timeline.

When leaders use one clock for everything, they either:

  • Overreact in the short term, or
  • Drift in the long term.

High-performing organizations operate with multiple time horizons.

Each clock answers a different question:

  • Where are we going?
  • How will we win over this bounded period?
  • What must change next?
  • Are we doing what we said we would do?

If those questions collapse into one timeframe, confusion follows.

If they contradict one another, stress follows.

If they are coherent and nested, focus follows.

The Mandate Horizon Is Contextual

The Mandate answers:

What are we trying to accomplish, by when?

There is no universal duration.

A Mandate horizon should be:

  • Long enough to require real capability building.
  • Short enough that the current leadership team owns the outcome.
  • Explicitly bounded so capital allocation decisions can be evaluated against it.

For many organizations, that is about three years.

For some, it is shorter.
For others, longer.

Three years is common because it is often long enough to require meaningful change and short enough to sustain accountability. But it is not doctrine.

The discipline is not in picking “three.”

The discipline is in making the horizon explicit and holding it steady long enough for strategy and investment decisions to compound.

Multiple Clocks Must Be Coherent 

One common architecture looks like this:

  • Mandate horizon → Defines destination
  • Strategy horizon → Defines directional choices
  • Initiative horizon → Defines staged change
  • Management horizon → Ensures execution discipline

For many organizations, that might roughly translate into:

  • Multi-year Mandate
  • Annual strategy framing
  • Quarterly initiatives
  • Monthly management cadence

But this is an example, not a rule.

  • Different organizations legitimately design different clock speeds.
  • What matters is not the exact durations.
  • What matters is coherence across them.

Match Capital Commitment with Time Horizon

The longer capital is tied up, the longer the planning lens must be.

Examples:

  • Hiring a senior executive → Mandate lens
  • Entering a new vertical → Mandate lens
  • Building a new sales discipline → Initiative lens
  • Running a marketing experiment → Management lens

Short-horizon thinking applied to long-horizon commitments produces fear and underinvestment.

Long-horizon thinking applied to short-cycle execution produces drift and lack of accountability.

Match the clock to the decision.

NOW and NEXT Must Be Far Enough Apart

In the Change Framework:

NOW → WHY → NEXT → WHAT MUST BE DONE → BARRIERS

NEXT must relieve the constraints of NOW.

If NEXT is too close:

  • You get incremental improvement.
  • The system remains fundamentally unchanged.

If NEXT is too far:

  • It becomes aspirational.
  • The team cannot see the path.

A disciplined principle:

Choose a future state far enough out that you can think beyond current constraints, but close enough that the current leadership team is accountable for reaching it.

That balance creates energy without fantasy.

Why Leaders Feel “Short on Time”

When leaders say they are short on time, often one of three things is happening:

  • The Mandate horizon is unclear.
  • Too many initiatives are competing at once.
  • The management clock is crowding out strategic thinking.

Clarity of horizon reduces emotional noise.

When the Mandate is explicit and bounded, urgency becomes focus rather than pressure.

Bottom Line

  • Time is not the problem.
  • Unbounded thinking is the problem.
  • Use multiple clocks.
  • Make each explicit.
  • Ensure they are coherent.

Let the longer horizon guide capital allocation.
Let staged initiatives translate direction into change.
Let disciplined review reinforce commitments rather than override them.

Get Clear. Align. Grow.

Operations

From Tool to Teammate: Six Practices That Make AI Work for Us

Leave a comment

At IntelliVen, we work from a defined body of leadership and management practice: the Manage to Lead (MtL) System. It is documented in our text, taught in our classes, and organized into more than sixty tools and templates and 70 insights and tutorials. We use these tools every day with clients and trainees and we are gradually giving each one AI support.

Key points

  • We turned a defined body of work (Manage to Lead) into an AI teammate, IVOA.
  • What you load into AI and how you use it matters most: a focused core pack, clear logic, simple ground rules.
  • The same six practices can turn your content, tools, and methods into an AI teammate.
  • The payoff is on-demand access for many more people with higher quality and consistency.

AI, in the form of our custom GPT, IntelliVen Operations Advisor (IVOA), has become a working teammate we did not know we needed or could afford. Grounded in our MtL text and tool tutorials, IVOA extends our thinking and lifts the quality and consistency of our work. Hours become minutes, and the output is sharper and more thorough.

Serious content is moving this way. Professors and authors will pair their books, courses, and toolkits with AI teammates that know their material, use their language, and sit beside the users of their work (leaders for us; scientists for a science professor) as they think, decide, and act.

This makes the originator’s best thinking available on demand to anyone, anywhere, at any time, with no enrollment required. Much of the IP is free to access. Revenue comes from deeper engagement: subscriptions for full access and community features, and paid classes and consulting to apply the knowledge and logic to real cases. That is the shift from tool to teammate.

What follows is what we have done with MtL so far and six practices that make AI work for us: three to set up a teammate like IVOA and three to use it well. IVOA is something we use extensively in our own work, and it is equally open and available for anyone to use or adapt.

SET UP

These three steps prepared IVOA to perform as part of our team and are the same steps you can use to turn your own body of work into an AI teammate. In the configuration window that opened when we set up the GPT, we:

  • Loaded a small Core Pack as its working knowledge base
  • Uploaded logic tutorials so it thinks the way we do
  • Set default behaviors so tone and structure fit our brand

The Core Pack is our MtL textbook plus about a dozen of our curated tutorials, templates, and e-books, each under 10 pages. These materials and the ground rules persist in IVOA’s configuration, so we don’t need to upload or restate them each time we use it.

1. Loaded a knowledge base

On advice from participants in our Manage to Lead (MtL) Executive Alignment System for Operations and Governance training program, we loaded the Core Pack, our MtL text, e-book, tutorials, and prompt logic into IVOA. The impact was immediate.

Consider the contrast when we ask IVOA versus a generic AI: “What’s the purpose of a business?”

IVOA (MtL-aligned):
The purpose of a business is to solve a specific problem for a specific customer set.

  • Purpose is external: it’s about the customer’s problem, not your internal motivations.
  • Teams that stay clear on WHAT they deliver, to WHOm, and WHY the buyer chooses them execute better and grow faster.

Generic AI:
Provide goods or services to customers, generate profit, create jobs, and contribute to the economy.

Same question. Both answers are reasonable English. Only one is tight enough, and specific enough, to guide how leaders think, talk, and act.

2. Uploaded logic

We configured IVOA with the guts of Manage to Lead: detailed tool logic, what “good” looks like, common failure modes, and the assess-and-suggest moves we use across the tools. When it works on a task, it runs the same checks and upgrades we use with clients, not generic internet advice.

It also runs those checks more consistently and exhaustively than we do; where a human often stops once something is “good enough,” IVOA keeps applying the full set of tests and upgrades without getting tired or impressed with itself. That logic base changes how it sees and improves work.

Here is what that looks like on a simple WHAT–WHO–WHY.

Example: IVOA sharpening a WHAT–WHO–WHY

We asked IVOA to assess an early draft W-W-W for a “leadership training” offer.

Draft:

  • WHAT: Leadership training for managers who need to be more strategic
  • WHO: Mid-level managers in growing organizations
  • WHY: They are too focused on tasks and need to operate more strategically

IVOA’s assessment surfaced several issues and concrete upgrades.

Feedback on clarity and specificity

WHAT

  • “Leadership training” is a service, which is good, but it is broad. Name the deliverables a buyer can point to (for example, program format, length, and core components).
  • The phrase “for managers who need to be more strategic” mixes in WHO and WHY. Keep WHAT focused on the offer itself, not on audience or motivation.

WHO

  • “Mid-level managers” describes participants, not the buying decision-maker. Specify the role that approves budget (for example, Head of L&D, CHRO, BU leader) and add simple qualifiers such as organization size and context.
  • Tighten targeting by using traits like pain, urgency, economics, authority, and advocacy.

WHY

  • The draft states the problem (“too focused on tasks”) but not why buyers choose this offer over alternatives. Frame WHY in the buyer’s words, with evidence where possible.
  • A crisp, customer-voiced WHY anchors growth and alignment; teams that describe WHAT, WHO, and WHY the same way perform better.

Suggested upgraded WHAT–WHO–WHY

  • WHAT: A 12-week strategic leadership program that combines cohort workshops, on-the-job applied projects, and 1:1 coaching, with toolkits and manager-sponsor check-ins.
  • WHO: Head of Learning & Development or Business Unit leader responsible for developing mid-level managers in organizations of ~500–5,000 employees.
  • WHY: They choose us to reliably shift managers from task execution to strategic operating behaviors through applied work tied to their business, with measurable improvements in planning, delegation, and cross-functional outcomes; strong internal references and repeat sponsorship reduce adoption risk.

Notes to strengthen further

  • Add simple qualifiers to WHO (industry focus, region, typical team size) and score best buyers on pain, urgency, economics, authority, and advocacy to tighten the ideal customer profile.
  • Bolster WHY with proof points buyers trust (for example, internal references, completion-to-application rates), keeping the focus on the buyer’s reasons, not your beliefs.

Why this matters

  • A specific, shared W-W-W keeps teams aligned on purpose and choices.
  • Clarity on WHAT, WHO, and WHY is foundational to better execution and growth.

Without uploaded logic

We also ran the same draft W-W-W through a general-purpose AI assistant.

It told us, in effect: “This is a very clear and concise statement of purpose. It covers the three W’s and only needs minor refinement.” It praised the draft, offered some marketing polish, and suggested using it as-is as a mission or elevator pitch.

IVOA did something very different. It:

  • Flagged that WHAT mixed service, audience, and motivation and pushed us to name concrete deliverables
  • Pointed out that WHO described participants, not the buying decision-maker, and asked us to specify the role and simple qualifiers like size and context
  • Reframed WHY from “the problem” to “why buyers choose us over alternatives,” and nudged us toward buyer-voiced language and proof points
  • Produced a sharper, more specific W-W-W that we could actually use to target, sell, and deliver

Both AIs wrote in fluent, confident English. The difference is that IVOA is tuned to our Manage to Lead logic and tools. It does not just sound right. It pushes our thinking to be right for the way we run and grow organizations.

If you want to see this in your own context, try this sequence:

  • Write your current WHAT–WHO–WHY.
  • Paste it into your favorite general AI assistant and ask for feedback.
  • Paste the same W-W-W into IntelliVen Operations Advisor (IVOA) and ask it to assess and upgrade it.
  • Then ask IVOA to compare its assessment with the other AI’s response and explain the differences.

The value is not that it writes nicely. It is that it knows the logic, tools, and standards behind the work and helps you apply them. The same AI teammate we use in our work is available for anyone to use or adapt.

3. Configured ground rules

When we configured IVOA, we set clear ground rules for tone, structure, length, and emphasis. We gave these instructions once. We override them only when a task needs a different style.

With guidance

“Use a direct, executive tone. Short paragraphs. Bullets by default. No filler. Focus on operational impact and next actions.”
→ Output fits our brand.

Without guidance

The AI invents its own style (which can be annoying!).

Example default ground rules to paste into GPT config:

  • Tone: direct and executive; warm when appropriate.
  • Length: be concise; short paragraphs.
  • Altitude: start with a high-level summary; add detail on request.
  • Format: bullets by default; numbers only when sequence matters.
  • Structure for substantial replies: Context and aim; What we see; What to do next; Risks and tradeoffs; Optional variants or examples.
  • Emphasis: actions, owners, timing, concrete examples.
  • Avoid: em dashes, tropes, filler, sycophancy, purple prose. Use plain language.

USAGE

With setup complete, day-to-day work is straightforward. The next three steps set context for the task, share our best current draft, and iterate line by line until the result is crisp and on target.

4. Set context

Before asking IVOA for help, we share everything relevant about the situation. It doesn’t need to be organized or polished. Completeness beats polish:

  • Role
  • Audience
  • Stakes
  • Constraints
  • What’s working
  • What’s not
  • Why it matters
  • Who cares
  • Etc.

With context

“I’ll be addressing a cross-functional leadership team that’s behind on customer onboarding. They’re feeling pressure on service levels. I want to open by acknowledging that pressure and the opportunity ahead if we align on the few priorities that matter. Tone should be direct, not rah-rah.”
→ It sounds like us.

Without context

“Draft an intro for my conference talk on building a team.”
→ Generic, motivational filler.

Power comes from knowing your world: role, audience, situation, goals, style, what matters most. We use our Core language when it fits and skip the frameworks when they don’t help.

5. Draft best effort

We use AI as a performance multiplier, not a blank-page generator. A rough outline, memo, bullet list, or old deck is enough to start. Give it something to sharpen and it will. Tell it what’s working, and what isn’t, in your draft.

With a starting point

“Uploaded is the current job description and here is where the CEO is frustrated […]. Rewrite to highlight expected leadership behavior and desired outcomes.”
→ We get an on-target draft.

Without a starting point

“Write a job description for our COO.”
→ Might be fine, but generic.

6. Iterate

Iteration turns a good draft into a ready asset. Lead with focused passes, then keep what works and tune what doesn’t.

With iteration

  • We read and refine with specific notes: “Tighten the second paragraph.” “Swap these two points.” “Raise the stakes in the opening.” “Cut jargon.” “Add a concrete example here.”
  • We work paragraph by paragraph. We avoid whole-document rewrites. We lock improved sections and move on.
  • We ask for one or two alternatives when a paragraph is close but not quite there.
  • We run a zoom-out pass after paragraph edits. We check sequence and placement, merge overlaps, trim repeats, and fix transitions. We rebalance if one paragraph got over-developed in isolation.
  • We use the right tools. A canvas editor for inline comments. Side-by-side views to compare versions and keep the best parts.
  • We run a quality check. We confirm every word says what we mean, remove filler, and fix lines that sound good but are not accurate or relevant.

Example prompts:

  • “Revise paragraph 3 for clarity; keep the ideas; cut 20%; offer 2 alternatives.”
  • “Tighten paragraph 2 to three short sentences; keep key terms; offer 2 tone variants (direct, warmer).”
  • “Zoom out: propose a better section order for flow to decision; list what you moved and why.”
  • “Find and merge redundancies; flag any paragraphs with overlapping content; keep the stronger phrasing.”

Without iteration

We accept the first draft and leave quality on the table.

Summary points

  • Short, focused passes beat one big rewrite.
  • Lock improvements as you go.
  • Always zoom out after tightening parts.
  • Read every word before you ship.
  • When what you do becomes guidance or a template, add it to the Core Pack.

Try IVOA

IVOA is live and available for everyone to use.

Start by asking: “What can you help me with?”

Ways to work with and learn IVOA

We welcome questions, suggestions, and feedback.

Get Clear. Align. Grow.