Your Paramark Growth Advisor is the human expertise layer of the Paramark product. They translate your MMM and incrementality results into decisions, hold the rigor of your experiments, and act as a strategic partner alongside your marketing leadership. They are not a marketing agency, a data engineering team, or an ad operations vendor.

This article walks through how the engagement works in practice: how often you'll talk, how fast we respond, what we deliver, what we need from you, and where the boundaries sit. These commitments are effective from May 2026 and apply to every Paramark customer.

How we work together

The rhythm of the relationship has three layers: a continuous async layer in Slack, a monthly live touchpoint, and a small amount of on-demand bandwidth for the in-between moments.

Bi-weekly Slack syncs

Your primary touchpoint with your Growth Advisor is your shared #paramark-[your-company] Slack channel. Every other week we'll align on what's in flight, what's blocking you, and what's coming up. We respond to standard questions in less than one business day during weekday business hours.

This is where the day-to-day work happens. If you have a question between meetings, drop it in Slack and you'll get a substantive answer the next business day at the latest.

Where to find shared designs, analyses, and educational materials

Your Growth Advisor may share links to a reports workspace at dashboard.paramark.com/reports where you can access shared designs and past analyses.

They may also share educational materials, such as decks that explain marketing mix modeling (MMM) and incrementality. If you cannot find a shared resource later, ask in your shared Slack channel and your Growth Advisor can resend the relevant links or files.

Monthly live calls

Once a month we meet live via video conferencing with a focus on discussing any insights and deliverables live, and most importantly to drive towards our aligned goals. The agenda covers progress against your stated business goals, your latest MMM readout and any scenario plans, and your experiment readouts and roadmap. Your point person on our engagement owns and runs this agenda. We come prepared with the analysis, the insights, and the recommended next steps; you drive the discussion priorities and decisions.

If helpful, you can share agenda priorities with your Growth Advisor ahead of time so we can prepare around the most important decisions or questions. For customers operating across multiple markets, monthly calls can cover more than one market, but the exact mix depends on what is most time-sensitive or decision-relevant that month. If there are specific markets you want included, the best practice is to flag them in advance so we can prioritize the discussion accordingly.

Weekly standing meetings are not part of the engagement. We will share any deliverables async and have found that bi-weekly Slack updates in addition to monthly live sessions give us more time for analysis and gives you cleaner, more decision-ready insights.

On-demand support, capped at 2 hours per month

Between scheduled touchpoints, your Growth Advisor will share any deliverables async, and holds 2 hours per month for ad-hoc work and calls. The ad hoc work can include a targeted question before an internal meeting, a quick cut of the data, a sanity check on a marketing decision, or analysis behind the scenes. If a request will take longer than that, we'll either scope it as a custom analysis (priced separately) or queue it into the next monthly cycle.

This cap is intentional. It protects the depth and quality of the work that your Growth Advisor is driving across your business.

Bi-annual strategic reviews

Paramark provides a look into our partnership together, our roadmap ahead and how we're operating together. This is where we align our goals together, make sure we're solving the right problems, not just executing well on the wrong ones. Reach out to your Growth Advisor to discuss further.

What you can expect from us

Our commitments on response and delivery times are below. These are written into the May 2026 engagement model and apply to every customer.

A few specific points worth calling out:

• Experiments stay rigorous because we own the design. Every test you run with Paramark is on a shared roadmap that we review together monthly. We design the experiments, we guide you through how to implement, and we analyze the results. We don't analyze tests we didn't design, because the rigor of the answer depends on the rigor of the setup.

• Experiment metrics are locked at launch and limited to 2. Before a test goes live we agree on the 2 metrics we'll analyze. We don't add or change metrics retroactively. We do this to maintain data science best practices and strongly encourage thoughtful experiment design on the front-end of the process. If there's a metric we should be tracking that we didn't, we'll design it into the next test.

• MMMs refresh monthly on our schedule. Your model rebuilds every month. If you need delivery within a fixed window of month-end (for finance close, board reporting, or similar), that's available as a paid premium delivery commitment. Talk to your Growth Advisor about scoping it.

• Taxonomy and channel-mapping changes apply month-after-next. A change you request in May lands in the July refresh, not June. The gap exists because we need to validate the change against your history before letting it move attribution. Plan ahead when you're rethinking your channel taxonomy.

What we need from you

Our ability to hit those SLAs depends on a clean, predictable inflow of data and decisions from your side. The May 2026 engagement model is explicit about what that looks like.

Data

• Your target metric and digital marketing data must be on automated feeds. That means a direct connection to your CRM, ad platforms, and analytics. Manual exports for these sources don't scale and create breakage that delays delivery. If something on your side breaks, we won't be able to absorb the delay; the deliverable will wait until the feed is fixed.

• Manual data must arrive in the format we provide. Some data sources can't be automated yet (offline channels, certain custom inputs). For those, we share a format. Filling it in correctly and on time is your team's responsibility, including any cleanup. We don't chase, translate, or re-format manual data, and we don't follow up with third parties on your behalf.

• You'll get one automated Slack reminder per month for manual data. That's the only nudge. If data is missing or wrong on the day of refresh, we hold the deliverable until it's right.

Meetings

• Your point person owns and runs the monthly agenda. We come prepared with the analysis and recommendations. Your team drives what gets discussed and what gets decided. The monthly call works best when there's a clear owner on your side who knows what they want to come away with.

Changes

• Taxonomy or channel-mapping changes must be flagged in advance so they can apply to the month-after-next refresh. Surprise changes don't make it into the next model.

• Experiment metrics must be defined upfront and are limited to 2 per test. If your team needs more dimensions in the future, we can plan for it on the experiment roadmap.

Custom work

• Anything beyond the standard scope is custom analysis at additional pricing. Examples: a custom-built model variant, a deep-dive analysis outside the monthly MMM cycle, a one-off study for a board meeting. Talk to your Growth Advisor about scoping it. We'll move some of this self-serve via Paramark Copilot and the API in future, but for now custom work is a paid scope.

What this looks like in practice

A few common situations and how the engagement model handles them.

"We have a board meeting next week and need a fresh cut of the MMM."

If the cut is small (a single channel view, a specific time window, etc.), this is what your 2 hours of on-demand bandwidth is for. Just ping your Growth Advisor in Slack. If it's a larger custom analysis, we'll scope it commercially. If you regularly need MMM delivered earlier in the month for board or finance work, talk to your Growth Advisor about the paid premium delivery commitment.

"Can we add a third metric to the experiment we just launched?"

Not retroactively. The 2 metrics are locked at launch. We can plan to track that metric in your next test on the roadmap.

"Our agency wants to attend our monthly Paramark call."

We're happy to do a partner onboarding session so your agency understands how Paramark works alongside them. Beyond that, we're not staffed for recurring working meetings with partners. We'll make sure your team has what they need to brief them async.

"Can Paramark share MMM outputs or supporting data with an external partner like MarketCast, our agency, or another measurement vendor?"

Yes, but start by routing the request through your shared Slack channel with Paramark and be specific about what the partner needs. In many cases, the fastest path is for your Growth Advisor to share the relevant report links, analysis summaries, or existing materials directly with your team so you can bring the right partner into the conversation.

If an external partner needs something more specific, clarify four things up front: who needs access, what exact outputs or datasets they need, why they need them, and when the request is needed. That helps Paramark determine whether the ask can be handled with existing shared materials, a working-session walkthrough, or a more custom data request.

A useful rule of thumb is that Paramark can help you share and explain the work we already produce, but we are not a general-purpose data engineering team for third parties. If the ask turns into a one-off custom extraction, reformatting exercise, or a deeper external deliverable, your Growth Advisor will tell you whether it fits within the normal engagement or needs to be scoped separately.

If you are making the request on behalf of a partner, the best first message is something like: “We need to share our latest MMM outputs with [partner name]. They need [specific tables, files, or readout materials] for [purpose] by [date]. What is the best path?” That gives Paramark enough context to respond quickly and point you to the right next step.

"We changed how we tag campaigns last week. Will that show up in this month's MMM?"

Not this month. Taxonomy changes apply month-after-next. Flag the change to your Growth Advisor now and you'll see it in the model two refreshes from now.

"Our usual meeting day does not work for the next couple of weeks. Can we move it or just cover things async?"

Yes. If a temporary shift in schedules makes the usual live touchpoint inconvenient, the default is to keep momentum asynchronously in Slack and use an ad hoc meeting only if there is a decision, review, or discussion that genuinely benefits from live time. If a nearby alternate time works for both teams, we can move the meeting. If not, we can cover progress async and schedule a one-off call later if needed. This is fully consistent with the standard engagement model: bi-weekly Slack updates, one monthly live call, and limited on-demand support for targeted in-between moments.

This also applies when Paramark has a temporary internal scheduling disruption, such as a team offsite. In those cases, we may pause the normal meeting cadence for a short window, continue working asynchronously where possible, postpone non-urgent meetings, and coordinate in advance on anything time-sensitive or business-critical so the right people are available.

During those short windows, the simplest expectation is: your shared Slack channel remains the best place to reach us, routine work may move a bit more slowly than usual, and we will resume our standard delivery cadence once the offsite or scheduling disruption ends. If you have anything urgent, deadline-driven, or business-critical that week, flag it in advance so we can coordinate coverage with the right people.

This is especially common around first-model timing. If your first MMM is still being finalized, your Growth Advisor may share the draft or summary asynchronously as soon as it is ready and then move the live walkthrough to a later date when the right stakeholders can attend. That way you still get the work for review without forcing a lower-value meeting before there is something substantive to discuss live.

If you are unsure whether a call is still worth holding, the simplest first step is to ask your Growth Advisor whether there are any agenda items that genuinely need live discussion. If there is nothing time-sensitive to review, it is completely fine to cancel or skip that instance and handle updates in Slack instead.

"We need to align internally before we confirm next steps. Should we wait to schedule the follow-up conversation?"

Yes. If your team needs a short internal regroup before deciding what to discuss live, it is completely fine to pause scheduling until that alignment happens. The simplest path is to post in your shared Slack channel that you are syncing internally, then come back with either proposed times for a follow-up conversation or the specific questions you want to handle asynchronously.

In practice, use this rule of thumb:

• Schedule the follow-up call when there is a decision, review, or discussion that will move faster live.

• Stay async in Slack when the next step is simply internal alignment, collecting questions, or confirming who should attend.

This keeps the meeting useful instead of holding live time before the right stakeholders or questions are ready.

"What will our monthly meeting cover, and will all markets be discussed?"

The monthly agenda is owned by your point person and usually centers on the decisions your team needs to make next. In practice, that often includes your latest MMM readout, current scenario plans, experiment readouts, and the forward-looking experiment roadmap.

Not every market needs to be discussed in every meeting. We typically prioritize the markets, channels, or decisions with the most new information, the biggest open questions, or the clearest action needed. If you want specific markets covered on an upcoming call, the best approach is to flag that in Slack beforehand so your Growth Advisor can prepare the right cuts and make sure those markets are included in the agenda.

If multiple markets are in scope, we may cover each one at a different level of depth rather than giving every market equal time. The goal of the meeting is not to mechanically review every market on every call, but to focus live discussion on the areas where it will be most useful for decision-making.

"Can we review an experiment design asynchronously and discuss it on our next call?"

Yes. That is a normal and often preferred way to work with Paramark. Your Growth Advisor may share an experiment design or proposal in Slack ahead of your next live session so your team can review it asynchronously, leave comments or questions directly in the shared document, and come to the call ready to focus on the decisions that matter most.

This is especially useful when there is a lot to review or when schedules do not line up neatly for an immediate walkthrough. Async review gives your team time to read the proposal carefully, gather internal feedback, and flag anything you want prioritized in the live discussion.

A good rule of thumb is:

• Use async review for preparation and feedback — comments, clarifying questions, and early reactions can all happen in Slack or directly in the shared document.

• Use the live call for decisions — the next meeting is the right place to align on tradeoffs, confirm the path forward, and close any open questions that benefit from discussion.

If your team already knows which areas you want feedback on, the fastest path is to leave those comments in the document before the meeting so your Growth Advisor can prepare targeted answers in advance.

"Our next live meeting is coming up, but the newest MMM data load is still being validated. Should we keep the meeting?"

Usually, no — or at least not as a standard readout meeting. If the main purpose of the meeting is to review the newest MMM and that refresh is still in data validation, the better default is to push the meeting until the updated model is ready or to handle interim updates asynchronously in Slack.

A good rule of thumb is:

• Keep the meeting if there is still a live decision to make that does not depend on the refreshed MMM being final.

• Move the meeting if the value of the conversation depends on the updated model, new validation outputs, or a fresh readout that is not ready yet.

• Use Slack for the interim status update so everyone stays aligned on whether the next step is data QA, model validation, or final readout preparation.

This is especially common when the next milestone is simply loading the newest month of data and validating it before the model can be discussed confidently. In those cases, waiting for the validated refresh usually creates a more useful meeting than reviewing a partial or not-yet-final version.

"How do I know if there are any outstanding deliverables assigned to me?"

The simplest check is to look at the commitments in this article and compare them against what is currently in flight with your team. In practice, the most common customer-owned deliverables are sending required manual data in the requested format and on time, owning the monthly meeting agenda, flagging taxonomy or channel-mapping changes in advance, and confirming experiment metrics before launch.

If you are unsure what is still open, ask your Growth Advisor in Slack. They can tell you whether anything is currently blocking a deliverable, such as missing manual data, an unanswered decision, or a change request that still needs your team's input.

A useful rule of thumb is this: if Paramark is waiting on information, a file, a decision, or advance notice from your team, that is likely the outstanding deliverable on your side.

"Can we set up a weekly standing meeting with our Growth Advisor?"

In most cases, no. The standard engagement includes bi-weekly Slack syncs, one monthly live call, and up to 2 hours of on-demand support for ad hoc work or targeted calls in between. We have found that this cadence creates more room for analysis and leads to more decision-ready recommendations than a recurring weekly meeting. If you need extra live time for a specific moment, ask your Growth Advisor in Slack and we can use available on-demand bandwidth or scope additional support if the need becomes ongoing.

"Can we set up a recurring bi-weekly live meeting instead of using Slack for those check-ins?"

Usually, no as a default working cadence. The standard engagement is designed around bi-weekly coordination in Slack plus one monthly live call, with additional live time used selectively when there is a decision, review, or discussion that benefits from being synchronous. If your team wants more frequent live touchpoints for a temporary period, raise that with your Growth Advisor in Slack and we can decide whether to use available on-demand bandwidth, shift a specific meeting, or handle that stretch asynchronously instead.

If you are trying to find time for a one-off or temporary recurring session, the simplest path is to send a few candidate windows in your shared Slack channel and your Growth Advisor can confirm what works on our side.

"Can our Growth Advisor jump on a quick call with our analytics team to walk through the methodology?"

Yes, this is part of the engagement. Use Slack to set it up. If the conversation needs more than an hour or turns into a recurring series, we'll talk about whether it makes sense to scope as a separate engagement.

"Are there any outstanding deliverables or action items I'm responsible for?"

Usually, the clearest place to confirm this is your shared Slack channel with Paramark. That is where your Growth Advisor flags current asks, pending inputs, and anything blocking the next deliverable.

In general, the responsibilities that most often sit with your team are:

• Providing required data on time, especially any manual data inputs that cannot yet be automated.

• Owning the monthly meeting agenda so the live discussion stays focused on the decisions your team needs to make.

• Flagging taxonomy or channel-mapping changes in advance so they can be incorporated on the right timeline.

• Defining experiment metrics before launch, since metrics are set upfront and not changed retroactively.

If you're asking about a current in-flight deliverable rather than these standing responsibilities, ask your Growth Advisor in Slack and they can confirm what is still pending from your side versus what Paramark is actively working on.

"We have roadmap questions or finance questions about metrics like cost per opportunity. Is Slack the right place to ask?"

Yes. Your shared Paramark Slack channel is the right default place for these questions. That includes questions about your testing roadmap, how to prioritize upcoming experiments, how to interpret efficiency metrics like cost per opportunity or incremental cost per opportunity, and how to prepare for an upcoming internal finance discussion.

If you already have a Slack thread or internal discussion that prompted the question, it is helpful to post the question in the shared Paramark channel with that context and tag the Paramark teammates you want input from. That keeps the conversation in one place and helps us respond with the right strategic or analytical context.

In practice, Slack works best when you include the decision you are trying to make, the channel or budget in question, and any timing context such as an upcoming planning cycle or finance review. If the question would benefit from a deeper discussion, your Growth Advisor can respond asynchronously first and then decide with you whether it makes sense to cover the topic on the next monthly call or use some of the available on-demand support.

If the question is specifically about the experiment roadmap, it is also helpful to say whether the goal is to find channels to scale, identify spend to cut, or pressure-test a hypothesis about a channel that appears efficient or inefficient. If the question is coming from finance, include the metric they are focused on and whether they care most about blended efficiency, incremental efficiency, or budget reallocation decisions.

"This just is not a priority for the next 90 days. What should we do?"

That is a normal planning outcome, and it is useful information rather than a problem to hide. The best next step is to say that plainly in your shared Slack channel with Paramark and add just enough context for your Growth Advisor to adjust the roadmap responsibly.

A helpful message usually includes three things: what is being deprioritized, roughly how long the pause is expected to last, and what should happen during the pause. For example: are you pausing a specific experiment idea, holding off on a broader budget reallocation conversation, or simply waiting until the next planning cycle before revisiting the topic?

In practice, a 90-day deprioritization usually means one of three paths:

• Pause that workstream and revisit it at the next planning window if there is no immediate decision to make.

• Keep the question on the roadmap but not in the active queue if it is still strategically important, just not urgent this quarter.

• Use async Slack updates only for now if there is nothing valuable to cover live until priorities reopen.

What matters most is clarity on whether the question is delayed, replaced by a different priority, or no longer worth pursuing. That helps your Growth Advisor avoid doing work against a stale problem and redirect attention toward the decisions that actually matter this quarter.

If the deprioritized topic is an experiment or roadmap item, the usual outcome is not that Paramark disappears or that the whole engagement pauses. Instead, we either refocus on a more urgent decision, keep momentum asynchronously until the next planning cycle, or revisit the idea when your budget, stakeholders, or measurement questions are more active again.

A simple rule of thumb: if something is not a priority for the next 90 days, tell your Growth Advisor early, say what replaced it, and say when you expect the topic to come back. That is the fastest path to keeping the roadmap realistic and the live discussions useful.

How to get the most out of your Growth Advisor relationship

A few things our highest-value relationships have in common:

• We have an aligned set of goals and vision. The stronger the alignment between your team and your Growth Advisor, the more we can focus on the big picture and find creative ways to deliver together. If your Growth Advisor doesn’t have visibility to the big picture, then the relationship can end up tactical and focused on delivery instead of outcomes.

• You have a clear point person who runs the monthly agenda and triages questions in Slack. Decisions move faster when there's one accountable owner on the customer side.

• You send data on time and in format. The teams that hit their MMM cadence reliably are the ones that don't treat the monthly reminder as optional.

• You use the monthly call to make decisions, not to receive a status update. The MMM readout and experiment results are inputs to the conversation, not the conversation itself. Coming in with a clear set of decisions you're trying to make sharpens the discussion and makes the Growth Advisor's recommendations land.

• You treat experiments as a roadmap, not a one-off. The customers getting compounding value from Paramark are the ones running 6 to 12 well-designed tests a year, building on each other. The roadmap is where that compounding starts.

Closing thought

The engagement model is designed so your Growth Advisor spends most of their time on the work that actually moves your business: rigorous measurement, clear recommendations, strategic partnership. The cadence, the SLAs, and the boundaries above all exist to protect that.

If any of this raises a question for your specific situation, ask your Growth Advisor in Slack. We'd rather get the expectations right early than have them drift.

Want to learn more? Check out other Paramark articles here