The Basement Like a blog, only interesting.


1
Mar/11
0

The Case for the $500 App

Last year I started a company that is developing iOS software for the architectural services industry. The price of our first app, Architactile Inception for iPad, is $499.99. This makes it one of the most expensive apps in Apple’s App Store. As you might imagine we get several comments about the price of Inception. While generally, the intended audience of the app (namely architects involved in business development) recognize the value Inception delivers, many folks can’t seem to get past the price. The suggestion seems to be that by virtue of running on an iPad, software has an upward limit in value. That somehow, no matter what utility is provided by an iPad app, it is simply inconceivable that it might be worth $500. So why then have we set the price of Inception so high?  Is it some sort of get-rich-quick scheme?  Are we trying to bilk our customers?  Quite to the contrary, we’re trying to do something important. We’re trying to improve the efficiency of the business of architecture.  And we’re trying to legitimize the iPad as a real business tool for architects. But to do that, a $500 price point for Inception is both necessary and justifiable. So before you make any snap judgements, please consider the case for the $500 app.

There’s a lot of talk about people using iPads at work, but the reality is there’s very little development going on for vertically-oriented point solution apps on the device. There are a few industry giants (Autodesk, SAP, Salesforce, Intuit, etc.) that are dabbling in app development, often publishing “free” apps that provide a mobile interface to their flagship products. And there’s lots of general purpose business software - voice recording, expense reports, time keeping, todo lists, notes, business card scanners etc. but when it comes to real application specific tasks, there’s not a lot of serious development.  So why is this?  There are lots of reasons. Many of which have to do with challenges to B-to-B business models when trying to provide software through Apple’s consumer centric iOS ecosystem such as fixed pricing and the lack of detailed customer information (Apple provides no more detail than the county in which an app is purchased to the developer - no name, contact information, etc.) But perhaps the biggest barrier to the success of B-to-B software for the iPad is the perception that apps should be cheap or free.

It’s ironic really, that Apple has simultaneously created the perception of a luxury brand and is able to fetch top dollar for it’s high design tablet, while simultaneously driving the perceived value of software targeted for the coveted device to almost nothing. The common perception is that “apps” are disposable and should be purchased on impulse, without thoughtful consideration. You don’t like that app? So what? It’s only 99 cents. For the consumer market this is quite brilliant. From the developer’s perspective, high quality, low cost applications with very limited utility or functionality can be produced and sold in large quantity to an audience conditioned to perpetuate the buy-use-delete disposable app cycle in an insatiable quest for the next Angry Birds. It’s a beautifully engineered system for all involved - the user, the developer and Apple.

This system works as well as it does for one reason: Apple has done an awesome job of creating a captive audience of massive scale. A well designed and marketed app selling for 99 cents can generate hundreds of thousands, or even millions of dollars in revenue for the developer.  Although blockbuster “hits” are hard to come by (and getting harder each day, especially for the small developer) even a part-time hobbyist can cobble something together that, priced at 99 cents, can pretty easily sell hundreds of copies.

But the model changes dramatically when the developer wants to target a narrowly focused vertical market. Instead of a market defined as “anyone with an iPad” it’s something smaller, perhaps much much smaller. In Architactile’s case, our market is “architects who are involved in business development who have, or are willing to buy,  iPads.” Furthermore, vertically oriented business apps typically require more functionality, domain specific knowledge, licensed 3rd party content, and so forth, not to mention customer training and support. From the developer’s standpoint this means higher development, maintenance and marketing costs, and smaller markets. For this type of model to be viable, the price for the app must be higher than that of less sophisticated apps with target markets of millions.

So what’s an app worth? The “value” of consumer apps designed for entertainment is subjective and intangible. Much of the value of consumer apps is derived from context. By setting the lowest non-free price of an app in the app store to 99 cents, Apple (perhaps unknowingly) set the de facto standard “value” for a typical iPhone app. The common consumer perception is that in order for an app to be “worth” more than 99 cents, it must be significantly better than the average app. “Better” again being subjective. For iPad the perceived value is slightly higher - I guess because the screen is bigger and bigger should cost more.

Unlike consumer targeted entertainment apps, business apps are different or at least (I argue) they should be.  With business applications a user should perform a cost-benefit analysis to determine the value of the app. For most business software there are both tangible and intangible benefits. Typically the tangible benefits (time savings, hard cost savings, etc.) should be able to provide a demonstrable cost benefit over the alternative solution in order to be selected.  Intangible benefits (perceived status, improved aesthetics, easier to use, more fun) are typically used to choose between multiple alternative with similar tangible benefits.

The great challenge with business oriented software for the iPad is that the users’ perception of the software’s value is largely based on the intangible context pricing of large market consumer apps instead of the actual cost-benefit provided to the business by the use of the app in practice.   This reasoning has resulted in criticism of high value yet moderately priced productivity software from great companies like The Omni Group who produce the $49.99 OmniGaffle for iPad which is often cited as one of the most expensive iPad apps.

It’s paradoxical that folks frequently argue that a $500-$830 piece of hardware is an essential, or even revolutionary business tool while simultaneously dismissing the validity of any software for the device priced at more than a few dollars. The reality is that, as a device, the iPad’s value to business is a function of what it can do for that business in terms of cost-benefit which is to say that iPad’s value to business is completely dependent on it’s software. The idea that the cost of iPad for use in business is justified before consideration of the nature and cost of the applications which will run on the device is sophomoric, unless of course browsing the web and playing Angry Birds at Starbucks alone is somehow sufficient justification.

Pricing is something we at Architactile take very seriously and we spent a lot of time considering it during the development of Inception (which sells for $499.99 in the iTunes App Store). We knew that the price would draw criticism, but at the same time we knew that in order to be viable as a business we needed to charge a significantly higher price than the typical iPad app because of our small target market. At the same time, we knew that we needed to provide a product that delivered benefit that far exceeds the purchase price if anyone was to buy it.

We spent a lot of time talking with architects and showing them early versions of the app to try to gauge value.  The general consensus is that for architects who are routinely involved in business development or other activities that involve developing high level scope and conceptual budgets for projects, that Inception will save several hours (at least 8 to 20 or more) on every project. At a cost of $500, most architects involved in business development that we talked with feel that Inception will pay for itself within the first 1 or 2 projects with measurable (tangible) time savings while providing the intangible benefits of producing higher quality deliverables for clients in less time than what they (and their competitors) are doing now.

We also spent a lot of time sizing the market. In the US, there are about 40,000 architectural services firms. About 80% of these are 10 employees or less. Half of all US firms report less than a millions dollars in annual revenue. In September and October we provided a free preview of Architactile in the App Store (called Architactile Lite) which was downloaded just shy of 3,000 times - about 1,200 of which were in the US market. Based on this information, our sales goals are in the low hundreds of copies per year.

Often when I tell people that we’re selling our iPad app for $500 they reply with some version of “I think you’d do better to lower the price to $50 or less and make up the difference in scale.” The problem with this approach is that, for us, the scale is simply not that big. Our total market is not millions, not even tens of thousands but more like a few thousand.

So let’s run the numbers. Let’s say that everyone in the US who downloaded the free app was willing to pay $50 for the non-free app. That’s 1,200 folks - a number that we consider ridiculously high when projecting our sales (at almost any price).

1,200 people x $50 / copy = $60,000 gross revenue.

Apple keeps 30% of this, or $20,000 leaving $40,000 net revenue.

Architactile Inception took 800-1,200 hours to develop. We’ll call it 800 to be generous.

$40,000 net revenue / 800 hours = $50/hour

First off, the going rate for an iOS developer is $75-125/hour. Secondly, this doesn’t include the marketing costs, equipment costs, 3rd party content licensing (parts of IBC 2009 for example), ongoing maintenance and updates, customer training and support, other operating expenses, etc. And keep in mind, this result is only if we could sell as many copies as we were able to give away for free in the US market - something that seems pretty unlikely.

The bottom line is “make it up in volume” strategies simply don’t work for point-solution, vertically oriented business applications on the iPad or any other platform when the target market is small.

The alternative is to set a fair cost based on the actual benefit of the app to the business, and aim to penetrate enough of the market to make the business viable. In the case of Inception we hope to sell 200 copies in the first year. The math looks something like this:

200 people x $500 /copy = $100,000.

Apple keeps 30% of this, or $30,000 leaving $70,000 net revenue.

Keep in mind that we’ve already invested about 1,000 hours in development. So even if we hit our targets, no one is getting rich quick - but it would allow us to expand and develop more applications for the iPad designed specifically for architects. We’re okay with this - we’re in it for the long haul.

So, how will architects perceive the value of iPad apps for their business? The jury is still out. But if architects (and other professionals) want to use their shiny slates for more than email, slide shows and PDFs, then they’ll need to measure the cost against benefit instead of Angry Birds. Otherwise, the market for industry specific B-to-B software for the iPad simply won’t be able to attract developers.

7
Jun/10
0

Architactile Named TESA Top 25 Finalist!

(cross posted from Architactile.com)

We're so proud to be named as one of top 25 finalist in the Tulsa Entrepreneurial Spirit Award for 2010. We've been working (mostly in stealth mode) for the last few months developing our first product, Architactile Inception for the iPad, which will hopefully be submitted (as a beta) to the Apple App store by the end of June. Here's an early look at Inception in action:

If you're interested in architecture applications for the iPad, please sign up on our mailing list and we'll keep you posted on our progress.

Congrats to the other 24 TESA finalists - especially my friends the Simpsons (@geoffreysimpson & @ShawnaSimpson) over at Moxie Software and John Fanning of Language Speak Easy. I wish you the best of luck... or at least the second best. ;)

6
Mar/10
2

Why iPad?

For those just tuning it, I'm starting a business developing software for the iPad. When I tell people that I'm targeting iPad I get mixed responses. Fanboys want to gush about how the iPad will forever change the destiny of man.  Critics want to talk about netbooks, iPad's missing features or the forthcoming Microsoft Courier.  Other folks want to describe an application that they've dreamed up that they think I should write (like I don't have anything else to work on) or people tell me that I should write software that can run on all the mobile devices iPhone, Android, Blackberry, Windows Mobile, Palm, etc. - you know, because cross platform development is easy.

What almost everyone has in common though is that most folks don't understand why I'm targeting iPad.

In fact, lots of folks make assumptions that are completely wrong. I'm not targeting iPad because it's cool (at least not entirely).  It's not a get-rich-quick scheme (although getting rich quick wouldn't suck). It's not riding the wave of hype surrounding the iPad (but I'm not ignoring this either). It's not (just) because I'm not a fan of Microsoft.

What you might find surprising is that I'm actually quite skeptical about iPad's success as Steve Jobs laid it out in his keynote. I don't think the iPad will be the ultimate internet browsing experience - I think that title will stay with our desktop and laptop computers. I think the absence of Flash and an (albeit large and responsive) touchscreen keyboard will substantially  hinder the web browsing experience. When we fantasize about being seen hanging out in the coffee shop with our shiny new iPad I think most people underestimate the predominance of text entry in the web browsing experience. The web browser, after all, was born on the desktop and is a desktop centric paradigm - it hasn't translated well to mobile devices, or television, or refrigerators.  Sure, some bookmarked content will be great on the iPad, but as an all purpose "ultimate internet browsing device" I think it will fall short.

And since the iPad won't fit in your pocket, you have to make a special effort you to take it with you. Once you've made the decision to lug along a device, the question is - What device will it be?  The somewhat limited but super sleek iPad or the truly versatile if not entirely aesthetically pleasing netbook or laptop?  The bottom line is that the iPad is not a netbook/laptop replacement (by Steve's own admission) and when given the choice between the two, most folks will pick the lappy. And if you already have a lappy, will you shell out another $500+ for an additional device?  I think most won't.

At this point folks ask me "Matt, if you think the iPad sucks, then why are you building a business around it?"  The answer is that I don't think the iPad sucks - rather I think it will be really, really good at something other than the perceived primary use case - namely point solution business applications. As I see the world I think there are hundreds of applications where laptops or other traditional computer forms are simply too cumbersome for business applications but where a well designed touch computing platform can excel. Anywhere where someone is carrying around a clipboard with forms or check lists, anywhere people are dealing with non-text data in a mobile environment, anywhere where a conversation is happening where a traditional computer would be distracting is an opportunity for touch computing.

Sure, there have been mobile computing platforms out there for decades from people like Microsoft, Symbol, Intermec, and Psion - but these platforms have been too expensive for smaller point solutions, too cumbersome in terms of UI/UX and too difficult to develop for. Historically there's also been a lack of easy to understand, reasonably priced and ubiquitous wireless connectivity for these devices.

The focus has been on "mobile computing" and not on "touch computing".  What's the difference?  Mobile computing is about trading usability and performance for mobility.  Touch computing is about a fundamentally different user experience - a user experience that's better that the previous paradigms.  Sure touch computing platforms like the iPad will also be mobile, but if designed well users will prefer using their touch computing device for some activities even when sitting at their desktop computer.

The opportunity is to recognize the applications that have been underserved by traditional computing, or mobile computing and exploit then with well designed touch computing interfaces. The secret to success for these touch computing applications is great design from which follows great usability and user experience. Applications designs must minimize required text entry, and rely more heavily on information visualization, and visual metaphors for data manipulation.

To do this effectively designers and developers need a great development platform, a stable and consistent hardware platform, and consistent user interface metaphors.  For wide spread market adoption we need a hardware vendor that is familiar and credible for end users, that has a good track record of being able to keep up with supply and support. The user experience is critical - so we need the most responsive touch interfaces with support for multitouch and advanced gestures.  And we need well established distribution channels for easy deployment.

Over the next year or so we'll see dozens of touch computing platforms enter the market. Some with price points way below the Apple iPad. When I survey the landscape I see only one platform, vendor and ecosystem that already exhibits all of the characteristics necessary to succeed with business focussed touch computing applications: the Apple iPad.

With our new business venture, Architactile, we hope to change the way the business of architecture is practiced through the application of touch computing. At least for now, the iPad provides us our best shot at doing it.

3
Mar/10
4

Architactile Cometh

My life has changed a lot in the last few months. Most folks that know me through the internet have no idea what I do professionally. Lots of folks think I'm somehow involved in marketing, public relations, social media consulting, etc. (I'm not.) This is partly by my own design. Both when I started blogging in 2005, and when I started playing on Twitter in 2008 I was at least partially motivated by professional dissatisfaction or boredom. Social Media was an outlet for me to explore and exercise the critical thinking skills that were atrophying at work. I've been careful to not intertwine my professional and online life too much - it just seemed simpler.

So what do I do professionally?  Well, I have a BS degree in Electrical and Computer Engineering from Oklahoma State University although my career is more accurately described as information technology. Thirteen years ago I became the Director of Technology for a small company called ODEN Insurance Services in Tulsa, Oklahoma. I had done some contract programming for ODEN a few years before that. ODEN had about 10 employees when I joined as a full-timer. In retrospect, what we did was pretty remarkable - we changed the way the property & casualty insurance industry works in the United States - at least in some small way.  Our organization researched insurance compliance law, summarized it into a standardized taxonomy and made it readily accessible to insurance professionals. This content was deliver 100% electronically - never on paper (which was revolutionary 13 years ago in the insurance industry.)  We then took this information and built a rules based document composition system that automated the process of creating termination notices to the insured. If you've ever had you car or home owners insurance policy cancelled, there's a better chance that it came from software that I managed than not.  While this may not seem like much, ODEN changed the way the insurance industry thought about cancellation and non-renewal of policies - and trust me, that's huge.

Over the years I was promoted to Vice President of Technology and eventually was given the opportunity to become an equity partner. The job was great for a good many years and the owners of the company, the Oden family, were tremendously generous to me and our entire staff. But the company reached a point where it was unlikely to ever grow significantly larger, unlikely to reach the proverbial "next level".  This is a limitation of many family owner businesses. I found myself with "golden handcuffs" - with an equity position in company and an easy job that had likely reached its pinnacle. This was great for my family but for a guy who likes challenge and change and was less than halfway through his working years this began to wear on me.

Then 3 years ago, our small company of 30 employees was bought by what is now the global behemoth Thomson Reuters. This was a terrific way for the Oden family to exit after nearly 20 years of building the company.  I stayed on after the acquisition. It was an exciting time and I imagined that great things that were possible.  Although, at the time I realized that the likely eventual outcome would be the elimination of the positions of me and my technology staff, I was hopeful that things might be different. I knew that if our products were to get to the "next level" it would be through a company like Thomson Reuters. I also knew that if things didn't work out that I'd finally be done, free to do... something else... anything else.

For the first year and a half or so after the acquisition I worked hard to try to find a niche for our products within our new parent company. Unfortunately after going through 3 Vice Presidents (one holding the position twice) in less than 2.5 years it was made pretty clear to me that there was to be no real future for me or my staff at Thomson Reuters. The week before Thanksgiving 2009, my boss called to inform me that my staff and I were being let go in a "reduction of force" and that our job functions would be transferred to the home office in Eagan, Minnesota. My last day with Thomson Reuters was last Friday, February 26, 2010.  This ended my 13 year association with Oden products.

Thirteen, it turns out, is my lucky number. A 13th of the month marks the births of three of my four children, as well as the anniversary of my marriage to my amazing wife of 6 years. It's only fitting that my run at Oden ends after 13 years so that I may start the next stage of my career.

Oden taught me that I love the excitement of growing a company and that a company needs strategic focus and growth to be vibrant. Thomson Reuters taught me that big companies can be insanely profitable even if they are slow and stupid... and that I really, really don't like slow and stupid. When thinking about what's next for me, I came to the realization that I don't really like working for people, but I love to work with people. I love building new products and processes and I love solving problems - I love creating efficiency. I really despise sameness on a daily basis, and I really like change and challenge.

So after some serious soul searching I've decided (with the support of my wife and family, and perhaps more importantly Bill & Shelli Handy) that the time has come for me to create my own company. I've partnered with an old friend named Taylor King who is an architect and partner at TriArch, an architecture firm in Tulsa.  Taylor and I collaborated on some iPhone apps in late 2008 (published in the iTunes Store under the name Armchair Design) and we're ready to take it to the next level. We're currently working on a product concept for the iPad that we hope will change the way the business of architecture is practiced... at least in some small way. We think that touch computing has huge potential in point solution business applications and we want to explore that idea for architects.

There's lots and lots to do before I can share too many details but stay tuned...things are about to get interesting.

So what's the name of our new venture? Architactile. What else.