Find the problem before your client does.
Your client's website runs in the background of your reputation. Between deployments the relationship usually goes quiet — until the first "something's broken" call. Continuous QA turns that call into an alert you get first: monitoring, an incident-response duty and reporting provided under the agency brand and billed on its invoice. The platform detects and notifies; the response remains the agency's part of the service.
The arrangement requires neither exclusivity nor an entry fee. The billing model is set separately for each client, not for the whole account.
Scope of monitoring
Before the service is added to an offer, its actual scope is worth knowing. Monitoring comprises a set of independent checks, each detecting a different form of unavailability or irregularity.
Availability and a control phrase
The platform verifies that the website responds and that the returned content matches expectations. A page returning a 200 code without the correct content also constitutes an outage, so the presence of a defined phrase is checked as well.
SSL certificate
Warnings are sent 14, 7, 3 and 1 day before expiry. An earlier notice would be premature, as automated renewal usually occurs around 30 days before the deadline.
Domain expiry
Reminders begin 30 days before the deadline, because recovering a domain after it lapses is time-consuming, costly and not always possible. The date is taken directly from the registry.
DNS and security headers
A changed DNS record or a removed security header can be the first sign of interference with the configuration. Each state is compared with the previous one.
Performance and content review
Designated addresses are measured under fixed conditions, with the measurement history retained. The content review detects missing sections, soft 404 responses and a reduced sitemap after a release.
Confirming an outage
A notification is preceded by a repeated check. A momentary network disruption therefore raises no alarm, so the agency duty keeps its credibility and is not burdened with false reports.
Reporting the client can understand
Retention of a subscription rests on documented care. At the end of each period a report is produced in PDF format and passed to the client as the summary of the month covered by the service.
Scope of the report
- Outages: time of occurrence, duration and how their resolution was confirmed
- Time to detection and time to notification, presented separately
- Certificate and domain events, reported in advance
- Content and configuration changes recorded during the period
What the report does not contain — and why
The report contains no SLA provisions or pricing. It presents the course of events rather than the commitments undertaken; those remain the subject of the agency's agreement with the client, not of a record of measurements. Response times and how they are billed are part of the agency's service.
The agency duty, built on the platform
The platform detects irregularities and notifies, while the response is taken by a person — on every plan that person can be the agency. The service comprises the duty, the response times and the repairs; the platform supplies the signal, the incident, the history and the report it rests on.
- 1
Alert
The platform confirms the outage and delivers a notification — by email and as a push in the mobile app.
- 2
Incident
The event is recorded in the panel with its time, address and history. The scope and moment of unavailability are unambiguous.
- 3
Response
The agency takes corrective action — precisely the element of the service the client entrusts to the agency rather than to automation.
- 4
Report
The incident and the time taken to handle it are included in the monthly summary as confirmation of the duty's effectiveness.
On the Start and Business plans the duty stays entirely with the agency — the platform provides none of its own there. On the Enterprise plan the agency may also run it on its own terms; the platform duty is then an optional add-on rather than a condition of the plan.
A mobile app for iOS and Android
A single native app serves both sides of the arrangement. Push notifications arrive independently of email, and the current website status is available from a phone — in one form for the person on duty, in another for the client.
For the person on duty
- Outage notifications as a push, with quiet hours and per-person settings
- The incident, its history and the website status visible on the phone
- A response possible without access to a computer
For the client
- The same app, in which the client sees the state of their own website
- A view of open incidents and monthly reports
- Peace of mind without calling the agency — confirmation that all is well
Two models of cooperation
Agencies run both models in parallel, so the panel supports each. The choice is made separately for each client.
Payment by the agency, re-invoicing the client
The agency purchases the plans in its own name and adds its own margin. A single consolidated settlement and a shared renewal date for every website in the account mean one invoice rather than many.
- A margin the agency sets itself
- A single consolidated invoice and a shared date
- The platform pricing stays invisible to the client
Payment by the client, commission for the agency
The agency carries out the implementation and hands over the payment by link; the client settles it directly, and the agency receives 20% of every invoice paid for the entire relationship. Keeping the client relationship means the commission continues to accrue.
- 20% of the net amount, a fixed recurring rate
- Payment handed over via a single link
- Commission for the entire client relationship
Benefits on both sides
The same service closes the gap in the agency's revenue and gives the client measurable proof of care.
For the agency
- Recurring subscription revenue in the gaps between projects
- 20% commission on net, or the agency's own margin on re-invoicing
- One panel and one settlement for every client
- A mobile app with push notifications — duty away from the office
- A PDF report and a status page under the agency brand
- Client onboarding via the CMS plugin with a referral code
For the client
- An outage detected before users notice it
- One technical caretaker and one point of contact
- A monthly report as proof of the care provided
- A public status page for the client's own audience
- The account stays the client's — full control and transparency
- Insight into the website state from the mobile app too
How the cooperation works in practice
One panel for all clients
Every client's websites in one place: plan, status, open outages and commissions. Switching between entities happens without repeated sign-in.
The client account
The account stays the client's property, and the agency receives an administrator role within it. The client sees the agency on the team list and can withdraw access — this is stated openly, because transparency is the basis of trust.
A plugin with the agency referral code
The WordPress plugin and the Neos, Sylius and Magento packages create the account with the agency referral code directly from the website panel. For an agency this is a more natural channel than banner materials.
Transparent settlement
The agency receives a statement and a PDF document and issues an invoice for the net amount (a PLN 200 threshold, or €50 for commissions earned in euro; each currency is settled separately). Once the transfer is made the settlement is marked complete — „settled" denotes funds that have left the account, not merely a scheduled payment.
Supplementary material before the conversation
An invitation to discuss the terms of cooperation
All that is needed is how many websites the service covers and which billing model is preferred. The terms are established together, with the model, the rate and the onboarding method adapted to the agency's existing way of working.
The formal programme terms are still being prepared, so partners are admitted through an individual conversation rather than self-service registration. The first contact is directly with the team.