Read more How Global Banks can make Acquire Hire work in Fintech using the Pirate model"> How Global Banks can make 'Acquire Hire' work in Fintech using the Pirate model - Bank Automation News
Bank Automation News

No products in the cart.

Subscribe
  • News
  • Data
  • Transactions
  • Events
    • Bank Automation Summit
    • Apply to Speak
    • Apply to Demo
  • Podcast
  • WEBINARS
    • On-Demand Webinar: Emerging fintechs: New technologies you need to know now
    • Webinar Library
Log In
No Result
View All Result
  • AI
  • Business Banking
  • Core
  • Cloud
  • Payments
  • Retail Banking
  • Risk & Security
Bank Automation News
  • News
  • Data
  • Transactions
  • Events
    • Bank Automation Summit
    • Apply to Speak
    • Apply to Demo
  • Podcast
  • WEBINARS
    • On-Demand Webinar: Emerging fintechs: New technologies you need to know now
    • Webinar Library
BAN PLUS
Log In
No Result
View All Result
Bank Automation News
No Result
View All Result

How Global Banks can make ‘Acquire Hire’ work in Fintech using the Pirate model

Bernard LunnbyBernard Lunn
February 24, 2015
in Archive
Reading Time: 7 mins read
0
Share on Facebook

Acquire Hire tends to mean:

  • The venture raised small amounts of capital (Friends & Family, Angels) but could not do a Series A and so was running out of cash.
  • The announcement does not show the amount the acquirer paid. This protects the reputation of the Founders and Investors who claim “Exit” on their track record.
  • The Investors usually don’t make a return and may lose money. Early stage investing is a win some/lose some game, so that is OK (as long as the Angel is reasonably diversified).
  • The Founders get a pay check and (this is the bit that matters) get to see their vision become reality.

I am now going to attempt to channel John Cleese who had a hilarious sales training video about “how to lose a sale” which is more memorable than all the “how to win a sale” materials.

How to mess up an Acquire Hire deal:

  • Lock them in with a 1-2 year earn-out period so that, no matter how much they hate working at your company, they will collect a pay check and watch the clock till 5pm rolls around and then after 1-2 years they will leave taking everything they learned at your company to their next startup.
  • Take the passion they have for the product that they built and kill it on the same day that you kill their product. You have now converted the passion that makes engineers want to work crazy hours and think about problem solving whenever they have a spare moment and turn them into just another clock-watching average engineer.

The fundamental mistake is to say:

“We found a great team that built a lousy product”

Of course, nobody says “lousy product”, but actions speak louder than words. If you kill the product, your actions say it is lousy, even if the corporate PR cranks out something about “not fitting our strategic direction”.

Unless you think it is a great product, pass on the deal.

The product has clearly not achieved Product Market Fit (PMF). If it has achieved PMF, VC money will flood in and you can no longer close an Acquire Hire deal. So you have to think the product is potentially great but needs some combination of:

  • Time for the puck to catch up. Some products are just ahead of their time. The entrepreneur skated to where the puck was headed but got there before the puck got there. That might sound cool, but it is a venture killer. It usually means they assumed that something external would be in place (e.g. mainstream adoption of global wallets as a precursor to Micropayments). In the meantime, they ran out of cash.
  • Regulatory approval. The lean startup model is tougher in Fintech. To launch a Fintech product where money changes hands you need things like regulatory approval and 5 nines reliability. Facebook may use Whatsapp for Payments, but only after Facebook has secured the necessary regulatory approval. Launching a Fintech startup without these will ensure that you do NOT achieve PMF. Launching a Fintech startup with these will ensure that it takes longer and costs more money to launch. The Zuckerberg Faceboook story – a few months of coding and then it catches fire – is inspiring but applies to the social media era and is a mirage when it comes to Fintech.
  • Minor UX change. The growth hackers know what it takes to get users to click the button that leads to engagement that finally leads to revenue. If you find a team that is running out of cash/time but says they know exactly what they need to do to get PMF but that just needs a few more months – they could be delusional or they could be right.

Culture is partly driven by deal and organizational structure. You cannot change the culture of the whole bank quickly enough to make the engineers feel buzzed about going to work on Monday morning. If you integrate the Acquire Hire team into your existing culture, you will make all the mistakes listed above in “how to mess up an Acquire Hire deal”. However if you simply buy a stake or buy the whole business and it has no connection to the Bank’s strategic objectives, all you are creating is a VC/PE firm within the Bank. While that VC/PE unit within the Bank may generate good profits, it does not create the needle-moving transformational change. The people running the VC/PE unit compete with pure-play VC/PE firms and eventually they find themselves focused on purely financial returns on a deal, making the Bank’s strategic objectives a minor consideration at best.

So there needs to be a middle ground between jamming a few engineers into the org chart and having them simply view your Bank as a VC.

The new model that can make the Acquire Hire model work needs to learn from what Google did with Android, which was inspired by what Steve Jobs did with the Mac team. I describe this in my post on Bank culture. Steve Jobs – as so often – is the great inspiration with the way he got the Mac product built within Apple by a team that were encouraged to view themselves as “pirates” within the organization. Google took the same approach when they acquired Android; they made sure that Andy Rubin and team wanted to stay at Google to help transform Google for the mobile era.

The Google Android story illustrates 3 key points that will help Banks use Acquire Hire and other acquisitions to create transformational change:

  • The mandate has to come from the CEO. This is a cultural shift at the top because CEOs and Boards are supposed to spend time on big deals that make a difference to the next few quarters. Spending time on a deal that might be only valued at a few $ million and that could take many years to move the revenue needle, is not normal.
  • Being early is OK if you spend very little. This is the “sandbox” era when the job is simply to get a great team, align them to a big blue ocean market opportunity and then get out of the way. This is pre PMF. The Google acquisition of Android in 2005 for $50m was Pre PMF.
  • Be prepared to spend a lot Post PMF. This is when as Peter Vander Auwera of SWIFT Innotribe so eloquently puts it – it is time to get innovation out of the sandbox. Google made many more acquisitions in mobile. Many were traditional M&A deals for acquiring current revenue and profit. Others were bolt on deals. However, all of this was possible because of a clear strategic vision very early of “where the puck is headed”, plus an entrepreneurial team that was focused on the big objective. In simple terms:
  • Pre PMF = Cheap and in the Sandbox (protect the fragile innovation)
  • Post PMF = Expensive and Grown Up (get out into the real world and conquer it).

The key structural issue is how to operate Post PMF. Google in 2005 was still able to motivate Acquire Hire teams with Google stock options. Banks cannot easily do that today, because a) the amount of stock options that engineers can get in a bank are limited and b) the chance of a 10x upside in the Bank stock is unlikely (but the normal expectation, however delusional, in a startup).

The way to get around this is to take the acquired venture through 3 stages:

  • Stage # 1: Pre PMF. This is within the sandbox, but keeping the brand independent. This stage costs very little. The team is encouraged to think like pirates (aka like entrepreneurs) knowing that Stage # 2 is the next milestone.
  • Stage # 2: Post PMF. This is when the Bank can bring in outside investors and get the venture out into the real world. The Bank can keep a right of first refusal to enable Stage # 3. That does limit the upside to some degree but a) the risk is reduced for investors so the deal should still be attractive and b) the valuation multiple range is not so wide that one cannot get an independent valuation to set the price.
  • Stage # 3: Post IPO scale. This is when the Bank can bring it back in-house to get to Bank Scale. Post IPO scale is typically $100m plus revenue. The Bank wants to get this to $1 billion plus revenue to move the needle. This is when the Bank can start to deploy other assets such as brand, cross-selling and capital because the venture is already mature enough for this kind of commitment.

It is Stage # 2 that is counter-intuitive to Banks. Why sell off a stake in order to only buy it back in at a later date? The Bank does not lack the capital to fund this expansion stage. There are four reasons to do this:

  • The best VCs have real expertise in scaling young ventures. Their money is irrelevant at this point. The Bank has money. The Bank does not have a track record to scaling a venture from PMF to $100m plus annual revenues.
  • Stop the young venture from being highjacked by an existing division of the Bank. That division may feel threatened or might want to grab the opportunity. This will kill the innovation because “when you have a hammer, everything looks like a nail”.
  • The team brought into the Bank in the Acquire Hire deal can now be motivated by what got their juices flowing in the first place. You now have a carrot which is far more effective than stock options in your bank and it does not cost you anything unless they create real value in the market.
  • This can also help get over one of the trickiest issues in Acquire Hire deals which is the lack of alignment between Investors and Founders. The Founders do OK in Acquire Hire deals. Investors often lose out. The possibility of bringing investors back in at the Post PMF Stage # 2 offers a way to “sweeten the deal”.

If a venture makes it through all three stages, Banks have innovation that moves the needle. More importantly, the CEO can point to the culture that created this rapid value creation as the culture to be emulated Bank-wide. By this stage the innovation cannot be shot down by naysayers because is neither a) wild, wishful thinking, but real hard revenue growth and b) it is not external disruptive innovation but “our disruption”. In short, this 3 stage process is a way out of the innovator’s dilemma.

 

Tags: Blue OceanInnovation As A Banking Practiceinnovation capital
Previous Post

SmartPesa could bring the Underbanked into the credit economy

Next Post

No, Google Did Not ‘Level the Playing Field’ Buying Softcard

Related Posts

Image by CanStock
Archive

Blend Labs integrates acquisition’s mortgage automation process

August 20, 2021
Photo by CanStock
Archive

Chilean fintech looks for slice of giant money transfers market

August 5, 2021
Image by CanStock
Risk & Security

Listen: How banks can protect themselves against cybersecurity risks

August 3, 2021
Next Post

No, Google Did Not 'Level the Playing Field' Buying Softcard

Please login to join discussion

Stay Informed with Our Newsletters

EMERGING FINTECH DIRECTORY

Emerging Fintech Directory

The Buzz Podcast

RETAIL BANKING

Huntington Bank’s new branch in Spartanburg

Huntington Bank resolves outage

May 7, 2025
bank

Barclays, Banco Santander, Lloyds plan product expansion

May 5, 2025
satisfactiin

Online banks lead FIs in customer satisfaction

May 2, 2025

SPONSORED

Just Released! 2025 Strategy Benchmark

May 1, 2025

Leverage Treasury Management to Turn Fraud Prevention Into a Strategic, Revenue-Generating Opportunity

April 1, 2025

A growth mindset in banking requires AI

March 27, 2025
  • About Us
  • Help Center
  • Contact Us
  • Privacy Terms
  • ADA Compliance
  • Advertise

 Manage Cookie Consent

Connect

twitter linkedin podcast podcast podcast
© 2025 Royal Media
No Result
View All Result
  • NEWS
    • All News
    • AI
    • Business Banking
    • Core
    • Cloud
    • Payments
    • Retail Banking
    • Risk & Security
  • DATA
  • TRANSACTIONS
  • EVENTS
    • Bank Automation Summit
  • PODCAST
  • WEBINARS
    • Upcoming Webinar
    • Webinar Library
  • SUBSCRIBE
  • Log In / Account

Welcome Back!

Login to your account below

Forgotten Password?

Retrieve your password

Please enter your username or email address to reset your password.

Log In
No Result
View All Result
  • NEWS
    • All News
    • AI
    • Business Banking
    • Core
    • Cloud
    • Payments
    • Retail Banking
    • Risk & Security
  • DATA
  • TRANSACTIONS
  • EVENTS
    • Bank Automation Summit
  • PODCAST
  • WEBINARS
    • Upcoming Webinar
    • Webinar Library
  • SUBSCRIBE
  • Log In / Account

THIS WEBSITE USES COOKIES

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “I CONSENT”, you consent to the use of ALL the cookies.

Cookie settingsI CONSENT

Review our Cookie Policies
.
Manage Cookie Consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
__cfruidsessionCloudflare sets this cookie to identify trusted web traffic.
__RequestVerificationTokensessionThis cookie is set by web application built in ASP.NET MVC Technologies. This is an anti-forgery cookie used for preventing cross site request forgery attacks.
_abck1 yearThis cookie is used to detect and defend when a client attempt to replay a cookie.This cookie manages the interaction with online bots and takes the appropriate actions.
34f6831605sessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
a64cedc0bfsessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
ak_bmsc2 hoursThis cookie is used by Akamai to optimize site security by distinguishing between humans and bots
ARRAffinitysessionARRAffinity cookie is set by Azure app service, and allows the service to choose the right instance established by a user to deliver subsequent requests made by that user.
ARRAffinitySameSitesessionThis cookie is set by Windows Azure cloud, and is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session.
AWSELBsessionAssociated with Amazon Web Services and created by Elastic Load Balancing, AWSELB cookie is used to manage sticky sessions across production servers.
bm_sz4 hoursThis cookie is set by the provider Akamai Bot Manager. This cookie is used to manage the interaction with the online bots. It also helps in fraud preventions
cf_ob_infopastThe cf_ob_info cookie is set by Cloudflare to provide information on HTTP Status Code returned by the origin web server, the Ray ID of the original failed request and the data center serving the traffic.
cf_use_obpastCloudflare sets this cookie to improve page load times and to disallow any security restrictions based on the visitor's IP address.
CONCRETE5sessionThis cookie is set by the provider Concrete5 web content management system. This is a necessary cookie used for maintaining the user session between pages.
connect.sid1 monthThis cookie is used for authentication and for secure log-in. It registers the log-in information.
cookielawinfo-checkbox-advertisement1 yearSet by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
cookiesession11 yearThis cookie is set by the Fortinet firewall. This cookie is used for protecting the website from abuse.
crmcsrsessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
ep20130 minutesThis cookie is set by Wufoo for load balancing, site traffic and preventing site abuse.
JSESSIONIDsessionThe JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application.
LS_CSRF_TOKENsessionCloudflare sets this cookie to track users’ activities across multiple websites. It expires once the browser is closed.
PHPSESSIDsessionThis cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.
sxa_sitesessionThis cookie is used to identify the webiste visitor's session state across page requests on server.
ts3 yearsPayPal sets this cookie to enable secure transactions through PayPal.
ts_c3 yearsPayPal sets this cookie to make safe payments through PayPal.
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
wordpress_test_cookiesessionThis cookie is used to check if the cookies are enabled on the users' browser.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
CookieDurationDescription
__cf_bm30 minutesThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_zcsr_tmpsessionZoho sets this cookie for the login function on the website.
663a60c55dsessionThis cookie is related to Zoho (Customer Service) Chatbox
bcookie2 yearsLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.
bscookie2 yearsLinkedIn sets this cookie to store performed actions on the website.
e188bc05fesessionThis cookie is set in relation to Zoho Campaigns
geosessionThis cookie is used for identifying the geographical location by country of the user.
iamcsrsessionZoho (Customer Support) sets this cookie and is used for tracking visitors (for performance purposes)
langsessionLinkedIn sets this cookie to remember a user's language setting.
languagesessionThis cookie is used to store the language preference of the user.
lidc1 dayLinkedIn sets the lidc cookie to facilitate data center selection.
optimizelyEndUserId1 yearOptimizely uses this cookie to store a visitor's unique identifier which is a combination of a timestamp and a random number. Different variations of web parts are shown to users that optimizes the website's user experience.
tableau_localesessionTableau uses this cookie to determine the preferred language and country-setting of the visitor - This allows the website to show content most relevant to that region and language.
UserMatchHistory1 monthLinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
CookieDurationDescription
AWSELBCORS20 minutesThis cookie is used by Elastic Load Balancing from Amazon Web Services to effectively balance load on the servers.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
CookieDurationDescription
__gads1 year 24 daysThe __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites.
_ga2 yearsThe _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_gcl_au3 monthsProvided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
_gid1 dayInstalled by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
ajs_anonymous_idneverThis cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before.
ajs_group_idneverThis cookie is set by Segment to track visitor usage and events within the website.
ajs_user_idneverThis cookie is set by Segment to help track visitor usage, events, target marketing, and also measure application performance and stability.
browser_id5 yearsThis cookie is used for identifying the visitor browser on re-visit to the website.
CONSENT2 yearsYouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
sid1 yearThe sid cookie contains digitally signed and encrypted records of a user’s Google account ID and most recent sign-in time.
uid1 yearThis is a Google UserID cookie that tracks users across various website segments.
vuid2 yearsVimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website.
WMF-Last-Access1 month 21 hours 5 minutesThis cookie is used to calculate unique devices accessing the website.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
CookieDurationDescription
_dc_gtm_UA-1038974-41 minuteUsed to help identify the visitors by either age, gender, or interests by DoubleClick - Google Tag Manager.
_fbp3 monthsThis cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.
_pxhdpastUsed by Zoominfo to enhance customer data.
fr3 monthsFacebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.
IDE1 year 24 daysGoogle DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.
test_cookie15 minutesThe test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
VISITOR_INFO1_LIVE5 months 27 daysA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSCsessionYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devicesneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt-remote-device-idneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt.innertube::nextIdneverThis cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
yt.innertube::requestsneverThis cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
CookieDurationDescription
049fc2ef5beb27056b07d9e4c4d13fd3sessionNo description
akaalb_http_misc_subssessionNo description
AnalyticsSyncHistory1 monthNo description
BIGipServermsocu-web-2-rr.webfarm.ms.com.10882sessionNo description
bm_misessionNo description available.
CX_4061522881 yearNo description
DCID20 minutesNo description
debugneverNo description available.
DrupalVisitorMobilesessionNo description available.
ep2033 monthsNo description available.
frbatlanta#langsessionNo description
geo_info1 yearNo description available.
GoogleAdServingTestsessionNo description
li_gc2 yearsNo description
loglevelneverNo description available.
loom_anon_commentsessionNo description available.
loom_referral_videosessionNo description
mkjs_group_idneverNo description available.
mkjs_user_idneverNo description available.
MorganStanley.ClientServ.Common.IPZipAccess.IPZipCookie.DEFAULT_COOKIE_NAMEpastNo description
NSC_us_nbsl-83+63+21+25-91sessionNo description
nyt-a1 yearThis cookie is set by the provider New York Times. This cookie is used for saving the user preferences. It is used in context with video and audio content.
nyt-gdpr6 hoursNo description available.
nyt-purr1 yearNo description available.
OCC_Encrypted_CookiesessionNo description
polleverywhere_session_id14 daysNo description
ppnet_2020sessionNo description available.
ppnet_2777sessionNo description available.
reuters-geosessionNo description
shell#langsessionNo description
smcx_0_last_shown_atsessionNo description available.
tableau_public_negotiated_localesessionNo description available.
vary1 monthNo description
www#langsessionNo description
X-Vive-CountrysessionNo description
xn_uuid1 monthNo description
Save & Accept
Powered by CookieYes Logo