software Archives

Subscribe to the software RSS feed.

CEO Survey, Fall 2010

TOPIC: How & What Growth-stage CEOs Are Planning for 2011

Below is the hyperlink to take the Q4 CEO peers speed-survey, exclusively for growth-stage CEOs.  This survey focuses on “How & What Growth-stage CEOs are Planning for 2011″

This shouldn’t take more than 5 minutes of a busy CEO’s time–

We here at BSG Team Ventures periodically take the temperature of the markets we serve. The survey is no more than 15 questions, most simple multiple-choice.

These surveys are created and compiled by BSG Team Ventures as a courtesy to our executive ecosystem with the belief that knowledge is power.  Aggregated peer-provided knowledge is “actionable power.”

For the survey results from Q2 2010, titled “Impact of Economy & Renewed Growth Planning”, go to http://www.bostonsearchgroup.com/blog/ceo-survey-results-q2-2010-%E2%80%93-impact-of-economy-renewed-growth/

We make an effort to survey only those who fit the category (in this case, sitting CEOs or board member/founders of technology/science-driven growth-stage companies). [Note, if you don't fit the aforementioned description, please refrain from responding.]

Feel free to forward to the qualified CEOs in your sphere of influence. The more data generated, the more accurate the trend lines.

All responses are anonymous due to the web-based survey technology employed.

We will forward the survey results within the next two weeks to the email address on file. Please let us know if there is another email address you wish us to send the results to as well.

Share and Enjoy:
  • Twitter
  • Facebook
  • Digg
  • del.icio.us
  • LinkedIn
  • StumbleUpon
  • RSS
  • Reddit
  • Google Bookmarks
  • Print

CEOs dish on How to Combat “Happy Ears” in Sales Pipeline Management

OK, admit it.  As CEO of a growth stage technology company, when it comes to your sales team, they all have “happy ears.”  Joyce Durst, former CEO of Infraworks, an enterprise security software company in Austin, TX, used the phrase in describing the eternal sales optimism she and her VP Sales have to counterbalance every week during their Monday morning sales pipeline meetings with their sales team.  You know, this is the optimism that insists that the prospect call that just took place the week before is not only a “sure thing,” but is also a particularly big sized deal, and will surely close before the end of the quarter, with room to spare.   Unfortunately, “happy ears” are the occupational hazard of a good sales person.  These are the ones that as often as not has to take a partially completed beta product, dress it up, sell it into a market where no other solution like it has ever existed, persuade someone that the solution is a “must have,” and then also persuade the other buying influencers within the customer that doing business with an underfunded start-up with perhaps less than 12 months of cash in the bank is a capital idea.

Working with growth-stage CEOs as executive recruiters, we’re often helping to hire sales VPs that will be able to build and manage a company’s sales pipeline.  Certainly hiring the right VP Sales is an important first step in sales pipeline management.  However, once you’ve gotten the right person in the seat, we asked a dozen or so early-stage technology CEOs what other tools, processes, and mistakes they’ve used or made that have led to their “best practices” for effective sales pipeline management.

TOOLS (technology)

Regardless of which tools were the favorites of each CEO, there was agreement that data hygiene was critical

Chuck Dornbush, CEO of Athenium Software, put it succinctly, saying, “Make sure the data is well organized, and frequently reviewed.”  Another location-based services CEO added, “no matter what CRM tool you use, as CEO you need to make sure every sales person is using it, and using it the same way.” Vinit Nijhawan, former CEO of Taral Networks, emphasized that sales people hate to use a system at all; you’re lucky to get them to enter the data once, and you’ll never get them to double enter for forecasting purposes.  So you need to use the same system for lead tracking and reporting/forecasting.”

PROCESS BEST PRACTICES

Meetings 1x-week—sales people defend their new pipeline additions

One of the above CEOs stated simply– “Know the basics, and do the basics.”  In more detail, he and several others sketched the basics out.   Have a weekly sales meeting.  For sales people to have a prospect “make the pipeline report,” they need to defend their putting the prospect into the pipeline, akin to a team interrogation.

7 categories involved in qualifying additions to the pipeline

Many of the CEOs talked about the minimum information requirements for a prospect to be added to the pipeline report.  Although some CEOs had four steps, and others had up to 40, the core must-haves most often included the following 7:

1. Budget—– Is there an earmarked budget set-aside for this category of expenditure?

2. Need –Is there a compelling need driving the prospect to make this purchase?

3. Time urgency—–Is there something that creates a sense of time-bound decisioning, or is this an important-but-non-urgent agenda item?

4. Internal champion—–Is there an individual inside the prospect who’s willing to go the extra mile and spend the political capital required to “fight the good fight” internally within their own organization?

5. Decision making power–—Who holds the real “power” to make the decision?  Can a clear decision-making organization path be mapped?

6. Clear ROI—–How is the prospective customer going to measure “success” for this product or solution?

7. Trust– Both in the relationship between the individual sales person and the individual representing the prospective customer company, and the prospect’s relationship with you as a company with whom to do business… do they trust your products, your company, and your sales people?

Tim Butler, former CEO at SiteScape and now CEO of growing RFID company Tego, said that as a reminder for his sales force, they have adopted a pneumonic, BUTANE–—budget, urgency, timing, authority, need & event.

Stages of the sales pipeline

Joyce Durst has her sales team and VP Sales apply a ranking/scoring system for each sales prospect.  If the customer is 50 points or less, they remain on the prospects list only, and don’t move onto pipeline report; if more than that, 50-70, they’re pipelined for NEXT quarter; if 70-90, they’re qualified as “committed;” If 90-100, the prospect is considered “ready to close.”

Athenium CEO Chuck Dornbush finds that it’s critical to “set entry/exit rules litmus tests for each stage.”  One CEO established the rule that “you couldn’t allow a prospect into the pipeline until at least their forth stage–qualified, demonstrated, formal price quote, and funds allocated. “

Other critical ingredients

Categorize every lead as “hot, warm, cold”

In addition to assigning probabilities as a percentage, try using some sort of ranking system.  Tim Butler uses another version– possible, likely, & probable

Add non-sales peers to pipeline meetings…

One of the CEOs stated  that it was very valuable to bring non-sales functions into sales pipeline meetings.  He added that personal accountability generated by sales people committing to forecasts in front of non-sales peers in a weekly/monthly meeting environment can do a lot to reduce the “fudge factor.”

Get the customer prospect to serve as proxy VP Sales for you…

Former Pantero CEO Pano Anthos who now is CEO of Hangout added a trick of the pipeline trade he’s found very useful– —“The customer needs to sign OFF on moving from one step to another.  Have the CUSTOMER via email play a proxy VP Sales role for you.”  Do this by having your sales person ask for a confirmation by email that the prospect has indeed passed from one stage of the sales pipeline to the next, whether confirming the ROI value proposition, or the budget allocation, or any of the other stages listed earlier.

If no date for next prospect action step, off it goes…

“Every prospect has to have an action item by date, or qualify it as ‘dead,’” another CEO offered up.

Kill the bad deals early…

Many CEOs listed this as critical to effective sales pipeline management.  Slow prospects should be turned over to the inside sales team.  Prospects that are particularly non-committal should get put in direct mail “tickler” mode.   “Stop spending the time on them, trying to actively manage them to close,” Marc Tremblay states, and adds that, “if feasible, you want to focus your sales team more on hunting than farming if you can.  You can get tied into prospects who may take two years to close… “  They may close, but “I always get my man” isn’t the most efficient proverb for sales.

Expect the unexpected…

When ending the quarter and/or the year there will be sales people who will say, “we’ll absolutely close these deals….” Even when all indications say they’re done, assume that some percentage will fall out, no matter HOW good they look.  Jim Lawton,  a veteran VP Marketing at a number of venture-backed growth-stage software companies who has seen a lot of sales pipeline management approaches states the reasons can include someone at the prospect company “getting sick, leaving the position, dog ate my homework… expect just about anything.”

“3x coverage” to mitigate the unexpected …

Continuing, Jim Lawton added, “If I’m trying to hit 3 million in quarterly sales, I want to have 9 million in the pipe.  Living on luck is tough, and you might hit a quarter or two with a thin pipe where you muscle the prospects and get a blue bird or two, but you’ll never make this repeatable.”

Consider having TWO sales pipelines

No, this isn’t two separate sets of books, nor is this a tool meant to be used deceitfully.  However, one of the CEOs offered up the fact that—–early on at least–there was a pipeline they kept internal, and one the executive team shared with investors that better illustrated the potential traction of their products.  The internal pipeline was more conservative.  As they grew the business, there was a natural convergence of the two into one.  Controversial, yes.  However, in order to manage burn-rates, and make sure you live to fight another day, it’s a survival tactic that no doubt many CEOs use, whether they admit to it or not.

Other Considerations

When to begin trying to do sales forecasting

Once you’re at what’s often referred to by venture capitalists as the “scaling stage,” most CEOs list their pipeline out and begin assigning probabilities.  However, Vinit Nijhawan cautioned that, “You rarely ever hit the forecast you set up.  After you get your 3 or 4 customers, you feel there is a market for your product, but actually what you’ve done is gotten the really early adopters.  And CEOs then start to scale too early, hiring resources, and making decisions that are difficult to undo.  Instead, you need to be in that strategic marketing role in sales longer than most start-ups might think.  Don’t even OFFER sales pipeline reports.  It’s not an issue with the start-up’s products, it’s the market.  Quarter-over-quarter projections are almost impossible.”  So where is the line, and where do you know that you have a product that the market is ready for?  “THAT is the art in sales pipeline management,” says Anthos.  “It’s definitely not a science.”

Strategic consideration in building the sales pipeline–—proper reference customer sequencing

Another wrinkle in building an early-stage sales pipeline CEOs mentioned was the proper ordering of reference customers.  There is a step before managing the pipeline process or implementing some tool to help in pipeline forecasting.  This is determining what is the optimal sequencing of customers you go to in order to create proof points and references to scale customer acquisition most efficiently and effectively. Do you sell big customers first, then the small customers, or smaller customers and build up to bigger ones?  CEOs concurred, —“It depends on capital resources available.”

MISTAKES & LEARNINGS

3 reasons deals don’t happen… [click "more" link for rest of article] More…
Share and Enjoy:
  • Twitter
  • Facebook
  • Digg
  • del.icio.us
  • LinkedIn
  • StumbleUpon
  • RSS
  • Reddit
  • Google Bookmarks
  • Print

SVP Technology & Software Engineering, SaaS software for financial services sector

The Leading Provider of Wealth Marketing Solutions

Based in New York City, our client provides strategic and interactive marketing solutions for wealth management firms and luxury brands. The company offers strategy planning and research services; online marketing and advertising programs; and e-marketing tools, which comprise a suite of software offering an e-marketing platform that allows communication with clients and prospects. It also provides marketing services, including print and online content publishing, brand and identity creative, creative strategy and planning, logo and mark creation, graphic design and layout, editorial design, copywriting, multimedia design, video and audio production, prepress and print, and collateral development services. In addition, the company offers interactive solutions, such as Web design, Web building and analytics, Internet and intranet/micro site development, information architecture, SEM/SEO, systematic design, content management, E-commerce, and Internet application development services,  and multichannel integrated marketing, rich and emerging media, media strategy, media planning and buying, and strategy and creative development services.

The company has become the pre-eminent provider of interactive agency expertise, accompanied by specific CRM oriented software tools to help their marquis clients, including Merrill Lynch, Morgan Stanley, Charles Schwab and Barclays.

The Position

Reporting to the CEO, the SVP Technology’s role is to oversee day to day activities of the software product development and enterprise architecture integration teams for the company’s Software as a Service (SaaS) offerings. The SVP will directly supervise a team of software developers, quality assurance, and business analysts; identify risk and opportunity areas; and coordinate all software development activities.

The head of technology will also work closely with Product Strategy on the business side and manage the Lead Technical Architect to envision and define features in the product roadmap and be accountable for the features development, deployment and support.  In addition to the technical leadership of the team, this role has full management responsibility and oversight for a cross-functional group of engineering personnel.

The SVP Technology shall:

  • • Manage software architecture, design, development, procurement, and integration. Also manage tier-2 and higher support once software has been placed into operations.
  • • Achieve cost, schedule, technical and quality performance for delivered software. Compile, maintain, schedule, resource, execute prioritized lists of development projects, including planning and managing the budget and scheduling personnel and vendor contracts to meet project needs. Collect metrics on development performance and report on them.
  • • Collaborate with other functional managers (customer facing business units, systems engineering, QA, and operations) to ensure architectural integrity, effective integration and test, and ongoing system stability.
  • • Direct technical subcontractor management including contract negotiation, technical support, budgetary management and program management of various contracts and associated budgets.   Coordinate vendor contracts, deliveries and schedule with affected company parties.  Contract with vendors for services to support engineering while addressing Intellectual Property, Non-Disclosures and Statements of Work.
  • • Manage short- and long-term staff planning, recruitment, performance management, work assignments, training, mentoring, career development, and recognition or disciplinary action.
  • • Be responsible for business planning and proposals, operating budgets and financial terms / conditions of contracts for both internal and external customers.

The successful candidate must also have the ability and experience to lead a multi-disciplined organization in a multi-location environment.

Qualifications

  • • Minimum of 10 years overall software development experience, with no less than 5 years in a SaaS environment as well as at least 5 years of management experience.
  • • 2-3 years of senior-level or leadership experience in a software environment with 10 or more direct reports.
  • • Experience working with product managers and other business stakeholders to set timeliness, budget resources, and manage expectations and quality of the development process
  • • Advanced understanding of SaaS web application programming architectures, including standards for security, scalability and configurability
  • • Expertise and experience in implementing and overseeing measures for data security, business continuity, disaster recovery
  • • Deep understanding of load balancing and performance optimization  principals for high volume/transaction web applications
  • • Strong skills in Java software development.
  • • Experience with refactoring and eliminating legacy dependencies
  • • Demonstrated substantial leadership in both technical and management areas
  • • Experience leading development efforts using a variety of different SDLC approaches (waterfall, agile, etc.)
  • • Knowledge of multi-threaded programming
  • • Outstanding collaboration skills, excellent communication skills, an ability to look at the big picture

Essential Job Functions/Responsibilities

  • • Lead software and front-end engineers in the specification, design and development and support of all our applications, including websites/products, our core services and our internal and external tools
  • • Provide hands-on technical management leadership and support to software development team of 12 – 15 engineers
  • • Identify skill and performance gaps in current organization and provide improvement plans
  • • Improve existing processes and establish new processes for efficient development and high quality output
  • • Evaluate and enhance overall development environment, release practices and Quality Assurance methodology
  • • Instate and maintain development standards, code reviews, unit testing and integration testing frameworks
  • • Maintain overall ownership / accountability for data security, business continuity, disaster recovery
  • • Work in tandem with Technical architect and development team to identify and implement new measures for system performance optimization under high load
  • • Lead, recruit, develop and supervise the development team members
  • • Evaluate and take accountability for decisions on key technologies adopted
  • • Ensure proper development of technical specifications and documentation.
  • • Estimate resource usage and timeliness for development team
  • • Review team members’ detailed design of components/modules/code
  • • Provide a good balance of experience and skills in several front-end and/or back-end technologies
  • • Strong relational database skills, preferably MY SQL Serve
  • • Knowledge of latest web technologies with understanding of AJAX and RIA
  • • Ability to translate technology choices into business implications

The diagram below illustrates the intersection of competencies critical in the SVP Technology position:

Compensation

Compensation is competitive with the position’s requirements.  In a performance-based environment, this will include base salary, incentive bonus structure based on both individual, department, and corporate qualitative and quantitative MBOs, and a potential stakeholder position in the company.

SVP Software Engineering, SaaS software for financial services sector
Share and Enjoy:
  • Twitter
  • Facebook
  • Digg
  • del.icio.us
  • LinkedIn
  • StumbleUpon
  • RSS
  • Reddit
  • Google Bookmarks
  • Print

CEO for growth-stage start-up in Denver focused on pixel OS

Our client is tearing down the walls of the pixel landscape.  The Company has developed proprietary breakthrough software that functions as a pixels operating system, moving video display from one source projecting one visual, to infinite sources projecting virtually unlimited visuals.  And all of this is at a pixel-density that can go beyond high-definition quality, at commodity projection device cost, with no manual calibration or image “stitching” required.  The Company’’s technology is used in various applications ranging from simulation and training to museum displays and digital signage.  The company serves corporate, government, and academic organizations.

pixel-os-show-and-tell

Market Opportunity

Industry Outlook (software-enabled displays):

  • •    Visual simulation and Large Venue Display – $1.4B and $22.2B
  • •    Growing rapidly – 14.1% and 23.3% CAGR
  • •    Incumbent companies expensive, inflexible, and manually aligned – the bottleneck to widespread use of advanced display
  • •    Commercial public venue display increased from $16.5B to $22.2B from 2005-2007
  • •    iSuppli (major research firm) predicts $51B by 2011
  • •    Multiple options for use: API for large, seamless displays and computing clusters with over 6xHD resolutions displays; or seamless displays up to 6xHD with no application integration.

A single Company server can calibrate multiple displays and is not limited by projection hardware type or resolution.

The Position

The CEO’s core responsibilities will include:

Marketing direction:

Marketing strategy & product marketing– Establishing a short and long-term business direction the drives the company to become an industry leader and maximize the penetration of the markets served.

Business development, including channel sales, OEM & relationships, and all distribution agreements

Operations– Product delivery, deployment, fulfillment and post-sales customer relationship management.

Manufacturing & Operations:

Oversight of manufacturing and production teams responsible for commercializing the technology, establishing build/buy/outsource decisions, etcetera. Working with the rest of the team, oversight of quality assurance, working with the CTO to ensure that product development meets various international multi-regional market-driven specifications and is “rolled out” smoothly and on schedule.

Staff- team building, development, mentorship:  The CEO is responsible for human capital planning and hiring.  As important, the position will actively be responsible for developing new and existing staff to help prepare them for company growth and increased leadership responsibilities at all levels.  Finally, the new CEO will serve as leader and mentor to the founding team and as a complement to their existing skills.

Investors/shareholders & board - milestone management, follow-on fundraising, liquidity strategy: The new CEO is primary liaison to the board and will aggressively manage milestone deliverables, be a key contributor at board meetings and to board/investor communications.  The CEO will be responsible for developing and managing against an annual operating plan and in addition to possible follow-on fundraising, will be accountable for optimizing the harvest for all shareholders.

Ideal Candidate Profile

The diagram below illustrates the intersection of competencies critical in the new CEO:

ceo-success-attributes-pixel-os

Compensation

Compensation is competitive with the position’s requirements.  In a performance-based environment, this will include base salary, milestone/incentive bonus structure, and a stakeholder position in the company.


Share and Enjoy:
  • Twitter
  • Facebook
  • Digg
  • del.icio.us
  • LinkedIn
  • StumbleUpon
  • RSS
  • Reddit
  • Google Bookmarks
  • Print
Newer Posts »