Manage website maintenance subscriptions by connecting the service agreement, billing schedule, payment status and support to the same customer. A portal makes that information accessible; the agency remains responsible for delivering the maintenance.
Define a service clients can understand
Describe included tasks, such as planned updates, backup checks and a support allowance. Identify exclusions such as redesigns, new functionality and separately purchased licences. Distinguish response time from resolution time and state whether unused support time carries forward.
Prepare a package worksheet
This fictional example is a planning tool, not price advice or PayRequest product pricing.
| Item | Example agreement |
|---|---|
| Website | example.example |
| Service | Maintenance Basic |
| Included | Planned updates, backup checks, 30 minutes of monthly support |
| Price | €60/month before any applicable tax |
| Excluded | New functionality, redesign, separately purchased licences |
| Support | Portal request during agreed working hours |
| Cancellation | According to the accepted agreement |
Record how customers approve extra work. Match the final service description to what your team can deliver.
Connect billing and customer access
Create recognisable PayRequest subscriptions with the correct customer, amount, period, first invoice date and payment method. Consult the subscription documentation for configuration. A recurring invoice is distinct from automatic collection; verify provider support and the required authorisation before promising automatic payment.
The customer portal brings invoices, subscriptions and support into the customer relationship. Keep maintenance scheduling in the operational tools that deliver the work.
Calculate delivery effort as well as revenue
Assume twenty fictional clients paying €60/month: monthly subscription revenue is €1,200 on the same tax basis. At an assumed 45 minutes per website, delivery needs fifteen hours a month. With an invented internal hourly cost of €40, that is €600 of delivery time.
The remaining €600 is before licences, hosting, payment processing, platform fees, sales, administration and other costs. This is a hypothetical sensitivity model, not a profit forecast. Replace all assumptions with your actual costs and time records.
Assign different incidents to the right owner
A failed payment needs billing follow-up. A failed backup needs technical investigation regardless of invoice status. A feature request needs a scope and approval decision. Cancellation needs an agreed end date and a final billing check.
Maintenance, hosting and domain registration can have different renewal dates. Stopping maintenance does not automatically cancel a domain or remove a website. Verify the actual status, agreement and operational consequences before changing services.
Start with one package
Prepare one maintenance product, review the customer view and assign a single owner for the next invoice when migrating. A customer export does not prove payment mandates can transfer. Review current PayRequest pricing: Business is €20/month, with access activated after setup and paid checkout. Provider fees and commission exceptions remain separate.
Explore the customer portal and use the agency panel setup guide to introduce it to clients.
*PayRequest Team. Sources checked 5 November 2026. Original hypothetical package worksheet and calculation; no customer outcomes or live collection tests claimed. Prepared with AI assistance.*
