Have IQ pressure-test your plan

What this is

Modeling a plan in the scenario modeler answers "what do the numbers do." Pressure-testing it answers a different question: what would your Co-COO actually say about this plan, given your real capacity, your cash cycle, and what breaks first if you push growth. The projection chart and the dollar figures above it are pure math, built the moment you move a slider. IQ's read is a separate step you ask for on purpose: it reasons over the exact numbers on screen against your operating picture and comes back with a verdict, not just a chart.

This is the on-ramp to the financing conversation. A modeled plan that ties up materially more cash than you run today is exactly the kind of thing a working-capital decision needs to see clearly before you commit to it, and IQ's read is where that cash reality gets said out loud.

Verinode does not decide whether to run the plan. IQ reasons over the numbers you gave it and hands you a read; you choose whether to commit it, change it, or drop it.

Where to find it

Open Forecasting from the sidebar at iq.verinode.ai/forecasting. In the Take Action row at the bottom of the page, the first tile is always Model a growth plan, labeled "Plan ahead." Click it to open the full modeler in an overlay. See Forecasting: past, present, and future demand for everything above that row: the demand outlook gauge, your capacity gauge, and IQ's connected read on the page itself.

Inside the modeler, set your three levers (field crew, gross margin target, demand adjustment) and read the 12-month projection. Below a hairline divider under the projection sits the section this article covers: IQ's read on this plan.

The capacity flag, before you ask for anything

The moment your plan pushes growth, meaning you've added field crew or dialed the demand adjustment above zero, and Verinode already has a flagged operating constraint in coverage, people, or equipment, a line appears immediately under the "IQ's read on this plan" heading. No click required, no Intelligence Capacity spent:

Capacity matters here: [the constraint, in plain language] is what breaks first. Fix that alongside this plan or the growth won't land.

For example, if your binding constraint is "Water line has no qualified crew," the note reads "Capacity matters here: water line has no qualified crew is what breaks first. Fix that alongside this plan or the growth won't land." It is marked with a small red dot, the same visual language Verinode uses elsewhere for something that needs attention.

This note only shows for constraints in the coverage, people, or equipment domains, since those are the ones a growth plan actually runs into. A cash or safety constraint doesn't block a growth plan the same way, so it doesn't trigger this particular flag (though IQ's cash-and-financing read below can still raise cash separately). And it disappears once you have a full read from IQ, since the full read covers the same ground with more context.

Running the pressure-test

Below the capacity flag (or in its place, if none applies), a button reads Have IQ pressure-test this plan, on a teal background, with a line underneath: "Reasons over your capacity, cash cycle, and what breaks first." Click it.

While IQ is working, the button's label changes to "IQ is working through it…" and it disables so you cannot double-fire the request. This is operator-initiated AI, so running it draws a small amount of your monthly Intelligence Capacity, the same way any on-demand specialist call elsewhere in Verinode does.

Once IQ answers, the button row changes: the heading "IQ's read on this plan" now has a Re-run link beside it (underlined, plain text) instead of the pressure-test button, so you can ask again any time without losing your place. Any lever you move afterward, crew, margin target, or demand adjustment, immediately clears the read on screen. That is deliberate: the read is only ever shown for the exact plan it was generated against, never a stale answer sitting next to numbers you've since changed.

Reading IQ's answer

When the read comes back, it renders directly on the page, flowing flat with no card frame, in this order:

The verdict pill and headline. A small rounded pill reads one of three words:

• Go, green, the plan holds.
• Caution, yellow, workable, but only with fixes.
• Stop, red, don't run this plan as modeled.

Beside the pill sits a short headline, no more than about ten words, stating IQ's call in plain language (for example, "Growth works if you fix coverage first").

The read. Two to four sentences underneath the headline, explaining what this specific plan actually does, in terms grounded in the numbers you modeled: your projected revenue, your margin target, your added or reduced crew, and what that means together.

What to watch. When IQ flags one to three concrete things, they appear as a bulleted list under the label "What to watch," each with a small yellow dot. These are the things most likely to break first if you run this plan as modeled, whether that's a coverage gap, a hiring timeline, or a margin assumption that's thinner than your history supports. This list is omitted entirely when IQ has nothing specific to flag.

Cash & financing. When the plan ties up materially more (or less) working capital than your current run-rate, a note appears under the label "Cash & financing," set off with a small copper rule down its left edge. This is where the cash-cycle reality gets stated plainly: growth that is profitable on paper can still strain you if the cash to fund it is tied up in receivables at your real days-to-pay. When cash movement isn't material to this particular plan, this block is left out rather than padded with a note that doesn't matter.

Next move. The last line is always the single highest-leverage next step, prefixed "Next move:" in bold. This is IQ naming the one thing to do first, not a list of five.

If you're out of Intelligence Capacity

If your account doesn't have enough Intelligence Capacity left to run the pressure-test, the button never queues a request that fails silently. Instead, the pressure-test button and its helper line are replaced with:

You're out of Intelligence Capacity for now. Upgrade or top up to have IQ analyze plans.

Nothing runs, and no verdict appears, until you upgrade your membership or top up. The modeler itself, the sliders, the projection chart, and the projected numbers, still works fully in this state; only IQ's reasoned read is paused. You can still commit a plan without a pressure-test read at all (see below), you simply won't have IQ's verdict, watch-list, and next move attached to it until your capacity resets or you top up.

Turning the plan into a decision

Whether or not you've run IQ's read, a Turn this into a plan button sits below the whole section, on a copper background. Clicking it (the button reads "Creating plan…" while it saves) writes the plan as a standard Verinode decision, the same kind you see in the feed and on /decisions. Once it saves, a confirmation line appears: "Plan created. Find it in Take Action and your Decisions."

The title Verinode gives the decision depends on your crew lever: "Grow: add N field crew, target X% margin" if you added crew, "Tighten: N fewer field crew, target X% margin" if you cut it, or "Hold crew, target X% margin" if crew stayed flat. The decision carries a concrete, ordered action plan, not just a headline:

1. 1If you added crew: line up the added field staff (hire, cross-train, or redeploy) before the capacity is needed, then lock in subcontractor and equipment capacity while backlogs are tight, so trades don't become the bottleneck.
2. 2If you cut crew: plan the reduction and re-sequence open jobs so cycle times hold.
3. 3Set the modeled gross-margin target with your estimators and hold the line on scope and supplements.
4. 4Review working capital for the ramp: with a longer cash cycle, confirm your float, or a line of credit, covers the growth before you commit to it.
5. 5Re-run this scenario in 30 days against actuals and adjust.

That last step matters: a plan committed today is a starting point, not a locked-in forecast. Re-running the modeler against your real numbers a month later is how the plan stays honest as conditions change.

The baseline behind every plan

IQ's read (and the projection it reasons over) always starts from your own operating numbers where you have them: revenue, gross margin, headcount, and average days-to-pay. Where any of those are thin or missing, peer medians fill the gap so a newer operator can still model a plan on day one. A small label above the sliders in the modeler tells you plainly which situation you're in: "Built on your own numbers," "Your numbers, peer-filled where missing," or "Peer medians until your data fills in." The more of your own data that's flowed in, particularly through connecting your data, the more the plan (and IQ's read on it) is actually about your business rather than the peer cohort.

Best-practice example

Say your demand outlook reads Busier and your capacity gauge shows a binding constraint: "2 service lines are one-deep." You open the modeler and add two field crew, matching the outlook's suggested demand lift. Because the plan grows headcount while a people constraint is active, the capacity flag appears immediately: "Capacity matters here: 2 service lines are one-deep is what breaks first." You click Have IQ pressure-test this plan anyway, since the flag alone doesn't tell you whether the hire timeline actually lines up with the season. IQ comes back Caution: the plan holds on paper, but your hiring lead time is likely to lag the demand ramp, and the working capital tied up at the new run-rate is meaningfully higher than today. Its next move is to start recruiting for the two field roles now, before the season lands, and to confirm your line of credit covers the gap in the meantime. You turn the plan into a decision, and the action plan opens with exactly that: lining up added staff before the capacity is needed.

Related help articles

• Forecasting: past, present, and future demand
• Understanding your margin
• The decision workspace
• Acting on decisions
• The feed
• Benchmarks overview
• Connecting your data

Data sources