The Sling AI Framework™5 stages · Every engagement · Every time

A repeatable
process, by design.

Every Sling engagement runs through the same five stages — same names, same deliverables, same exit criteria. You'll know exactly what we're doing and exactly what you should be seeing. No mystery, no consulting kabuki. The Framework is the operating discipline that makes the technology dangerous.

02 / Why a framework

Discipline beats
brilliance.

Most consulting is heroic — clever people making it up as they go. That's how engagements drift. The Framework is the opposite. Boring on purpose. Predictable by design.

01

Consistency over heroics

A framework means we don't have to be brilliant on the fly — we have to be disciplined. The wins compound. The losses get caught early. Your engagement looks identical in shape to the one we ran last quarter, and the one we'll run next quarter.

02

Visibility you can trust

You know which stage we're in. You know what should arrive at the end of it. You know when to push back. The Framework gives you the language to manage the engagement — instead of waiting for a status update that explains nothing.

03

Exit criteria, on purpose

Each stage has explicit exit criteria. We don't move to the next one until they're met. That's the bargain — predictable progress, no surprise resets. If we miss the criteria, we eat the rework, not you.

03 / The five stages

Same names.
Same deliverables.
Same exit criteria.

Each stage produces a specific artifact. Each stage has a specific timebox. Each stage has explicit exit criteria — the list of things we must demonstrate before we can move forward. Predictable on purpose.

01 / 05

Assess

What's actually going on here?

Timebox

2–3 weeks

Before we propose a thing, we listen. Assess is the stage where we map your workflow, talk to the people who run it, and identify where AI fits — and where it doesn't. The deliverable is an Opportunity Report: prioritized, costed, honest about what AI can't fix.

What we ship
  • Stakeholder interviews (3–8 people)
  • Workflow map of the area in scope
  • Opportunity Report with ranked use cases
  • Honest 'AI isn't the answer here' callouts
  • Recommended next stage + scope
What you do
  • Open the door to your team
  • Share existing process docs, even rough ones
  • Tell us what's already been tried
  • Read the report. Push back hard.
Exit criteria
  • Opportunity Report delivered + reviewed
  • Top 3 priorities ranked + budgeted
  • Decision: continue to Design, or part ways
What if it doesn't go to plan
  • We find AI isn't the right tool. That's a fine outcome.
  • We find more opportunity than you expected. Also fine.
02 / 05

Design

Decide what to build — before you build it.

Timebox

1–2 weeks

Design is where we get specific. Architecture. Tool selection. User flow. Data model. The output is a Solution Spec your team can read in 20 minutes — and a working prototype of the riskiest part. If we can't prototype it in a week, that's a signal, and we say so.

What we ship
  • Solution Spec (20-page max — readable)
  • Working prototype of the riskiest piece
  • Tool / model selection memo
  • Cost model with monthly run-rate
  • Fixed-bid quote for the Build stage
What you do
  • Review the spec — every page
  • Stress-test the prototype with real workflow
  • Approve the quote, or renegotiate scope
Exit criteria
  • Spec signed off
  • Prototype demonstrated against real input
  • Fixed-bid Build quote accepted
What if it doesn't go to plan
  • Prototype reveals a blocker. We replan together, on us.
  • Scope grows. We re-quote transparently before we touch keyboard.
03 / 05

Build

Ship the thing.

Timebox

2–12 weeks

The Build stage is where most consulting firms disappear. We don't. Build runs in weekly check-ins, visible inside the COS, with a working artifact at the end of every week. By the end of Build, your team has the tool deployed in your environment, the code in your repo, and a one-page handoff doc.

What we ship
  • Weekly working build, no exceptions
  • Deployment to your environment
  • Source code in your repo (not ours)
  • Documentation in your wiki
  • 30-day post-launch support included
What you do
  • Show up to the weekly check-in (30 min)
  • Test what we shipped that week
  • Tell us when something doesn't match the spec
Exit criteria
  • Acceptance criteria from Design — all met
  • Production deployment verified
  • Handoff doc accepted by your team
What if it doesn't go to plan
  • We under-quoted the work. We eat the overage. Always.
  • You change scope. We re-quote in writing before continuing.
04 / 05

Train

Make your team dangerous.

Timebox

1–3 weeks · runs in parallel with end of Build

Software you can't use is software you don't need. Train is where we transfer the operating knowledge to your team — not in slides, but in shoulder-to-shoulder time. The goal is competence, not certification: by the end of Train, the people who'll use this every day actually use it confidently.

What we ship
  • Hands-on training sessions (live, recorded)
  • Prompt library + playbook tailored to your team
  • Office hours via Slack for 30 days post-launch
  • Champion identification — who's your in-house lead?
What you do
  • Send the people who'll actually use the tool
  • Schedule the sessions inside work hours
  • Designate the in-house Champion
Exit criteria
  • Champion identified + trained
  • Team demo'd live, using the system on real work
  • Playbook accepted, in your wiki
What if it doesn't go to plan
  • Team isn't ready to adopt. We extend Train or pause to Optimize.
  • Champion turnover. We re-train under AaaS retainer.
05 / 05

Optimize

Measure, tune, graduate.

Timebox

Ongoing · month-to-month · graduation in 6–12 months for most teams

Optimize is the ongoing stage — and the one most engagements forget exists. We measure against the success metrics defined in Assess, tune the system monthly, and aim to make ourselves unnecessary. The COS tracks the work. The AaaS retainer covers the cost. Graduation — when you don't need us anymore — is the goal, not the threat.

What we ship
  • Monthly ROI memo against agreed metrics
  • Active tuning of prompts, agents, dashboards
  • Quarterly playbook updates
  • Graduation roadmap — when you stop needing us
What you do
  • Approve monthly priorities (30-min sync)
  • Surface friction the moment you see it
  • Tell us when you're ready to graduate
Exit criteria
  • Metrics moving in the agreed direction
  • Champion running internal office hours
  • Or: graduation — engagement closed clean
What if it doesn't go to plan
  • Metric doesn't move. We diagnose + tune at no charge.
  • Team graduates faster than expected. Best outcome.
04 / On a calendar

What a typical
engagement looks like.

A common shape — Assess → Design → Build → Train → Optimize — on a real calendar. Most engagements hit production inside 90 days. AaaS picks up from there. Your exact timeline gets quoted after Discovery.

Assesswk 1–3
Designwk 4–5
Buildwk 6–11
Trainwk 11–12
Optimizeongoing →
12345678910111213141516
/// Weeks · counting from kickoff
05 / The operating system

Every stage
runs through the COS.

The Sling Consulting Operating System is where every engagement lives. You get login access from kickoff. You see the stage. You see the deliverable due dates. You see the metrics. You see what we billed and what's left in the budget. We built it because we were tired of consulting that hid its own work.

Live pipeline

You see what we're working on, in real time. No surprise status emails.

Stage tracking

You always know which of the five stages your engagement is in.

Shared metrics

The KPIs we agreed on at Assess are visible to both of us, all the way through Optimize.

Budget burn

Hours spent, hours remaining. Updated daily. No invoice surprises.

Artifact ledger

Every deliverable, signed off, dated. Permanent record of what was promised and what shipped.

Pause anytime

AaaS retainer can be paused via the COS. No phone call, no haggling.

06 / Start at stage 01

Every engagement starts
with a Discovery Call —
your stage zero.

30 minutes, free, no pitch. We learn what you're trying to solve and tell you whether the Framework fits. If it does, you'll get a scoped Assess quote in 48 hours. If it doesn't, we'll tell you that too.

Book a Discovery Call See the pricing menu

You'll hear the stage names again

On the Discovery Call, in the quote, in every weekly check-in. The Framework is the language we use to manage the work.

Skip Assess?

If you already know what you want, the Paid MVP Sprint compresses Assess + Design + Build into 5–14 days. See Pricing.

Capacity check

12 of 15 Pro retainer slots taken. We can run 4 active engagements concurrently. Plan accordingly.