Skip to main content

Collecting Logos vs Productive Partnerships

[No update on yesterday's post]

The early days of ChiliSoft were the early days of they dynamic web, and the very, very early days of corporate adoption of web technologies. 

We had little credibility, which made it difficult to sell our first product, ChiliReports, which was the first web component to write data from a database to an excel spreadsheet in real time, pre-formatted to your liking. 

Geoffrey Moore was right in "Crossing the Chasm"; the mainstream buyers need to see other mainstream buyers endorsing and buying your product before they will, which raises the question: how do you get your first "mainstream" buyers?

At the time, it was impressive to people if you had a partnership with a major tech company.  The major tech companies had either no, few, or incomplete internet technology stories, so we were able to garner early press and get some attention from the majors at the time like IBM, Microsoft, and DEC. 

I did a lot of logo collecting, trying to establish "partnerships" with as many major companies as possible. A "partnership" was basically a joint press release that lauded each other's contributions to whatever, with no real specifics, and a light agreement to publish each other's logos on each other's sites. 

And that helped with the credibility issue a bit. Winning Best of PC EXPO in the developer tools category helped a lot more, and garnered a ton of positive press. 

The press was always looking for reference customers, and we had some early adopter fans who would sing our praises; those early adopters worked for mainstream companies, so it was a huge boost when Bill from AT&T said we had promising stuff.

But the logo collection wasn't what I'd call productive partnerships. A productive partnership is one where you work together toward common or mutually beneficial goals and achieve those goals. 

Your goal might be increasing your customer base by 10%. Theirs might be to provide an answer to customer questions, like, at the time, "How do I get data over the web in something other than a static HTML page?" Microsoft pointed customers to us at the time because they had no viable solution, and it kept their cutting edge customers happy for a time. 

My point is this: you can spend your time collecting logos so people think you're a going concern; endorsements from major companies can help make you look better and bigger than you really are, and that provides some comfort to potential buyers. 

But I'd focus on the productive partnership, where you know specifically what the deliverable is, the goals are, and the expected outcome is. A distribution partnership with a revenue share makes sense to me. Exchanging logos and press releases really doesn't. 

I'd limit the number of productive partnerships to 2 or 3, unless it's clear that you'll get either linear or exponential growth as a result. And I'd be very, very careful about which companies to partner with;  large companies can be a bitch to work with. ATT took 3 years to close. 

IBM paid $3 million for the port of ChiliSoft ASP to RS6000 and S/390, but it took years and a huge amount of effort that should have been focused on building our core markets. (IBM was not a player at all in the late 90's and tried to buy its way around its cultural swamp) .

Neither of those deals was worth it.

It's much more important to focus on getting early customers who can serve as reference accounts for the press and other customers. 

If you aren't profitable yet, no partnership is likely to get you there, and it will drain your time, energy, and focus that would be much better directed toward serving your customers. 


Popular posts from this blog

Beta Signup

I've been working for quite a while on a new search concept, though the further in I get, the closer the rest of the world gets to what we're doing. So today I'm inviting you to sign up for the rather modest beta, which will be ready soon if we can nail down a few difficult  details. Jawaya is a way of navigating the web and getting better results. And that's as much as I can say right now, because we're not a funded startup, and things are moving really fast in this space--it's going to be very competitive. I predict there will be about 10 funded startups in the next 6 months doing something similar. One of them will be mine, and we aim to make it the best. We're raising a round of capital to fund the team, and are shooting for early sustainability. This is my fifth company; my fourth in the tech space, and my third software company. I think it will be the biggest and can possibly have a positive impact on the world by reducing the amount of time it takes

Where Innovation Happens

As I get closer to a go/no-go decision on a project, I've been thinking about the difference about my vision for the project and the supportive innovations to enable the core innovations The vision combines (in unequal parts) product, core innovation as I imagine it, the application of that core innovation, design, marketing,  developer ecosystem, and business development. The core innovation enables everything else, but it's the application of the innovation that makes it meaningful, useful, and in this case, fun. This week we're testing initial approaches to the implementation for our specific application, and that's where we'll develop the enabling innovations, which is basically where the rubber meets the road. The difference is that the enabling innovation happens at the source of real problems only encountered in the making of something, and in a project like this just getting the essence of it right isn't enough; it also has to be safe, the compone

The Real Jobs Problem

It's the economy, stupid.  Well, yes, it always has been, if you're in the distortion field of politics.  But whose economy? The pundits, the White House, the Republican candidates all miss the mark. They keep talking about debt, taxes, and monetary policy. None of those things tell the real story behind today's economy.  The Old Economy Keynes was right--in the old economy. Economy gets weak, pump some money into the economy through public works projects, which  1) puts people to work, which  2) boosts the economy and  3) generates new tax revenue, while  4) leaving us with another generation of reliable infrastructure to support  5) more growth (for growth's sake, which is another post).  The Beach Ball Imagine a beach ball, partially deflated to represent a recession. Got it? Now imagine the govt pumping that beach ball back up through sensible public investment (which we haven't seen for decades). The New Economy Same beach ball, same pum