service-first pricing

built around implementation scale, not seats

heptaloop pricing is scoped around the intelligence system your teams need: decision-science services, usage-based data capacity, storage, compute, custom agents, integrations, and operating support

service led usage aware custom scoped enterprise governed
starting shape

choose the operating shape. then scale the usage and services

instead of a generic plan table, heptaloop starts by mapping the decision loop you want to run and the enterprise work required to keep it trusted

best when

you need recurring market intelligence that moves teams every week

expand acquisition, scoring, interaction, publishing, and paid activation into a governed operating loop supported by maintained agents

  • multi-source data refresh and storage
  • agent workflows for analysis and activation
  • custom reporting, routing, and review rituals
  • usage capacity tuned to decision velocity
what changes scope

five levers shape the engagement

pricing expands with implementation intensity: how much evidence flows through the system, how often it refreshes, how many agents act on it, and how much decision-science support is needed to maintain trust

01 data surface

public, partner, first-party, market, social, media, census, CRM, and research sources

02 compute + storage

refresh cadence, evidence retention, model training, and high-throughput processing

03 agent execution

analysis, interaction, publishing, paid media, routing, and next-best-action automation

04 integrations + governance

CRM, BI, marketing clouds, approval flows, audit trails, compliance, and security posture

05 decision science services

onboarding, model tuning, operating reviews, experimentation design, and advisory support

service layer decision scientists

maintain the agents, translate signals, tune models, and keep business decisions defensible

usage layer data + compute capacity

scale ingestion, storage, processing, model execution, and evidence refresh by operating demand

integration layer enterprise workflows

connect the loop to CRM, BI, content ops, paid media, approvals, and executive reporting

service first

a pricing conversation starts with the work, not a feature checklist

heptaloop combines platform access with structured implementation services because consumer intelligence and activation fails when data, models, governance, and action workflows are scoped separately

scope matrix

every engagement is assembled from the same operating ingredients

same ingredients. different scale

layer launch blueprint operating loop enterprise command
platform access one governed decision workflow recurring intelligence loop multi-market command layer
data + compute priority sources and initial graph scheduled refresh and storage high-throughput ingestion and models
agents analysis and routing prototype maintained analysis and activation agents custom agents across teams
decision science setup and validation cadence weekly operating reviews executive governance and advisory
integrations lightweight handoff CRM, BI, content, and media workflows security, compliance, audit, and reporting stack
how to think about it

designed for enterprise scope, not public plan theater

the useful question is not “how many seats?” it is “what decision loop should exist, how much evidence must feed it, and who maintains trust in the output?”

is heptaloop priced per seat?

no user access matters, but the engagement is primarily shaped by services, usage, data, storage, compute, integrations, governance, and agent workflow depth

can we start with one loop?

yes many engagements begin with one decision loop, then expand once the evidence model, scoring logic, and action workflow prove useful

what expands scope?

new data sources, faster refresh cadence, more markets, additional agent workflows, deeper integrations, larger evidence stores, and more decision-science operating support

why include decision scientists?

heptaloop agents are maintained and supported by decision scientists so the system produces trusted decisions, not just automated outputs

why no fixed public price table?

enterprise consumer intelligence and activation varies by evidence complexity, compliance, operating model, and activation depth a fixed public table would hide the real implementation drivers

next step

bring one decision loop. we will map the scope

share the market problem, data surfaces, workflow owners, and decision cadence. heptaloop will return a service-first pricing architecture matched to the implementation