(If you're interested to try it yourself, you can check it out here - https://sdk.livecycle.io/signup2 )
Suggestions welcome and appreciated... Thanks!!
In my opinion - I'm not so sure if the product should be marketed to "dev teams" per se! To me it looks like a collaboration tool around product development... not just for developers.
I would think the primary buyer would be PMs (Product / Project Managers) who would then push for the tool-use onto the dev teams as a way to improve collaboration and close the feedback-loop across all stakeholders (design, marketing etc). Yes, for that to be a success it requires devs to love it and indeed make thier job easier, but I don't think they're the primary buyers. Developers, in general, are notoriously hard to sell to because they filter out marketing jargon!
After that, make it super-simple to try out. The more friction, the less traction. Ironic, huh.
Where to pitch is the easy part. Getting the pitch right. Well, that's where things go wrong too often.
I'll have a look at a tool if:
1. What is does blows my mind and/or it think it might change the world.
2. I'm super curious about how it works (the technology behind the tool).
3. I think that today or sometime in the next 12 months the tool will help me get shit done.
For example, not one hour ago I was blown away by the potential of WasmEdge (https://news.ycombinator.com/item?id=33792322). Already downloaded it and run its Hello World program.
And FYI Vercel already offers built in commenting in the precise environments. I think it's in beta but we have it enabled on our preview deployments.
Like others have said, I'd suggest to polish the messages on the marketing site
What type(s) of dev teams? sales, marketing, etc. Ah, ok end of 2nd sentence -> developers.
Why would someone develop NEW SDK for a 80's c64 commodore for sale reps when current stuff is supported/understood by by both in-house IT, sales reps and management.
All of which wouldn't change the groups understanding of how to use the old SDK.
With extra resources on pi, would be able to port everything over to open source version of VMS & use non-monochromatic terminals! (perhaps even emulate the c64 under openvms and slowly roll out port behind scenes)
Given a stack of academic papers, what would the typical reader do if had a choice between a) read a paper & develop an introduction/abstract before deciding if paper is worth time to read or b)move on to paper(s) with introduction/abstract spend 0 time the paper without an abstract/introduction.
Someone with sales/marketing background (friend, google advice) would be aware of things such as https://www.questionpro.com/blog/beta-testing-community/
Recommended hire or see a consultant with suitable background, because then can assess if there are conflicts (aka competitor) with advice being given before potentially waisting time on a suggestion(s).
Yes, even if end product will be open source.