Learn · Build shared judgment
Use the free Academy for individual foundations or Company AI Foundations for an employer-sponsored group. Learning does not choose company priorities or authorize workplace use.
Decide · Manufacturing AI readiness
AI Direction is a fixed-scope, three-week manufacturing AI readiness and strategy engagement. It evaluates up to five candidate workflows, analyzes the strongest two, and turns the evidence into an owned 90-day roadmap—not a list of demos—including valid prepare, process-improvement, no-AI, and stop decisions.
Free first step
The AI Fit Call is for an owner, executive sponsor, or senior functional leader with a real business problem. Bring non-sensitive context about company priorities, current AI use, one or two frustrating workflows, and material constraints.
You receive a verbal fit assessment, a recommended next step, and a short follow-up email with relevant resources. The right answer may be the Academy, company learning, AI Direction, another provider, process improvement, or no immediate action.
The call tests fit and routes the next step. It is not a free AI readiness assessment, workflow analysis, business case, strategy engagement, or implementation design.
Included
Not included
Fixed-scope decision engagement
Where should we use AI, where should we not use it, and what should we do over the next 90 days? AI Direction examines actual workflows rather than treating a generic maturity score as a prediction of success.
Use learning when people first need shared judgment. Use AI Direction when leaders have real candidate workflows but need evidence, priorities, and a roadmap. Bounded implementation starts only after one workflow has earned a proceed decision. Managed AI is for approved tools and workflows that need recurring operating responsibility.
Use the free Academy for individual foundations or Company AI Foundations for an employer-sponsored group. Learning does not choose company priorities or authorize workplace use.
Compare up to five actual workflows, analyze the strongest two, record boundaries and prerequisites, and leave with owned decisions and a 90-day roadmap.
Configure, integrate, or build only after a workflow has a sponsor, users, approved information, review authority, a baseline, and a measurable target.
Use recurring management after approved tools or workflows need evaluation, records, user support, vendor review, escalation, and leadership decisions.
| Decision criterion | Evidence expected | Possible decision |
|---|---|---|
| Problem and value | Named users, current workflow, delay, rework, cost, consequence, and a usable baseline or a plan to establish one. | Advance, measure first, improve the process, or stop. |
| Information and source authority | Approved sources, ownership, access, sensitivity, version or conflict rules, and representative non-sensitive examples. | Advance, clean up sources, restrict the scope, or stop. |
| Human authority and review | A workflow owner, qualified reviewer, escalation path, and explicit decisions that AI may not make. | Advance with review, add an owner or specialist, or stop. |
| Technical and operating fit | Current tools, identity and integration constraints, IT/MSP input, users, support owner, and the smallest adequate solution layer. | Use an existing feature, configure, integrate, build, prepare, or stop. |
| Risk, economics, and success measure | Material failure modes, specialist constraints, test method, target, cost range, and the decision rule for continuing or ending the work. | Proceed to a bounded project, prepare, redirect, or stop. |
Three-week process
| Week | Work | Decision produced |
|---|---|---|
| Week 1 · Align and understand | 90-minute leadership education and kickoff; up to five stakeholder interviews; review current use, tools, policies, priorities, and constraints; initial IT/MSP and quality discussion. | A factual operating context and candidate set. |
| Week 2 · Map and evaluate | Two 90-minute mapping sessions; identify effort, delay, handoffs, rework, and knowledge dependencies; score up to five opportunities and analyze the strongest two. | Value, feasibility, boundary, risk, and smallest-adequate-layer evidence. |
| Week 3 · Decide | Prioritize, develop an initial business case and operating boundaries, build the 90-day plan, and hold a 90-minute executive readout. | Owned decisions, prerequisites, stops, and next actions. |
Eight concrete outputs
The customer owns the delivered artifacts and has no obligation to retain Magnetta for implementation or management. The outputs document decisions and assumptions; they are not a compliance certification, general IT assessment, production approval, or promise that every company or workflow is ready for AI.
Executive decision brief
AI opportunity register for up to five candidate workflows
Two detailed workflow briefs
Buy, configure, integrate, build, or no-AI recommendation
AI responsibility map
Safe-use boundary
90-day roadmap
Managed AI recommendation
| Decision field | Illustrative entry |
|---|---|
| Candidate workflow | Pre-screen supplier certification packages for missing required items before a qualified quality reviewer evaluates the package. |
| Boundary | AI may identify possible omissions and point to the governing checklist. It may not approve, reject, disposition, or release a package. |
| Current decision | Prepare—do not implement yet. The checklist owner, current missing-item baseline, approved test information, and conflict rule are not yet confirmed. |
| Next 90 days | Name the owner and reviewer; confirm the controlled source; establish the baseline; approve synthetic or non-sensitive test cases; define accuracy, escalation, and stopping rules; then reassess. |
Customer effort
Possible outcomes
Different workflows from the same company may receive different dispositions. A Direction Sprint is successful when it clarifies the right owner and action, including when Magnetta should not implement anything.
| Outcome | Use it when | What happens next |
|---|---|---|
| Process improvement or no AI | The friction is better addressed through clearer work, source cleanup, deterministic automation, or an existing non-AI feature. | Assign the process or system owner; do not create an AI project. |
| Prepare | A credible opportunity lacks a baseline, owner, approved source, policy, access path, reviewer, or success measure. | Complete the prerequisite and reassess before implementation. |
| Bounded implementation | One workflow has a credible problem, owner, boundary, authorized test information, and measurable target. | Scope one typical 4–8 week configure, integrate, or build project. |
| Managed AI | Approved AI tools or workflows already need recurring review, records, user support, vendor review, and leadership decisions. | Confirm the operating baseline and define the Core or custom management band. |
| Stop or refer | The consequence, economics, authority, information, technical conditions, or required expertise make the work unsuitable for Magnetta. | Record the reason, refer when useful, and do not force another offer. |
Responsibility and outcomes
Who owns what
You receive documented recommendations and a 90-day plan. Production deployment is not included, and your team retains all investment, risk, policy, and production decisions.
Perform the agreed education, mapping, analysis, and documented recommendations.
Supply accurate context, choose priorities, and make final investment and risk decisions.
Clarify infrastructure, identity, security, integration, and support constraints.
Make delegated quality, legal, HR, security, engineering, and compliance determinations.
Included
Not included
A practical next step