Welcome to the Corporate Gibberish Generator™ by Andrew Davidson. andrewdavidson/at\andrewdavidson/dot\com
Enter your company name and click
"Generate" to generate several paragraphs of corporate gibberish
suitable for pasting into your prospectus.
(The gibberish is geared more toward Internet and technology companies.)
Your budget for envisioneering should be at least one-third of your budget for architecting.
We here at Refrigeration Engineer believe we know that it is better to enhance extensibly than to upgrade ultra-perfectly.
Our technology takes the best features of Perl and PNG.
We think that most B2C entry pages use far too much ASP, and not enough AJAX.
We will augment our capability to drive without diminishing our power to scale.
Imagine a combination of WAP and XSLT.
If all of this sounds alarming to you, that's because it is!
We frequently matrix one-to-one web-readiness. That is a terrific achievement taking into account today's market conditions!
Do you have a game plan to become revolutionary?
Imagine a combination of ActionScript and OWL.
What does the commonly-accepted standard industry term "user interfaces" really mean?
Our leading-edge feature set is second to none, but our enterprise e-commerce and user-proof operation is invariably considered a terrific achievement.
We believe we know that if you revolutionize dynamically then you may also scale vertically.
Have you ever wanted to recontextualize your back-end feature set? Right now?
We will envisioneer the capability of systems to engage.
What does it really mean to benchmark "robustly"?
What does the standard industry standard industry term "process management" really mean?
We often disintermediate subscriber-defined e-services. That is an amazing achievement considering the current and previous fiscal year's conditions!
If all of this comes off as discombobulating to you, that's because it is!
We think that most backward-compatible web sites use far too much IIS, and not enough C++.
The metrics for re-purposing are more well-understood if they are not frictionless, e-business, virtual.
The collaborative CAE factor is revolutionary.
What does the jargon-based commonly-accepted term "re-purposing" really mean?
What does the standard industry term "action-items" really mean?
We invariably enable innovative, cross-media C2C2B, front-end 60/60/24/7/365 branding. That is a remarkable achievement taking into account the current and previous fiscal year's cycle!
What do we orchestrate? Anything and everything, regardless of abstruseness!
Have you ever been unable to cultivate your B2B2C feature set? Without having to learn SMIL?
What do we morph? Anything and everything, regardless of namelessness!
We think that most revolutionary splash pages use far too much RDF, and not enough RDF.
Think fractal. Think affiliate-based. Think back-end. But don't think all three at the same time.
What do we synthesize? Anything and everything, regardless of abstruseness!
We realize that if you extend virtually then you may also revolutionize intuitively.
We will streamline the term "fractal".
We will architect the ability of supply-chains to integrate.
We think that most customized, real-time web-based applications use far too much PGP, and not enough PGP.
Quick: do you have a ubiquitous strategy for monitoring emerging experiences?
Do you have a plan to become fractal?
Without world-class, robust branding management monitoring, you will lack Total Quality Management.
Have you ever had to enhance your subscriber-defined feature set? Free?
We think that most wireless entry pages use far too much Python, and not enough RDF.
A company that can seize faithfully will (someday) be able to scale fiercely.
The global technologies factor can be summed up in one word: virally-distributed.
If you innovate efficiently, you may have to grow perfectly.
We realize that it is better to utilize virally than to scale proactively.
Think 60/24/7/365, mission-critical.
The branding factor is transparent.
What does the term "super-infinitely reconfigurable, synergistic TQM" really mean?
Our functionality is unparalleled, but our robust bandwidth and simple configuration is always considered a terrific achievement.
Without well-planned wireless bleeding-edge TQM, relationships are forced to become revolutionary, real-time.
Our technology takes the best aspects of C++ and SMIL.
Imagine a combination of Python and J++.
Have you ever been pressured to exploit your feature set? With one click?
We usually architect enterprise TQC. That is an amazing achievement when you consider this quarter's cycle!
The metrics for backward-compatible, enterprise mega-branding are more well-understood if they are not revolutionary.
Think nano-holistic.
The super-cyber-C2C2C CAE factor is compelling.
The systems factor can be summed up in one word: out-of-the-box.
Is it more important for something to be dynamic or to be virtual?
Imagine a combination of XHTML and VOIP.
Think macro-1000/60/60/24/7/365.
What do we harness? Anything and everything, regardless of anonymity!
We pride ourselves not only on our feature set, but our user-proof administration and simple operation.
What does the term "ultra-social networks" really mean?
Refrigeration Engineer practically invented the term "bloatware".
Imagine a combination of PGP and DOM.
Without re-sizing, you will lack client-focused, intuitive experiences.
We will strategize the capacity of platforms to mesh.
We think that most back-end splash pages use far too much XMLHttpRequest, and not enough Java.
A company that can orchestrate defiantly will (eventually) be able to leverage fiercely.
We pride ourselves not only on our functionality, but our simple administration and easy operation.
We will benchmark the capacity of paradigms to deploy.
Your budget for branding should be at least three times your budget for embracing.
The capacity to deliver iteravely leads to the capability to implement proactively.
Is it more important for something to be back-end or to be holistic?