Attentive Pricing: The Quote and Costs Around It

Attentive pricing needs an invoice-to-operation worksheet

A defensible Attentive pricing decision reconciles the provider’s quote with the work your brand must still perform to make the programme useful. This proposed worksheet separates message usage, purchased scope, retained operations and exit obligations. It exposes costs that a software quote cannot fully describe, without inventing a universal monthly rate or assuming every listed charge applies to you.

Attentive’s pricing page identifies message volume, subscriber list size, selected channels and premium AI products as pricing inputs. The page presents a modular offering rather than a single rate that determines every merchant’s bill. Request a proposal for your intended programme and use its definitions as the basis of the comparison. Attentive pricing.

For a $3M–$30M brand using Shopify Plus or a paid subscription platform, the purchase should be judged on a working lifecycle programme. Finance needs to understand the invoice, marketing needs to maintain the journeys and support needs to handle the customer consequences. An attractive software fee cannot establish whether the resulting operating model is affordable.

The verdict is to buy only a scope whose charges can be reproduced and whose continuing responsibilities have owners. This guide is not a lowest-price roundup or a prediction of the offer Attentive will make your business. It is a method for assessing a real proposal, including reasons to narrow the scope or decline it when the business case remains incomplete.

Ask for the charging basis before discussing discounts

A comparable quote defines what creates a charge and when the charge changes. Ask Attentive to identify the billable population, message units, included products and any applicable commercial commitments in your proposal. Do not infer contract treatment from a general description of usage-based pricing. Finance should be able to apply the written terms without relying on a salesperson’s verbal explanation.

Use a scope sheet that distinguishes the channels you intend to operate from the channels you could theoretically add. Provide your intended campaign pattern, triggered journeys, recipient markets and service needs. Mark assumptions that still depend on implementation. A quote built around a future programme you have not staffed can obscure both unused scope and unbudgeted labour.

Request an ordinary operating scenario and a separately labelled expansion scenario. The ordinary case should reflect the programme the team can deliver now. The expansion case should show what changes when the business activates additional products or activity. Ask which commercial terms would need revisiting rather than treating the first estimate as an indefinite promise.

The table is a proposed procurement checklist, not a claim that Attentive charges every category to every customer. Require “not applicable” where appropriate and attach the answer to the buying record. A blank cell should remain unresolved rather than becoming a zero-cost assumption in the financial model.

Message count is not enough to forecast spend

Attentive distinguishes campaign messages from SMS message segments: a text message can contain more than one segment. That distinction matters when the commercial unit is a segment rather than the number of recipients or creative messages. Ask the implementation team to translate your planned content into the units specified by your proposal. Attentive messages and segments guide.

Use representative approved creative for the estimate. Include the variations your programme intends to send, such as personalisation and different content formats, then ask how the actual composed output is assessed. Avoid pricing a short placeholder and treating the result as a budget for every final message. The forecast should follow the delivered programme rather than the copy draft used in procurement.

Separate campaign activity, triggered activity and customer responses in your usage inventory. Attentive’s Billable Spend report describes campaign, triggered and received messages, with message costs and carrier fees. Ask finance to reconcile the applicable categories to your agreement instead of assuming that the marketing calendar alone describes all relevant usage. Attentive Billable Spend documentation.

Triggered activity needs its own estimate because it depends on customer events as well as planned campaigns. Identify the event population, entry conditions, exclusions and number of intended actions in each journey. Use your own observed records where available and mark missing inputs metric to confirm. Do not substitute a vendor performance example for your store’s expected workload.

Set a process for reviewing forecast changes before activation. A revised audience rule or an additional journey step can alter usage without appearing as a new software purchase. Give the operator a way to assess the commercial effect and seek the appropriate internal approval. Budget ownership should follow configuration changes, not arrive only when an invoice becomes surprising.

The spend report is not the complete invoice

A message-spend report should be reconciled to the invoice rather than treated as a substitute for it. Attentive documents exclusions from its standard Billable Spend report, including base and sender fees, email, commitment adjustments, credits, taxes and various additional product or service charges. The applicable invoice remains the source for your complete charge assessment. Attentive report exclusions.

Build an invoice bridge with a line for usage explained by the report and separate lines for every other applicable charge or credit. Use the same reporting period and record any timing difference your finance team needs to understand. Assign unexplained amounts to an owner rather than putting them into a general “platform cost” bucket that cannot be audited later.

Keep invoice credits separate from the programme’s underlying cost. A temporary concession can reduce cash expenditure during a period without changing what the operating model costs afterwards. Ask finance to show both the actual invoice and the continuing commitment expected under the agreement. That distinction helps prevent an onboarding incentive from becoming the assumed permanent baseline.

A useful invoice acceptance exercise asks a reviewer who did not negotiate the purchase to explain the bill using the retained documents. The reviewer should trace each line to a charging definition or an agreed adjustment. If the model requires an account manager to reconstruct the deal every time, the commercial documentation needs improvement before scope expands.

Identity capabilities still leave work with the merchant

Identity should enter the price discussion as a dependency with an acceptance requirement. Ask which customer identifiers and events the proposed programme uses, where they originate and how the system resolves incomplete records. The commercial question is what your team must supply and maintain for the purchased capability to produce a usable decision.

Attentive’s pricing page includes identity-related platform positioning and distinguishes optional product choices. That provides a reason to ask how your proposed package treats identity, not evidence that every historical customer or session will be recognised. Request the actual scope and limitations for your implementation without building forecast revenue on an unverified recognition assumption. Attentive platform and product scope.

Use a representative identity acceptance pack. Include a known customer, a customer with incomplete details and a conflicting record that should not be joined automatically. Ask the implementer to explain the resulting audience and the evidence available to an operator. An identity demonstration is useful when it shows how ambiguity is contained, not merely when it finds a convenient sample shopper.

Estimate the work of maintaining those inputs. Storefront changes, catalogue changes and integration updates can affect the records a journey relies on. Assign responsibility for detecting and correcting a mismatch. A purchased capability may reduce some work while creating a continuing dependency on merchant data quality, and both effects belong in the buying model.

Keep recognition separate from permission. Finding or linking a customer does not itself answer whether a particular marketing action is authorised under your approved policy. Treat any uncertainty about channel or purpose as a state to resolve, not as additional reach that can be inserted into a revenue forecast. The identity business case should count only the intended eligible programme.

Consent operations are an operating cost

Consent operations include more than adding a form to a storefront. The proposed work inventory should cover approved collection language, source records, channel-state mapping, opt-out handling and investigation of disagreements between systems. Have counsel assess the relevant legal requirements for your business and markets. The implementation team then needs a defined policy it can translate into behaviour.

Before importing an audience, ask who verifies the evidence and who approves the destination interpretation. Include channel, purpose and source context wherever your approved process requires them. A larger imported list can make a purchasing presentation look better while leaving the actual sendable population unresolved. Model the programme you are entitled and prepared to operate.

Opt-out propagation deserves an acceptance test across the systems your brand will retain. A customer change should reach the relevant sending decision without being overwritten by an older source record. Ask who investigates a disagreement and which system is authoritative during the transition. Neither a connector label nor a successful import establishes that ongoing preference changes are handled correctly.

Budget the human review that remains. A staff member may need to resolve an ambiguous profile, answer a customer question or verify a source before a record is usable. Measure that work in a representative evaluation rather than applying a generic support-time assumption. The purchase should make retained tasks visible enough to staff, even when their volume remains uncertain initially.

Integration labour continues after the connection works

List the business actions your implementation needs before counting integrations. For each action, record the source event, required customer context, destination decision and responsible owner. A connection that receives an order event may still need work to apply the right exclusion or make the event useful in a message. The cost estimate should follow that full chain.

Attentive documents webhook notifications for events such as subscription changes, message sends and clicks. Its guide also provides configuration and verification steps. Those interfaces establish a supported way to receive particular notifications; they do not remove the merchant’s work of interpreting, storing and acting on the information in a custom system. Attentive webhook management.

Ask the provider or agency to price setup and continuing ownership separately. Setup might include field mapping, journey reconstruction and an initial test pack. Continuing work might include monitoring, incident investigation and changes to the merchant’s source systems. Treat these as proposed scope categories to confirm, not assumptions that Attentive charges separately for every task.

Use a failure rehearsal in implementation acceptance. Supply an incomplete event or describe a delayed update in an appropriate test setting, then ask how the team identifies the affected customer journey. The operator needs to know whether to pause sending, correct a mapping or wait for a documented recovery process. A successful ordinary event is not evidence that exceptions are manageable.

The email marketing strategy guide can help define the wider programme, while the buying worksheet should stay focused on the tasks your proposal funds. Do not let a large catalogue of possible journeys substitute for a scoped implementation. Unbuilt automation is neither realised value nor a reason to exclude its future construction cost.

Service scope must say who performs the work

A support promise and a managed deliverable answer different questions. Support may help your team understand a feature, while a performed service may create or maintain a specific output. Ask the proposal to name which activities the provider completes, which it advises on and which remain entirely with the merchant. A phrase such as “strategic support” needs an operational translation.

Build a responsibility schedule for audience decisions, content approval, journey configuration, monitoring and reporting. The merchant should retain authority over offers and customer promises even when a provider performs execution. A schedule with named roles prevents the brand from assuming that access to an adviser means somebody else owns the weekly work.

Ask what happens when the normal contact is unavailable or a request falls outside the agreed scope. Include an escalation scenario that crosses a vendor and an agency, such as a journey receiving the wrong source data. The value of a service model depends partly on whether it produces a clear next action during a problem, not merely on the convenience of the relationship during onboarding.

Contract review gate: do not count managed-service savings until the proposal names the task the provider performs, the evidence of completion and the merchant approval it requires. “Support included” does not establish that your team can stop doing the work.

Keep AI-assisted work within the same accountability model. Generated copy, audience suggestions or automated recommendations need an owner for the resulting customer decision. AI should not authorise refunds or consequential actions from unreliable records. Cost savings attributed to automation remain a hypothesis until the approved workflow demonstrates what human work actually disappears or changes.

Measure contribution before declaring the platform worthwhile

The value model should distinguish attributed revenue from incremental contribution. Ask the proposal’s author to state how a marketing interaction receives credit, which orders are included and how returns or cancellations are treated. Finance needs to understand those definitions before comparing a vendor dashboard with another platform or with the store’s total sales.

Use the same reporting boundary for the current programme and the proposed Attentive programme. If one view includes different interactions or a different window, label the difference rather than treating the larger number as better performance. A dashboard can be accurate under its own definition while remaining unsuitable for a direct commercial comparison.

Where feasible, design an evaluation that can distinguish the intended intervention from other changes occurring at the same time. State its limits openly. A new offer, altered audience and different message programme can all affect results. The business case should not assign every favourable change to the platform purchase without a defensible attribution method.

The flow revenue calculator can help explore your own baseline and scenario assumptions. Use it to inspect what must be true for the purchase to make sense, then include message charges, offer cost and retained labour in the economic decision. A sensitivity exercise exposes dependencies; it does not prove a forecast.

Keep cash savings separate from released capacity. If the same staff remain employed but spend less time on a task, the benefit may be additional work they can complete elsewhere. That can be valuable, but it is not automatically a payroll reduction. Record the actual expected benefit so the purchase is not approved on an accounting shortcut.

Exit and export requirements belong in the original quote

Ask how your brand will obtain usable customer, eligibility and performance records before it needs to leave. Attentive documents SFTP data feeds, which provides a concrete export-related mechanism to discuss. Confirm the availability, scope and commercial treatment for your agreement; the existence of documentation is not a guarantee that every required record or service is included. Attentive SFTP data feeds.

Request a sample export and its field definitions during evaluation. The intended recipient of the data should confirm that the fields can be interpreted and mapped to the next system or archive. A file that downloads successfully may still lack the context finance or lifecycle operations needs. Acceptance should establish usability rather than merely the presence of an export button.

Define the exit treatment of forms, pending journeys, credentials and historical reports. Ask who performs each task, which access continues temporarily and which obligations remain after sending stops. Have the appropriate advisers review the actual contract. Do not assume termination of a commercial agreement completes the operational handoff automatically.

Include transition labour in the decision horizon finance chooses. A move can involve overlapping access, rebuilding working journeys and reconciling the final state of audience records. These are not necessarily reasons to reject the product, but they are part of a defensible total-cost comparison. The brand should understand the conditions under which it can leave without losing necessary operating context.

Buy only after the acceptance pack is concrete

Require a compact acceptance pack containing the commercial definitions, representative invoice reconciliation, verified customer journeys and responsibility schedule. Each item should have a merchant reviewer and an agreed outcome. A proposal becomes reviewable when the business can say which evidence would make it accept or reject the delivered programme.

Test the boundaries that affect money and customer treatment. Include an ineligible contact, a profile with incomplete information, an event that should stop a pending message and an invoice adjustment that finance must explain. Use controlled records and appropriate environments. The aim is to test important decisions rather than collect screenshots of every available feature.

Do not buy a broader package solely because its bundled price appears attractive. Decline or narrow the proposal when essential data is unreliable, when the team cannot operate the promised scope or when projected savings depend on unspecified service work. A simpler programme with clear ownership can be more valuable than a larger purchase whose useful activity remains hypothetical.

Attentive pricing is a lifecycle flows decision because software, customer data, message decisions and retained staff work jointly determine the cost of the programme. The lifecycle flows service frames that connected work. Approve the purchase when finance can reproduce the charges and operators can perform the promised journey, with accepted limits and owners for everything left outside the quote.