Cloud

Meet Stephy, my clawdbot

Note: Updated on February 12, 2026 to reflect the name change. While most of this post still stands I encourage you to look at https://openclaw.ai/ first if you're deploying it in the future as this product has changed the name twice since I've mentioned it -- and I'm sure best practices will too.

I've been experimenting with AI for years now and this is the first project I've become absolutely obsessed with. Don't get swayed by supernatural Twitter claims by lying "influencers" - no, it will not print money, no it will not make you a fortune trading crypto while you sleep, no it cannot run your entire business - as a matter of fact it's a clunky pile of #vibecode npm nightmares that barely functions. When it does work though - it's miraculous. It's why I named mine Stephy, after the best admin/marketing miracle worker I ever had a pleasure of working with.

What is it? ELI5

It's a robot that lives in your computer, with access to the same tools and web services you have access to. You chat with it through your favorite chat app and tell it what to do. It has a soul, personality, heartbeat, and a scheduler that enables it to remember your interactions and perform tasks for you on schedule.

At it's core it's a npm package that uses an LLM (OpenAI, Codex, Claude, etc) to coordinate and execute tasks based on instructions it keeps in markdown files. As you talk to it through your chat app (Telegram, Slack, WhatsApp, etc) it references those files for instructions on how to perform a task, how to respond to you, which tools to use, etc. It also has skills which are npm packages that enable it to interact with web services and tools to get the job done. Over time as your md text files grow and you get the context down to exactly what you want, it can perform your tasks on a schedule in a cron it maintains on it's own.

I'm sold, where do I put it?

Resist the temptation to buy a Mac mini. I know it's all the rage right now and the potential is there -- but it's pretty half baked and just like every other npm project out there you're likely to mess it up adding vibe coded skills and broken dependencies. YMMV.

You don't need a dedicated PC or a laptop for this, unless you expect to have it use your Chrome browser (ffs don't!) or edit video the resources of a free VPS from Amazon or Oracle Free Cloud are more than enough. I have one running on Raspberry Pi 4 for house stuff and it's just as happy as the one that lives in a 16GB Proxmox container in my data center. If you don't have Linux skills or aren't in a mood for a learning curve to setup the free VPS instance, check out VPS providers like RackNerd or Digital Ocean.

February Update: This is the friendliest YouTube guide I've seen on getting started but it's as outdated as this post - AI development moves fast! I still recommend watching it just so you can get an orientation on how to install the package, ssh tunnel, and a Telegram bot https://www.youtube.com/watch?v=3DBpfB0ao50

How do I install it?

The installation is actually the simplest part of the process, you just run this command in your shell:

curl -fsSL https://openclaw.ai/install.sh | bash

This process will install all the required packages and the next thing you need to do is "hatch" your bot.

openclaw onboard

You're now setting up your bot and I cannot encourage you highly enough to keep the documentation handy. I have only one recommendation here: when it comes to gateway bind it to 127.0.0.1. Idiots are binding their gateway to 0.0.0.0 and getting pwn3d left and right so please don't do that. Lot's of newbie YouTube walkthroughs are sponsored by VPS providers whose IP ranges are well known and it's trivial to nmap the whole range for an open 18789 port and steal your credentials. Don't be stupid.

Once you finish deploying your bot and onboarding it you have several ways of interacting with it. My favorite to get started is openclawd tui which will give you immediate access to your bot through the same terminal interface you used to install it. Give your bot a personality, name, what you want it to call you and how you prefer to interact with it.

If you'd rather interact with it through the powerful web interface, bring up an SSH tunnel. I'm assuming you've downloaded your VPS issued ssh key to your ~/.ssh so mind your paths and filenames

ssh -L 18789:127.0.0.1:18789 vladbot@demo.vlad.net -i ~/.ssh/vladbot-demo-vlad-net

vladbot@demo.vlad.net is my username and my vps server, the part at the end is path to my ssh key. Yours will be different but once you launch this you'll be able to talk to your clawdbot at https://localhost:18789

What else do I need?

Next you have to pick a chat agent. I've personally used it on my infrastructure through Telegram, WhatsApp, Slack and Mattermost but it supports a TON of chat platforms. I loathe Facebook properties and I've found that it's the most reliable on Telegram. On Telegram you just start a chat with Botfather, /newbot and follow the instructions to get your bot. By default this is locked down to you and tui or webUI make configuring the chat part of this super easy.

Some Tips

Most of what you see on social media is pure hype and fantasy. Remember these dudes hype and cut scenes to get the clicks and go viral... and if you follow them step by step at best you're going to get hacked. Here are some of my suggestions when it comes to use:

  1. Make backups. Keep your bots markdown files backed up often. This is perhaps the best way to learn how clawdbot works, instruct it to make backups in ~/backups/ every day at midnight and report back. You will mess up your bot and your config as you play with it and copying back the *.md files will get you back to the experience quickly without having to recreate everything.
  2. DO NOT GIVE IT ACCESS TO YOUR ACCOUNTS. But Vlad, how am I going to get rich if I don't give it access to my Polymarket and Coinbase accounts? Just like every other crypto influencer that hasn't blown their brains out in the back of a rented Lambo - you won't. And if you're reading this post you likely don't have a body for OnlyFans so calm down and give your bot it's own accounts. It is much easier to create a forwarding rule for mail or to share a read-only calendar than it is to get your accounts back once someone has hacked it.
  3. Take it easy with skills and plugins. Remember that most of these addons are community built and have not gone through any sort of a security audit. Same caveats as Chrome plugins. It might be able to run your entire company but it also might send all your data to an intermediary, use your brain.

Have fun!

If you've ever used ChatGPT or Claude or CoPilot you know how much fun they can be but you've also probably experienced hallucinations and outright wrong answers. What makes Clawdbot special in my experience is the memory and instructions. It knows how to interact with the LLM to get the answer that I am looking for and it knows how to format it right. By giving it additional instructions and corrections it keeps adding specs to your markdown files which makes it far more fun and personable that ChatGPT - even when used in context with projects.

Leveraging automation with memory feels like a giant new step in the AI evolution. Happy to be alive to see what this thing does next.

Saa(pocalyp)S(e)

It has been years since I've felt like I've had a thought I wanted to share that needed more than 140 characters to fully explain. In the two years that have passed since my last blog post I have mostly been trolling my developer friends with AI and using it to learn and build cool stuff. With each passing month, those jokes get less and less funny as the AI tools become more and more sophisticated... to the point that I have no doubt this stuff is going to automate most of the present day white colar work.

For context, the last time I published a post on Vladville I was still spending my whole day in Microsoft Office. Any software solution that needed to be built required meetings, planning, skilled designer, skilled developer, documentation writer, training and marketing collateral, and most expensive of all - time.

Few months ago I got dragged into a Slack huddle at one of my businesses and the team was discussing a diagnostics and troubleshooting SaaS solution, contemplating developing one vs. licensing, frameworks, security, resources, timeline, all the usual software architecture stuff. I was at home, enjoying The Great Garlic 6" (highly recommended) sub and typing in bits and pieces of their conversation into Claude AI. Naturally, what it spit out was absolute garbage but I kept on snacking and tweaking it and as the group was ready to wrap the meeting I asked if I could share my screen. I showed them a fully functional SMTP header analyzer, to many laughs and mockery.

Me: Ok, I know it's ugly but watch this "Please make the interface minimalist and beautiful, use Tailwinds CSS. Use a blue color scheme. Oh, and add the latency between each hop, if it's under 60 seconds only show the seconds s, if it's over 60 seconds show the minutes m : seconds s.

Team: Laughing, please STOP!!!

Me: OK, now I want you to add a graph. Make it a bar graph with the hostnames on the Y axis and seconds latency on the X axis.

Team: STOP!!!

This went on for a few minutes and the laughter definitely died down while the STOP turned more into a nervous whimper. Before I even finished my Subway sandwich I had a complete and functional project that the team of 8 highly competent people was going to spend an entire month or more putting together, testing, designing, optimizing, securing. If that sounds like a lot, consider that the SaaS we were going to license this solution from would have cost us several thousand dollars - per month.

You're already dead, you just don't know it yet

The AI tools have only gotten better in the few months since that huddle and the era of highly profitable SaaS solutions may be looking at a sunset. The way you make money as a SaaS business is by dragging every employee into it. It doesn't work if everyone isn't working in the same system, with the same data, and the same SOP. There is no money in solving a small problem so often these platforms become bloated in order to maximize profits deliver great value.

The way you deliver even more value is by tiering your solution. You want to secure your cloud service with MFA, LDAP integration so you don't have to manage and reconcile accounts across different platforms, that's gonna be extra! Mobile apps? Oh that's gonna be extra. You want to remove branding? Call for pricing. Hint: It's gonna be a lot. And you're gonna need a software maintenance and support contract too.

Meanwhile, the real world is moving from co-pilot to auto-pilot. AI agents and RAG (Retrieval Augmented Generation) are driving efficiency at a level that obsoletes people. You see, as a SaaS developer you spend a lot of time designing dashboards, data grids, charts, reports and spend an eternity trying to deliver information to a human. Information, that in context and with expertise, can lead to better business decision making. Well, if the AI agent is the one consulting you on a business process, it does not care about the menu, the styling of the report, the workflow, the dark theme, or the features - it just consumes the API and data. All that extra stuff we do for humans.. rapidly loses value.

As does the overall value of a massive platform. As data based decisions go from co-pilot to auto-pilot, all those human "creature features" become irrelevant. Inedvidably, the power users and large organizations suddenly need way less seats. The licensing model built on "pay-for-features" suddenly has way fewer users and the entire model collapses.

That's not even accounting for the resurgence of middleware, where companies can quickly mock up a software solution with relatively little expertise. I'm old enough to remember when Visual Basic came out and suddenly high school kids that were editing the yearbook last year were building software interfaces with the same basic skill set. The sales conversation around SaaS goes from "what problem does your software solve" to "how does your software work with my AI agent, or integrate better into our workflow"

And that's a difficult environment in which to make a profitable software business. Or to justify a career in software development.

It's actually worse..

In my retirement, I've actually moved to a Mac. I know, I know, I feel dirty about it too but the transparent way in which AI and agent workflows are integrated makes me far more efficient. Instead of sitting in Outlook all day and setting Benjamin's on fire every year for every PC, Apple Mail shows me a quick summary of the whole email instead of just the sender and the subject. I know I'm not the only one based on the amount of people big tech seems to be sending to unemployment lately.

I'm not saying that this is going to wipe out SaaS, or that it can even affect solutions that require delivery of millions of transactions at scale. But it's going to make the business of software a lot more difficult when people aren't paying for features but for outcomes. When you're getting paid per transaction it's a lot harder to make a massive profit off a company licensing software that most of the employees barely use.

Yet, that's been the model of wealth for Microsoft, Adobe, Oracle, and most other Chrome tabs on your work PC.

P.S. I have a shoulder surgery coming up that's going to put me on the sideline for a while. It's going to be a minute before I can come back to the gym, November Project, motorcycles, and cool nature stuff. I am going to test my hypothesis and see if I can replace something we charge a fortune and some things we pay a fortune for.... with something free.

Do Something

About a year ago, I retired. More on that later.

 

                          What if an outage meant compromise/breach?

Over the past year or so, I've done quite a bit in terms of email security research, bouncing ideas at random hours and even more random levels of sobriety with my team @ExchangeDefender. And while there is a thin line between genius and insane, there is a very clear red line when it comes to compliance, standards, international/national/state/industry/blah regulations that are governing email at an increasingly detrimental value to the email user. At one point earlier this year a large email provider went lights out for an entire day and this post caught my eye:

"We're rerouting email. We cannot afford for the client to be down, but we also can't just point it direct and risk that someone clicks on something that gets them hacked."

unknown/paraphrased

Since then I've talked to some of my industry friends about a concept of a non-profit email research service focused on sharing security information. Much like my pile of Corvette projects, it remained in random stages of discussion and whiteboarding.

Then Dorian came up. Ever since the earliest days of ExchangeDefender (and it's ETRN predacesor at DialISDN) we've offered free email failover MX service to folks in a way of a disaster, and it's always been popular. But thanks to the red tape, freebie anonymous access to the ExchangeDefender would blow compliance on many levels. That bugged me but, really, not much I can do.

WineFast forward to Friday afternoon, while enjoying a lovely glass of pinot noir waiting for my 4-hour-delayed flight... Dorian got upgraded to a category 4 hurricane. My flight got delayed again due to storms in Dallas, and my glass of wine got upgraded to a bottle. I called my boy Travis (CTO, ExchangeDefender) and after hearing "No" about 94 times, he agreed to vlan off some decomissioned hardware for the project. Three days of writing, testing, and tweaking the first inbound node went up at inbound.xdwall.com. It's already up and running and queueing/delivering mail for servers in the way of this storm.

Once I come up with a less stupid name, I will announce it here. Once the nonprofit is organized, licensed, etc we'll make a big deal of it but here is the skinny:

$x is an email security/resiliancy project. Nearly all the security problems organizations have start with an email and relying on the user to stop them is just simply naive. Commercial email operations are more concerned about selling advertising / productivity software and devices than they are about a working communications product, further discouraged by an excessive regulatory process that is slowing down innovation. I am building $x as a free email security layer, designed to provide a layer of common sense security at the edge of the network.

DorianMore on all that later. If you are in the way of the storm, send me an email at vlad@exchangedefender.com and point your secondary MX (of a significantly higher weight) to inbound.xdwall.com.

We'll make it through this storm together. There will be more storms. There will be stronger storms. And when we're not fighting mother nature, we'll be fighting a random assortment of Russians, Chinese military, and an occasional African prince that really, really, really needs to get his fathers money out of the country. Worst case scenario, an unscrupulous marketing scammer will be forced to get a real job. And no matter how funny, all of these people pose a direct threat to you. So.. you can sit at the airport and get drunk or you can do something.

Profiting vs. Commoditizing

Email is a commodity as far as IT goes. Has been for a better part of a decade and with the few exceptions (compliance, audit, disaster recovery) not a highly profitable task without massive scale.

Two years ago we started offering migrations as a part of our hosted email model, then extended that with migrations of compliance archiving products as our competitors started going out of business, started piling on support, billing, etc to get our partners a profit profile that is consistent and virtually eliminates the costs associated with email support entirely.

As you may imagine, this is something that appeals to small business IT the most as they have the least amount of time and flexibility to provide these services around the clock profitably, consistently and effectively. And, much like myself, you’d be completely wrong in that assumption.

Here is what my typical SMB partner discussion goes like:

Vlad: So here is what we do [... blah blah ...] does any of that seem like it would help.
Partner: We resell Office 365/Google Apps/Appliance X but we don't make much margin there.
Vlad: Right, so (repeating) here is what we do that eliminates the cost structure of it all..
Partner: But that costs more.

Sometimes it gets tiring trying to convince people whose business model is convincing other businesses to outsource IT to outsource the most expensive and least profitable piece of that business. But that’s my job and here is the other part of it..

As I’ve been talking here for the past year or so, this is the gold rush moment for SMB IT – and we’re doing all we can to help partners all over the spectrum to get to the cloud faster and more profitably. The more clients you have the larger market you serve the more services you can provide. We’ve spent better part of the year developing those and we’ll be launching them in 2016.

Here is how I see it: The only thing that matters at the end of the day is the service, not the price. We’ve raised the price in 2014 and will likely do so in 2016 and we’ve grown right along with it – people don’t sit around trying to knock $1 off the price (some, like me, might try to do so just as a sport) but they go livid when things don’t work. That’s how we continue to build the business and how we view the future – yeah, we’ll lose people to Outlook.com or Gmail but I can show you the numbers of our archiving, encryption, compliance and services that come on top of it that people love to pay for.

I used love for a reason, mostly because I hear it a lot. When things go well and when things go wrong. “I love you guys because you have to deal with that stuff and I hate it.”

I am always asked about “What’s next?” yet the response is rather boring and strategic: Find out what I can build scale at, generate profits, outsource annoyances and keep delivering services that others hate being accountable for. Some folks consider commodity as something that lacks value – but if people need it and rely on it who am I not to profit from it? You think the Walmart heirs are crying themselves to sleep?

Cloud is a commodity, but are you?

Over the past year that I’ve been off the road I’ve been working very intensely with my partners on getting them rocking in the cloud. As you may have noticed here, I have for the most part given up on the general IT provider population and have declined a very large number of invites for presentation and training because.. quite simply.. the easy cloud money will put enough people out of business in very short order as they let that v in VAR become largely minimized. So be that as it may, I have no real agenda here beyond just stating my opinion.

Let me just sum this whole thing up by saying that I’ve seen this movie before. I know how it ends. I know what happened to IT staffers that didn’t keep their skills up, what happened with massively vertical-focused shops that dealt with Y2K and cars and real estate/builders when the economy collapsed, what happened to people that were system builders and many of my fellow SBSers through the years. Cloud is a commodity and a transactional business, if you are not making a moat around it then you’ll soon find yourself out of the castle along with all your “services” the client could really do without. So let’s get started:

For most people, the migration to the commodity cloud will be the last large project of their career or business.

Cloud is a commodity, no argument there. But if you’re one of those VARs, MSPs, etc and treat it as such you’re pretty much putting up your tombstone.

There are many great reasons for someone to “sell” a client Office 365 hosting or Gmail, who can beat the appeal of a cheap mailbox. It’s what the clients are asking for: Vlad, I need the $4 mailbox. Convince me why I should pay double or triple? Hypothetical question of course, I’d hang up on someone that was that clueless. But we do get to compete against Gmail or Office 365 often so here is how we do it:

Case: Client needs Office 365. They want it. It’s $4.

Vlad: Not a problem, I can have that contract for you by the end of the day. There are some terms but let me ask you a few questions…

Few questions later, the person sort of realizes just what a crappy deal they are getting and how many compromises they are about to accept. While on the surface everything looks the same, people that run businesses or are responsible for IT departments don’t buy the bottom shelf Dell hardware specials for a reason.

And to be honest, we have not had an issue selling anything from our Exchange at $4 to the full “Office 365” stuff at over $25/month (I use the quotes around the office because it’s the same software/features that Microsoft offers it just runs off the network and the servers we control).

How Much Is Your Expertise A Commodity

I ask my partners this all the time.

Another one (credit to Lee Evans): Should your expertise save them money?

One of the misconceptions about small business is that in small business we all have each others back and we try to save one another a ton of money. Guys that thought that went out of work/business last decade.

There are two kinds of business models that are thriving today:

Cloud transactional – people selling a ton of different cloud services due to the demand and their ability to roll them out quickly.

Project and legacy models – from web design to hardware maintenance to hybrid of MSP / project based solutions.

Only one of these will survive. And if you think I’m on the side of the cloud… you haven’t been paying attention.

For the past few years we have been at an inflection point between buying stuff and buying services. The moment people buy a service (and get on it) the need for an IT person is eliminated. Smart people are partnering with companies that enable them to be the sole provider of that service – folks that don’t pay much attention are simply connecting the dots and facilitating the sale and effectively removing themselves from the IT channel. Yes, they delude themselves into thinking that their MSP contract means they are tied to the client but I hear from more and more people each day that are dismayed that their client decided to give up the office, the hardware, the infrastructure that was being managed.

Imagine offering your clients a great phone system and managing their PBX and providing service with their phones, etc. Then one day you saved them some money by moving all that stuff to the cloud but they kept their gadgets on their desks and everything was the same. Well, new release came out and there was no real need for the desk phone, their cell could do the same thing and thanks for the years of business but it doesn’t seem we need these cables, phones, contracts or warranty. Replace the phones with computers and the PBX with the cloud services and there you have what I’m seeing more and more out there.

The inflection point – preparing you for which I’ve made endless blog posts over the years – was to help you create your own plans, your own support, your own backoffice (hopefully powered by ExchangeDefender and Own Web Now). You either built it or decided it didn’t matter because you had all these other gadgets that needed to go in play. All I can hope for is that either you gave us (or similar) a shot and that your luck is different from the hordes of people that are suddenly knocking on my door.

The notion that that cloud.. is just a computer that is in some other office.. is a gross oversimplification that eliminates experience, skill set, training, investment and a common goal of providing an excellent service. But suppose all of that was indeed worth nothing, how would you explain your client what you are charging them for stuff every month?

Something to ponder as you think what your business is actually worth when put up against a commodity.

diggingyourowngraveSo I’ll say it very simply and succinctly: If you are rolling out a cloud solution where you are not in control of the account, not in control of the data, not in control of the backup and disaster recovery… You are outsourcing the part of IT the business actually cares about. I know you think your service is important, I know your tools are sophisticated, I know your knowhow is earned and your relationships are strong. But you are digging your own grave. Good luck with that.

P.S. The really ugly thing, for folks that aren’t naive, is the aspect of the cheapness and liability. In the past when clients decided to go cheap and make mistakes you at least had billable hours and projects to help them roll out of their mess. When those mistakes happen to services, and trust me cloud is far beyond flawless, who really has your back? Your clients? What sort of control do you have over the situation? How about that data? Folks consumed with the dizzying array of Azure and Amazon Web Services options and services are running around trying to do their best to sell more, find more clients, get more leads, specialize in a more lucrative vertical – but all they are doing to themselves in the process is cutting away client dependence and future profit prospects. While the liability explodes because there is no way to throw money at fixing a problem after the lawsuits start to fly. Again, something to ponder. Cause if you think you have a simple and easy answer to this.. it’s going to hurt.

DaaS Problems

Once upon a time, in the long long ago, I started writing a book on Cloud Services. More specifically, I wanted to write a book to help people build or add a cloud line of business inside their existing technology service.

So I laid out our entire process – that was the book outline.

Then I started outlining each section first starting with how things actually worked.. and then a list of ideas, suggestions, recommendations and ways things really should work.

The more I worked in this world of fantasy about how things “should work” instead of as they really are the more it became a wishlist than a blueprint. And I realized that if I ever actually completed and published this work of fiction I would lose all credibility and self respect. Yes, I’d become an IT coach.

Disingenuous As A Service

Let me be clear – I am not a genius. Not by a long shot. Yeah I’ve built some nice businesses and lots of beautiful disasters over time – some worked out and some didn’t – but there is no real skill in consulting, just the self confidence that your pile of bullshit will actually get a cashable check after you send your victim client an invoice. And this is not just a slam piece on coaches, which I’ll destroy the few that aren’t out of business already later, rather than the inevitability of business reality.

Here is my theory, business managers fall into two groups:

1. Those that know the uncertainty in what they are doing, consider opinions, act, evaluate, revise and actually do the hard work needed to succeed. There are few of these out there.

2. Then there are those that are certain that someone else knows exactly what they are doing. And yet, instead of becoming millionaires and billionaires running successful franchise spanning the globe, they retire to their basement to sell emotional security and confidence conveniently wrapped in a blueprint that can’t fail – they haven’t tried it but other people are paying them for that advice so surely it must be worth something!

Listen, I get it, it’s hard running a business. Everyone needs a cheerleader. But I get the same SPAM you all get – for all the promises about transforming your business that you’ll get what you’re actually getting is a bunch of wishful thinking combined with the ugly realization that everything you need to do will require a lot of hard work or a ton of money for someone else to do it. And if you’re smart enough – you realize that no third party understands your business like you do or the kind of talent you have or the kind of clients you serve.

I can boil the whole effort of any consultative effort to you in a single line:

Ask your clients what they want, ask your team how to do it.

Then figure out how to make $ with it.

This first coaching advice is free, if you need more I am available on contract basis. Smile

Update on CompTIA’s Cloud Trustmark Progress

comptiaAs I wrote here before, I am on CompTIA’s Cloud Executive Council and several of us are helping CompTIA come up with a Cloud Trustmark that would help IT Solution Providers determine, in a nutshell, how credible the cloud service provider happens to be. The following are my opinions and impressions and do not represent CompTIA, other members of the executive council or any other entity. I hope this information gives you a perspective for the hard work that is being done in our industry and encourages you to participate.

First a little bit of background – I originally objected to the idea of the Cloud Trustmark for the simple reason that the same executive council spent nearly a year just to come up with a well rounded definition of “What is the cloud” and creating a unified certification of the same would be either expensive or meaningless. The point of the association though is not just to sit and object to things that are difficult but to craft something that would be useful. Here is the summary of the major discussion topics:

Should we require a physical visit? Some felt that the certification would be neutered and meaningless without verifying that the physical location of the servers was not confirmed in person. The concern was rejected because the effort would be too expensive to execute, wouldn’t be relevant for a large number of cloud service providers that do not have a physical server infrastructure or had a very large footprint (multiple data centers).

Should we certify security or financial information? This was a broad discussion over what financial and security processes could be identified, verified and how they would be reported. For example, should the certification conduct a PCI-like scan and if so what would be done if the company had no PCI-requirement. Does a company pass or fail the certification solely on their extensive backoffice infrastructure or does lack of one create a liability? As you can tell, this was a long discussion that revealed the complexity of even CompTIA’s ability to effectively report on the credentials of a service provider.

What should the certification include? Should the certification be a pass/fail, a checklist of applicable criteria, score based or something else? The complexity of the cloud service provider business models lead us to the final question:

What would be valuable to the VAR/MSP/consulting community? The entire meeting included only vendors and CompTIA staff. While we know what helps us position our solutions, are those necessarily the same components that you would value? This is why it’s so important for IT Solution Providers themselves to be a part of CompTIA AMM and annual meetings and voice their needs (in part writing posts like these is to solicit your opinion and encourage you to). The decision was made for the CompTIA research team to conduct a poll of service provider members and gather some feedback.

I will keep you up to date as this develops further and encourage you to both send me your feedback and attend the CompTIA Cloud meetings and conferences. There are Cloud Café’s at major IT conferences this year, please get involved. Yes, it’s free.

My personal opinion: CompTIA has no footprint/legitimacy in the cloud so the Trustmark as an endorsement wouldn’t be meaningful on the same level as many other industry standards that evaluate security, credit card transactions, accounting standards, operations management and so on. Where CompTIA does have a foundation to build a certification on is it’s relationship with the IT workers and in my opinion the true value of the certification would be in helping IT staff compare cloud providers on equal footing in terms of which standards they comply with, which industry standards are being met and so on. Passing a trademark for the sole purpose of having another trademark that less than a few dozen people would be interested in only cheapens the value of other established trademarks and CompTIA’s reputation in the IT industry, if you feel that there is a need for this certification to exist and can clearly demonstrate the criteria that are important I implore you to join us and help us build it.

Impatience, Shortcuts & Quickies

One of the more annoying themes in IT is the lack of understanding that anything valuable and complex takes time. We recently launched a new service at work and I’ve spent the past month on the phone talking to people and discussing some common problems and issues we have with the business / people and the fallacy of impatience.

aintnobodyI need huge margins and immediate results. I understand, I need to lose 50lb in one day but the only way for that to happen is if I chainsaw myself in half. Nobody wants to clean that up – and I’m pretty sure it would be less of a legal challenge than if you took that chainsaw to your clients Exchange server. Yet many people want to do just that. Ain’t nobody got time moment.

Since this is likely to only be valuable to people that don’t have a long attention span I’ll make it quick: Nothing good happens fast. If you have no experience and you think you can fix a problem in a split second because everyone around you is an idiot, grab a buddy – use them as a human shield when you earn your “experience” and something blows up.

When it comes to complex issues, particularly the ones involving the cloud and infrastructure / process shift, it takes time. You won’t be a millionaire by the end of the week. Or month. Or a year. But that doesn’t mean you just turn your back to it and wait for it to errode you out of business – ask all the Geeksquad MSPs how well they are doing next time you visit them at Target, Car Max or another IT vendor job – ignorance is not a business model. It takes time to build, promote, sell, implement and sustain a new business line or a new product and if you’re just hoping to find that next “set it and forget it” piece of IT then it’s going to be a rough winter.

My Story

I have (a lot of) projects that fail. I don’t want to give you an impression that I have any magic solution to failing, just my process for handling failure.

1. It starts with planning. All new ideas come with plans, tracks, stages, estimates, priorities, outcomes, scenarios and so forth. Most crackheaded ideas don’t even see the light of day.

2. It’s sustained through monitoring. You have to stay on top of your plans and you have to keep on checking how things are going. Everyone at every level of management will tell you that their reports are task avoidance ninjas, trained in the art of avoiding any hard prolonged work. Quick bursts of output, no problem. Repetitive mindless droning, got it. Six week project with deliverables, unknowns, research, etc – it’s due in six weeks, right? We’ll worry about it in 5, I’m stalking something on eBay. If you aren’t paying attention to your business nobody else is.

3. It lives and dies through evaluation and persistence. How is the plan progressing? Has anything changed? Do we make changes or push forward?

Ineffective people fall on the opposite parts of the spectrum: They either get consumed in their projects and never get anything done and don’t know how to quit… or they quit at the first problem they encounter and don’t give their projects enough time to develop.

I want it all and I want it now. But I don’t want to take the time to get there and I don’t want it to require hard work. Who am I to say you can’t dream?

But waking up in the IT services landscape we have today paints a picture of ridiculously complex and overpriced infrastructure that never lived up to it’s billing, competing with a cloud infrastructure that is seemingly free and easy but it’s really neither. The challenge of bridging the two for a business is a difficult, painstaking and process oriented task that will be neither easy nor quick. And that’s your job. Embrace it, take it and build a business around it.

Or look at the alternative: It is quick and easy and nobody needs you. Your call.

What is the value of on-premise mail server?

I’d honestly like to know. If you’d like to see why and what we’re doing (disclaimer: this is a vendor event skewed towards ExchangeDefender and what we do)  feel free to join us.

In particular, when dealing with small business (not big/enterprise), I would like to know what are the key values of having a mail server on premise in the office. The following are my opinions on which key values used to be relevant that are no longer important (again, just my opinion, I don’t care if you disagree, I just care about the ones I am missing):

Issue of connectivity “Client has slow or unreliable connectivity, large attachments, etc”  - Dismissed largely because Outlook in cached mode uses comparably the same amount of bandwidth as on-premise Exchange, if they are mailing large attachments around they should be shot, etc.

Issue of broadband “My village only has dialup Internet” – Fair point. That sucks but that’s not a growing opportunity for anyone to sell software or services into (except maybe an ISP)

Issue of security “Client only trusts their server if it’s in their office” – Gotcha, security through ignorance. Hope it’s not connected to the Internet. 

Issue of legacy applications “LOB requires server A which requires CDO which only works on premise” – Legitimate but again, dinosaur.

When you dismiss all the old world psychological problems of comfort (it’s always been on-premise),  paranoia (NSA is reading my email), LOB (our vendors have us bent over), hoarding (“realtime access to email from Internic in 1996 is business critical”), and voodoo economics (“on premise Exchange with my $350 / server + $50 / workstation MSP fee to keep it all together poorly is more affordable than the cloud)… what is left?

What else am I missing as a giant selling point of in-house mail services?

Legitimate Reasons

Compliance by submission – Anytime legal and accounting get involved in managing technical operations of a company you’re guaranteed two things: it’s going to be expensive and it’s not going to make any sense so you better just do what they ask. The challenge there is that you’ll take on the legal liability and assume all of it on your own while managing the whole nightmare as well. Compliance is big in the enterprise and even midmarket and we’re making a lot of $ on our ExchangeDefender Compliance product even in the SMB but it’s not cheap by any means.

Long Term Storage – Email has, for better and mostly for worse, become a defacto file storage locker for small businesses over the past two decades of crappy file server implementation failures. One thing that has remained consistently reliable has been the ability to just “email it to me” and companies (read: massive amount of unskilled labor only capable of doing it one way that will never ever ever change) have storage needs for email that transcend the IRS record keeping requirements or any technical recommendation any sane engineer would ever recommend. Where there is pain there are profits.

Trust – While many either trust or have no other option than to trust or simply do not care because they have nothing to hide.. corporate fiduciary responsibility at times calls for additional safeguards and measures to protect data that may be stored in the cloud. As people leverage cloud services more and more the amount of trust will have to grow which isn’t likely due to the government espionage, cloud service provider reliability shortcomings, cheaper and unproven cloud services, drive to shorten the release cycle of cloud services, etc. Eventually the ability to assure continuity of business meets the convenience of not being responsible for daily operations of the infrastructure and you have you CYA.

Challenge

The problem, from experience, with the above 3 areas is that while they are all important and all relevant and all probably critical.. they tend to be a very hard sell. Small businesses have a hard time parting with money and at times assume greater risk for greater savings (only to be burned or outright put out of business at a later time, “but that won’t happen to me”)

Somewhere between the good reasons, good intentions and the right price there is an answer to the majority of small business mail concerns that the cloud alone cannot address. Microsoft has failed at this. Others have no incentive or interest in anything beyond the consumer (Google Drive, Skydrive, iCloud) and other commercial services are aimed at storage and large scale server imaging and redundancy (because it’s easy to sell those)

If you can think of anything that I’m missing, please let me know. vlad@vladville.com

-Vlad

There is nothing on the Internet

At some point in the 90’s with hundreds of channels and pay-per-view options there was suddenly “nothing on TV” and the selection of random redundant choices made most people simply tune out (and only come back later for “reality TV”) – we are at that point with the web content.

Recently Google announced it would shut down Google Reader. Everyone was outraged. How dare they shut down free software for which there was no similar comparable replacement? Allow me to break it down for you:

Everyone = media, bloggers clinging to a rapidly disappearing headline-scanning audience, people with irrational fascination with RSS.

Shut down = nobody uses this @#% anymore.

So when nobody cares about something that nobody uses and nobody can make money off of it, it dies. The end. All this outrage and insanity and supposed millions of orphaned and homeless readers out there… well, it accounted for about 500,000 transfers to feedly (the second most popular option)

The would-be blogging elite is even so bold to question it’s reliance on Google – if they can shut down stuff nobody uses that they can’t make money on, what is next? Could a private company shut down all of it’s unprofitable projects that the unsuspecting innocent public is mooching on? Yes. And even with all the sound and fury, it will signify nothing.

It’s not negative

You may be reading this thinking this is a bad thing. Quite the opposite.

Yes, the disaffected English majors are yet again forced to face the fact that they are fucking useless and should have gotten a real college degree. Sorry, New Media. Your brief, uneventful moment of relevance is again sunsetting. It’s not Google’s fault – it’s that majority of people simply don’t care to scan thousands of headlines or read opinions of people who don’t actually participate in the industry directly.

This is a good thing in a sense that the web has matured to the point where it’s not about “new and exciting” but actual purposeful implementation -  web is the new application medium not just a collection of porn, shopping sites and meme libraries. And the race to document and organize each and every one of those is making way for things that are actually relevant – connecting people, organizations and applications.

My generation built this Internet web thing into a mainstream afterthought… I for one am glad to be alive and to see it take it’s next step.

P.S. Some of you have asked why I use @#% to mask profanities when I have no problem using other four letter words right next to it. It’s quite simple: sometimes it’s hard to pick the right word and depending on the level of (percieved) intensity the reader will likely fill in the blank with the much more appropriate choice than I could.