What is a 'Frankenstack'?
A group of separate systems, loosely clubbed together, usually through a one-way sync, with no single source of truth.
Sold as a 'Tech Stack' by multiple vendors.
5 tell-tale signs you have a 'Frankenstack'
5 or more different tools
& tech vendors
Your tools don't talk to each other
You're spending big on 'integration' & 'customization'
You don't know
the total cost
You're afraid of
your back office team
This terrifying 'tech stack' monster manifests in 3 forms:
MARKETPLACE OR PARTNER-DRIVEN
Recruitment vendors that have either acquired businesses and hacked together different products...or clue: they sell big on 3rd party apps in their marketplace.
THE PLATFORM PLAY
Typical examples are applications like Force.com or Microsoft Dynamics. They rely heavily on partners to deliver services and the platform itself.
BUILD YOUR OWN
A custom built mess of hardware and software. Typically stitched together over a number of years by a small team of developers to support changing business needs.
How the ‘Frankenstack’ kills growth
💀 Integration & customization nightmares
💀 Misaligned contract end dates. Uh-oh, you’re trapped
💀 Excel hell. No 2-way sync means spreadsheets, and more spreadsheets
Disconnected systems means you have data lurking across multiple tools. This equals data entry, manual reporting, and spreadsheet wrangling needs to be done in order to get the ‘big picture’.
💀 Negotiation horrors
💀 A eulogy to budgeting & ROI
💀 Welcome to the ‘Vendor Blame Game’
Ok- so you’ve spent an arm and a leg integrating various platforms. But as soon as the something goes wrong who takes ownership? Who do you go to for support? Vendors will typically blame each other rather than take accountability and help you get the issue resolved.
💀 Privacy issues creeping up on you
Every additional tool that contains data, will require additional work when data audits for GDPR and rights to be forgotten are requested. Think on that….Scary.
💀 Training, support and upgrade woes
Different vendors means separate training arrangements, separate support portals and keeping up with multiple release cycles.