Skip to content
Courses/AI Consultant: From Assessment to Production/Read a business before proposing AI

Read a business before proposing AI

A company is not its software list. Before suggesting AI, understand how it earns revenue, serves customers, fulfils work and learns from failure. You are looking for facts, not a polished story about innovation.

The five questions

  • Who pays, for what outcome, and how is that value delivered?
  • How does a new customer move from first contact to paid work?
  • Where do people wait, repeat work, re-enter information or make judgement calls?
  • Which systems hold the records needed to understand the process?
  • Who owns the process and can approve a change?

Northstar business snapshot

Northstar receives leads through a web form, phone and email. A sales coordinator copies the request into the CRM, asks suppliers about availability, then prepares a quote. The customer may wait two days. A salesperson follows up when they remember. This is a business narrative; it still needs records before it becomes a diagnosis.

Do not confuse a symptom with a process

“Our team is overloaded” is a symptom. “Quote requests are copied from inbox to CRM, then wait for stock confirmation before a salesperson sends a price” describes a process you can inspect. Start with the smallest process that connects to money, quality or material risk.

Terminal
Business reading note
Customer outcome: ____________________
Trigger: _____________________________
First human owner: ___________________
Systems involved: ____________________
Decision points: _____________________
Evidence available: __________________
Unknowns: ____________________________

Practical mission

Fill this note for Northstar's quote process. Mark any detail you cannot prove as unknown. A good assessment begins by protecting uncertainty instead of hiding it.

How this course fitsOpen the map only when you need it.

Complete Aulafy map

How all courses connect

This is not a checklist. Start with the foundation, choose an outcome, and go deeper only when your project needs more control.

  1. 1Understand
  2. 2Apply or build
  3. 3Operate with confidence
01

Choose an application

Turn the foundation into a visible outcome: a website, a business improvement, media, or an interactive experience.

Continue into the technical branch when you need to maintain code, data, or infrastructure.

02

Build with code

Prepare your environment, work with coding agents, and run models while keeping control of your projects.

This branch prepares you to design and operate reliable AI systems.

03

Take systems to production

Combine retrieval, agents, evaluation, security, deployment, and model adaptation when the problem requires it.

You do not need every course: choose the component your system needs and return as it grows.

View full catalogue