4 Biggest Custom Software Buying Mistakes - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IT Leadership // CIO Insights & Innovation
12:32 PM
Josh Oakhurst
Josh Oakhurst
Connect Directly

4 Biggest Custom Software Buying Mistakes

Procurement is broken. Here's how companies can avoid the biggest blunders.

Stagnant procurement processes often kill innovation. As more companies look to build software instead of buy it off the shelf, the first process that requires improvement is the one where the contract gets signed.

At Skookum Digital Works, our 55-person shop in Charlotte provides tech investment strategy advice and also builds hardware and software from scratch, so we live this. To avoid irrational fears, policy-driven blinders, and downright rule-bound stupidity during the  procurement process for innovative technology, avoid these four mistakes.

Mistake No. 1: You think you're buying a product
You're not. You're going on a journey. Custom software development is not something you should purchase like paper clips. Procurement departments are wired to haggle over incremental per-piece pricing, volume numbers, and delivery dates.

Pre-packaged technology providers have "inventory" sitting on the self; they sell what's in the box. In contrast, custom technology consultants take pains to map out investment options and craft custom software executions. When business units express the desire to go on a technological journey, procurement should help them pick a tour guide, not insist on cross-shopping hotels. Projects slow down or can implode altogether when procurement gets this wrong.

[Considering custom software? Don't miss this post from Coverlet Meshing: Build Vs. Buy: A Dangerous Lie.]

Custom software service companies exist because someone decided what's in the box won't work. For a custom execution, the process is the product.

Mistake No. 2: You require the contract have a hard delivery deadline
Custom technology engagements are best controlled by budget and ambition, not deadline. The goal of a tailored software creation process is to create working software as soon as possible. After all, code is a liability; you want the least code possible. Features determine how much code will be written, and at the moment of contract signing, the features you think you'll include are always dubious.

What you will want in the contract is a nod toward a delivery date for a minimum viable product, and a proposed sprint schedule. But it's folly to assume anyone knows the final end date of your journey at the time of contract signing.

Mistake No. 3: You view custom software as a dollar-per-hour commodity
Developer cost per hour is a terrible way to look at a custom software project. Is the value of the Empire State Building a function of the price of steel and the labor hours that went into it?

Procurement departments run straight into this trap because developer cost per hour, like the price of steel, can be easily measured. If custom software development were merely a function of developer time, then hiring an array of the cheapest offshore coders would get the job done. You're paying for business technologists who can implement or invent technology that does what you asked for -- make your business faster, more efficient, more profitable, more robust.

Mistake No. 4: You assume the standard software contract deductions apply
Because out-of-the-box software contracts have been negotiated with standard deductions, buyers often assume custom software is also highly negotiable. But the logic of volume pricing doesn't apply to creation-from-scratch. Always fighting for a discount off sticker price is not only obnoxious, it's myopic. (And, in some cases, downright stupid.)

Procurement helps its business units succeed by doing a complete cost-benefit analysis. Often, the best way to measure the value of custom software development is to stack it against the cost of doing nothing.

Simply, you can't get a unique act of creation wholesale.

Best custom software procurement practices
So how can procurement pros know they're getting the right price, and not getting taking to the cleaners, on custom software procurement? Here are some guidelines:

  • Use this value cheat sheet: pre-packaged software = tech to-do list; custom software = tech wish-list. Since there is no rate for technology invention, assess custom software providers based on the business value they created for past clients, not comparatively between off-the-shelf vs. custom options.

  • Factor speed of decision making into how you support your business unit heads and their partnership decisions. Be a speed facilitator, not a speed bump.

  • Treat the hiring of custom technology providers much like hiring management consultants. Both are tasked with (and will be measured by) business-change -- specifically with increased revenues or process automation. So if you’ve ever hired management consultants, you might already have a procurement paradigm for custom software.

  • If you want a markdown, be willing to compensate your technology partner for the increased profits or productivity you receive on the other end.

  • Instead of uniformly and reflexively beating up vendors, find another way to demonstrate procurement performance. On innovative technology contracts, factor in speed of approval, flexibility (novel), problem solving ability, and general helpfulness, as measured by reviews from leaders in the requesting business unit.

Businesses often try custom software when they see a chance -- often fleeting -- to grab new revenue. But the lack of neat edges on the forefront of innovation can cause some real problems for policy-driven departments like procurement.

In short, procurement leaders need to be as innovative as their fast-moving business units require. 

Engage with Oracle president Mark Hurd, NFL CIO Michelle McKenna-Doyle, General Motors CIO Randy Mott, Box founder Aaron Levie, UPMC CIO Dan Drawbaugh, GE Power CIO Jim Fowler, and other leaders of the Digital Business movement at the InformationWeek Conference and Elite 100 Awards Ceremony, to be held in conjunction with Interop in Las Vegas, March 31 to April 1, 2014. See the full agenda here.

Josh Oakhurst is the Chief Strategy Officer at Skookum Digital Works, a growing technology investment and innovation partner hiring NY, SF, and SV refugees since 2005. He's @joshoakhurst on Twitter and linkedin.com/in/oakhurst.  View Full Bio

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
User Rank: Ninja
2/19/2014 | 12:45:27 PM
Re: No Hard Deadline?

I spent many years as a software developer and I can attest to all these mistakes.  I'd settle for a building a building project apporach to software development but in many cases the seat of the pants approach is taken by CFOs and CEOs.   The key to delivery dates is a fully defined and designed deliverable that doesn't change over the time of development.  That rarely happens in the real world.  Try starting a building project when you're not sure how many floors it will contain or half way into the project two more floors are added by management.  A building contractor would never allow that to happen and if did would not have a fixed date.  However it happens most of the time in software development but its a mistake.  To allow for "fix" delivery dates the deliverables need to be short and sweet developed over not more than six months otherwise scope creep is about to creep in and destroy your time line, guaranteed.

User Rank: Author
2/19/2014 | 8:50:49 AM
No Hard Deadline?
I'm wondering how companies can manage their business planning without a hard deadline for completion. When I hear of companies building custom software, it's often because there's some really pressing need or ripe opportunity -- meeting a competitor's app offering, or a looming cost savings. Business units then often turn to outsiders because they think they'll get it faster. Would you go into a custom contract with no hard delivery date? How do you manage business unit expectations in that case?  
User Rank: Apprentice
2/19/2014 | 6:33:35 AM
Re: Really re build?
Hi Lorna,


Cloud & SaaS are delivery mediums, not reasons unto themselves to invest in better enterprise technology.

Our deployment practices match your trends. 

However, when companies decide better technology can give them a competitive advantage, increasingly, they call us because the pre-existing market (regardless of delivery method) leaves them wanting.


In short, companies are finding that their specific opportunities for unique process automation requires equally unique and progressive technology solves.

Lorna Garey
Lorna Garey,
User Rank: Author
2/18/2014 | 3:13:07 PM
Really re build?
I'm wondering what you base your premise on, that companies are choosing to build vs. buy off the shelf. What about SaaS? Our data seems to show the trend is toward a service model. For example, our InformationWeek Enterprise Applications Survey has tracked this for a few years - and SaaS use is trending up, to 46% in our June 2013 poll from 38% in April 2012 survey.

Even the dreaded ERP was cited by almost one-fifth as likely to go to the cloud.
<<   <   Page 2 / 2
IT Careers: 10 Industries with Job Openings Right Now
Cynthia Harvey, Freelance Journalist, InformationWeek,  5/27/2020
How 5G Rollout May Benefit Businesses More than Consumers
Joao-Pierre S. Ruth, Senior Writer,  5/21/2020
IT Leadership in Education: Getting Online School Right
Jessica Davis, Senior Editor, Enterprise Apps,  5/20/2020
White Papers
Register for InformationWeek Newsletters
Current Issue
Key to Cloud Success: The Right Management
This IT Trend highlights some of the steps IT teams can take to keep their cloud environments running in a safe, efficient manner.
Flash Poll