SkyPlanner is now an OpenAI Select Partner. Announcements like this usually arrive with more enthusiasm than substance, so here is the honest version: what it changes for the teams we work with, and what it deliberately does not.
We are a Salesforce Consulting Partner. That has been true for a long time and it remains the centre of what we do. As of this month we are also an OpenAI Select Partner, a tier within the OpenAI Partner Network, the programme OpenAI launched in June 2026 for organizations that build, deploy and support AI solutions with their technology.
We are pleased about it. We are also aware that a partner badge, on its own, tells a client very little. So this piece is an attempt to answer the only question that matters: what does this mean for a company running Salesforce?
Why this particular combination
Most of the difficulty in making AI useful inside a CRM does not sit in the CRM, and it does not sit in the model either. It sits in the space between them.
That space is where the awkward questions live. What data can the assistant reach, and is that data trustworthy? What is it allowed to change? What does “qualified” mean in this company, and does the AI know? When the answer is wrong, whose problem is it: the platform, the model, or the way it was configured?
When those two sides are held by different vendors, that middle ground is exactly where accountability goes missing. Everyone is technically doing their job, and the client is the one holding the problem.
Being credentialed on both sides does not make that space disappear. It does mean one partner owns it.
What actually changes
Three things, and we would rather describe them modestly than oversell them.
Our team gets trained on what they are configuring. The programme includes enablement and certification. That sounds like an administrative detail, and it matters more than it sounds: the difference between a competent AI deployment and a disappointing one is very often configuration, not capability. The people doing that work being formally trained on it is a real improvement, not a marketing line.
We work closer to the technology behind PilotIQ. PilotIQ, the assistant we built to work inside Salesforce, runs on OpenAI models. Until now that was a technical dependency. It is now a relationship, which means better access to guidance when we hit something genuinely hard.
One partner is accountable across the whole path. From assessing whether a Salesforce org is ready, through configuring the assistant, to keeping it working afterwards. Not two vendors and a gap.
What does not change
This is the more important half, and it is the reason we wrote this rather than just posting the news.
Closer access to better models does not fix undefined fields. It does not document a process that currently exists only in a senior colleague’s head. It does not decide what an assistant should be allowed to change, or agree what your company means by “at risk.”
Those remain the things that decide whether AI is genuinely useful in an org or merely impressive in a demo. We have written at length about why the foundation, not the model, decides the outcome, and nothing about this week changes that view. If anything it sharpens it: we now have a clearer view of what the technology can do, which makes it more obvious how often the constraint is somewhere else entirely.
So we will keep starting where we always start. With the data, the processes, the permissions and the definitions. The unglamorous part.
Wondering where your org actually stands?
Our AI Enablement Services start with a readiness assessment: an honest picture of your data, processes and access rules before anything is deployed.
A note on Salesforce
Worth saying plainly, because we have been asked: this is not a step away from Salesforce. It is not a comment on Salesforce’s own AI capabilities, which continue to develop quickly and which we work with.
Organizations end up with a mix. Some capability comes from the platform, some from elsewhere, and the interesting work is making the combination coherent inside one org, with one set of rules about what can be accessed and changed. Our job has always been to make Salesforce work for the business in front of us. This is a continuation of that, with a wider set of tools and better standing to use them well.
Thank you
Credentials get earned in rooms nobody sees. A client who let us try something before it was fashionable. An admin who stayed late to test a build. A team who told us early that something was not working, when it would have been easier to say nothing.
That is where the work behind this actually happened. Thank you to the people who let us learn on real problems.
If you are weighing AI for your Salesforce org
Our position is unchanged, and it is not a difficult one. Start by finding out whether your org is ready. Fix what is cheap to fix. Choose two or three things genuinely worth doing. Then build.
If you would like a straight answer on where you stand, that is what our AI Enablement Services readiness consultation is for. About 30 minutes, no obligation, and you leave with a clear picture either way.
SkyPlanner
