Archive for April, 2010

I left my heart in San Francisco

Posted on April 27th, 2010 in Page.ly News, WordPress | 5 Comments »

Holy WordPress Batman!

We are pretty stoked to head out to SF this weekend for the 2010 WordCamp in San Francisco. Our folks on the inside tell us this is the WordCamp of the year.  Page.ly is proud to be a sponsor of what is shaping up to be a pretty awesome event. Our hosts for the event, Automattic are of course the folks behind the great WordPress.com service and their leader Matt, kinda invented the WordPress software we use here on page.ly.

We picked up a few extra tickets for the event and ran a little contest to give them away, so congratulate the winners if you meet them.  We look forward to seeing old friends and meeting new ones. Please please please make an effort to come meet us. We really want to get to know our customers and fans, and yes even our frenemies.

See you there!

PS: We will have a very (I mean very) limited number of the ultra soft and rare page.ly T’shirts on hand, come say ‘Hi’ and hit us up for one.

Update coming, WordPress 3.0

Posted on April 26th, 2010 in Page.ly News, Page.ly Service Updates, WordPress | Comments Off

WordPress 3.0 will be released very soon as the core team is working on the final details.

Page.ly will auto-upgrade all customer accounts shortly after. Likely 1-2 weeks after the official release. We wait to push big upgrades like this for 2 reasons:

  1. To allow more time for plugin developers to update their plugins which limits breakage
  2. The pattern of past releases shows there is typically a .1 (like 3.1) release shortly after a major release to address any last minute issues.

We would like to allow some time until the .1 release to further ensure a smooth upgrade for all customers.  If no .1 release is forthcoming after a week or two we will go ahead and push the 3.0.

Customers may update their own site at any time by using the built in WordPress updater.

Our Upgrade Procedure:

All customers will be notified by email, and this blog before an upgrade. The upgrade should be transparent to customers as were all the past upgrades. We will push the upgrade late at night and then test the sites to make sure everything seems to be working. When you login next you will see a “WordPress Database Update” screen where you simply need to confirm yes on.

If for any reason there is a problem that we do not detect first (likely caused by an outdated plugin) you may use our Whitescreen Eliminator to disable all plugins or request a roll back of your site to a previous backup. We maintain 7 days worth of live backups we can restore immediately, and older backups we will access if needed.

A reminder:

Page.ly will not support the MultiSite option in 3.0 on our base ($14.98/mo) service. If you require MU/MultiSite please look into our Enterprise plans.

Specific notes about 3.0 and the page.ly MultiSite policy can be found here.

WordPress for Real Estate by page.ly

Posted on April 20th, 2010 in Page.ly News, Page.ly Service Updates | 3 Comments »

In Real Estate?

Heard about WordPress or currently use it?

Need a great website you can maintain yourself that includes MLS/IDX data, property search, lead capture, school and neighborhood data, excellent design, social media integration, SEO, and a blog to boot?

Coming this Summer… a complete website and blogging solution for Real Estate Agents and Brokers.

Powered by WordPress, Brought to you by page.ly. Register to be notified when we launch.

Real Estate Websites

The Cost of Support

Posted on April 15th, 2010 in On Business | 6 Comments »

This is in no way a rant. I/We love our customers to death and pride ourselves in taking great care of them. ++extra mile

So with any SaaS type of business your users will need support. They will have questions about your service, or issues that come up where something breaks, or does not function as expected. Sometimes the issue is related to your product or code, like a software bug and sometimes the issue is user error. And one could argue that a case of user error is actually a defect in your product in that for some reason something was unclear or not obvious.  Example: You cant blame the user if that setting config menu item was 4 clicks deep and then required that something in another menu 2 screens over was activated first for your buried menu to even function.

Dumb stock photo metaphor

There are bookshelves of studies and reports I am sure on how to make your support system efficient and limit time per call, and incidents per account. I have not read any of them.

But I have come to learn this: Providing support costs money. Not providing support costs money. Providing half assed support costs money, and providing great support.. or even better; eliminating the need for support costs less money and can even make you money.

Lets explore:

There is one rather large internet company I know of that treats support as a sales channel. Grandma calls support for issue x, and gets sold z,q, and p upgrades that really, don’t help grandma.  Support staff there appear to act as semi-trained sales staff that are incentivized with bonuses and perks to keep call time to a min., and upsells to a maximum. On the surface looks like a win for megacorp. Not so much for grandma.

flipside…

There is another company I know of that also sees support as a sales channel, but does so from the place of a happy customer is a repeat customer that recommends new customers. They don’t upsell you (unless it is most appropriate; like a limit ceiling you have reached on your account) and then of course just mention it as possible option. The owner once told me his support system is his largest source of new/repeat customers. Seems like a win for the company, and a win for the user.

Support still costs money

Indeed it does. Take a low dollar hosting outfit customer at like $4.95/mo.. that is a ~$60/yr gross income account. Whittle that down after cost of providing said service and then figure each customer may have 3 support incidents a year. Figure a support incident may include some email exchanges, a live chat, maybe even a phone call. Pay the light bill and the support teams’ salary.. etc. A heavy support user would burn away all profit for their account in no time. Sales volume makes up for it but you get the idea.

How I see it

So I think like the company in our second example. Provide stellar support and reap the rewards of referrals and repeat business. I also proactively look for ways to improve the product to minimize support and find ways to automate support tasks. Our WhiteScreen eliminator is a good example of this automation. I noticed support volume on the same issue, so we built a self-service system to handle it. Even better would be to prevent the issues all together.. something I trust the WordPress Core team is working on feverishly.

I would like to think of our support as a long-tail profit center, as in time we will reduce overall support requests relative to customer volume by improving the system, but also just by going the extra mile for our customers and keeping the upsells to a min. will yield more repeat customers and referrals over the duration.

Conclusion

Support is part of business. Do it well and prosper, or don’t and piss off your customers and tank your brand.

How Secure is your WordPress Site?

Posted on April 13th, 2010 in Page.ly News, Page.ly Service Updates | Comments Off

Recently we moved from our old provider to the ultra secured hosting environment at Firehost.com. Besides the fact we were growing so fast that our old iron could not keep up, we specifically chose our new provider for their reputation for security. They secure us, we secure you.. it’s like our own private party inside Fort Knox.

Firehost security boss says: You on the list?

All servers that host websites are subject to being pummeled by malicious bots looking for vulnerabilities. The trick is to stay ahead of the malicious attempts. FireHost specializes in secure environments. We like to think that we are very proactive in regards to your security and will go above and beyond to ensure the health of your site. Thanks to our growth and the fine people of FireHost we were able to extend the best secure servers on the market today to our clients.

This graph below was taken from our weekly security report (you know how the President gets a daily security briefing by his Generals and the CIA, it’s kinda like that) and illustrates the events logged and blocked by just 1 (of the many) security layers on just 1 network node, in just 1 day. Over 30,000 nefarious events stopped before they even started.

Just think about if your site is not protected like ours, and then do something about it. Of course we recommend you give us a try, but you may also read up on best practices below. And for all that is holy, use a strong password. It all starts with a password.