Author – Page 7

1987: Business by Handshake

As a four-year mutually beneficial relationship ended, turning our cooperation into competition, Emmett Ramey offered this as a final thought:

So now we’re competitors, but we can still be friends. The way I see it, it’s like two people fishing on a pier. I’m not worried about the fish nibbling on your line, because there’s plenty of fish nibbling on my line at the same time.

Emmett Ramey and I did business together for four years, money was spent and earned, and the business relationship ended amicably with an agreement to compete against each other, all based on a handshake, without either of us signing a contract.

Yes, it’s a true story. No, I’m not suggesting that this is the right way to do business; it’s an anachronism, definitely out of date. Still, it happened.

Emmett and his wife Ardella were owner-operators of Oasis Press in Milpitas CA when this happened in 1984. I was a one-man company called Infoplan, doing planning and market research, writing books and magazine columns, and working out of a home office.

We got together because I’d developed a business plan template, for use with Lotus 1-2-3 and Microsoft Excel, for the financial portion of a business plan; and Oasis Press had published Develop Your Business Plan, by Leza and Placencia. My financial templates worked very well with that book. We agreed that Oasis Press would buy the templates from Infoplan and add them into the book, as an option.

That deal lasted for about four years. I sweetened the pot for both of us by taking payment for a monthly column in Business Software magazine as a free black and white ad for Oasis Press, rather than money. The ad advertised the templates and the book. Oasis Press took the sales, and paid me for the add-on.

It worked really well until Emmett called one day, sounding embarrassed, saying that his authors wanted royalty payments from me for my software. That didn’t make sense to me. I’d already written books published by McGraw-Hill, Dow Jones-Irwin and other publishers, and business planning was my favorite topic, and the authors hadn’t contributed anything to my software. So we agreed, again without having to negotiate with lawyers or sign anything, to split it apart.

So I stopped selling the template for Develop Your Business Plan, and developed Business Plan Toolkit, which was released in January of 1988. Oasis Press continued to sell the book, but without software. It moved to Oregon in 1991 and was purchased by Entrepreneur Press in 2003.

And, with apology for repeating, I’m not recommending you do it this way now. I guess this was the exception, not the rule. And in this case, business by handshake worked perfectly well.

1979: Forecasting a New Market

(Reposted from timberry.bplans.com. In the summer of 1979, after we had moved from Mexico to Escondido Village on campus at Stanford, while waiting to start the MBA program, I worked with Creative Strategies International as a contract consultant. My last Mexico employer, Business International, owned Creative Strategies and helped me get the contract work.)

In 1979 Creative Strategies International, a high-tech market research company, assigned me the job of forecasting the market for automated teller machines in the U.S.

There were a very few of them already in place at the time. Maybe a few hundred.

I got the numbers as best I could. I found out how many banks there were, and how many branches. I got data for growth in banking customers and growth in branches. I got data for employees in banks.

I talked to dozens of experts. Product managers in companies making ATMs, or companies that could possibly be making them. Lots of bankers, lots of consultants to bankers, several journalists involved in bank-specific trade magazines.

Not all of them wanted to talk to me, but an older and more experienced vice president in the same firm (Tom Arnett was his name) had some good advice (and I’m paraphrasing here, it’s been 30 years):

They have to be interested in what they do, the market they’re in, or they couldn’t get up in the morning.

So hook them in fast. Tell them you’re forecasting the market for Creative Strategies. Tell them you’re thinking the market is going to grow at some percent — it doesn’t matter — but most experts disagree. Make it clear as quickly as possible that you’re going to offer opinions and information as part of the conversation, if they have time to talk to you.

Most of them will. They want to feel like experts. They want to be asked. And they want to know what you’re thinking too.

I used Tom’s advice a lot, and talked to a few dozen experts.

In the end, though, there was not technical or mathematical way to forecast ATMs. At least I was able to relate the projection to numbers of branches to give me some sense of error check, but it wasn’t clear that ATMs would all be in bank branches.

What made the biggest difference to that forecast was the placement of two ATMs at Stanford Shopping Center on the side of the Bank of America branch there. We lived in grad student family housing at the time, and we would ride our bikes over to the shopping center. The ATM was very convenient. It gave me cash fast. It gave me cash after banking hours. I used it a lot.

Most of the bankers told me people would never accept doing business with a machine. They’ll never warm up to that.

Happily, I believed what I saw instead of what the bankers told me. I projected a very fast growth rate for ATMs. As the years ticked off, it turned out I was very close. The forecast I made in 1979 gave a relatively accurate view of the future, given how much uncertainty was there in the system.

Take note, however: it was a human educated guess. The math helped me to compare my projection to the numbers of bank branches, but that was just a reality check. I was guessing.

1974: Jews? Yes, Tomato.

(Reposted from timberry.bplans.com.)

Although it was tame compared to recent years, Israel was very tense in 1974. It was just a few months after the Yom Kippur war. Still, tourism went on. I was a temporary tour guide, in charge of a group of about three dozen people going around the world from Mexico City.

The group was a Mexican group, mostly from Mexico City with some couples from other parts of Mexico. It was an expensive tour so they were economically well-to-do, which in Mexico usually correlates with speaking pretty good English.

Julio Sanchez and his wife Carmen were exceptions. They were from El Salvador and they didn’t speak English. At least they hadn’t spoken English at the beginning of the trip, but during the trip they picked up a lot. Waiters and hotel clerks and people along the day were much more likely to speak English than Spanish. So Julio and Carmen learned how to order meals, and find restrooms, and give taxi directions back to the hotel.

Despite the tension in Israel, it was also Jerusalem, an amazing city to visit, a place people in the group had wanted to visit all their lives. They’d visited the Taj Mahal, Hong Kong, and other splendid places, but Jerusalem was, to most of the group, the highlight. The organized tour went through as many of the main places in Jerusalem as possible — Bethlehem, the Wailing Wall, the stations of the cross — but not the Dead Sea. It was left out on purpose, because of the recent war, meaning tightened security, and more danger.

So it turned out that on the one free afternoon of the stay in Jerusalem, six of my group set out on their own to see the Dead Sea. Normal tours weren’t going there, but they found a taxi driver who, for a fat fee, was willing to take them. I didn’t know until later, but it wouldn’t have been up to me anyhow. They were all consenting adults. I was in charge of tours, logistics, meals, baggage, but not discipline.

They started late. They arrived at an abandoned Dead Sea bathing area late in the afternoon. They had to walk several hundred yards from the parking area and normal beach spot — which was pretty much abandoned — to the water. The taxi waited.

Night fell. They weren’t sure of which direction to walk back to the taxi. They argued. Then suddenly, spotlights, a loudspeaker in a language they didn’t understand. There were military vehicles, people in uniforms pointing guns at them. Angry men, shouting at them and pointing guns, loaded them into a military vehicle. They were driven through the night to a military outpost with a lot of searchlights, and led into a closed room with no windows.

They stood in front of an officer, surrounded by men with guns. There was not a lot of light in the room. The officer asked them questions, angrily, but it was a language they didn’t understand. They could only shrug and shake their heads. What had they done? They couldn’t even ask each other, because the men were angry if they tried to speak to each other at all, and more so because it was Spanish, a language they — the guards, the officer — didn’t understand.

It was at this point — I heard the story a few hours later, in the hotel — that Julio’s newfound English, learned just during the recent weeks of the trip, saved the day.

“Jews?” the officer asked angrily, “Are you Jews?”

Julio’s face brightened. At least, some words he recognized.

“Yes, thank you,” he answered. “Tomato, please.”

They said it took a couple of seconds before the group realized, and started laughing. The tension was broken. The captured tourists, suspected of being terrorists, and the guards, and the officer, laughed together. Both sides switched to English, and understood each other (Julio and Carmen needed help, but they were there with four fellow tourists who did speak English, and the Israeli army personnel all spoke English.)

The taxi was long gone, presumably hoping not to get disciplined for taking tourists to the deserted Dead Sea area at night. The Israeli solders took the tourists back to the hotel. Check points were passed, the story was told, there was a lot of laughter along the way.

So that’s the end of the story. It’s as true as it was when they told it to me that same night, in the hotel bar, where they found me waiting for their return and pretty worried.

This happened in 1974, when I lived in Mexico City and worked with United Press International. We worked six-day weeks at UPI, so we got six weeks of vacation.

And I took the picture here from our hotel, looking across the street, that same day:

1987: The Heat, the Kitchen, and Credit Cards

(This is reposted from my blog at timberry.bplans.com)

I was furious. This guy had stolen from us, blatantly, by ordering a software product, returning it, getting his money back from us, and then getting his money back from the credit card company.

This was back in the “old days,” the beginnings of Palo Alto Software, when I was the only full-time employee. I knew the guy’s history. He had done the same thing with the previous version, and then he did it again with this version.

So I was furious when I called the credit card merchant services line to get my money back. This guy was stealing from us and the credit card people were empowering him.

I got about five minutes into the call when I finally had to take a breath, which gave the very smart and presumably very well trained woman on the other end of the call a moment edgewise.

“Mr. Berry, can I interrupt you, break your train of thought for just a moment?”

“Okay,” I said, but begrudgingly.

“If your company is going to do business with customers who have credit cards, this is going to happen to you from time to time,” she said, calmly, with a reassuring tone.

“What’s happening is that our biggest problem is credit card fraud, merchants who take customers’ money and skip out. We live and die on our customers trusting us that credit card purchases are safe.”

I was listening. She continued.

“So you have to just think of it as a cost of doing business. We are always going to side with the customer, at the drop of a hat. It comes with the territory.”

And by then, I was getting it. Like the old saying, “if you can’t stand the heat, stay out of the kitchen.”

“So basically,” I asked, “anybody who is prepared to lie to you can take my goods and get them free?”

She hesitated only a few seconds, just the right amount.

“Well, please don’t quote me on that,” she said, “but think about it. Is it worth it to you to take credit cards?”

I thanked her, gave up the issue, and went on to do something else more useful.

1988: Focus on What Was Right

(Reposted from timberry.bplans.com)

Years ago we were coaching a soccer team of six-year-old girls. That was me and two of my teenage kids. Another of my kids was on the team. After a game with a team clearly way more organized and much better coached than ours, I asked the other coach how he did it.

“Oh it’s not what we do,” he said. “It’s what we don’t do, and even what we don’t say.”

He explained that they kept things very simple.

“We don’t tell them about passing or dribbling or very much of anything. We just tell them we want the ball in the goal.

“We don’t call them halfbacks or fullbacks or strikers or sweepers. They’re kickers and honeybees and goalguarders. Kickers go where the ball is, honeybees go where the ball is going to be, and goalguarders kick it away if it gets close.”

And perhaps the most interesting thing of all:

“We never tell them what they did wrong, or what they’re doing wrong,” he said. “Instead of that, we wait until they do something right, and when they do, we make a really big deal of it. We make sure all the others know what they did right.”

This made so much sense that we started copying it immediately. By the following year, the girls had way more fun, the parents had more fun, and the coaches had more fun, and oh, by the way, not that it mattered, but that team also won every game.

1983: I Don’t Create Competition

In 1983: The First Day of a New Business I told the story of leaving Creative Strategies and going out on my own to write books and, as it turned out, build my business planning and market consulting business. I was recently reminded of an offshoot of that story, valuable to me as a lesson in running a business right.

The lesson came from Larry Wells, who was the founder of Creative Strategies, president of Creative Strategies when this took place, and was later a venture capitalist in his own firm and then Citibank Venture Capital. I don’t know where he is these days. It’s been a long time, and I moved from Palo Alto to Eugene, but if you’re out there Larry, send me an email. I just Googled you and it didn’t work, there are many Larry Wellses out there, none seem to be the one who started Creative Strategies.

Larry and I remained friends during and after my exit from Creative Strategies. He kept me on retainer for more than a year, passed some business over to me, and made sure I got all of my accumulated vacation pay. I stayed on an extra nine months longer than I wanted, because my original exit date was awkward. Larry was trying to buy back the company from Business International and wanted me to remain until after the deal was done.

There was, however, one thing he wouldn’t do: help me build a business to compete against him. That’s exactly what he said when I asked him to cosponsor a newsletter that became Infotext: the Strategy Letter (and died many years ago).

“Sorry Tim, that would be helping you to build a name to compete against us. I never do that. That’s always bad business.” Larry looked me straight in the eye and answered as simply and clearly as possible. I got it.

It’s a good lesson. Don’t build the competition. Even if you’re friends, or allies, you have to be able to look into the future and see where that leads.

1982: Metrics, Swag, and 3 Types of Lies

(Reposted from timberry.bplans.com)

This is a true story. Back in my market research days, 20-some years ago now, I watched one of my friends and colleagues (call him Fred) present a market forecast to a committee of IBM executives. They objected to his numbers, which seemed way off of what they expected, which was also what they’d received from competing market research companies.

The pause that followed seemed to me to take forever. I watched with excruciating pain as the IBM executives in the room exchanged glances. I was sure they thought we were idiots; and expensive idiots too.

It was probably only a second, maybe two. Fred, thank goodness, was a seasoned veteran of this kind of moment, an alumnus of Stanford Research Institute with a lot of degrees and a lot of experience. He responded immediately. “Oh, that’s because we define the market differently,” he said, quickly and confidently. Then he started asking questions. “How do you define PCs? Does the processor make a difference?” Our clients seemed bewildered first, then apologetic. Fred resumed his presentation. We were home free.

What I knew, but kept to myself, was that Fred had changed definitions as quickly as a carnival con man changes peas underneath walnut shells. There’s sleight of the hand and sleight of the definitions. Definitions are a market research consultant’s best friend.

Which brings me to the subject of metrics. By that I mean numbers, measurement, a scorecard. People want to see how they’re doing and we’re used to scores in numbers. I’ve posted on this blog before about the importance of metrics, which drive accountability into planning and management. Metrics are to management what mortar is to a brick wall. How can you have accountability if you can’t measure performance?

In three ways to make your employees miserable I quoted author Patrick Lencioni saying that employees need, deserve, and want metrics. Earlier I had posted the magic of metrics, about how much I like metrics in my own work life.

My story here is about another side of metrics, the pliability of metrics. There’s an old quote, attributed to Mark Twain, Alfred Marshall, or Benjamin Disraeli:

“There are three types of lies: lies, damn lies, and statistics.”
Mark Twain

Sometimes we manufacture truth to fit our purposes. It’s not necessarily bad. When our Palo Alto Software soccer team went 8-1 in the city league last year we called a local trophy shop and ordered our own trophy, which most of the players assumed was given by the league for finishing in first place (and if this is you reading this, sorry, we thought you deserved it). This gets particularly interesting when we do this with the metrics that are built into our management.

That comes to mind today for the juxtaposition of a story in the New York Times and a post by Seth Godin. In How Many Site Hits? Depends Who’s Counting, Louise Story reports on widely varying ranges of traffic statistics on different websites, depending on the source.

…big media companies — including Time Warner, The Financial Times and The New York Times — are equally frustrated that their counts of Web visitors keep coming in vastly higher than those of the tracking companies. There are many reasons for the differences (such as how people who use the Web at home and at the office are counted), but the upshot is the same: the growth of online advertising is being stunted, industry executives say, because nobody can get the basic visitor counts straight.

I do remember that in the old days of the dot-com boom we could manipulate definitions to change Web traffic numbers. For example, there were visits, visitors, unique visitors, unique visits, page views, hits, lots of different but related numbers. Of course the true measure was sales, but even with sales, did we count returns? Did the month end at midnight of the last day of the month, when orders were made, or when the orders were tallied and posted? There’s always some wiggle room.

In his post “The New York Times Bestseller List”, Seth Godin points out that the New York Times is manipulating the list to serve various purposes. But, he adds,

The best part… it doesn’t matter. Cumulative advantage is so powerful that even though the accurate reports of book sales often completely contradict the Times list, authors and others still obsess over it. We’re always looking for clues, especially in crowded markets.

The easy answer to this puzzle is consistency. Measure performance by one consistently applied measure, without making it matter much which measure you use, but stick to the same measure so you can see change over time. In the real world, however, even those consistent measures over time are subject to change.

Fred, the market researcher in my opening story, was in his early fifties when I was working at Creative Strategies, myself in my early thirties, and he taught me a thing or two. One of them was his use of the term SWAG as a data source. SWAG stands for “scientific wild-ass guess.”

1983: First Day of a New Business

(This is reposted here from my blog at timberry.bplans.com)

This is a true story. I think it’s worth telling because it’s one real example, one that I lived through, of how plans change and you have to adapt. And it’s also an example of how random businesses are, and how many different ways people get started on their own path.

I’m a business planner by profession, and I find it humorous how differently my own steps in my own business went from what I had planned.

It was a hot day in August of 1983. I sat typing in to a home-built business computer that was bigger than a dorm-room refrigerator, writing a book on spreadsheets, using mostly Wordstar and SuperCalc. I was in my home office at the corner of Mariposa and Miramonte in Palo Alto, CA. My third daughter and fourth child, Cristin, 18 months old, shared the office with me, playing on the floor with a used keyboard. I needed to finish the book to collect the second half of the advance, which was part of my plan.

The plan, however, was not going to work. What I had planned was to make a sufficient living writing computer books. Stuart Brandt had collected a $100,000 advance (or so it was reported) for the Good Earth Catalog. It seemed like publishers were looking for computer books and I was a computer lover, former journalist, and MBA, well positioned to write them.

I didn’t know then that my plan wasn’t going to work. The book was on schedule and I had contracts for two others.

I had left Creative Strategies International, a high-tech market research and strategy-consulting firm, two months earlier. When I left I was vice president of the software group, which had the company’s highest margin and highest gross sales, so I was well positioned. But, I had decided that what I wanted to do was the work, not the supervision of other people doing the work. I liked writing and analysis, and I liked market forecasting and market research. What I didn’t like was checking on other people and managing them. I needed to make money to support my family of six; we had no savings, and debts left over from business school, so it was foolish to give up a good job, but I actually thought, foolishly, that I could make as much, or more, money writing computer books.

The phone rang. It was Hector Saldana, who managed Apple Computer’s Latin America group. I had done several market research jobs for Hector while at Creative Strategies. I had a good background for market research in Latin America, having lived for several years in Mexico City and having experience in consulting and market research, and a good set of degrees.

“Tim, I need you to go to Venezuela for me as soon as possible. I need a market study of Venezuela quickly,” Hector said.

“Hector,” I answered, stupidly, “I’m not with Creative Strategies anymore. I’m on my own now, writing computer books.”

“I know,” Hector answered, “They told me that when I called them. What do I care about that? Why would I want to pay them for your work instead of you? Now seriously, how soon can you get down there? I can pay you well.”

I was on a plane three days later, and three weeks later I delivered a Venezuelan market study along with an invoice for more than the combined advances of three computer books. My career as a business planning consultant had begun.

I went on to 12 years of consulting with Apple Computer. I was never an employee, but I worked for Apple Latin America, Apple Pacific, and Apple Japan regularly until 1994. That phone call changed my book writing into a filler and my consulting into a career. It wasn’t my plan; but that’s the way it happened.

I did eventually finish the books I had contracted, but my focus had changed. I admit that thinking I could actually survive economically and support a family only by writing computer books was really dumb, but at least I had the good sense to jump tracks when the opportunity arose.

I Predicted Remote Working

Ed note: This was written in 2007 at timberry.bplans.com … looking back from 2024, it seems prophetic.

I admit it. I’m a hypocrite. I worry about global warming, and people, and how much humanity we waste every day in large cities all over the world with people stuck in traffic, moving their physical bodies from their homes to their offices, and back. I believe in the abstract in telecommuting as a good idea for not really saving the world, but delaying slightly its descent into chaos and destruction. So why am I a hypocrite? Because my own company discourages telecommuting.

I don’t think I’m atypical. There are a lot of times when running a business means compromising with some extremes.

In my defense, we’re in Eugene, Oregon, a college town of 150,000 where the commutes are way easier than in any freeway-clogged major urban area. Some of our people live outside the town 20 or 30 minutes away, but most of have fairly short drives, five or 10 minutes.

I paid my dues with commuting through heavy traffic (nine years in Mexico City, and 12 in Silicon Valley) so I’ve been sympathetic to the idea of telecommuting for years. For whatever reason my memory has stamped forever a time I was sitting in a taxi in Tokyo traffic, in the early 1990s, thinking about how much humanity was wasted every work day, in larger cities all over the world, sitting in traffic.

What brings this to mind today, with thanks to Steve King of Small Biz Labs for the tip, is ABC News covering the virtual office and (implictly) telecommuting with a piece they called Any Time, Any Place Management. What’s interesting to me isn’t the story itself — hey, most of us have known about telecommuting for a long time now — but rather the recognition in the mainstream. ABC is noting that larger companies (they use IBM as an example) are opening up to this, bringing it into the mainstream.

Back then, stuck in traffic, maybe 15 years ago now, it seemed to me that this was an unrecognized major problem facing the urban portion of humanity, a problem that needs solving. At the time I was consulting extensively with Apple Japan, doing a lot of work from my office in Eugene OR, using email and telephone. I did have to go to Tokyo about one week a month, though, and I didn’t like it. I particularly didn’t like getting from one place to another in Tokyo when it involved any means of transportation other than walking or subway. And, for that matter, subway in non-rush hours.

I solved my commuting problem by moving to Eugene OR (subject of a recent post on this blog) but that didn’t make me forget how bad it was to lose a couple of hours a day to traffic. However, here comes the compromise. In this company we like to have our people on our team together during the day, in our one location, mostly a bunch of cubes. We like the instant communication involved, the immediate contact, the sense of team. Programmers talk to other programmers, and marketers talk to other marketers.

Years ago we tried working with programmers in Pakistan, and although the people were competent, the outsourcing didn’t work well for us because they were on the other side of the world, asleep while we were awake.

It does make a lot of sense for a lot of reasons. Think about trendy for a second, the problem of global warming for example, and then if some of the smaller things we do makes a difference, how about taking a significant percentage of people off of the road — less fuel, fewer emission, aside from the wear and tear to the human spirit. Sure, telecommuting doesn’t work for a lot of jobs like retail sales clerk or construction workers or traffic cops, but what percentage of the work force doesn’t really have to go from one place to another to work? I used to think about that when caught in traffic. There should be a campaign, a global building of awareness, I thought.

One roadblock was the idea of acceptance by employers. Does somebody working from home contribute as much to a company as the poor commuter who moves the physical body from home to office and back again every day? Now, today, this ABC news story is a reminder that mainstream employers are increasingly more likely to accept the idea, and, back in the real world of small business, I’m not. Not, at least, except for some special cases and special circumstances.

Like I said, I admit.

1992: Moving to Eugene

People ask why Palo Alto Software is based in Eugene, Oregon. I think business stories are a good way to communicate different elements of business, so I’ve decided to share that in detail. This is why we moved Palo Alto Software to Eugene.

One day in the late 1980s my wife Vange asked me this question:

“Tim, we put up with all the down side of you insisting on doing your own business. Why don’t we get the upside too? Why don’t we just move to somewhere else, somewhere where we want to live?”

At the time Palo Alto Software was based in an office at 260 Sheridan, Palo Alto, CA. That’s a couple of blocks from California Avenue, towards the Fry’s store and the Fish Market. Home at the time was on Pitman Street, a couple of blocks from the public library.

It wasn’t just that one question that one day. We wanted to move. It was nothing against Palo Alto, which is an ideal location in many ways. Palo Alto is right in Silicon Valley, it contains Stanford University, it has beautiful neighborhoods, the second highest number of graduate degrees per capita in the U.S., the second highest average income in California, and we had a nice house. We, however, wanted to move somewhere else that had less traffic and a different, if not higher, quality of life. And we wanted to reduce our fixed costs, because our variable income from consulting was driving us crazy. Our_house_in_eugene

Theoretically we chose Eugene after a rigorous analysis of university towns in the west, including Chico, Santa Cruz, and Irvine in California, Boulder in Colorado, Spokane and Walla Walla in Washington, and Corvallis and Eugene in Oregon. We looked at factors including pricing, neighborhoods, outdoor activities, quality-of-life indicators, pollution, nearby airports, and others. Eugene came out as the best bet.

In truth we chose Eugene because we had lived there before and we liked it. I did an MA in Journalism there (University of Oregon) after we were married and before we had kids. We’d been visiting off and on for vacations. We’d been happy there. It was a known quantity. Eugene

One thing that helped make a move possible was the lack of employees. We were a very small company surviving on my consulting income. I was the only full-time employee.

Although the company kept, and still has, its original name, it was a very different company from what it is now, with 70% market share in a product business and 40 employees. It was essentially a professional service business entirely dependent on my consulting, but one whose owner nonetheless stubbornly insisted on following a long-term plan to “sell boxes, not hours.” The vast majority of the revenue came from consulting with Apple Computer’s Apple Japan subsidiary, based in Tokyo. The software product was called Business Plan Toolkit, which was essentially a nice manual (if I do say so myself) on how to do a business plan along with templates for Mac or PC, Lotus 1-2-3 or Microsoft Excel. We advertised in the small ads in the back of computer magazines, and in some special promotions like in the box with Microsoft Excel. The software business lost money every year, but I supported it with consulting revenue.

Judy David was director of finance for Apple Japan. On one of my trips to Japan — I was going about one week a month, consulting in strategic planning — I had lunch with Judy and told her we were thinking about moving from Palo Alto to Eugene. Judy, one of the smartest and most competent people I’ve ever worked with, said the following:

“Tim, we don’t care where you get on the plane.”

She had a good point. Airfares, which the client paid, were about the same from Eugene to Tokyo as from San Francisco to Tokyo, so Judy’s comment eliminated the main business objection.

The actual moving was hard for lots of reasons not directly related to business: finding a house, dealing with teenage children, finding movers, things like that. On the business side, I contacted some local agencies responsible for fostering economic growth, from which I got good recommendations for banks, bookkeepers, and insurance agents.

There were also some legal implications. With the help of a local attorney we created an Oregon corporation named Palo Alto Software, merged the California corporation named Palo Alto Software with it, and eventually, two years later, dissolved the California corporation.

Of course we didn’t change the name, despite the name tie-in to Palo Alto the city. By the time we moved to Eugene we had already existed for five years, we had products in the market, advertising, and branding established. Palo Alto Software was always a good name for the company, because it evokes both Stanford University and Silicon Valley.

So Palo Alto Software moved to Eugene, Oregon, in 1992.

(Reposted from timberry.bplans.com)