Contact
Talk to an expert
Tell us what you are running, what is getting in the way, and when you need it resolved. Every new enquiry is read by someone technical and answered within one business day.
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
Already a customer?
Incidents and service requests should go to 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 exactly the wrong moment.
Open a support requestSend an enquiry
The fields below exist to route your enquiry to the right specialist first time. Industry, size, timeline, and areas of interest decide whether this lands with our licensing practice, our consulting team, or the security lead — so the more you tell us now, the fewer qualifying questions you will have to answer later.
What happens next
After you press send
A short, predictable sequence rather than an unexplained silence. We would rather you knew what to expect and when, so that chasing us is never the only way to find out where an enquiry has got to.
Most enquiries follow the same four steps. 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 that lapses this week — telephone instead of using the form.
Acknowledgement
You receive confirmation that the enquiry has arrived, sent to the address you gave us. If you have not seen anything within a few hours, check your junk folder before assuming the message was lost — filtering catches more first-contact email than most people expect.
Triage and routing
A member of the team reads the enquiry and decides who should own it. A licensing question goes to the CSP practice, a migration brief goes to consulting, a security concern goes to the security lead. Routing is a human decision rather than a keyword rule, which is why the detail you provide is worth the extra two minutes.
A scoping conversation
We arrange a call or a meeting, typically thirty to forty-five minutes. The purpose is to understand the environment, the constraint that prompted you to get in touch, and who inside your organisation needs to be satisfied by the answer. We will ask questions rather than present slides.
A written proposal or assessment scope
You receive something in writing: either a proposal with scope, assumptions, and commercials, or a scope for a paid assessment where the honest answer is that nobody yet has enough information to price the work properly. If we think the engagement is not a good fit, we will say that instead.
Before you write
What to include in your first message
You do not need a specification. You do need enough context that our first reply can be 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. A short paragraph of background changes the quality of the answer considerably.
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 one tells us who to involve. The same applies to projects: a migration driven by a data centre lease expiring in March is a different piece of work from one driven by general modernisation ambition.
Constraints are not an embarrassment; they are the most useful thing you can give us. A capital budget that only opens in the next financial year, a site with a link that will not carry a bulk data transfer, a procurement policy requiring three written quotations, or a team of two people already at capacity — every one of those changes what we would recommend. Designs that ignore constraints stall at implementation, and we would rather find out now than in month three.
A useful first message covers
- What you run today — Microsoft 365, Azure, on-premises servers, a mix, or something 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 if you know them, 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: budget cycle, connectivity, procurement rules, or skills available inside 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.
Who answers
You will speak to someone technical
Enquiries are read by consultants and engineers, not routed through a call centre or a qualification script.
Whoever replies to your first message is capable of discussing the substance of it. If you ask whether Business Premium covers your risk profile, or whether a workload should move to Azure at all, you will get a considered answer rather than an offer to book a discovery call before anything can be said. Where a question needs more depth than the first responder has, it goes to the relevant practice lead — licensing, consulting and architecture, security, data protection, or managed operations — and that person joins the conversation directly.
We are in Accra and we work in your time zone. That is a practical point rather than a marketing one: it means a question asked at ten in the morning is usually answered the same day, and that when something needs a meeting, a meeting can happen without arranging a window that suits a support desk on a different continent.
One more thing worth stating plainly. If we do not think we are the right partner for what you are asking — because the work sits outside our practice areas, or because your existing provider is already doing it competently — we will tell you. Winning an engagement we cannot deliver well costs us more than declining it.
Routing
Other reasons to contact us
Not every message is a sales enquiry. Sending yours to the right place keeps it out of a queue it does not belong in.
New business and project enquiries
Licensing reviews, cloud assessments, migrations, security work, infrastructure, and managed services. Use the form on this page — it captures the context that shortens the first conversation.
Use the enquiry formExisting customer support
If you already hold a service agreement with us, raise incidents and service requests through the service desk rather than the sales form. Tickets raised there are logged against your account and triaged by severity.
Go to supportPartnership and vendor enquiries
Vendors, distributors, and technology partners looking to work with us in Ghana and the wider West African region. Tell us which platform you represent and what the commercial model looks like.
Email the partnerships inboxCareers
Speculative applications from engineers and consultants are welcome. Send a CV with a short note about the platforms you work on day to day and the kind of work you want more of.
Send your CVMedia and speaking
Press questions, analyst briefings, and requests for a speaker on Microsoft cloud, security, or infrastructure topics in the region. Please include your deadline.
Email the media contactInvoices and account queries
Billing questions, purchase order requirements, and reconciliation of subscription invoices against active seats. Quote your account reference so we can pull the right records first time.
Email accountsNo brief yet
Not sure what you need yet?
A short diagnostic conversation costs nothing and frequently establishes that there is less work to do than feared — or that the real problem is somewhere other than where you were looking.
Plenty of the calls we take begin with an uncertainty rather than a requirement. Costs have drifted and nobody can explain why. An auditor has asked a question that cannot currently be answered. A migration has been discussed for two years without moving. In those situations, the useful first step is not a proposal — it is thirty minutes with someone who has seen the pattern before and can tell you which of the three things you are worried about actually matters.
We do not charge for that conversation, and it does not commit you to anything. If it turns out there is real work to do, we will scope it. If it turns out that your environment is in better shape than you thought, or that the fix is a configuration change your own team can make in an afternoon, that is a perfectly good outcome and we will say so.
What a diagnostic call covers
- Where you are now. The platforms in use, roughly how many people depend on them, and what has changed recently.
- What is actually hurting. Cost, reliability, security exposure, audit pressure, or the fact that one person holds all the knowledge.
- What you already own. Licences frequently include capability that has never been switched on, which changes what needs buying.
- A sensible first step. Usually an assessment, occasionally a single configuration change, sometimes nothing at all.
Office hours are Monday – Friday, 08:30 – 17:30 GMT. Calls outside those hours are returned on the next working day unless you hold a service agreement with extended cover.
Questions
Frequently asked
The questions that come up most often before a first conversation.
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.