Talk to an expert
Tell us what you run, what is getting in the way, and when it needs to be resolved. Every new enquiry is read by someone technical and answered within one business day.
- Response target
- 1 business day
- Office
- Accra, Ghana
- Telephone
- +233 243 182 362
- Hours
- Mon – Fri, 08:30 – 17:30 GMT
Accra office
We work with organisations across Ghana and the wider West African region. Cloud work is usually delivered remotely; we attend site where infrastructure, workshops, or user enablement genuinely require it.
- Address
- Suite 2134, Atlantic Towers, Liberation Road, Accra, Ghana
- Telephone
- +233 243 182 362
- Office hours
- Monday – Friday, 08:30 – 17:30 GMT
- Message the team
Already a customer?
Incidents and service requests belong with the service desk rather than this form. Tickets raised through support are logged against your account, triaged by severity, and measured against the response targets in your agreement. Anything sent here has to be re-entered by hand, which costs you time at the wrong moment.
Send an enquiry
Choose the enquiry type first and the form adapts, asking only for the details that matter to that route.
After you press send
A short, predictable sequence rather than an unexplained silence. Chasing us should never be the only way to find out where an enquiry has got to.
We aim to respond to every new enquiry within one business day. Complex briefs occasionally need a second conversation before anything can be priced sensibly, and we will tell you if that is the case rather than producing a proposal built on guesses. If your matter is genuinely urgent — a live outage, a suspected security incident, or a renewal lapsing this week — telephone rather than using the form.
- 01
Acknowledgement
You receive confirmation that the enquiry has arrived, sent to the address you gave us. If nothing appears within a few hours, check your junk folder before assuming the message was lost.
- 02
Triage and routing
A person reads the enquiry and decides who should own it: licensing questions go to the CSP practice, project briefs to consulting, security concerns to the security lead. Routing is a human decision, which is why the detail you give is worth the extra two minutes.
- 03
A scoping conversation
We arrange a call or a meeting, usually thirty to forty-five minutes. The purpose is to understand your environment, the constraint that prompted you to write, and who inside your organisation needs to be satisfied by the answer.
- 04
A written proposal or assessment scope
You receive either a proposal with scope, assumptions, and commercials, or a scope for a paid assessment where nobody yet has enough information to price the work honestly. If we are not the right partner, we say so instead.
What to include in your first message
You do not need a specification. You do need enough context that our first reply is useful rather than a list of questions.
The least productive enquiry we receive is a request for a price with no context attached. It is not that we mind quoting; it is that a number given without knowing user counts, existing licence position, connectivity, or what the system has to do is either wrong or padded, and both waste your time.
Impact matters more than symptom. “Email is slow” and “the finance team cannot open the shared mailbox they invoice from” describe the same class of problem with very different consequences, and the second tells us who to involve.
Constraints are not an embarrassment; they are the most useful thing you can give us. A capital budget that opens next financial year, a site whose link will not carry a bulk transfer, or a team of two already at capacity all change what we would recommend.
A useful first message covers
- What you run today: Microsoft 365, Azure, on-premises servers, a mix, or an estate you inherited and have not fully mapped
- What is not working, described as impact rather than symptom — who is affected and what they can no longer do
- Licence renewal or contract dates, even approximately
- The timeline you are working to and what is driving it: an audit, a lease expiry, a merger, or a board commitment
- Constraints we should design around, such as budget cycle, connectivity, procurement rules, or the skills available in your team
If you do not have all of this to hand, send what you do have. An incomplete enquiry answered today is more useful than a complete one that never gets written.
Other reasons to contact us
Not every message is a commercial enquiry. Sending yours to the right place keeps it out of a queue it does not belong in.
New commercial enquiry
Licensing reviews, cloud assessments, migrations, security work, infrastructure, and managed services. The form on this page captures the context that shortens the first conversation.
Existing customer support
If you hold a service agreement with us, raise incidents and service requests through the service desk. Tickets logged there are triaged by severity against the targets in your agreement.
Partnership or vendor
Vendors, distributors, and technology partners looking to work with us in Ghana and the wider region. Tell us which platform you represent and what the commercial model looks like.
Careers or media
Speculative applications from engineers and consultants are welcome, as are press questions and speaking requests. For a role, tell us which platforms you work on day to day.
Before you get in touch
The questions organisations most often ask us at first contact. If yours is not here, ask it directly.
We are based in Accra, Ghana, and work with organisations across Ghana and the wider West African region. Remote delivery is normal for cloud work; on-site attendance is arranged where infrastructure or user enablement requires it.
With a conversation, then a short assessment. For most organisations the first paid piece of work is a readiness or licence review, because it produces a defensible plan and often pays for itself in licensing corrections.
Yes. Small teams often benefit most from CSP licensing plus a managed baseline, because it gives them enterprise-grade security and support without hiring an internal IT function.
Often, yes — particularly where we bring a specialism they do not have. What matters is that responsibility boundaries are documented so nothing falls between two providers during an incident.
Your tenant, your data, and your subscriptions remain yours. We provide documentation, transfer the CSP relationship where applicable, and remove our delegated access. Exit should be as clearly defined as onboarding.