PTENES
TRACK 1

🧭 Fundamentals: the work behind the label

The “AI consultant” label opens doors now — but it’s temporary. The work doesn’t change: find the real constraint and prescribe the simplest solution that works. Here, you ground that in the solutions pyramid and learn when the best answer doesn’t involve AI at all.

cost · time · risk ↑ AI agents maximum risk AI workflows more power, more failures Deterministic · no AI cheap, fast, reliable start here
4
Modules
24
Topics
~3h
Duration
Base
Level

Learning path map

Detailed content

1.1~40 min

🪧 The “AI Consultant” label: the window and its expiration date

Why the label sells now, why it will disappear, and how to use it as an entry point without confusing it with the real work.

What it is:

"AI consultant" is one of the strongest labels in the business world right now. There's search demand, available budget, and companies actively looking for someone to come in, analyze their operations, and tell them what to do with the technology.

Why learn:

Recognizing the window of opportunity lets you use it to your advantage: the label opens doors that it won’t open a few years from now, because it will be an expected basic competency.

Key concepts:

Real, temporary advantage; demand + budget exist; the market seeks judgment, not jargon.

What it is:

AI will seep into almost everything. In a few years, the qualifier “AI” will disappear — consultants won’t lose business because “AI” isn’t in their title; they’ll lose because they’re bad consultants.

Why learn:

Plan your career knowing that the lasting differentiator is the quality of your diagnosis, not the label of the day.

Key concepts:

The label is temporary; competence is permanent; the work is still about solving the right problem.

What it is:

When Excel first appeared, some people called themselves “Excel specialists for accounting”; today that would sound strange. “Internet marketing” agencies became just marketing agencies. AI is doing the same to consulting.

Why learn:

The historical analogy sets expectations: we’ve seen this cycle before, and it always ends with the tool becoming an invisible standard.

Key concepts:

New technology becomes standard; the qualifier disappears; the advantage shifts to those who use it well.

What it is:

If you’re positioning yourself in the market, use the label—it works. Just don’t confuse the label with the work: it gets you in the room; results are what keep you there.

Why learn:

Take advantage of the marketing without falling into the trap of believing the answer always has to involve AI.

Key concepts:

Entry point; honest positioning; delivering results keeps the contract.

What it is:

When everyone knows how to talk about AI, what sets you apart is the discipline to solve the real problem with the simplest solution possible.

Why learn:

It’s exactly this discipline that this course trains—and what will keep you relevant after the label loses its meaning.

Key concepts:

Simplicity first; focus on the problem, not the tool; durable judgment.

What it is:

Positioning yourself as someone who solves problems using the best tool — sometimes AI, sometimes not — is stronger than promising AI for everything.

Why learn:

Clients have already been burned by AI promises; consultants who weigh the options earn immediate credibility.

Key concepts:

Outcome message; tool in service of the problem; credibility through restraint.

View Full
1.2~45 min

🔧 The work that doesn't change: find the real constraint and prescribe a solution

The consultant comes in, identifies the real constraint, and prescribes a solution. Technology is the toolbox, not the job title.

What it is:

Like a good doctor, the consultant diagnoses first and only then prescribes. Prescribing before diagnosing is negligence — in healthcare and in business.

Why learn:

This model protects you from rushing to “sell the solution” before understanding the disease.

Key concepts:

Diagnosis before prescription; symptom ≠ cause; the tool comes last.

What it is:

The client asks for “an AI chatbot,” but the real constraint may be a broken onboarding process. The request is the symptom; the work is finding the cause that limits the outcome.

Why learn:

Fulfilling the literal request without investigating is the fastest way to end up with a project that doesn’t move any numbers.

Key concepts:

Request ≠ problem; 5 whys; business outcome as a compass.

What it is:

Every system has a constraint that limits the whole. Improving any other step doesn’t increase the outcome—only the bottleneck matters until it’s resolved.

Why learn:

Directs AI investment where it actually unlocks results, instead of spreading effort around.

Key concepts:

Identify-exploit-subordinate-elevate; local optimization is waste; focus on the bottleneck.

What it is:

Clients hire you for your judgment, not the tool you use. Trust is built throughout the assessment and makes the next contract possible.

Why learn:

The relationship of trust is the real product of consulting — and what makes the practice scalable.

Key concepts:

Judgment as a product; trust compounds; repeat business comes from credibility.

What it is:

Anyone who calls themselves an “AI consultant” starts thinking the answer always involves AI. If all you have is a hammer, every problem looks like a nail.

Why learn:

Recognizing the bias in your own label is what keeps the diagnosis honest.

Key concepts:

Tool bias; the law of the instrument; separate identity from diagnosis.

What it is:

The client doesn’t buy a “model” or “agent”; they buy lower costs, more revenue, less risk, and greater speed. The consultant translates technology into results.

Why learn:

Without this translation, the best technical solution won’t be approved or adopted.

Key concepts:

Business language; value before features; outcome > output.

View Full
1.3~45 min

🔺 The solutions pyramid: deterministic → AI → agents

The mental model that organizes every recommendation. The higher you go, the more expensive, slower, and more ways there are for things to go wrong.

What it is:

The base consists of deterministic workflows: rules, fixed automation, integrations, and SaaS. No AI. Inexpensive, fast, and reliable — they always do the same thing.

Why learn:

Most business problems can be solved here. It’s the default and almost always offers the best value-to-risk ratio.

Key concepts:

Predictable; no hallucinations; cheap to maintain; always start here.

What it is:

The middle layer puts an AI model into one step of the workflow (classify, extract, summarize, generate). More powerful than rules, but more costly and with more points of failure.

Why learn:

It’s where AI adds real value when there’s language, imagery, or ambiguity that rules can’t handle.

Key concepts:

Surgical AI in one step; probabilistic output; requires validation.

What it is:

Agents are at the top: AI with autonomy, tools, and a decision loop. Maximum capability, maximum risk, and the longest time to deliver.

Why learn:

Knowing that this is the riskiest tier helps you avoid promising agents when a simple flow would suffice.

Key concepts:

Autonomy; more points of failure; higher cost and oversight.

What it is:

The higher up the pyramid you go, the more it costs, the longer it takes, and the more ways things can go wrong. Moving up means taking on risk.

Why learn:

Makes explicit the trade-off you present to the client with each recommendation.

Key concepts:

Cost ↑, time ↑, risk ↑; each level above needs to pay for itself.

What it is:

Start at the foundation. Move up only when the problem truly requires the next level. This is the principle behind all the recommendations in this course.

Why learn:

It’s the heuristic that prevents over-engineering and protects the budget and the client’s trust.

Key concepts:

Default to the baseline; moving up is a justified exception; choose the lowest-risk option that solves the problem.

What it is:

Email triage: base = rules by sender/subject; middle = AI classifies intent; top = agent responds and takes action. Same problem, three costs and risks.

Why learn:

Seeing the same case at all three levels trains you to choose the right floor in practice.

Key concepts:

Same pain, different solutions; the right level is the lowest one that solves it.

View Full
1.4~35 min

🚦 When NOT to use AI — and how that builds trust

Forcing AI where it doesn’t fit is the fastest way to lose the client’s trust. Saying “you don’t need AI” is often the most valuable recommendation.

What it is:

Low volume, clear and stable rules, a 100% accuracy requirement, or lack of data: all are signs that AI isn't the way to go.

Why learn:

Recognizing the signs early prevents expensive projects that should never have started.

Key concepts:

Low frequency; determinism required; no data, no AI.

What it is:

Many problems that seem to call for AI are actually poorly structured data. Fixing the database solves the problem without any model.

Why learn:

The foundational solution is usually cheaper, more durable, and enables future AI if needed.

Key concepts:

Foundation before features; data as the cause; fix the foundation first.

What it is:

Switching to a better SaaS product or building a simple, reliable deterministic workflow solves much of what gets labeled an “AI use case.”

Why learn:

The foundational solution delivers value faster and with less risk — and frees up budget for what truly needs AI.

Key concepts:

Buy > build when possible; simple workflows win; less is more.

What it is:

Recommending against AI when it isn’t a good fit signals honesty and competence. The client sees that you’re looking out for their results, not the sale.

Why learn:

It’s the move that builds the most long-term trust—and generates referrals and repeat business.

Key concepts:

Honesty sells; trust > one-time deal; reputation compounds.

What it is:

AI solutions have ongoing costs: APIs, monitoring, human oversight, model drift. The bill doesn’t end at deployment.

Why learn:

Considering total cost over time changes the recommendation — sometimes the base option wins precisely for that reason.

Key concepts:

Total cost of ownership; operational fragility; maintenance is part of ROI.

What it is:

A short checklist — is there enough volume? Is there data? Is there ambiguity that rules can’t cover? Is the error tolerable? Will the benefit cover the ongoing cost? — helps you decide whether to move up the pyramid.

Why learn:

Makes the decision explicit and defensible to the client and your own team.

Key concepts:

Objective criteria; decision recorded; move up only with justification.

View Full
← Back to start Next track: Map →