We syndicate audio podcasts to Spotify podcasts to take advantage of the network effect there, relying on an RSS feed to update the Naftiko podcast account, working to build our audience on the platform with a regular cadence of podcasts twice a week on relevant topics.
YouTube is the primary location where we publish all video for Naftiko, from shorts to podcast episodes, maintaining distinct channels for each area we are publishing, beginning with the Naftiko Capabilities podcast, but then also video shorts to include in our blog posts and social media.
We publish to API Evangelist properties to take advantage of existing SEO and traffic, but also to provide a more opinionated perspective on some topics that we probably wouldn’t want to publish to the primary Naftiko blog, keeping the brands separate but working together.
We syndicate audio podcasts to Apple podcasts to take advantage of the network effect there, relying on an RSS feed to update the Naftiko podcast account, working to build our audience on the platform with a regular cadence of podcasts twice a week on relevant topics.
We are building our profile on LinkedIn, spending time to follow people who fit our ideal customer profile and persona, while also syndicating blog posts and content from the community to bluesky on a daily basis to keep building traffic and gaining followers over time.
We have published a basic profile to Crunchbase for Naftiko and will continue to round off the profile as we evolve, grow, and take on more funding, keeping it our primary business profile that works in concert with LinkedIn to communicate with the investor class of our community.
We are currently using Daily.Dev for information gathering, finding relevant sources of news and information for our market research and go-to-market activities, but will also be syndicating news there from our blog and the ecosystem to help contribute to the news and information.
We are currently using Dev.To for information gathering, finding relevant sources of news and information for our market research and go-to-market activities, but will also be syndicating news there from our blog and the ecosystem to help contribute to the news and information.
We haven’t started using Discord, but a few of the standards we are tuning into have channels there, so we will likely be adopting alongside Slack to engage with the Naftiko community, but also using it to paraticipate and contribute to the wider ecosystem that operates there.
We have a profile available on DockerHub and will be publishing container images there when ready, using the marketplace in conjunction with GitHub to deliver artifacts that developers can download, fork, and use in their work, while also including in our go-to-market storytelling.
We have adopted EIN Presswire as our primary press release channel, establishing an account there and using to launch Naftiko. We will also be issuing a press release for any product or major capbilities release, using it as a standard format for announcing new significant work.
We are currently using G2 for information gathering and market research, but we will also start reporting more information as part of their formal processes once we have a couple releases under our belt, ensuring that our product is aligned, but also part of the G2 narrative.
We are only currently tuned into the Gartner ecosystem as part of our go-to-market, but once we have a product we will begin formally engaging with the Gartner ecosystem as a paid customer, but for now the Gartner reports play a strong role in the go-to-market storytelling.
GitHub is our primary artifact and source control community, telling stories via READMEs, and engaging with the ecosystem via issues and the discussion forum, making GitHub a primary channel for our go-to-market activities, which are primarily centered around capability repositories.
We are currently just using Hacker News for information gathering right now, but as we continue to build our profile and network there, we will begin sharing information from the ecosystem, and when we get confident enough we will begin publishing our own stories and conversations there.
LinkedIn provides the primary business profile for our go-to-market activities, tapping into the network of founders, but also working to build the presence of the Naftiko page, publishing regular posts and stories, and engaging with the ecosystem when it comes to capabilities.
We are using Medium as a secondary blog network, while also using it for information gathering as part of market research, but we will increasingly be publishing blog posts there that we first publish to the Naftiko blog, and then syndicate later to Medium for the network effect.
The Naftiko blog is the primary destination for stories and conversations, providing a regular and consistent cadence when it comes to storytelling across a variety of topics, but centered around capabilities, building traffic over time and using it as a center of other networks.
Right now we are primarily using Reddit for information gathering as part our market research and community building, but we will begin syndicating content from the ecosystem there, and eventually when we gain more confidence, begin publishing Naftiko stories there about capabilities.
We use Slack as the primary chat channel for Naftiko, and we are using it for coordinating with partners, but will also be opening it up to the community soon–when it makese sense, evaluating Slack alongside Discord, and possibly Microsoft Teams when it comes to community engagement.
We aren’t using Twitch right now, but have setup a profile there, and once we get traction with the Naftiko Capabilities podcast we will light up a channel at Twitch and stream regular updates there, or likely begin doing other live activities there that are part of go-to-market activities.
We are using the Visual Studio Marketplace for information gathering right now, learning from the service providers and the extensions they have published there, but when ready, we will be regularly using the marketplace as part our go-to-market along side GitHub and DockerHub.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.