IT services enquiry
Tell us what needs support, and what the current setup looks like
Enquiries are reviewed individually. The more context provided here, the more useful the first response can be - and the fewer assumptions have to be made about your environment.
- Written first A described problem is easier to scope than a described product.
- Nothing sensitive Credentials and access secrets are arranged separately, never by form.
- No obligation An enquiry is not a commitment. Scope is agreed before any work.
Useful detail
Six things that make an enquiry easier to answer well
None of these are required. Each one removes an assumption that would otherwise have to be made.
-
Roughly how many users
A band is fine. It affects licence considerations, device planning and how much of the work is repeatable.
-
Which cloud platforms
Named generically is fine - business email suite, file storage, accounting platform, CRM.
-
Where the network struggles
Which part of the building, at what time of day, on which devices, and for how long it has been happening.
-
Existing arrangements
Any current IT provider, internet provider or supplier already involved, and what they cover.
-
What has already been tried
Previous attempts, temporary workarounds and anything that made the problem better or worse.
-
What good would look like
The outcome you actually want, in your own words. It is often more useful than a technical diagnosis.
The process at a glance
Where this enquiry sits in the wider process
Submitting this form is stage one of seven. The full detail of each stage is set out on the process page.
- 01
Submit IT Services Enquiry
Starting from a written description keeps the conversation grounded in the actual problem rather than assumptions about it.
- 02
Share Current Systems, Users and Requirements
Recommendations are only as reliable as the information behind them. Gaps are recorded rather than filled with guesses.
- 03
Review Cloud, Network, Devices and Supplier Context
Cloud providers, internet providers and software vendors set their own rules, service levels and availability. Those boundaries need to be visible from the start.
- 04
Confirm Scope, Access, Security and Responsibilities
Clear scope and access boundaries protect the business, keep expectations realistic and avoid assumptions about who is responsible for what.
- 05
Plan Support, Configuration or Improvement Work
IT changes affect people who are trying to do their jobs. Planning around the business reduces disruption and surprises.
- 06
Deliver Agreed Support and Documentation
Documented work can be handed over, audited and picked up later. Undocumented work becomes a dependency on one individual.
- 07
Review Follow-Up, Risks and Future Improvements
IT environments change constantly. A short structured review keeps decisions deliberate instead of reactive.
Before you submit
What an enquiry does and does not commit either side to
Client responsibility includes providing accurate system information, access permissions, supplier details, licensing information, data handling instructions, security requirements, user feedback, approvals, and timely communication. Legal, data protection, cybersecurity, insurance, procurement, employment, sector-specific, and regulatory requirements should be reviewed with appropriate specialists where required.