MarqIQ
Browse all help topics
How to25 min read

Read the Suggested Plan

Last updated 19 October 2026Available onFree TrialProBusinessEnterpriseNeedsHubSpotSalesforceMarketoPipedriveZoho CRMMicrosoft DynamicsPardotMailchimpSalesforce Marketing CloudAdobe CampaignAdobe Journey OptimizerAny one of these connected and synced. Starter does not include the Suggested Plan. Two parts need more than that: the AI-written brief needs an AI account connected under Account then AI & Providers, and the AI-visibility tile needs a brand profile, which is a Business-plan feature.

The Suggested Plan page turns one tool’s data into a quarter plan: five headline numbers, a grade per area, what to invest in, what to fix, and a six-month roadmap. This article goes card by card and says what each figure was measured on, because that is the question your board will ask. If you only want to know where to start on Monday, read What should you fix first? instead — this article is the one to read before you quote a number from the plan to anyone.

Before you start

You need one tool connected with its first sync finished. The plan reads that tool’s synced records; nothing on this tab reads any other tool.

Tip

Set the Created filter before you read anything. The Executive Read, Data Audit, Analysis and Suggested Plan views all cover the same population, so the four agree on how many people and deals you have. The filter lives in the page address, so a scoped view can be pasted to a colleague.

Two figures are not scoped by that filter

The Submissions, no first touch tile and the AI answers that mention you tile are measured on different populations, stated in full under The five tiles below. Everything else on the tab is measured on the records the audit analysed.

Open the Suggested Plan

  1. Open Insights in the left-hand menu, then Suggested Plan.

    The other views are Executive Read, Data Audit, Analysis and Field Intelligence. Report Templates stays on the tool’s own page under Data sources.

  2. Pick the tool you want the plan for along the top.

  3. Set the Created filter to the period you plan against.

  4. Wait for the plan to draw.

    It reads your audit, your submissions and your profile, and it waits up to 40 seconds for the Analysis suites. An analysis slower than that contributes nothing, and What this plan could draw on says so in as many words.

  5. Click Rebuild after you change anything.

    The plan is held for five minutes per tool and per date range, so re-opening the tab is instant. Rebuild is the only thing that ignores that. The time underneath is when the plan you are looking at was built.

The headline, the brief and the line between them

The top card carries four things. Read them in order.

  • A badge reading Suggested plan or Readiness plan. The second means MarqIQ refused to rank anything — see When you get a readiness plan instead.
  • The headline: the title of your first investment bet, or of your first fix when there is no bet, or “Where to spend the next quarter” when neither fired.
  • One line saying what the plan covers — for example “Read all 77,662 people.” or “Read 12,400 people created in the last 12 months (of 77,662 in all).” That is the population every figure below rests on, apart from the two tiles named above.
  • A short brief. It appears a beat after the numbers and never holds them up.

The line under the brief says where the brief came from. Written by AI from this plan — every number checked against it means a model wrote it. Summary from the plan means MarqIQ’s own wording shipped instead.

What the brief is allowed to do

It is allowed to say the plan well. It is not allowed to add to it. Every draft is checked against the plan it was written from: any number that does not appear there verbatim fails the draft, and so does any currency symbol followed by a digit, or any figure carrying a K, M or B. A failed draft is never shown to you — MarqIQ’s own summary ships in its place. That is why the brief can go into a board pack as it stands.

Where the numbers come from

This is the short answer to “can I trust it?”. Four rules hold across the whole tab.

  • No model chooses, computes or words any figure, verdict or ordering. The plan is worked out the same way every time from the same inputs. AI writes one paragraph, and only over numbers the plan already contains.
  • Every figure names what it was measured against. A card’s evidence rows read “value of denominator”: a rate always arrives with the number of records it was computed on, never on its own.
  • There is no benchmark of any kind. Every comparison is against your own overall rate, never against an industry average, because MarqIQ holds no cross-customer dataset.
  • A rate that cannot clear a volume floor and a confidence bound is reported as not enough to go on, never quietly dropped. A missing section reads as “we checked and it was fine”, which is worse than an absent one.

Take care

MarqIQ stores the current state of each record and no history of how it got there. Nothing on this tab describes time in stage, stage-to-stage conversion, or whether records are slowing down. That limit is printed under Show the working on every plan.

The five tiles

The strip across the top frames everything under it. The three columns below are what each tile counts and, in the third, the population it counts it on — the part that decides whether two tiles can be put in the same sentence.

TileWhat it countsMeasured on
Contact → customer, or Win rateThe share reaching the positive outcome, to one decimal place. The label tells you which of the two you are reading.The records the audit analysed under the Created filter. The caption reads hits of decided: customers over contacts carrying a lifecycle value, or won deals over won plus lost with open deals excluded.
Lead source fillHow much of the database carries a source at all, to the nearest whole per cent.The same analysed records. The caption under the number is the field’s own label as your tool spells it, never its internal key.
Submissions, no first touchThe share of tracked form submissions that arrived with no usable first source.MarqIQ’s own captured submissions for the whole workspace over the last 365 days, at most the 20,000 most recent. Not your CRM records, not this one tool, and not the Created filter.
AI answers that mention youThe share of AI answers that name your brand.The scored answers of your latest finished visibility run. The caption reads “N of M answers” — answers that came back, of calls attempted. Prompts that already name you are asked but never scored, and they are excluded from the rate and from the count beside it.
Records analysedHow many records everything above and below rests on.The analysed records. The caption names the tool, or reads readiness mode.

Colour is set on stated thresholds, not on judgement. Lead source fill is green at 70% or more, amber from 50% to 69%, red below 50%. Submissions, no first touch is green under 15%, amber under 25%, red at 25% or more. AI answers that mention you is green at 40% or more, amber from 20%, red below.

A dash on a tile is not a zero

The outcome tile reads Outcome rate with a dash when no outcomes are synced. The lead source tile keeps its label and reads a dash over no source field when no source field resolved at all. The submissions tile reads Tracked submissions · 0 · script not live when nothing has been captured. The AI tile distinguishes no brand profile, no run yet, last run failed — no engine answered, partial run, run health unknown on a run made before MarqIQ recorded how much of it came back, and every prompt names you — none scored. Each of those is a different thing to do about it.

The scorecard

Five areas, one grade and one line each: Data foundation, Lead scoring, Lifecycle & handoff, Campaign mix, and Content & enablement. It exists so you can see the shape of the problem before opening a single card.

GradeWhat produced it
ANothing fired in that area, and its inputs were available. The line reads “Nothing here needs changing this quarter.”
BThe worst finding in the area is medium or low.
CThe worst finding in the area is high.
DThe worst finding in the area is critical.
—Not measured: the area’s inputs were unavailable and nothing fired in it. The line names what is missing and what would fix it.

The line beside the grade is the title of the leading finding in that area, with “(+2 more)” when there are others. Findings that were real but held back by the three-item cap still count towards the grade, so a fourth problem never turns an area into an A.

A dash is never a pass

Each area declares the inputs it needs. Data foundation and Lifecycle & handoff need synced CRM records. Lead scoring needs records, outcomes and a scoring model. Campaign mix needs outcomes, lead source coverage and the segment conversion breakdown. Content & enablement needs outcomes and that breakdown. Where an input is missing and nothing fired, you get the dash. Where an input is missing but something did fire, the area is graded on what fired — a real problem is not a blank.

Where to invest

At most three growth bets, ranked on their own number rather than on severity, and read in the same sitting as the fixes rather than after them. Two different kinds of item compete for those three slots.

  • Ranked bets, which compare a segment against your own baseline. There are four of them, and each writes its own headline from your records, so the card is titled with the finding rather than with a fixed name — “Put more into Paid Search — it converts at 2.4× your baseline”, for instance. You see their fixed names, Where to invest next, Your best buyer, from the data, What to stop feeding and Revenue concentration, only under What we could not tell you, where a bet that did not run is listed. All four need enough decided outcomes to rank anything.
  • Growth motions, which rank no channel and so need no conversion statistics at all: a win-back to the people you can still email and have stopped talking to, a second way in when one form carries the intake, one campaign tagged properly so a single cohort is clean from the start, and a campaign that creates the behaviour a score will read when scoring is not set up.

Each motion carries its own volume floor, stated on the card: 100 or more quiet and never-engaged people; 30 or more people a form brought in, with one form holding at least half of them; 200 or more people with at least a quarter of them carrying no source; and, where MarqIQ has checked that your tool supports lead scoring and found none set up, 100 or more people.

Where to invest next has to clear three tests before it appears: at least 30 records in the segment, at least 2% of the volume in that field, and a conservative lift of 1.5× or more over your baseline. The lift quoted is the Wilson lower bound, not the raw ratio — the number MarqIQ is willing to defend rather than the flattering one. Your best buyer, from the data puts every firmographic field through those same three tests and combines the winners.

The other two bets are tested differently, and the difference matters when you quote them. What to stop feeding needs 60 or more records on the value, at least 10% of the volume in that field, and a conservative lift of 0.6× or below — the Wilson upper bound this time, so the segment is under baseline even read generously. Revenue concentration runs no rate test at all: it needs two or more values carrying a recorded amount, with the largest holding 40% or more of that recorded revenue.

Open Where to invest next and you get its evidence rows, each with its denominator: the segment’s rate of N records, your overall rate of N records, the conservative lift against baseline, customers above baseline as “produced versus expected”, and the segment’s share of volume. A revenue row appears only where your CRM carried an amount on those records. The other three bets carry their own rows, each written the same way.

Tip

Read the Done when line and the Stop if line together. A scale-up is bounded on purpose: “still at or above 2× baseline at the higher volume” is the condition, and the moment the rate drops towards baseline you have found the channel’s ceiling. That is the answer, not a failure.

When the section is a paragraph instead of cards

Where no channel cleared the test, the card shows the reason and the threshold in full — the record floor, the volume share and the lift it would have needed over your stated baseline — rather than disappearing.

What to fix

At most three repairs, in order. Three things decide that order and nothing is re-judged here: severity first, then reach — how much of the analysed population it touches — then effort, so a tie goes to the cheaper action.

Every card folds open on its headline, its owner role, one number and its definition of done. Open it for the full evidence. Inside, each card reads in the same four parts: What we found, What to do, Why it matters, Done when.

  • The owner is a role, never a person: Marketing Ops, Demand Gen, Content, RevOps, Sales leadership, CRM admin or Leadership. A recommendation with nobody attached is the one that gets nodded at and never scheduled.
  • Done when is a condition the same analysis can confirm on its next run — “Lead source populated on at least 70% of records, with one system as the writer” — never an invented percentage lift. MarqIQ has no counterfactual, so it does not quote one.
  • A finding raised by an Analysis suite carries a line reading Found by the … analysis with a See the evidence link straight to the analysis that holds it.

Two more repairs sit under Worth doing alongside, inside Show the working. They are the cheap end of what is left, picked because they can be absorbed without displacing the three above.

This week

The low-effort items on a 30-day horizon, sorted by severity, at most three, each prefixed with the role that owns it. Hand them to whoever has capacity now and ship them while the quarter plan is still being agreed. The section does not appear at all when nothing qualifies.

What sales should know and What RevOps should settle

The same plan restated in two columns, at most four lines each. No claim is added here — both columns are re-cut from findings that already fired.

  • What sales should know is a prioritisation change: which segment to work first and the rate that justifies it, the best buyer written from your records, which segment is getting negative scoring weight, and where qualified records are landing with no owner.
  • What RevOps should settle is definitions, denominators, handoffs and governance: fix the source denominator before any channel number is quoted, write sourced and influenced into the field descriptions, instrument the handoff with an ownership timestamp and an SLA, agree a survivorship rule before any merge.

Note

The sales column reads “Nothing specific this quarter.” when no relevant finding fired. The RevOps column always carries at least one line, because it closes with the plan’s first definition — so the two-column block is on screen whenever the plan produced definitions at all.

The six-month roadmap

Six months as a strip, starting the first of next month. Open a month for its card. The sequence is ordered by dependency, not by your calendar.

MonthWhat sits there
1Fix the measurement foundation, when the plan found data gaps. Otherwise baseline and instrument, so month 6 is not an argument about the starting point.
2The segment your own records convert best in. Failing that, the buyer you named on the business form. Failing both, segment discovery.
3The controlled test, with a holdout. Or a channel test where you run a channel the tracked data cannot see.
4The engine: a nurture path where records are parking at a stage nobody actions, otherwise a content engine for the segment.
5Visibility: answer-engine work, a re-measure where the last run was not usable, or a posting rhythm on a platform you told us about.
6Re-audit and re-plan against the KPIs written down in month 1.

Every month card carries an Audience, Channels, Ship (the assets), Measure (the KPI, with its baseline where there is one), a Stop if on anything that is a bet, and Why here. A month that depends on an earlier one says so under After.

The chip beside each theme is the one to read first. From your data means the month rests on something measured. From what you told us means it rests on the business form. Data + what you told us means both. Those deserve different confidence, and hiding the difference is how a roadmap becomes a template with a logo on it.

A hold is not a gap

A month with nothing honest to put in it reads Hold: keep the running work clean and names the work it is letting run. Nothing is invented to fill a slot.

One roadmap KPI is worth knowing the arithmetic for. The answer-engine month appears only when a usable run shows a mention rate under 25% across at least five prompts, and its target is your own baseline plus exactly 10 points, capped at 100. It states that baseline as a percentage of a named number of answers across a named number of prompts. Where the last run was not usable, the month becomes a re-measure instead, because aiming a quarter at a measurement gap is not a programme.

Above the strip sit two short lines. The first is the premise the roadmap was built on: what you sell and who buys it, where you have told us, and otherwise the sentence “Built from your synced data alone.” The second reads Sharper if you tell us … and names the single most useful thing still missing from the business form.

The roadmap’s own caveats are not on this tab

The roadmap carries a list headed What this roadmap is not claiming — that no spend, revenue or ROI figure appears in it, that months resting on stated context will be confirmed or corrected by the next audit, and that the months are ordered by dependency rather than by your calendar. The strip on this tab is the compact one, and it does not print that list. The plan’s own limits do appear, under What this plan is not claiming inside Show the working, and they are the ones to read before quoting a figure.

What this plan could draw on

Twelve rows under Show the working, with a count in the heading reading “n of 12”. Each row is one input the plan could have used, whether it did, the real figure behind it, and — where it did not — the exact setup step that would unlock it.

RowTicked whenWhat the unlock says
CRM records500 or more records analysed.Connect a CRM or import a larger file; 500 records is the floor.
Outcomes to compare against30 or more records have reached a decided outcome.Sync lifecycle stage (contacts) or closed-won/lost (deals).
Lead source coverageA source field resolved and filled on 50% or more of records.Populate lead source to at least 50% — the channel plays gate on it.
Segment conversion breakdownAt least one field has its values ranked by rate, which needs a value clearing the 30-record floor with an outcome.Regenerate the audit after the next sync; channel and content plays need it.
Scoring modelAt least one score-like property was found.If you score leads, sync the property your model writes to.
Form submissions (MarqIQ script)100 or more tracked submissions.Install the tracking script; channel-level KPIs and form checks need it.
Website & positioningA brand profile exists and your site has been read.Set up the brand profile under AEO; it reads your site in seconds.
Social presenceSocial links found on your site, or posting cadence given by you.Tell us where you post and how often — MarqIQ cannot see posting activity.
AI-answer visibilityYour latest visibility run is usable — not failed, partial or pre-tracking.Run an AEO visibility check, or the run’s own unlock sentence.
Email activityOnly from the Integration Audit report. Never on this tab.Run the Integration Audit for HubSpot to include email performance.
What you told usThe business form is at least 40% filled in.Tell us the two questions it names.
Analysis findingsThe Analysis suites were read for this tool.Open the Analysis view once, then rebuild the plan.

The unticked rows are the point of the strip. They are the shortlist of what to connect or tell us to make next quarter’s plan sharper, and they are why a plan that lists its own blind spots is the one a sceptical executive can read.

Show the working

One toggle at the foot of the tab, reading Show the working — what this drew on, what else fired, definitions and limits. It holds five things: the coverage strip above, Worth doing alongside, What we could not tell you, Definitions used here and What this plan is not claiming.

Definitions used here

The terms this report uses, as it uses them, so the meeting does not start with an argument about denominators. It always states which of conversion rate or win rate you are reading and what its denominator is. It adds how “sourced” was classified and from which field when the audit could compute that, that stages are a snapshot of where records sit today and not a history of how they moved, and how many records were analysed from which tool over which created window.

What this plan is not claiming

Printed, not footnoted. Every plan carries the no-history limit. A workspace with no opportunity rows also carries a line saying no figure anywhere carries a currency amount. A contact-grain workspace carries a line saying its rates are conversion rates and are never mixed with a deal win rate. A sampled audit says its figures describe the records analysed and not the whole database. Every plan carries the line that there is no cross-customer benchmark anywhere in it.

What we could not tell you

Every check that did not reach the page, with its reason and what would bring it back. Most reasons are written by the check itself and name the figure that failed — “No lead-source field resolved in the analysed records.”, for example. Six reasons are written by the plan rather than by a check, and those six mean different things.

The reason readsWhat happened
Real, but ranked below the items aboveIt fired and lost the cut to three primary items. It appears in the next plan once the items above are closed.
Real, but held back so the first items get doneThe same, on a readiness plan.
A real opportunity, held back so the three bets above get funded firstA growth bet or motion outside the top three.
Folded into “…”, which the … analysis found with fuller evidenceAn Analysis suite raised the same problem while reading the tool far more closely, so the plan’s own thinner check is not said twice.
Folded into the investment bet on …The bet and the channel test named the same segment; the bet carries the evidence and the controlled-test design.
Withdrawn: …An analysis looked closer and knows the check does not apply here. Today one check does this: the missing stage-stamps item is withdrawn when the Funnel analysis is already timing every step from your tool’s own stage-entry dates.

A check suppressed by the outcome gate is listed here too, with the figure that failed the test and the sentence “Sync outcome data and reach at least 30 decided records, then this runs.” A check that threw an error reads “This check could not complete against the current data.” and is retried on the next audit; nothing is dropped in silence.

When you get a readiness plan instead

Before anything else runs, MarqIQ asks whether there is an outcome to measure at all. Any one of four answers stops it ranking:

  • Fewer than 500 records were analysed. That is the count under your Created filter, not everything you have synced, so a narrow filter can trip this on its own.
  • No outcomes are recorded at all.
  • Fewer than 30 records have reached a decided outcome.
  • A source field resolved and is populated on under 50% of records, so a channel ranking would describe the recorded minority. A workspace where no source field resolved at all passes this one and is stopped by the checks above instead.

What you get then is a different document, not a shorter one. The badge reads Readiness plan, the headline becomes “Making the next quarter measurable”, and the fix column is titled Make the next quarter measurable with the line “Nothing here ranks a channel; every item makes the next quarter measurable.” Only checks that rank nothing are kept. The growth motions stand beside them, so the quarter is not all repairs.

Work those items first. They are what makes the next plan rankable, and the reason on screen names which of the four stopped it, so you know what to fix.

One number on the decided-outcomes reason is the wrong one

Where the third check stops the plan, the sentence reads “Only N records have reached a decided outcome; at least 30 are needed.” The test is run on the number of decided records, but the N printed is the number of those that reached the positive outcome, which is always the smaller of the two. The Outcomes to compare against coverage row repeats the same figure. Read the caption on the outcome tile instead — it reads hits of decided, and the second number is the one the 30 is compared with. Do not quote either sentence’s number as your decided count.

Which parts stay blank, and for which tools

Nothing here is hidden, but several sections read differently depending on what your tool holds. These are the ones worth knowing before you present the plan.

What changesWhich toolsWhy
No currency figure appears anywhere, and the outcome tile is a contact conversion rate rather than a win rateMarketo, Mailchimp, Salesforce Marketing Cloud, Adobe Campaign, Adobe Journey OptimizerMarqIQ syncs no deal records from these five, so there is nothing to carry an amount. The limit is printed on the plan. Deals do sync from HubSpot, Salesforce, Pipedrive, Zoho CRM, Microsoft Dynamics and Pardot.
The Email activity coverage row is never ticked, so the count in the heading stops at 11 of 12Every tool, on this tabThat row is only ever filled from the Integration Audit report. Open the plan from Integration Audit instead to include email performance.
The growth motions do not appear, and the Analysis findings coverage row is never tickedAn uploaded spreadsheetBoth are built from the Analysis suites, which read a connected tool. On a spreadsheet plan the row still shows, unticked and with no unlock line under it, so there is nothing there to act on. The ranked bets and the fixes are unaffected.
The AI answers that mention you tile reads a dash, and two coverage rows stay untickedAny tool, on Free Trial or ProThe tile and the Website & positioning and AI-answer visibility rows all rest on a brand profile, which is a Business-plan feature.
The Submissions, no first touch tile reads Tracked submissions · 0 · script not liveAny tool, before the script is installedThat figure comes from MarqIQ’s own captured submissions, not from your CRM. No sync fills it.
This week is missing entirelyAny toolNothing that fired is both low effort and on a 30-day horizon. That is a result, not an error.
A month of the roadmap reads Hold: keep the running work cleanAny toolNeither the data nor your stated context supports a launch that month. A stated hold is more useful than an invented initiative.

Tip

The fastest way to fill several of these at once is the Tell us card near the foot of the tab — it reads Update once you have filled in enough of it, and shows how much of the picture you have given. What you sell, who buys it and how you sell cannot be read from any CRM, and months 2 to 5 of the roadmap are written from it. Click Rebuild after saving.

If it did not work

Two tiles seem to disagree, or a tile does not match the Data Audit

Why: They are measured on different populations. The outcome, lead source and records tiles are measured on the records analysed under the Created filter. The submissions tile is measured on the whole workspace’s tracked submissions over the last 365 days, at most the 20,000 most recent. The AI tile is measured on the scored answers of your latest visibility run.

Fix: Read the third column of the table under The five tiles before comparing any two of them. Quote each figure with the population named there.

The plan shows fewer items than the analyses found

Why: The output is capped at three bets, three fixes and two maintenance items, whatever fired. Nobody sequences fourteen things.

Fix: Click Show the working and read What we could not tell you. Every real item that missed the cut is there with its reason and when it comes back.

An area on the scorecard shows a dash rather than a grade

Why: That area’s inputs were unavailable and nothing fired in it. A blank is never treated as a pass.

Fix: Read the line under the dash — it carries the unlock sentence from the coverage strip, so it names the connection or setup step that would make the area measurable.

Where to invest is a paragraph rather than three cards

Why: No channel cleared all three tests: at least 30 records, at least 2% of the volume, and a conservative lift of 1.5× over your baseline.

Fix: Read the paragraph — it quotes the thresholds and your own baseline. Either more resolved outcomes or a channel that genuinely outperforms will bring the cards back; nothing else will.

The Analysis findings coverage row says the analyses were still being read

Why: The plan waits up to 40 seconds for the Analysis suites and builds without them rather than failing.

Fix: Open the Analysis view once so the suites are computed, come back, and click Rebuild.

The brief did not appear, or reads as a plain summary

Why: The brief is a second request that never holds up a number. MarqIQ’s own summary ships instead in four cases: no AI account is connected, the provider sent nothing back, the draft failed the grounding check, or you have already asked for more than six briefs in the same minute.

Fix: Nothing is wrong. The line under the brief says which you are reading, and every figure in it is checked against the plan either way. Connect an AI account under Account then AI & Providers if you want the written version. A brief is then held for half an hour against the same plan, so clicking Rebuild without changing anything underneath returns the brief you already had.

You fixed something and the plan has not changed

Why: The plan is held for five minutes per tool and per date range, and the figures underneath it only move after the next sync.

Fix: Click Rebuild at the top right of the plan card. If the numbers still look stale, click Recompute in the page header to work the audit out again first, and check that no grey line under the tabs says the figures are an earlier computation.

A number in the plan does not match the same number on the Analysis tab

Why: Usually one of the two is being read at a different Created range, or you are comparing a workspace-wide figure with a per-tool one.

Fix: Check the Created filter on both, then read the line under the plan’s headline: it states in one sentence which people the plan covers.

Next steps

Related articles

Was this article helpful?