Maybe you misspoke here, but based on this quote I think your approach could be improved.
1) You went to a friend. Unless this person is an experienced designer of commercial websites, that doesn't sound like the right approach.
2) Your primary concern is preserving the site's "geeky/minimalist character", although that seems to be your Achilles heel. The last time Tarsnap was on news.yc, I made the same incorrect assumption, that this was not really a business, but just a side project of an academic. You and I even talked about that in the comments.
3) You're framing the problem as aesthetics, but it's really about poor communication. Engineers often make the mistake of thinking that visual design = making something look nice. This is like saying a database designer makes data nice.
Just like a database designer sees important patterns to capture, a great producer or designer understands how to drive website visitors to the right understandings and behaviours.
It sounds to me that if you go down the route you descirbe, you'll have all the pain of redoing the site, without solving the more fundamental problems.
I went to a talented web designer who understands my vision. I think understanding my vision is important -- otherwise I'm likely to pay $$$ only to be presented with a website which I hate and don't want to use.
I mean, if you're interested in pageviews, and revenue--and your comments wrt Balsamiq seem to indicate you are--you need to realize that the aesthetic you're looking for is likely costing you customers and hence money.
Nobody's going to fault you if you prefer to make less money and keep your website any way you want, but if you're going to complain about sluggish growth you've gotta realize that your customers' habits and tastes are much more important than your own.
In related news, the demographic you seem to be targeting is quite possibly either unwilling or unable to pay for it; the former because they'd rather hack something up on their own and the latter because they may not be the decision maker for their organization.
Think of it like the crackpots who submit their own math/physics theories. Sure, a professor can critically examine every submission, but it's not a good use of their time. It's easier to just read results in refereed journals.
If someone eccentric is doing something truly groundbreaking (Perelman solving the poincare conjecture), then most people expect somebody to tell them about it. Craigslist is like this -- if you saw the same layout on bobslist.com, you'd know it was some rinky-dink site. But craigslist built a reputation and that reputation is what made it spread.
Unsolicited advice, but long story short: people make snap judgements to save time, and often times they are correct (I suspect most unprofessional-looking sites are not run by professionals in that domain). This can be overcome with word of mouth, but it's ideal to not have to "overcome" their initial snap judgement and make a good first impression.
I mean, keep the existing website. And create a second one, using more traditional modern UX techniques. In my perfect fantasy here, this new one would be the .com and your current site would be the .net. That's likely not possible so you may need to find a variation of the domain or, hell, a completely new name for this "non geek" version. After all, "tar" doesn't have any meaning to the non-geek IT Biz Mgr anyway. Being sticky isn't a horrible visual for a backup service, but it's nothing special.
I'm dead serious, here. You have a vision. This is your vision. It's apparently not being successful in the marketplace. So why not just say, "hey, maybe I'm wrong" and go for an approach nearly 100% opposite of your current strategy?
But unless your customer demographics are vastly different than those of many of the people here who earn good money with proven UI techniques, I'd bet you could do better with different marketing (website, etc.). But you don't really have to bet. What'll it cost you, 10 bucks for a domain name and some time? The first rounds don't really even need a designer, though you'll save some time if you procure one now instead of later.
Test, test, test. There are a good number of qualified people (not me) that are giving good advice, but your test results are king. Start running variations, and you and HN can look at the data and start making progress.
Tarsnap has one of the technically best back-end implementations available, but the barrier to entry for an interested customer is incredibly high -- not just on OS X, but on UNIX as well.
Even on UNIX, producing a working backup setup requires writing custom scripts to do so, and implementing anything like snapshot-based backups is complicated enough that even I spent a couple hours getting everything working/tested, and I'm very familiar with this area.
I'll be bold: You solved the backup problem, now the number one hinderance to your growth is solving the user experience problem.
The UNIX utility should have an exceptionally easy way to configure backup schedules. Possibly even an optional web UI.
A Mac release must have a native OS X GUI (no qt!), be easy to use/configure, and be well-integrated into system services.
After the first iteration on the above you should consider implementing support for network-based backup administration, so that we can control backups/restores across all of our desktop/server installations from a centralized administration console.
If the above is not your forte -- if you're only interested in the crypto and backup issues -- then you need to find a parter or contractor who can step in and solve them for you.
I agree 100% -- and this was exactly my intention. I wanted to make sure that I had a solid backup system in place before I made it easy to use, because I hear far too many nightmare stories about backup software which is the opposite way around -- easy to use, but doesn't actually work.
A GUI will happen. Sample cron jobs for automating backups will happen. A web interface... well, that might happen, but really it needs to be built in to something like virtualmin.
That might be part of the problem as Davidw is hinting at.
Linux, BSD, Solaris, OS X, and Cygwin. Probably other UNIXy OSes too, but I don't know anyone using AIX or Tru64.
Tarsnap doesn't support Windows (except via a POSIX layer like Cygwin) or GNU Hurd.
EDIT: Ok, finished thinking. Let's see how much traffic $20 gets me.
Experiment day is Thursday, so I'll probably have useful numbers early next week.
Promoting Tarsnap as a solution for OS X runs into the GUI problem: Most OS X users don't have a clue what to do with a command-line interface. Tarsnap will gain a GUI at some point in the future, but of course this is a rather non-trivial amount of code to write...