By Ka Wai Cheung,
We Are Mammoth

I work at a small web shop. We do work for clients. Six guys in a wide-open room building microsites, web sites, and rich applications for big agencies and startup clients.

We’re also a small ISV. We’ve built two web products for public release: a data-modeling platform for Flash and Flex developers called X2O (www.x2oframework.com), and a web-based issue tracking tool called DoneDone (www.getdonedone.com).

Since launching both of these apps in the past year, we’ve had to do some in-house juggling – support our grassroots ISV business while maintaining our client work. In the meantime, we’ve stumbled upon some great lessons and observations from the trenches.

Here’s how we got our own products out the door and started making money while our client business thrives more now than ever.

Build products that’ll help your business right now

It’s hard to justify building apps that might not actually make a dime for months and months when there are clients willing to pay for your services right now. So, hedge your bets. Build products that help your business now. That’s reason enough to build a product anyways. Looking at it in reverse, if you’re already building internal apps for your own business, why can’t you turn it into a product?

We built X2O to get rid of the tedious nuances of building database-driven Flash and Flex applications for our clients. Instead of building database schemas, SQL queries, server-side code, web services, and client-side data parsers by hand for every client project, we wrote code generators to handle that for us. After a few months using it internally, we decided to wrap all of those generators up and built a web client on top of it, and – voila! A product was made. X2O was a product we needed anyway. The months we spent on it were helping us build apps for clients much faster.

The same thing was true for DoneDone. We paid $120 a month for a web-based issue tracking tool that flat out sucked. A horrible UI, too many dropdown boxes and filters, and not enough direction. We searched for other tools and they all did too much. So, I started to write my own, with our own rules and unique focus. In three months, we were using it to track our own bugs. Two months later, we threw a billing component behind it and started selling subscriptions to other similarly-jaded companies.

Building apps you’ll use anyways takes the pressure off. I worked on DoneDone for weeks at a time while the other five focused on client projects. If DoneDone weren’t something we could use right away, the pressure would really be on. If this app doesn’t succeed, what’s to become of me???

Avoid the “pet project” syndrome

Client projects are rarely completed on-time. But pet projects are never completed…period. If you’re serious about building a microISV, better treat your product as part of a client project and not just a pet project. There’s a chance in hell that it might actually get out the door. If you build tools that you need anyways, make them a natural part of your client work.

It also helps maintain momentum. Deadlines don’t have to be arbitrary. With X2O, we added big features (like a CMS generator) and small tweaks (like support for non-western languages) when we needed them for our clients. The due dates for X2O fell in line with due dates for other client deliverables.

Bonus? Your testing infrastructure is already set up. There’s something tangible to test your product against. The hypothetical get answered right away. If we were actually using this bug tracker…wait, we are actually using the bug tracker!

Pet projects don’t have the same sense of urgency that client projects do. Make your products as much a part of your client work and you’ll notice a huge difference.

Be the good client to your own products

There’s an interesting psychological switch that happens when you start building your own products after years of building products for someone else. You’re thrust into the role of being your own client. When should we launch? Can we launch without A, B, and C? Can we just add this one little piece? It can’t be that hard, can’t it? Suddenly, you become that client – the one that keeps you awake at night is now staring you directly in the mirror.

Be the good client. Don’t get caught up in the weedy details and focus on what makes the app better, not what makes everyone in your room happy. Do it to get your product up and running faster. It may just be a refreshing new way to work as well.

Decisions in groups of three

We don’t have big roundtable discussions for our apps. We don’t need a dozen opinions. If one of us wants to add email-to-ticket support to DoneDone, or RSS feeds for our issues, we decide what to do right now.

We found that decisions should be made in a group of three. We debate for 20 minutes and take a vote. Majority wins. Usually, we’re unanimous by the end of a debate. And, if three people think it’s a good idea, it’s likely that four, or five, or six people will to.

We have to make decisions quickly because there’s other work to do.

Let your apps rest

You should always rest a steak when it comes off the grill. Cut it open too quickly and all the juices flow out. Once it gets tough there’s no going back.

The same is true for your product once you’ve launched. Early on with DoneDone, we kept tweaking it. Slightly new iterations would pop up on an almost-daily basis. There’s a tendency to finagle too much with your own products because, well, they’re yours. Stop working on your app constantly. When you’ve gone live, making constant iterations (especially interface tweaks and functional additions) can hurt the user experience. Even if a new version is better, it’s unnerving to have things change so soon. Let users get used to what’s there before you adjust it again. It’ll give them a chance to tell you what really needs to be fixed.

As an added reason, there’s other client work to keep us occupied – work that’s generating revenue right now. If products were the only thing we worked on, then we probably would feel the itch to add new features to them constantly. In a way, having client work still be the focus of our business makes our products mature better.

So, if you’ve been thinking about dabbling into products, it doesn’t have to be an all-or-nothing proposition. In fact, it very well may enhance your client business, not hamper it.

Now, what happens as your product grows its customer base and you need to start adding support? Price it just right and the amount of effort you expend on it will be worth the increased time you need to devote to it. It just becomes a bigger client of yours.

Oh, and how do you price software just right? I’ll leave that question to someone else.

————-

My name is Ka Wai Cheung. I’m a partner at We Are Mammoth in Chicago. We build rich data-driven web apps for clients of all flavors. I’m also a designer/programmer, avid blogger, and co-author of the book Flash Application Design Solutions.

2 Comments

  1. Love the concept of “Let your apps rest”. Quick fixes here and there need to be fixed, but you’re right, let the app settle in before making big UX changes. I suspect suspect most scope creep happens right then when you feel the need to hurry and improve something – when really what you need to do is focus.

  2. Very inspiring article, and very informative. I too run a small (myself and a few partners) business for website/web app development and I’m looking to release my first “solution” in Q4 this year. I always appreciate when people in our industry are willing to enhance the industry overall with lessons learned and their own war stories. There’s plenty for everyone in this business, and this kind of information really does serve us all and elevates the industry on the whole.
    Thanks!

Write A Comment