The questions you would ask on a call, answered here

With a conversation, not a proposal. The first call is thirty to sixty minutes and it is mostly questions from us — what is slow, what is manual, what keeps getting escalated, and what you have already tried. There is no charge and no obligation, and we will not send a quote afterwards unless you ask for one.

If it looks like there is something worth doing, the next step is usually a working demonstration or a scoped proof of concept rather than a document.

No, and most clients do not have one. Describing a symptom is enough — the report nobody trusts, the process that takes three weeks, the system everyone works around. Turning that into a requirement is part of what you are hiring us for.

If you do arrive with a detailed specification, we will read it carefully, and we will tell you what we think.

The initial conversation and a walkthrough of our existing proofs of concept are free. A full discovery engagement — where we spend days with your teams and produce a documented current-state assessment and roadmap — is chargeable, and we will tell you the price before it starts.

What you own at the end of a paid discovery is yours, including if you take it to another supplier. We will not produce a discovery document whose only real deliverable is a proposal to hire us for the next phase.

It depends on the size of the engagement and the specialists involved. Small projects can usually start within two to three weeks; a large implementation might take longer to staff properly. We discuss the timeline during the agreement review.

No. A significant part of our work is with small and mid-market organizations, and we scope engagements for that reality — phase one measured in weeks, priced so it proves itself before phase two is commissioned. We are not structured to only take enterprise programmes.

We run multi-entity, multi-country implementations across regulated industries, and we have a global team to staff them. We are here to solve complex problems at a large scale.

Microsoft is our center of gravity and where our deepest expertise sits. But we hold partnerships across infrastructure, networking and security — Dell, Lenovo, HPE, Cisco, Fortinet, Check Point, Sentinel One, Proofpoint and others.

We integrate with whatever you are keeping. We have no interest in a rip-and-replace project for its own sake, and we will say so when your existing system is fine.

Less than you would think. The disciplines that make an industry solution work — understanding the process, the regulator and the reporting obligation — transfer further than the sector label suggests. Describe your operation, and we will tell you what we think.

Most of our managed services work sits alongside an internal team, taking on the parts they do not have capacity or specialization for. Some clients have no internal function and want everything run by us.

Regularly. Common examples: when your existing licensing already covers what you are about to buy, when a Power Platform application on your current systems would solve the problem more cheaply than the SAAS subscription you were considering, when a Copilot deployment should wait until permissions are cleaned up, and when a workload should not move to cloud at all.

Defined project work is fixed price, agreed before anything starts.

Managed services are priced per period against agreed service levels. Resourcing is priced per person per period. Advisory can be either, depending on whether the outcome is defined.

It is raised in writing when it arises, with the cost and schedule impact stated, and you decide. We do not perform out-of-scope work and invoice for it afterward.

We can, and many clients find it simpler to procure through one channel with one invoice and one renewal calendar. But our first piece of work is frequently a licensing review that reduces what you buy.

If you would rather buy licenses elsewhere and use us only for services, that is entirely fine and changes nothing about how we work with you.

Project work is contracted for the project. Managed services typically run on a twelve-month term with a notice period, because a service desk has to be staffed against a known volume — but we will discuss shorter initial terms where you want to try before committing.

It varies too much for a number here to be honest. A licensing and entitlement review is a small, defined piece of work. A Power Platform application for one process is modest. A multi-entity ERP implementation is a different order of magnitude entirely.

What we can tell you is that we will give you a fixed number before you commit, and we will scope phase one so it pays back before phase two is authorized.

Named people, introduced at kick-off, and the same people through delivery. The person who scoped your work stays involved.

Every engagement of any size has three named roles: a PMP-certified project manager, a customer experience manager, and a technical lead, plus a director named as escalation.

We have teams in the United States, the Middle East, and India, and we are open about which parts of an engagement each covers.

If your procurement or regulatory position requires work to be performed in a specific country, please inform us, and we will confirm in writing.

You hear about it as soon as we know. Weekly status reports against the original dates — so a slip is visible while there is still time to respond.

If caused by something on your side, we will have flagged the dependency in advance and will replan with you.

Yes. Every phase has a defined end point and a decision to continue or not. We would rather you stopped at phase one having got value from it than continued into a phase two you were unconvinced by.

You keep the documentation, the configuration and everything produced up to that point.

Against a baseline agreed with you in writing before design starts — the current numbers, the target, and the method by which both will be measured. We report against those figures afterward, including if we fell short.

The minimum required for the work, at the lowest privilege that will do the job, granted for the period it is needed and revoked afterward.

We are happy to work within your privileged access management process.

Every engineer holds Microsoft certification plus the vendor-specific credentials their specialism requires, and project managers are PMP-certified. Background screening is standard, and we can meet enhanced vetting requirements where a client's sector demands it.

Yes — we have a local presence in the United States, Saudi Arabia, the United Arab Emirates, and India.

Please inform us of any data residency requirements if we missed bringing them up.

Yes, as needed.

Professional indemnity, public liability and cyber liability cover, with certificates available on request. Our standard terms include confidentiality, data processing provisions and a defined liability position, and we are used to negotiating enterprise procurement terms.

Our managed service operates 24/7, staffed across three regions and with an on-call engineer at your local office. That distinction matters: at 3 am your time, someone in another region is at their desk working a normal shift, in addition to your local team.

Support is available through the help desk portal, by email at support@jjcsystems.com, or by phone.

Response targets are agreed per client and stated in your service agreement, because a system outage means something different in a hospital than in a back-office. Severity levels are defined jointly rather than imposed, and we report performance against them monthly.

Named people who know your environment. The service desk is staffed as a team so cover is never dependent on one person being available, but you are not explaining your estate from scratch on every call.

Raise it with your account manager, or with the customer success team, who are independent of both delivery and commercial. If neither resolves it, a director is named as your escalation from day one and expected to be used.

We also commission independent third-party satisfaction surveys rather than running our own, precisely because a score a supplier collects about itself is not evidence.

You do. Configuration lives in your tenant, documentation is written for your staff and held by you, and custom development is yours under the terms of the engagement. Nothing we build for you sits on our systems as a condition of it continuing to work.

Deliberately not. We build with configuration over code wherever possible and train your team to maintain it.

We hand over properly — documentation, credentials, configuration detail and a transition period with our people available to answer questions. We have done this and will do it again.

Yes, subject to those clients agreeing.

For a live reference conversation, ask your account manager, and we will arrange it with a client in a comparable sector.