An executive-led business
SolutionExec is built around the expertise and network of James Kaikis, an enterprise technology executive and community builder who works with some of the largest companies and leaders in the ServiceNow ecosystem.
We started the company from scratch with James. That included the logo, the brand, and everything you see on the public web — not a later polish pass on something that already existed.
That creates an unusual business. The product is not sitting neatly inside a piece of software. It is spread across James’s expertise, his relationships, executive conversations, presentations, events, content, community, and the opportunities that emerge from all of them.
We have worked closely with James across that entire system. What started with building the visible identity gradually became something much broader: helping build the infrastructure around how an executive-led company communicates, distributes ideas, develops relationships, and turns those relationships into commercial opportunities.
Understand James first
You cannot build an executive-led business by separating the executive from the brand. James has his own way of speaking, his own point of view, his own relationships, and an audience that follows him because of those things.
So a large part of the job has been learning how he thinks and translating that consistently across different formats. A website. A presentation. An executive conversation. An event. A newsletter. A social post. A sales asset.
They should not feel like seven different agencies produced them. They should feel like James. That required getting close enough to the business that we could understand the intent behind something rather than simply execute a brief.
Presentations
James regularly needs to communicate complicated ideas to executives, customers, partners, and communities. We have worked with him on corporate presentations, executive narratives, event materials, and other communication where the job is not simply making slides look better.
The first question is: what does this audience need to understand? Then: what should James say? What evidence supports it? What does not belong? What should the room remember afterwards?
Only after that does it become a design problem. That same approach eventually influenced almost everything else we built.
The public-facing business
The work expanded across SolutionExec’s digital presence: the logo and brand system, website, executive content, social carousels, newsletters, events, campaigns, and sales materials. These were not useful as isolated deliverables. They were all different ways for the market to interact with the same business.
Someone might first encounter James through a LinkedIn post. Another person might attend an event. Someone else might subscribe to the newsletter. An executive could see a presentation. A prospect might enter through a completely different introduction. The interesting problem became: what happens after that?
Connecting the pieces
SolutionExec was generating valuable interactions across several platforms, but each system naturally saw only its own piece of the relationship. Luma knew about event registrations. Mailchimp knew about email engagement. Substack knew about subscribers. Notion held other parts of the operation. LinkedIn created another layer of audience activity. And the team knew things about people that none of those systems knew.
We began connecting these pieces. Using tools including Notion, Zapier, Mailchimp, Luma, Substack, and Clay, we built workflows around audience management, enrichment, events, distribution, and commercial follow-up.
The point was not to collect more data. It was to stop throwing context away.
Events as a commercial system
James and SolutionExec bring people together through events and executive conversations. Originally, an event could easily behave like an isolated activity: invite people, run the event, follow up, move on. We started treating it differently.
Every registration tells us something. Every attendee represents a company and role. Repeat attendance tells us something else. Engagement after an event creates another signal. Over time, those interactions form a relationship history.
So we worked on connecting registration, audience information, enrichment, and follow-up so that each event could strengthen the intelligence available for the next one. The event did not have to end when the room emptied.
Enrichment
Once we knew who was entering the ecosystem, we could understand them better. Using enrichment workflows and tools such as Clay, we could identify companies, roles, and other information around people already interacting with SolutionExec.
That allowed us to ask better questions. Is this person part of the ICP? Is their company relevant? Have they interacted with James before? Are multiple people from the same organization appearing? Is there enough context to justify a conversation?
This changed the objective from “how do we send more outbound?” to “who is actually worth talking to, and why now?” That is a much more useful question.
Content as infrastructure
The same thinking applied to content. James already had the difficult ingredient: ideas worth distributing. Our job was to create more leverage from them.
An executive conversation could reveal an idea. That idea could become content. Content could drive newsletter subscriptions. A newsletter could promote an event. An event could create new relationships. Those relationships could be enriched. Enrichment could expose commercial opportunities. And those opportunities could lead to another executive conversation.
What initially looked like separate marketing activities started becoming a loop.
A role that is hard to categorize
Over the course of the relationship, we have worked across executive positioning and communication, corporate and CEO presentations, brand and visual systems, website strategy and execution, sales and marketing collateral, executive content, social distribution, newsletter infrastructure, events and registrations, audience and community operations, lead enrichment, ICP identification, prospect intelligence, outreach workflows, funnel infrastructure, automation, GTM operations, and coordination across people, platforms, and external specialists.
We do not personally need to be the world’s best specialist in every one of those disciplines. That is not the role. When something requires another expert, tool, vendor, or collaborator, we are comfortable bringing them into the system and working across those boundaries.
The responsibility is making sure the whole thing works, not protecting a particular scope of work.
Still working together
SolutionExec is not a finished case study in the traditional sense. The relationship continues. The problems change.
Sometimes James needs an important presentation. Sometimes there is an event to launch. Sometimes we need to improve distribution. Sometimes there is an operational bottleneck. Sometimes we discover information we are collecting but not using. And sometimes the next useful thing was not part of any original plan.
That is possible because we have accumulated context about the business over time. We do not have to rediscover SolutionExec every time something new needs to happen.
What this taught us
SolutionExec reinforced something we had already started learning through other engagements: a company does not experience its problems in agency categories. James does not wake up with a website problem, a design problem, a Clay problem, and a presentation problem. He has something he is trying to accomplish. Everything else is infrastructure around that objective.
The more context we accumulated, the more useful we could become across those boundaries. And that is increasingly how we think about NextGrid. Not as the company you call because you have already decided what needs to be built. But as the company you can bring into an important problem early enough to help determine what should happen, who needs to be involved, and then help get it done.
With SolutionExec, we started by building the company with James from scratch — the logo, the brand, and the public web. Over time, we have helped build more of the system that connects James’s ideas, his audience, his relationships, and the commercial opportunities around them.
James Kaikis and the related ecosystem
James’s own channels sit beside SolutionExec, and GTMshift is a related go-to-market initiative. The public system is one loop: website, LinkedIn, newsletter, podcast, executive roundtables, Off The Record — and the people who move through it.
Questions
Is SolutionExec a software product?
The product is not sitting neatly inside a piece of software. It is spread across James Kaikis’s expertise, relationships, executive conversations, events, content, and community. We started from scratch on the brand and public web, then helped build the operating system around that executive-led business.
What did you actually ship?
The visible identity, the public web, and the infrastructure for how the company communicates, distributes ideas, develops relationships, and turns those relationships into commercial opportunities.
