The Corporate Organizational Structure of SaaS

orgstructures_WendelFranks_226x150

Recently, I had someone ask me how they might think about the organizational structure of their SaaS startup.

Here are some lessons I learned over my 25 years working on the operating side in what started out as small, private start ups (Oracle and Siebel Systems ) but turned into large companies – along with my experience working with many early and mid stage SaaS companies as an investor.

  1. Who the CEO elects to have as direct reports tells customers, employees, business partners, and shareholders what matters to her/him and what she/he believes is critical to the company to succeed. So, choose your reports carefully as you are signaling to a lot of people what is important to you.
  2. More layers between the CEO and the people who execute the business model can slow down decision making and reduce the speed of execution of the company. I have found that lackluster execution is what usually kills most start ups. CEOs are usually CEOs because they have excellent intuition and the ability to analyze data and make good decisions quickly. Relying upon others to “interpret” data and report on it may slow down and introduce sub-optimal decision-making (subjective decisions by lower level staff that may not be as experienced as the CEO or have ‘political’ agendas).
  3. The people who are responsible for executing the business model should be direct reports to the CEO. For a SaaS business model, this means the following:
    1. VP Marketing – responsible for the initial creation of revenue through demand generation (top of the funnel) and “future” revenue; revenue from future sales periods.
    2. VP Sales – responsible for delivering “in period” revenue via direct sales – inside and field sales
    3. VP Support – responsible for ensuring the product works as marketed/sold
    4. VP Service – responsible for implementations – if critical to the success of converting “contracted” MRR to “realized” MRR as projects are delivered
    5. VP Products – responsible for specifying a complete product that meets market requirements
    6. VP Engineering – responsible for building and delivering a complete product
    7. VP Customer Success – a “new” exec position critical to the SaaS model responsible for the bottom of the business model funnel – I wrote about this role previously in my blog . This role is responsible for making sure customers are happy and using the product every day (1 customer success rep for every $1M ARR is best practice). New products such as Totango are this function’s new “system of record” and the CEO’s window on usage metrics which is critical for renewals and reduced churn. You spend a lot of $ to acquire customers (CAC ratio), you need to make sure they stay as customers or the SaaS model falls apart.
    8. VP Finance – among many things, responsible for the accounting and collection of revenue
    9. Optional – VP Alliances/BD – if you need to interface with many different ISVs to deliver a complete solution
    10. Optional – VP Channels – if indirect sales is a key part of your business model

In my experience, a CEO and/or a GM,  should be able to handle 7-10 direct reports if each of those reports are A players and run their organization effectively.

In terms of process, what worked best for me as a divisional GM – modeled after successful executive staff meetings I was a part of – was a weekly meeting where each of my direct reports was required to cover what was accomplished the prior week and what was expected to be accomplished the following week — along with the usual review of revenue forecasts and financials.

Typically, for the forecast, we covered key deals for the quarter, and a WEB (Worst, Expect, and Best) revenue number and the critical elements required to achieve the forecast. By having all the functional leads in the room, we could quickly surface issues – product, deal terms, support issues, etc. – and collectively put together a plan of action to resolve them.

During each weekly meeting, as issues materialized, we generated a “resolution plan”, assigned owners and due dates and then reviewed the issues captured in the plan each week until they were resolved.

Each week at the overall Exec Staff meeting I attended, I covered the major metrics generated from my division’s weekly staff meeting.

These things worked for me so perhaps they will be helpful to you as you think through the optimal structure for your organization and its decision-making.

Fusing Collaboration Into Enterprise Applications – Enabling the “Real” Social Enterprise

I, along with many of you, have been watching the evolution of enterprise internal collaboration products/companies such as Yammer, Chatter, Jive, and Cubetree over the years.

I was an early investor in Cubetree which was acquired by SuccessFactors and then became part of SAP when SAP acquired SuccessFactors a short time later. SAP has since renamed Cubetree to SAP Jam and it now serves as the backbone to SAPs collaboration strategy.

These products are supposed to mitigate – eliminate ? - the need for email within the enterprise and dramatically improve internal collaboration offering far easier and superior ways to capture and share information v. email/spreadsheets, etc.

However, if you can get the product managers and/or CEOs of these product/companies to speak candidly off the record, with rare exception, the adoption level of these products has been far less than the creators and the companies that purchased these solutions had hoped for.

Why? I have a simple thesis.

Testing the Big Bend Theory: And the Winners Are….

Last November, I wrote an article posted in PandoDaily titled, “A VC wants startups to move to Bend, OR so he can incubate them.”

I have been traveling to Bend on summer vacations for many years. It is a fantastic outdoor community located in Central Oregon with around 100,000 people in the town and surrounding area. If you like to hike, bike, camp, fish, raft, ski, or drink incredible microbrew beer, Bend is your kind of place.

Over the past 10 years, however, Bend has been quietly transforming from its sleepy recreational roots into a burgeoning high-tech community with senior executive Silicon Valley transplants, a tech accelerator an annual venture conference, data centers from Facebook and Apple located nearby, and more than 40 software companies in and around town.

Dino Vendetti is a transplanted Silicon Valley VC who now lives in Bend fulltime. He and I were connected through some mutual acquaintances and began to strategize on how we might get even more startups interested in moving to Bend.

Why? Because Dino saw an ecosystem for tech startups starting to form, and he believed that with some help it could flourish, bringing more stable jobs to a community where people value education, family and a healthy lifestyle. Thus began his mission to develop and nurture this ecosystem in Bend, recruiting people like me to a play a part.

So, Dino and I came up with an idea for a contest. We called it “The Big Bend Theory.” Our objective: to introduce and recruit top tech talent into the area.

We opened the contest to anyone with a high-growth startup, or an idea for a startup. We asked entrants to send us their pitches and tell us what they are doing and why Bend is where they should be doing it.

We offered to treat a few entrepreneurs from the winning companies to an all-expense-paid weekend in Bend, giving them the opportunity to experience Bend for themselves and to see if this might be a place to locate their company, employees, and even families.

If they should choose to relocate their businesses to Bend, we offered to provide temporary tech space (at no cost), assistance with getting their team and families settled, and help in their funding efforts.

After reviewing 30 qualified applications from entrepreneurs around the nation, we made some difficult decisions and whittled it down to four winners. Originally we’d planned to select three, but with so many good candidates we couldn’t resist awarding a weekend in Bend to four entrepreneurs we think have the vision to contribute to the community – and a company worth investing in.

Today, I’m pleased to announce our four winners!

Company: TheSphere – www.thesphere.comCEO: Charles Armstrong
What they do: The leading platform for 360º content. Its technology is backed by 20 pending patents and is reaching the market through partnerships with companies like HomeAway, Sony and Samsung.
Why we chose them: “Insanely great” 360º video technology.

Company: AdStage – www.adstage.comCEO: Sahil Jain
What they do: All-in-one advertising platform for Facebook, Google, Bing, and LinkedIn. Why we chose them: Leading edge LinkedIn advertising platform.

Company: Aria Systems – www.ariasystems.comCEO: Tom Dibble
What they do: Help companies around the globe using its cloud-based, enterprise-class platform for subscription and usage-based billing.
Why we chose them: Part of the InterWest portfolio. Interested in moving an entire function inside the company to Bend, reducing ability for others to recruit key talent away from the company.

Company: Stealth
CEO: Eric Bahn
What they do: We can’t tell you but trust us, Eric is a pretty cool guy with some great ideas.
Why we chose them: We could tell you, but then we would have to kill you, which would ruin the whole thing for everyone.

On March 13th these winning entrepreneurs and their significant others will fly up on a direct 50-minute flight from SFO to the Redmond, OR airport that is just a 20-minute drive from downtown Bend.

Everyone will stay at Bend’s suave Oxford Hotel, and we will kick off the excitement with a networking event on Thursday evening at The Loft, a private social club in the heart of Bend.

On Friday, our guests will have the opportunity to meet with some of the talented software entrepreneurs headquartered in Bend along with key business leaders, educational leaders, Silicon Valley transplants, and real estate professionals. This should give everyone a better idea of what Bend has to offer beyond clean air and uncongested roads.

On Saturday, the visiting entrepreneurs and their guests will enjoy some of the fun outdoor activities that have put Bend on the map (and drew me here in the first place), followed by another exclusive networking event that evening.

On Sunday, we will wrap it up, everyone will fly back to SFO, and our hope is that some of these entrepreneurs will be inspired by what they experienced in Bend.

Dino and I are very excited to host this event. We believe we have some great people representing some great companies that would make great new additions to the thriving tech culture that is heating up in Bend.

The Big Bend Theory started as an experiment to see what would happen if you introduced really smart people to a growing tech community. I’ll let you know how our experiment goes after we meet with a few of the companies next month.

 

Siebel v Salesforce — Lessons from the Death of a Tech Goliath

Yesterday, Fortune.com posted an article I had been contemplating writing for several years.

It was a point of view story on the collapse of Siebel Systems and the rise of Salesforce to become the global leader in CRM. Well, at least a large portion of the CRM market.

In case you didn’t see the Fortune article, click here to read it. When you have finished, come back and the following narrative might add some color as they had to edit down the original and it lost a few points I had wanted to make.

Been a while….

It’s been a while since I made my last post. A number of people have actually noticed and asked, “What’s up?”

In fact my youngest daughter said, “Hey dad, you didn’t make the Forbes’ 10 Best Venture Capital Blogs for Entrepreneurs“. She works for Salesforce in Product Marketing and reads this stuff.

“Yea…thanks for pointing that out,” I said as if I hadn’t already seen the article and been contemplating on how to boost my ratings for next year.

She said, “You need to post regularly if you’re going to win these things, you know.”

I said, “Thanks for the marketing advice.” Having adult children who aren’t afraid to point out your failings can be extremely annoying. I need to remember this the next time I look at revising the Will.

I had thought about making some sort of lame excuse about “being busy” but the truth be told I just haven’t felt compelled to write a new post until now.