01 — CONTACT · Ad hortum
Come and walk the borders.
Every engagement starts with a conversation about what you are actually worried about, which is rarely the thing written in the tender document. You do not need a specification, a budget code, or a finished idea of what you want tested. A few lines is plenty to start.
Sales enquiries: sales@therose.garden
Careers: careers@therose.garden
Not sure what you want? Try hello@therose.garden
02 — BEFORE YOU WRITE · Instructiones serendi
A scope comes together faster when we know roughly what we are looking at. If you have these to hand, include them.
- What you would like tested — an application, a network, a cloud tenancy, or the people.
- Rough scale — how many applications, how many live hosts, how many user roles.
- Why now — a launch, an audit, a customer questionnaire, or a bad feeling.
- When you need the report in hand.
- Whether a particular scheme or standard applies — CHECK, CREST, PCI DSS, ISO 27001.
And if you have none of it, write anyway. Working out the scope is part of the job, not a prerequisite for asking.
03 — WHAT HAPPENS NEXT · Ordo rerum
I. A conversation. Half an hour with the person who will do the testing. No charge, no slide deck, and no discovery call about the discovery call.
II. A written scope. What is in, what is out, what it costs, and what you receive at the end. Fixed price, agreed before anything starts.
III. Dates in the diary. Signed authorisation, an agreed testing window, and a named tester. Then the work begins.
IV. A report you can act on. Written by the consultant who did the testing, delivered with a debrief, and followed by a retest of anything you fix.
04 — PARTICULARS · Notae
Correspondence – sales@therose.garden
Hours – Monday to Friday, 09:00 to 17:30 GMT. Testing windows by arrangement, including out of hours and weekends where a change freeze demands it.
Response – Within one working day.
Registered – The Rose Garden Ltd, company no. 17236497, registered in England and Wales.
We answer our own email. There is no form here, no ticket number, and no queue – only the person who would be doing the testing.