15 Questions You Should Ask About Their API Before Selecting A Platform

A good friend and mentor wrote posed a question to me and I’d like to use my responses for this post. His questions were a little more focused on one industry (Email), so I’ve generalized my responses to all APIs. He asked what questions a company should ask a vendor about their API before making a selection. Why Do You Need APIs? An application programming interface (API) is the interface that a computer system, library,

The Web Development Triangle

All of our contracts with our clients are ongoing monthly engagements. Very rarely do we pursue a fixed project and almost never do we guarantee the timeline. That may sound scary to some but the issue is that the goal shouldn’t be the date of release, it should be the business results. Our job is to get our clients business results, not take shortcuts to make launch dates. As Healthcare.gov is learning, that’s a path

Content Variety and Formats Drive Results

Your audience varies. While you may appreciate a long-copy whitepaper, another prospect may simply want to review a feature list before they contact you for business. This great infographic from ContentPlus, a UK-based content marketing service, provides an overview of the variety of content offerings that exist, why they work, and some supporting data. They also have an accompanying blog post that ties it all together. Internet users have become sophisticated content consumers in recent

Dear Tech Marketers: Stop Marketing Features over Benefits

The last couple weeks, I’ve been slowly adding marketing tools to the new site. One of the overwhelming things that I’ve noticed is that technology companies love to market features and totally neglect to market benefits. Case in point is a comparison ofHootsuite versus CoTweet™: CoTweet’s marketing on their home page pushes the benefits of using the platform: CoTweet is a platform that helps companies reach and engage customers using Twitter. Monitor your brand –

Less = More

I’ve been wanting to follow up my Open = Growth post for a while. Described in that post is the likelihood of success when folks concentrate on how their solutions can be integrated with other solutions. There’s a flip side to this, and that’s for companies to limit the functionality of their solutions to the core of how they are used. Adding a plethora of products, services, and features can be dangerous. Programmers call it