TechFold - Bold tech & web commentary

5 Suggestions to make Teqlo a Survivor

Teqlo is a company that needs to find a strategy and a community - or it will at best languish in obscurity. Like Ning in its prior incarnation or Yahoo! Pipes, Teqlo aims to turn the average Jane or Joe into a developer - “A Mashup Platform for Everyone Else!” Teqlo’s everyone-friendly platform consists of an often confusing UI that allows you to link a limited selection of widgets together via a limited set of interactions to create an application which you can then run in your Teqlo account.

What Teqlo has missed are the same two points that drove Ning’s recent self-reinvention as a canned social network host, and what will keep Yahoo! Pipes a curiosity:

Conjecture #1: There’s a big difference between those who would create something new, and those who wish someone else would create it.

Conjecture #2: Those motivated enough to create something don’t need an “everyman” platform in which to do it.

Human nature is a pain in the ass when it contradicts an idea that sounds golden on paper. Teqlo’s stated target market is the very small slice that includes those with motivation but without a traditional web skill set - an awkward, small middle ground between the masses and the technically competent.

If you recall, Ning had a gruesome, flat-growth year trying to grab this market before they switched value propositions and streamlined their business model. Teqlo is heading for the same place.

Teqlo need not end up as an eBay firesale, however. IMHO, their challenge is the same as Ning’s: market segment identification. Teqlo has a unique and valuable infrastructure that should be tailored to increase acceptance in a few key, revenue driving segments.

To get there, Teqlo needs to open up their platform, and segment their marketing:

1. Make the “everyman” platform part of a larger segmentation strategy, and focus on the “motivated people” and find ways to make their work easier. Ning has targeted a single segment in their relaunch - social networkers; in doing so they’ve gotten out of the tiny slice left by conjectures one and two above.
2. Publish a widget spec so that the Teqlo community isn’t dependent on Teqlo for functionality. If WordPress can do it, you can too. Keep all of the widgets GPL’d too to spur community development. See what widgets are developed and let this inform your strategy. Support the widget community like Ballmer supports developers.
3. Enable external publishing of applications. If the functionality is there, enable it already, see how its used, and let that usage inform your strategy.
4. Clean up the vocabulary. Are they “Teqlets” or “Widgets?” What’s a “teqlet” anyway? Is a “PowerPack” like a template, or something else entirely? The mishmash of un-words makes the creation process difficult to parse out conceptually.
5. Aesthetics of the process: Implement a cleaner UI on the application builder. Again, IMHO WordPress sets the benchmark with their easy handling of plugins, themes, and widgets.

That’s it in a nutshell. Teqlo no-doubt has great value tied up in their plumbing, but without a strategy (other than “build it and hope they come”) informing its deployment and a community contributing to the project (as opposed to just using it), its going to fizzle away.

api, ning, pipes, techfold, teqlo widgets

Share This

If you enjoyed this post, make sure you subscribe to my RSS feed!