September 7, 2026 Commercial AI Automation Plans
Pay vs Consulte: How to Choose Your First AI Automation Engagement
The first AI automation engagement fails less often on model choice than on commercial shape. Teams either Pay a published package before the problem is crisp, or they Consulte forever without a scoped win. Those are two honest paths — not two identical buttons with different labels.
Map it with Discovery — $99
Between Pay and Consulte? Get a written map before you pick the wrong path.
This article helps ops and IT leads choose the right first move: self-serve Pay (Starter ZG06 when ready), Consulte when the shape is messy, or Discovery $99 when you are between paths. Package ladder: plans. Discovery vs Starter detail: Discovery $99 vs Starter $2,500. Service catalog entry: services. Strategy framing: AI consulting services and managed IT services.
No invented case metrics, savings percentages, or client logos. Fit patterns only. The test after kickoff is process clarity and a named definition of done — not a slide claiming “automation ROI.”
Two honest commercial paths
Zion’s commercial surface for AI automation is intentionally split.
Pay means you buy a published package with known price and expected shape — most often Starter $2,500 (ZG06) for one scoped automation or ops improvement. You are saying: the problem, systems, and acceptance criteria are clear enough that implementation should start.
Consulte means you start a human-scoped conversation via /contact/. You are saying: the SKU is unclear, stakeholders disagree, controls matter before code, or the SOW will not fit a package. Consulte is not a delay tactic when used correctly. It is the path when forcing Pay would create a bad pilot.
These are not two CTAs for the same deliverable. If a page asks you to “Pay or Consulte” as if they were twins, ignore the sameness and ask: is my problem SOW-ready? If yes → Pay path. If no → Consulte (or Discovery as the cheap map). Catalog lanes under services support both paths; the path choice is commercial, not decorative.
A practical filter: write the one-page SOW you would sign tomorrow. If you can fill problem, systems, access, exception owner, and done criteria without a workshop, you are on Pay. If the page is half blank or three teams must rewrite it, you are on Consulte — or Discovery as the cheap map between them.
Map it with Discovery — $99
Written recommendation: Pay, Consulte, or stop — before a bad pilot.
Pay path — Starter ZG06
Pay Starter ZG06 when problem, KPI (or operating signal), and systems are already clear.
Starter — $2,500 (ZG06) is a project to implement one agreed automation or ops improvement. It expects:
- A one-paragraph problem statement your ops lead can defend.
- Named systems and an access path (who grants tickets, CRM, identity, billing, or tool access).
- An observable success signal — queue quality, exception handling, routing accuracy, spend alerts — without inventing a savings percentage.
- A named acceptor on your side for the definition of done.
Pay fails when kickoff still debates which process to touch, who owns the data, or whether the helper may write. That debate belongs in Discovery or Consulte, not inside a $2,500 SOW pretending to be a pilot.
Published packages and ladder: plans. If you need the deeper SKU comparison first, read Discovery vs Starter.
Pay also implies you will protect the pilot from scope creep. One automation means one. Adding “while you’re in there” desk, FinOps, and agent work turns ZG06 into an unpaid Consulte engagement. Split those into a second SOW or move to Consulte before you pretend the package still fits.
Consulte path
Consulte via /contact/ when the commercial unit is a conversation and a custom SOW — not a checkout.
Consulte fits when:
- Unclear SKU — you do not know yet whether the work is RPA-style automation, service desk helpers, FinOps controls, managed IT coverage, or a blend under AI consulting.
- Multi-team — IT, security, finance, and a business owner all must agree before anything touches production data.
- Regulated or high-audit — evidence, retention, and exception queues must be designed before Pay.
- Vendor maze — existing MSPs, SIs, or cloud partners already own part of the stack; a package pilot will collide without stakeholder design.
- Scope larger than Starter — multiple workstreams, phased rollout, or operating-model change before automation.
Consulte does not mean “we never Pay.” Many engagements Consulte first, then land a Starter ZG06 or a larger SOW once the map is honest. The mistake is using Consulte as endless free discovery — or avoiding Consulte when Pay would be dishonest.
Bring to Consulte: the pain in one paragraph, the systems you think are involved, who must approve production changes, and what “stop / proceed to Pay” would look like. That keeps Consulte from becoming an open-ended tour of every AI idea in the company.
Discovery $99 as the cheap map
When you are between Pay and Consulte, Discovery — $99 is the cheap map.
Discovery is a paid diagnostic: session plus written map of systems, owners, gaps, risks, quick wins, and recommended next track. It is not implementation. It is not a free lead magnet. Book on Discovery.
Use Discovery when:
- You could fund Starter, but you cannot yet defend which automation to fund.
- Pay vs Consulte feels like a coin flip — you need a written recommendation, not another internal debate.
- You want a low-cost gate before a Consulte call so the conversation starts with a map, not a blank whiteboard.
Discovery output often says one of three things: Pay Starter ZG06 next; Consulte because the shape is enterprise-messy; or stop — the pain is process/ownership, not an automation package. All three outcomes are valid. Paying $99 to avoid the wrong $2,500 pilot is the commercial point. Full comparison: Discovery vs Starter.
Map it with Discovery — $99
Then Pay ZG06 if ready — or Consulte when packages are the wrong unit.
Fit patterns (RPA, service desk, FinOps pilot)
Patterns only — no client logos, no invented before/after metrics.
RPA-style process automation. Fit for Pay/Starter when one repetitive back-office flow is documented, systems of record are named, and exception handling has an owner. Fit for Consulte when the “process” is actually five variants across teams with no single owner. Service detail: robotic process automation.
IT service desk automation. Fit for Pay/Starter when L1 patterns are catalogued (access, reset, known errors), routing rules can be written, and humans stay on exceptions. Fit for Consulte when the desk, MSP, and identity owners disagree on who closes what — or when AI helpers would touch privileged actions without a gate. Service detail: IT service desk automation. Coverage model context: managed IT services.
FinOps pilot. Fit for Pay/Starter when cloud or model spend surfaces are known, alert thresholds can be agreed, and finance/engineering share one envelope owner. Fit for Consulte when billing accounts are fragmented, showback is political, or GenAI spend is tangled with classic cloud without a shared map. Pair with AI consulting when strategy and spend control must move together — not as a fake “ROI guaranteed” package.
Across all three: if the pattern is clear and one owner can accept done → Pay path. If ownership and controls are the product → Consulte (or Discovery first).
These patterns are illustrative fit tests, not industry case claims. Your stack, vendors, and audit bar decide the path — not a template that pretends every mid-market desk looks the same.
What good looks like after kickoff
Good after kickoff is process clarity — not a manufactured ROI chart.
- Written scope that still matches day 10. The problem paragraph did not mutate into a second project. Change requests are named, not smuggled.
- Access landed. Systems needed for the automation are reachable; blocked access is escalated with a named owner, not silent drift.
- Definition of done is operational. A live workflow, governed helper, routing path, or spend alert — with who reviews exceptions. Not “we explored AI.”
- Exception queue exists. Humans know what the automation must not decide alone.
- Next track is explicit. Stop, extend via Consulte/SOW, or move toward ongoing coverage under managed IT — decided with a map, not momentum.
We will not claim a deflection rate, a savings percentage, or a certified outcome. If your internal sponsor needs board language without fake math, start from Discovery’s written map and the operating signal you chose at kickoff — then report what actually moved.
Bad after kickoff looks familiar: access still pending after two weeks, success redefined to “demo,” exceptions closed without review, or a second process bolted on without a change order. Stop and re-scope — Consulte or a new SOW — rather than burning the Pay path’s credibility.
Catalog and lane entry points: services · RPA · service desk automation · plans.
Proof chips only: Discovery $99 · Consulting $499 · Starter $2,500 (ZG06) · Response within 24h. Prefer email first? kleber@ziontechgroup.com
Map it with Discovery — $99
Pay Starter ZG06 on plans if ready — or Consulte when the shape is messy.
FAQs
What is the difference between Pay and Consulte for AI automation?
Pay buys a published package (typically Starter $2,500 ZG06) when problem, systems, and acceptance criteria are clear. Consulte starts a human-scoped conversation via /contact/ when the SKU is unclear, multi-team, regulated, or needs a custom SOW. They are not two labels for the same deliverable.
When should I Pay Starter ZG06?
When you have one named process or automation, known systems and access path, an observable operating signal, and a named acceptor for done. If kickoff would still debate what to build, do not Pay yet — use Discovery $99 or Consulte. Packages: plans.
When is Consulte the better first step?
When SKU is unclear, multiple teams must agree, the environment is regulated or high-audit, vendors already own parts of the stack, or scope will exceed a single Starter. Consulte designs the SOW; Pay can follow. Contact: /contact/.
How does Discovery $99 sit between Pay and Consulte?
Discovery is the cheap map when you are between paths: paid diagnostic with a written recommendation for Pay, Consulte, or stop. It is not implementation. Book Discovery. Deeper SKU comparison: Discovery vs Starter.
Do you publish case study ROI for RPA or service desk automation?
This guide uses fit patterns only — no client logos and no invented savings percentages. Good after kickoff means process clarity, access landed, and an operational definition of done. Service pages: robotic process automation and IT service desk automation.
Where do Consulting $499 and the rest of /plans/ fit?
Consulting $499 sits between Discovery and Starter when you need RACI, operating model, or roadmap without buying a pilot yet. Starter ZG06 is the Pay pilot. Growth is ongoing coverage after the model is clear. Full ladder: plans. Strategy lanes: AI consulting services and managed IT services.
See also: Discovery $99 vs Starter $2,500 · Discovery $99 · Plans · Consulte / contact · Services · RPA · IT service desk automation · AI consulting services · Managed IT services