Marketing Software, For People Who Would Rather Be Building It
kalzumeus.com
kalzumeus.com
Feel free to ask questions if you have them.
By the by, I also think that a lot of what you suggest for direct response marketing also has branding effects - just think about educating people by email for free - so the two things aren't necessarily in contrast. And I don't think that there would be much to debate about the value of your personal brand here (meaning no offence - if you don't like the word brand, just substitute "reputation" to it!).
I've heard Rob Walling recommend this approach on his podcast, and noticed you do it for AR, but I've never seen you write about it. I would love to hear just a little more about it and any A/B data you've collected on it.
On the one hand it obviously decreases the number of users passing through the sign up stage of the funnel, but on the other hand it's obvious that the customers who do sign up convert a lot more.
Thanks!
For many of you, assistance directly from the CEO in integration is a really
compelling offer, because wow, you can’t get that anywhere else. [...]
We’ll do the copy‑pasting for you ... and it will actually be done by a freelancer
that we’ve hired and told them how to FTP stuff.
On a side note, if your Vimeo account is Pro/Plus, please check the 'make accessible for mobile devices' option in account settings.
Any other good conferences like this one? From what I can see, this is all content and zero fluff, not cheap but not outrageously expensive either. I'm more than ready and willing to book even if it's a few hours from now for something like this. Share your thoughts, guys!
To explain in my eyes, I see marketing as everything you do to promote your project (i.e. brand/product/etc.), which may not always have a direct financial payout tied to it. For instance, FOSS projects have their own motivations for gaining usage and popularity, and revenue may be tied to that, but they're not explicitly selling anything. But, they do wish to get noticed, to have people try them out, etc. and so they are selling the idea of their project even though they're not actually ringing anything up at the register.
On the other hand, "sales" is much more closely coupled with driving a user to purchase (or maybe even just 'sign-up' for) your service or product. This is what I'm mostly seeing in the slides: pricing, email campaigns, conversion rates, etc. These are all pretty exclusive to making a sale, and while they do embody marketing concepts, there's a lot more to marketing than simply corralling the customer to the register.
Why am I droning on about this? I'll admit that it's for selfish reasons; I was hoping to see some marketing guidance for the page itself. I review lots of projects, and a majority of them that are created by engineers fall into one of the following buckets:
* zero marketing whatsoever, possibly only a github page with a couple sentences in a readme
* poorly-constructed marketing, such as using lots of buzzwords and generic phrases without actually telling me anything at all about what the project actually is or does; for instance, many times the only blurb given is akin to "cures what ails you"
Now there are some that get it right, though I suspect that many of these either have someone with marketing skills on the team, or they've had an actual marketing guru help them out. That, or they're generally really observant and pick-up on it without having to study.
Either way, when I review a project, it's a shame that the basics are so often neglected:
* problem definition: in explicit terms, what problem(s) does your project solve?
* product differentiation: if yours is "the best", "an alternative", "the new way", etc., then why do you think that? Why should I choose yours over X? If you can provide some concrete examples here, all the better.
* product demo: if it can be demo'd, then please at least create a simple working demo. Note: I don't consider projects that include demos as a part of the source code, which must be downloaded, built, and configured as a proper demo. I also don't consider any that require you to register or provide an email address as a proper demo, either. Unless it's a very pressing need that I have, I'm not going to spend 5-15m fiddling with your source or giving away my info. Just host it somewhere so that I -- and possibly my CTO/CEO/purchasing agent -- can see it in action.
* licensing, terms and conditions, etc.: make them prominent enough that I don't need to browse your source files or open a support request to find out if I can even use it.
Sorry, this got longer than I anticipated...
* a simple, non-distracting design
* text is easy to read and there's no feel of keyword stuffing or buzzword bingo
* you define the problem and offer product differentiation both in the first 2 sentences (can't get much better than that IMO)
* you have both an "about" and a FAQ
* terms are easy to find
The main thing I'm seeing that you're missing are more of what the OP talks about, in the sense that the 'call to action' seems weak. There's the "for developers" part, though nothing for the "for users". If I understand correctly, perhaps you could link to /browse for the users? Or conversely, if the "for developers" is the meat & bones and there really isn't too much for users, I might suggest making the "for devs" a little more prominent and the "for users" a little less prominent -- such as placing devs above users or something... not sure, but it does seem that your site has a strong opening and good content, but is lacking somewhat in guiding users what to do next. For instance, I'll keep it in mind incase a need for something like this ever makes itself apparent, though if it a list of projects involved and recognized one I use, I might dig in further to see if I wanted to pledge (I do realize this could be the chicken & egg problem if it's a new site).
Users will normally enter the site through a link given them by a developer, that will take them to one of the developer's proposals; that's where their call to action should be, I think. (There is one, but it needs to be more prominent and a little easier to use.)
But I have a more fundamental problem: I have yet to find any developers who actually want to use this thing. I mean, any at all. Admittedly, I haven't been looking much yet outside my own circles, which are fairly small. But it seems at first glance that there aren't that many OSS developers who are even interested in being paid for their work. It appears that a fairly focused search is going to be necessary to find the ones who are.
So what I wanted to ask you is this: in your reviews of OSS projects, what fraction would you say evince a reasonable degree of marketing savvy? Would you be comfortable sharing any names of those who do? My thinking here is that those who actually think about their project as a product, to some extent, are likelier candidates to be interested in my site.
Any general observations you might have about OSS developer psychology would also be of interest.
* Product management: the feature/function/benefit of the product and (most important function in all of marketing) pricing/packaging.
* Marketing communications (marcom): what you've defined "marketing" as: promotion, promotional writing. Also, advertising.
* Sales support: awareness campaigns and events and, particularly, lead-gen. This is what the CEO see as the most important function of "marketing".
* PR/AR: relationship management with publications and analysts.
EDIT: Anyone else that would consider themselves to be the equivalent of a (to use a very-much cliched term) rock-star hacker in the field of sales, PR, or marketing: please drop me an email!
(Or at least post your process for coming up with them.) I think bitcoin might be another technology that makes big "ripples", no?
Think of a business. Think of any phone call, incoming or outgoing, which is sufficiently standardized that you could teach any college graduate to execute that. That person can be replaced with a Twilio script, at a fraction of the cost.
My wife is sleeping in the room with my business notebooks so I'll hold off on finding and scanning it for the moment, but it was literally as simple as a) write down business, b) write down the calls they make, c) star the ones that sound like money.
I think bitcoin might be another technology that makes big "ripples", no?
We will have to agree to disagree on that one. Bitcoin's core innovation is the distributed self-organizing boiler room. As a transaction processing system it's technically innovative but wildly inferior to legacy payments for transactions which need to touch the real world. (It's interesting for transactions which don't, but could be replaced with a SQL update statement, which would improve upon it in virtually every way.) As a currency/commodity, the arguments in favor of it having a sustainable value north of zero are not credible to me. The main reason I have not nailed an 8,000 word stake in its rotten heart is that I think there's a non-zero risk that people will use every additional quantum of attention given to it as a reason to convince other people to "invest."
That being said, I just got a US phone number and I get at least 3-4 calls a week for the previous owner of my phone number. Those calls seem to be revolving around credit loans that she had.
To me it seems as if they try to remind her that she should pay those loans back. One could pretty easily build a really annoying twilio-based version of those phone calls...
Giving them ways to pad their budget was also an eye opener for me. The idea that they might not even be conforming to our rational actor model of balancing cost and value opens up new pricing considerations. I wonder if a monthly 'flex' option where they can temporarily boost their budget to some ridiculous figure would work. The engineer in me does cringe at the thought of it though
- SAAS Pricing when marginal costs are fairly high. For example, how would you price a service that offered human translation of a company's social media posts into N different languages?
- Accounting / corporate structure for bootstrapped SAAS companies: do you use an LLC, and if so things to take into account for cash vs accrual accounting, pass-through vs. corporate taxation, guaranteed payments vs. distributions, finding a good accountant, etc.
- The 8,000 word "stake through Bitcoin's heart", or at least the part that talks about how and why banks are going to stop taking Bitcoin exchanges as clients. There is a surprising amount of doublethink going on to allow people simultaneously believe "Bitcoin and traditional banking are natural enemies", "at least one Bitcoin exchange will always be able to access the banking system", and "the nominal price of Bitcoins can only increase in the long run."
My accountant, Cameron Keng, is giving an attendee talk on this very topic at Microconf this year. I'm going to be taking notes. (The cheapest advice from him I'll get this year, for certain. ;) ) Remind me to post them if he doesn't.
Noted on the other two suggestions.
How to convince them to use your off-the-shelf product instead of demanding a bespoke solution that requires you to essentially fork your entire code base.