1
Client stores already in production, monitored regularly but without minute-level criticality.
Agency plan
Agency plan Base: monitored stores with AI.
Built to hand back clear monitoring, client site by client site €12 / site / month · 25 monitors/site · 5 min checks · 90 days.
Agency plan
Base · A framed offer to sell proof, not only monitoring.
Cadence, history, alerts and handoff are framed so clients see the signal, proof and next action Niveau Base : 25 monitors/site · 5 min checks · 90 days.
- 25 monitors/site
- 5 min checks
- 90-day history
- Per-site billing
- Readable client reports
Best fit
2
Agency needing a standard technical and commercial watch per site without a heavy cockpit.
3
E-commerce portfolio where incidents must be spotted, timestamped and explained in client language.
4
WooCommerce maintenance contracts where monitoring complements human intervention.
What this plan brings
25 monitors per site
Base covers essential pages and checks for a client store: home, product, cart, checkout, framed payment signals and useful technical indicators.
5-minute checks
The cadence fits stores where the agency must be informed quickly without continuous escalation.
90-day history
Three months of data show trends, recurring incidents and evidence for monthly client discussions.
Readable handoff
Alerts and reports focus on actionable explanation: affected step, observed signal, priority and proof instead of raw logs.
Per-site billing
Each client site is treated as an independent monitoring unit, making resale and gradual rollout easier.
Plan limit
Base fits regular watch; for advanced white-label, tighter checkout cadence or frequent client reporting, Medium is the better fit.
Complete offer inventory
This exhaustive description repeats every item that defines the Base agency: price, pricing-card scope, target use cases, functional items, proof items, exclusions and support boundary.
Price and billing scope
Base is presented at €12 / site / month; this Base billing basis is visible before activation framing, so the agency plan can be evaluated without hidden price assumptions.
Positioning on the pricing card
Put every monitored store under readable control and estimate exposed revenue. The Base agency plan positioning explains the risk level this tier is built for and how it differs from the neighbouring offers.
Pricing scope: 25 monitors/site
25 monitors/site means the number of monitored checkpoints available for each client site attached to the agency account. In Base agency, that coverage is allocated to the revenue signals this tier can realistically own: product, cart, checkout, payment, confirmation or selected technical endpoints.
Pricing scope: 5 min checks
5 min checks is the regular page-check rhythm for Base. Base uses it to watch availability, page content and journey signals before a checkout-specific incident becomes visible to the team.
Pricing scope: 90 days
90 days is part of the Base offer boundary. The Base page spells it out so the team knows what this tier does, what it proves and when a higher tier may be needed.
Use case 1
Client stores already in production, monitored regularly but without minute-level criticality. This Base agency plan use case is included so buyers can decide whether the offer matches the operational situation, not only the price. For the Base agency plan, it clarifies the store, portfolio, campaign or team context that should be validated before activation.
Use case 2
Agency needing a standard technical and commercial watch per site without a heavy cockpit. This Base agency plan use case is included so buyers can decide whether the offer matches the operational situation, not only the price. For the Base agency plan, it clarifies the store, portfolio, campaign or team context that should be validated before activation.
Use case 3
E-commerce portfolio where incidents must be spotted, timestamped and explained in client language. This Base agency plan use case is included so buyers can decide whether the offer matches the operational situation, not only the price. For the Base agency plan, it clarifies the store, portfolio, campaign or team context that should be validated before activation.
Use case 4
WooCommerce maintenance contracts where monitoring complements human intervention. This Base agency plan use case is included so buyers can decide whether the offer matches the operational situation, not only the price. For the Base agency plan, it clarifies the store, portfolio, campaign or team context that should be validated before activation.
25 monitors per site
Base covers essential pages and checks for a client store: home, product, cart, checkout, framed payment signals and useful technical indicators. This functional item is part of the Base agency plan commitment and is intentionally repeated in the complete inventory. In the Base agency plan, it states the practical change in coverage, cadence, proof, client handoff, operational priority or plan boundary.
5-minute checks
The cadence fits stores where the agency must be informed quickly without continuous escalation. This functional item is part of the Base agency plan commitment and is intentionally repeated in the complete inventory. In the Base agency plan, it states the practical change in coverage, cadence, proof, client handoff, operational priority or plan boundary.
90-day history
Three months of data show trends, recurring incidents and evidence for monthly client discussions. This functional item is part of the Base agency plan commitment and is intentionally repeated in the complete inventory. In the Base agency plan, it states the practical change in coverage, cadence, proof, client handoff, operational priority or plan boundary.
Readable handoff
Alerts and reports focus on actionable explanation: affected step, observed signal, priority and proof instead of raw logs. This functional item is part of the Base agency plan commitment and is intentionally repeated in the complete inventory. In the Base agency plan, it states the practical change in coverage, cadence, proof, client handoff, operational priority or plan boundary.
Per-site billing
Each client site is treated as an independent monitoring unit, making resale and gradual rollout easier. This functional item is part of the Base agency plan commitment and is intentionally repeated in the complete inventory. In the Base agency plan, it states the practical change in coverage, cadence, proof, client handoff, operational priority or plan boundary.
Plan limit
Base fits regular watch; for advanced white-label, tighter checkout cadence or frequent client reporting, Medium is the better fit. This functional item is part of the Base agency plan commitment and is intentionally repeated in the complete inventory. In the Base agency plan, it states the practical change in coverage, cadence, proof, client handoff, operational priority or plan boundary.
25 monitors/site
25 monitors/site means the number of monitored checkpoints available for each client site attached to the agency account. In Base agency, that coverage is allocated to the revenue signals this tier can realistically own: product, cart, checkout, payment, confirmation or selected technical endpoints.
5 min checks
5 min checks is the regular page-check rhythm for Base. Base uses it to watch availability, page content and journey signals before a checkout-specific incident becomes visible to the team.
90-day history
90-day history is the Base agency retention window used to compare incidents, recent changes and recurring patterns. Base agency keeps enough evidence to decide whether a break is isolated, repeated or linked to a maintenance window.
Per-site billing
Per-site billing defines the commercial and operational scope of Base: what is activated, billed or tested before expanding coverage to another store.
Readable client reports
Readable client reports is the packaged Base incident handoff: affected step, observed signal, timeline and next action. the agency can hand the Base agency report back to the client without exposing unnecessary customer data.
Comparison item: Price
Price: €12/site/month. This comparison item is repeated on the Base agency plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Comparison item: Use
Use: Regular watch. This comparison item is repeated on the Base agency plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Comparison item: Coverage
Coverage: 25 monitors/site. This comparison item is repeated on the Base agency plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Comparison item: Cadence
Cadence: 5 min checks. This comparison item is repeated on the Base agency plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Comparison item: History
History: 90 days. This comparison item is repeated on the Base agency plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Comparison item: Handoff
Handoff: Readable report. This comparison item is repeated on the Base agency plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Comparison item: Not for
Not for: White-label need. This comparison item is repeated on the Base agency plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Not for Base agency plan
Portfolios that need white-label, tighter checkout cadence or operational escalation. This exclusion is part of the Base agency plan description because it prevents Base from being read as a universal promise. It tells buyers when the Base agency plan is too small, too advanced or not aligned with the expected operating model.
Base agency plan support boundary
Base detects, prioritizes and documents incidents at the cadence and scope described above. For the Base agency plan, remediation stays with the agency, merchant, hosting provider, payment provider or development team, so this tier sells proof and coordination rather than an automatic repair guarantee.
Functional item details
Every functional item listed for the Base agency tier is repeated here with its operational meaning, so the page does not hide any condition behind a short label.
25 monitors per site
Base covers essential pages and checks for a client store: home, product, cart, checkout, framed payment signals and useful technical indicators. In the Base agency plan, this item is not a generic promise: it is part of the operational scope presented to the team before activation, with its own role in coverage, cadence, proof, handoff or plan limits.
5-minute checks
The cadence fits stores where the agency must be informed quickly without continuous escalation. In the Base agency plan, this item is not a generic promise: it is part of the operational scope presented to the team before activation, with its own role in coverage, cadence, proof, handoff or plan limits.
90-day history
Three months of data show trends, recurring incidents and evidence for monthly client discussions. In the Base agency plan, this item is not a generic promise: it is part of the operational scope presented to the team before activation, with its own role in coverage, cadence, proof, handoff or plan limits.
Readable handoff
Alerts and reports focus on actionable explanation: affected step, observed signal, priority and proof instead of raw logs. In the Base agency plan, this item is not a generic promise: it is part of the operational scope presented to the team before activation, with its own role in coverage, cadence, proof, handoff or plan limits.
Per-site billing
Each client site is treated as an independent monitoring unit, making resale and gradual rollout easier. In the Base agency plan, this item is not a generic promise: it is part of the operational scope presented to the team before activation, with its own role in coverage, cadence, proof, handoff or plan limits.
Plan limit
Base fits regular watch; for advanced white-label, tighter checkout cadence or frequent client reporting, Medium is the better fit. In the Base agency plan, this item is not a generic promise: it is part of the operational scope presented to the team before activation, with its own role in coverage, cadence, proof, handoff or plan limits.
Pricing card item by item
Every visible element from the Base agency pricing card is repeated and explained here: price, positioning and scope limits.
Plan name
Base is part of the public Base card and is repeated here so the agency plan can be evaluated without ambiguity.
Public price
€12 / site / month is the public Base price shown before activation. This agency tier is billed per monitored client site, so the same portfolio can combine several Base sites without hiding the per-store cost.
Positioning
Put every monitored store under readable control and estimate exposed revenue. explains why Base exists in the agency plan catalogue and when this tier should be preferred over the others.
Scope item
25 monitors/site is the Base agency plan commercial boundary visible on the pricing card. It tells the team what Base agency plan includes before any custom framing or upgrade discussion.
Scope item
5 min checks is the Base agency plan commercial boundary visible on the pricing card. It tells the team what Base agency plan includes before any custom framing or upgrade discussion.
Scope item
90 days is the Base agency plan commercial boundary visible on the pricing card. It tells the team what Base agency plan includes before any custom framing or upgrade discussion.
Every offer item explained
Base is detailed item by item: each visible promise from the offer card is repeated with its operational meaning for this agency plan.
25 monitors/site
25 monitors/site means the number of monitored checkpoints available for each client site attached to the agency account. In Base agency, that coverage is allocated to the revenue signals this tier can realistically own: product, cart, checkout, payment, confirmation or selected technical endpoints.
5 min checks
5 min checks is the regular page-check rhythm for Base. Base uses it to watch availability, page content and journey signals before a checkout-specific incident becomes visible to the team.
90-day history
90-day history is the Base agency retention window used to compare incidents, recent changes and recurring patterns. Base agency keeps enough evidence to decide whether a break is isolated, repeated or linked to a maintenance window.
Per-site billing
Per-site billing defines the commercial and operational scope of Base: what is activated, billed or tested before expanding coverage to another store.
Readable client reports
Readable client reports is the packaged Base incident handoff: affected step, observed signal, timeline and next action. the agency can hand the Base agency report back to the client without exposing unnecessary customer data.
Who this plan is not for
Base agency
Portfolios that need white-label, tighter checkout cadence or operational escalation.
Important limit agency
Base agency detects and documents incidents at its planned cadence. Base agency leaves the actual fix to provider, hosting, payment or code owners.
Deliverables, frequency and support · Base
Base handoff
Base frames alerts, history and evidence so the agency can explain the issue per client site, without exposing customer data.
Base cadence
25 monitors/site · 5 min checks · 90 days. Base aims for a signal fast enough for the maintenance promise attached to this tier.
Base support boundary
Base provides detection, proof and recommendations; the agency keeps control of client communication and corrective work.
Concrete example
Base
Example: a client checkout rejects payment after a plugin update. Base helps the agency show the affected step, time window, evidence and recommended next action in a client-readable handoff.
Next step
Base : We frame the first site, alert channels and expected handoff before activation.