A missed renewal is a client's website going dark.
Hosting is a small amount of money repeated a great many times, and the whole job is making sure none of it is forgotten. Gydon holds the domains, the plans, the renewal dates and the recurring invoices against the client they belong to, with the support tickets in the same place.
Everything with a date on it, in one list
Domains and hosting plans are their own modules rather than notes on an account, because the thing that matters about them is a date. Each one sits against the client, carries what it costs and what it is sold for, and can raise a task or an email before it expires rather than after.
Which turns the worst phone call in hosting, the one where a site has gone down because nobody renewed something, into a diary entry that somebody has already dealt with.
- Domains and plans against the client, with renewal dates and cost against price
- Workflow triggers on a date, so the reminder happens without anybody remembering
- The margin on each line visible, which for resold hosting is easy to lose track of
- History on the record, so who changed what and when is answerable
The client record everything else hangs off.
Small invoices, a lot of them, on time
Recurring invoices go out on their own schedule with a payment link on them through Stripe, and they land in Xero with everything else. Nothing about a hosting business is intellectually difficult; it is just relentless, and it is exactly the sort of work that should not be somebody's Monday.
Because the invoice, the plan, the domain and the tickets all sit on the same client record, a query about a charge is answered from one screen rather than three systems.
- Invoices raised on a schedule from your own templates
- Card payment links, so a small invoice does not need a bank transfer
- Overdue visible as a figure rather than a feeling
- Xero sync both ways, so your accountant carries on as they are
What is out, what is paid and what is late.
The ticket and the hosting on one screen
Tickets sit on the client they belong to, next to the plan they are almost certainly about. Whoever picks up the phone can see the site, what it is hosted on, when it renews, what was invoiced last month and the last three things that went wrong, without asking the caller to hold.
Service levels, canned responses and a knowledge base keep the answers consistent when more than one person is answering.
Tickets against the client, beside the billing and the plan.
What hosts usually switch on
- Domains
- Domain records against the client, with renewal dates and what each one costs and sells for.
- Hosting and Web hosting
- Plans, what a client is on, and the recurring billing that goes with them.
- Support and ticketing
- Helpdesk on the client record, with SLAs, canned responses and a knowledge base.
- Workflow automation
- Triggers on dates and statuses, which is how a renewal reminder happens without a human diary.
- Xero and Stripe
- Recurring invoices, payment links, and the accounts package left as it is.
- Always included
- CRM, quotes and invoices, tasks, calendar, timesheets, reporting, document templates, workflows and permissions, whatever else you switch on.
- What Gydon is not
- It is not a control panel and it does not provision anything. No cPanel or WHM automation, no DNS editing, no server monitoring and no uptime checks. It is the commercial record of what you host, not the thing that hosts it.
Bring your renewals spreadsheet
Whatever shape it is in. We will show you what it looks like once the dates, the invoices and the tickets live on the client instead.