Inevitable / Consulting firms

Your method is the asset.
Make it software.

Make it defensible. Encode the steps, sources, reasoning, and review gates that distinguish your practice. Give your team a branded workspace that carries the method from a client question to a decision, through delivery, and back to an approved lesson.

Illustrative / One method, separate client workspaces
A firm method with a reviewed lessons loop The firm method supports separate client A and client B workspaces. Each holds its own evidence and decisions. Only approved reusable lessons can return to the firm method. Firm method Steps · sources · review Client A Own evidence Own decisions Client B Own evidence Own decisions Reviewed lessons Approved for reuse

The consulting asset

A method your team can run, inspect, and revise.

The value is in how your firm asks questions, weighs evidence, and decides what deserves a partner's attention. Make those choices explicit without pretending judgment can be automated away.

Encode the method

Capture the engagement sequence, accepted sources, analytical frameworks, and review gates. Define what a complete decision file contains and which uncertainties require escalation.

Deliver the work

Apply that method to client evidence. Compare alternatives, prepare a recommendation, and turn an approved decision into scoped tasks with named reviewers and deliverables.

Compound approved lessons

Review what happened against what was expected. Approve reusable improvements to the method, such as a better question or review gate, while keeping client evidence within its agreed boundary.

The engagement loop

The recommendation is one step in the work.

Keep the question, decision, execution, and observed outcome connected so the next review has a record to work from.

  1. Encode

    Set the steps, evidence requirements, analytical rules, and partner review gates.

  2. Reason

    Build alternatives and examine how several drivers interact. Expose assumptions and evidence gaps.

  3. Decide

    Record the selected path, rationale, unresolved conditions, and approval.

  4. Execute

    Release scoped tasks within the approved authority. Keep deliverables and dependencies visible.

  5. Observe

    Compare actual milestones and outcomes with the decision's expectations.

  6. Improve

    Review proposed changes and approve what can become part of the reusable method.

Illustrative practice / Business strategy

Market entry: enter, wait, or pass?

A client sees an adjacent market growing. The engagement must establish whether the opportunity fits its capabilities and economics, which entry route is credible, and what evidence would change the recommendation.

  • Growth
  • Competition
  • Regulatory path
  • Capability fit
  • Cost to serve

Combine market and competitor sources with client interviews, operating constraints, and cost assumptions. Keep source dates, conflicting observations, and the consultant's interpretation beside the analysis.

Causal exploration varies several drivers together. Slower growth combined with higher service costs may change the preferred route; a simpler regulatory path may change its timing. The model's assumptions stay visible for review.

  1. Review and authorize

    A partner challenges the recommendation. The client approves a bounded validation plan before partner outreach or further work begins.

  2. Run scoped tasks

    Prepare partner diligence, validate service costs, and draft the entry plan. Each task has an input, deliverable, reviewer, and approval boundary.

  3. Edit and regenerate

    Revise the service cost deliverable and regenerate its dependent economics and entry memo. This task counterfactual traces a deliverable change; it is distinct from moving market drivers in a causal model.

  4. Observe and revise

    As validation proceeds, record partner findings, actual costs, and approval progress against the plan. A review can reopen the decision and propose a reusable diligence question.

Illustrative practice / Energy strategy + origination

Build, buy, or partner?

An energy client needs a route to serve growing power demand. Strategy compares where and how to allocate capital. Origination discovers candidate sites, assets, and owners and assesses whether they warrant diligence. Those are related workflows with separate decisions.

  • Gas supply
  • Power demand
  • Utility power delivery timing
  • Permits
  • Capital structure

Test fuel availability, demand evidence, utility delivery assumptions, permitting dependencies, and financing terms together. A change in gas supply and utility timing may alter the preferred capital route before any particular asset is selected.

Explore origination for source discovery and site or owner assessment. Explore strategy reasoning for comparing alternatives and their dependencies.

  1. Separate the approvals

    Review the strategy allocation and the candidate assessment independently. Authorize a defined diligence scope before outreach, commitments, or transaction work.

  2. Run scoped tasks

    Verify ownership, request utility timing evidence, examine gas supply terms, and prepare a permit dependency memo. Review each deliverable before it informs the investment case.

  3. Edit and regenerate

    Replace an assumed utility delivery date in the timing deliverable. Regenerate the dependent schedule, financing analysis, and investment memo for review.

  4. Observe and revise

    Track actual utility responses, permit milestones, and financing terms against the decision file. Review any divergence before revising the route or approving a lesson for future engagements.

Your application / Shared foundation

Your practice defines the work. The foundation supports it.

Your terminology, engagement method, and client experience sit above shared capabilities for source intake, reasoning, decision records, task execution, and application delivery.

Use a workflow

Begin with an existing workflow and assess its fit against one engagement. Agree on the sources, review requirements, and operating boundaries.

Encode your method

Translate your frameworks, templates, and partner checks into a branded application. Reuse the method across separate client workspaces.

Build a practice application

Add custom interfaces, integrations, and delivery steps where the practice requires them. Define branding, licenses, bespoke work, and responsibilities in the agreement.

Your practice. A connected foundation.

Practice layer
Your method, branded client experience, templates, and integrations.
Intelligence and execution
Source discovery, model routing, causal reasoning, decision files, task execution, and monitoring.
Operating services
Identity, access, tenancy, and commercial services beneath each client workspace.

Source discovery and geographic resolution feed infrastructure hosted and operated in your client's cloud. Each workspace keeps its own evidence, decisions, and task records. Reviewed lessons improve the method without pooling client data.

Start with one engagement

Make the method concrete before expanding it.

Bring a representative engagement, its templates, permitted sources, and the people who review the work. Define the decision to support and the boundary of any execution.

  1. Capture

    Document the method, evidence requirements, and review gates.

  2. Run

    Apply it in one client workspace and produce a decision file.

  3. Partner review

    Challenge the reasoning, alternatives, and proposed tasks.

  4. Revise

    Edit a deliverable, regenerate dependent work, and inspect what changed.

  5. Expand or stop

    Review usefulness, effort, and operating fit against agreed criteria before widening the scope.

Discuss an engagement