Server, website or cloud
Post a task. Get a scope and a price.
One page, top to bottom. Say what the work is on, how soon you need it and where to reply. A senior engineer reads it and comes back with what it involves, what it risks and what it costs. Most of these never need a call.
Direct senior work
No hand-offs and no junior devs. Your request is read and answered by a senior infrastructure engineer.
- A reply within one working day
- No agencies and no middlemen
- A price agreed before work starts
- No credentials asked for through the form
Three steps
What the form asks you
What needs doing
A server, a website or cloud. Add a title and the detail.
When you need it
Urgency, the shape of the work, and where to reply.
Who you are
Name and email. A company adds a VAT number.
Task request form
What is the work on?
Now the detail, and the more of it the better. What is happening now, what you want instead, when it started, what has already been tried, what depends on it, and anything that would surprise somebody seeing it for the first time. A long description is read in full and usually means a price without a single question back.
0 / 6000
Please do not paste passwords, SSH keys, server addresses or usernames. We do not need them to scope the work, and access is arranged separately once the task is agreed.
How soon, and how to reach you
Every answer here takes one click and none of them is required. They are what lets us come back with a real answer instead of a request for a call.
How soon
Urgent means other work is moved aside for it, which is what the priority rate pays for. Most things do not need to be urgent, and saying so honestly usually gets the same result for less.
How you would like it handled
Where should we reply
Pick as many as you like. Adding one does not replace email, it just tells us where else you are.
Who is asking
Are you an individual or a company
It decides the VAT treatment and the hours we would be working in. If yours is not listed, pick Somewhere else and say where in the description.
Still needed: what the work is on, a title, a description, your name, a valid email.
The shape of a good request
One line saying what is wrong, then the detail. These are examples of the shape, not real submissions.
- A serverFlexible
Upgrade MySQL 5.7 to 8.0 without losing a night
End of life, nightly backups now take four hours, and the site crawls while they run. We want it moved with a rollback that has actually been tested, in a window that does not cost us a Saturday.
MySQL / MariaDBPlesk - A websiteWithin a week
Checkout takes eight seconds under load
Fine at 10am, unusable during a campaign. Nobody has traced where the time goes.
Speed and Core Web VitalsCaching and CDN - CloudFlexible
Our AWS bill doubled and nobody knows why
No new customers, no new services. We want the cause, not a spreadsheet.
AWSCost reduction - A serverUrgent
Plesk stopped renewing certificates on 40 domains
Customers are seeing browser warnings. Renewal worked until a month ago.
PleskSSL certificates - CloudWithin a week
Move a two-node cluster off a single region
One region, one point of failure, and an audit that has started asking about it.
Kubernetes - A websiteUrgent
Site went down after a plugin update
Rolled back and it is up, but we do not know what broke or whether it will repeat.
WordPress
Tags you can add
- A server
- A website
- Cloud infrastructure
- AWS
- Backups
- Caching and CDN
- CI/CD pipelines
- Cost reduction
- cPanel / WHM
- Hardening
- Kernel patching
- Kubernetes
- Magento
- Mail server
- Malware cleanup
- Migration
- Migration to cloud
- Monitoring
- MySQL / MariaDB
- OS upgrade
- PHP
- Plesk
- Scaling
- Speed and Core Web Vitals
- SSL certificates
- Terraform
- Uptime and downtime
- WordPress
- Something else
All optional. A tag with two dots belongs under both categories, and if none of them fit, the last one is a real answer rather than a fallback.
Questions people ask before sending one
- Do I have to know exactly what is wrong?
- No. Pick the closest category, say what you are seeing, and the reply will tell you what it looks like from here. Half of these arrive as a symptom rather than a diagnosis, and working out which it is comes before any quote.
- What happens after I send it?
- You get a reference number and an email copy straight away. A senior engineer reads the request and replies with the scope, the approach, the risks worth knowing about and a price. Usually within one working day.
- Do you take payment up front?
- For a new client, yes. A deposit is invoiced once the scope is agreed and work starts after it clears. That is why the form asks a company for its legal name, address and VAT or registration number, so the invoice can go out the same day rather than after another round of emails. Existing clients are billed on their normal terms.
- Why does the form not ask for my server details or password?
- Because it does not need them to scope the work, and a form is the wrong place for a credential. Once a task is agreed, access is arranged over a channel you pick, in whatever way your security policy requires.
- Is this only for one-off tasks?
- No. The second block asks whether you want a single task, hourly help as needed, or ongoing monthly support. All three are normal and the answer changes what gets quoted.
- How is an urgent request different?
- Urgent means other work is moved aside for it, and it is charged at a priority rate. Most things do not need to be urgent, and saying so honestly usually gets a better price and the same result.