I often say that you should sponsor @LastWeekinAWS because you should. @davidcheal took me seriously and filled out the form!

I read his pitch, chatted with him a bit, declined to take his money, and have his blessing to deliver my feedback via Twitter thread. Let's begin.
First, I don't usually see the sponsor forms; it was passed to me. There's an editorial firewall!

Second, I won't take people's money if sponsorship won't help them.

David's product is thermite.red. Sponsoring me won't help him.
You're greeted by a mountain of text. People never read nearly as much as you'd think they would. The tagline ("meaningful insight into AWS usage") is half of the AWS partner network and a third of their own services if we're being honest.
Those four things it devolves into doing are all about what Thermite does. This is a common failure pattern for v1 offerings! It's normal! David is doing a good job!

What comes next is the realization that customers don't care about what he's built; they care about a problem.
If people ask you how you do what you do, often they're not going to become your customers. The customers instead talk about outcomes and their pain points. So what pain does this solve?
The first three of those items are pretty generic. Dress this up in Powerpoint a bit and you can probably raise 2-5 million bucks in VC. The fourth one though – that's something novel.
It automatically generates pretty reports in Word, complete with charts and such? I've never seen this before and it's super valuable.

I would basically toss everything on this page in the trash and replace it with the following tweet instead.
Explain this: To people who understand this:
"Thermite explains something complicated and obnoxious to business users" is a massive win. Include a few screenshots of what it does!
At the end of the page we see this, which has a similar theme, but it's unclear whether Thermite is a report, a Word doc, a breakfast cereal, or a SaaS app.
The only three options on the page for navigation are these.
The bottom of both the sign-in and login page feature this, which can be rephrased as "I enjoy it when computers kick the everloving shit out of me." Power to @davidcheal, but that's not what customers care about.
The "Contact us" button is simply a mailto link.

Okay; let's unpack this a bit.
I'll suspend disbelief and register an account. This thing spins for quite a while. All I've done so far is given and confirmed an email address and a password.
A page reload unwedges it. Fair, it's early days. Then I'm greeted with this.

Wait, I can whitelabel it? It's aimed at consulting firms? First I'm hearing of this! That's a sales proposition; "Nessus for AWS Consultancies."
Next step on the walkthrough. Hmm. Ideally it'll tell me what perms to set, and I really hope it assumes roles but it doesn't look like it.
We'll upset @ben11kehoe later. Next, there's this thing. Okay, not much to say about it.
The red ".red" keeps making me think there's an error or whatnot.
Not a bad first pass at collaboration, if you can countenance inflicting Amazon Cognito upon your colleagues. RBAC probably comes in later.
This absolutely needs to not require an account / you to be logged in unless @davidcheal enjoys answering 50K support requests a week once he finds traction.
And this is what it finishes with. Okay then!
One thing that absolutely must be on the site before account creation is something about who @davidcheal is. Giving you credentials to an AWS account requires a fair degree of trust. Talk to me about data security, who you are, give me contact info, etc.
Inside of the app's docs stuff we see that David has spent more time getting the services arranged with their sub-services and the proper logos than @awscloud ever has.
Ah, I can grant it a role after all!
Skipping ahead, I have a shitposting account just for this purpose. Yay! The perms are unfortunately "ReadOnly" which is WAY too broad for anything prod. There's also a disconnect between "first time new user" and "person who built this" as far as flow goes.
(You can always benefit from having someone who has no clue what monstrosity you've built kick the tires on it to find the sharp edges. Maybe even before you ship it to customers, AWS service teams.)
And the task failed. At a guess it's trying to query regions that aren't enabled in this account and not exception handling properly, but that's a completely blind shot in the dark.
Now then, enough engineering. Onto why sponsoring my nonsense won't help @davidcheal reach his goals...
The @LastWeekinAWS newsletter has ~30K subscribers. More to the point, they're people who presumably work with AWS and might be able to buy or influence the buying of a variety of enterprise SaaS things. The long term value of a customer is enormous.
I'm talking "buy out every sponsorship slot in advance for the next ten years and you still turn a tidy profit" enormous.
Sponsorship is inherently a top of funnel activity; getting more eyeballs on your offering. For that to work, you have to have a working funnel that turns people from tire kickers into customers.
"Nobody visits my site" means that you haven't gotten that far.

"Everyone who visits doesn't try my demo" means you have a conversion problem.
All sponsorship can do is turn up the volume of people who come to your site with a vague idea of what it is that you do. That's all. You've got a chance to give prospects a glimpse of what you do, and a hook to entice them.
It's clear that @davidcheal is onto something with Thermite; a few more cycles and it's got the glimmer of something valuable and interesting. I hope he charges for it! Right now there's no pricing information.
But right now taking his money would deliver almost no value to him; @LastWeekinAWS readers would see it as a curiosity at the moment. His value proposition is still unclear.

Pro tip: if you can't help someone, don't take their money.
So that's where we'll leave it for now. @davidcheal will sand off the rough edges, have a better story, and one day sponsor @LastWeekinAWS, just as you should.

I will now field questions! Hit me.
Bingo. I've got a lot of respect for small companies who let me do things like this. I don't give large companies the choice. And as always, nothing I do on Twitter is sponsored content.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Corey Quinn

Corey Quinn Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @QuinnyPig

6 Oct
Given that my daughter has broken her arm and Twitch / Amazon infosec have broken my heart, I distract myself from both with a thread devoted to answering this question, because I've lived it.
It's Day One, and you're the first DevOps hire at a startup. A bunch of developers probably interviewed you and almost passed on your hire because you suck at whiteboard algorithms; you saved it by whiteboarding AWS architecture on the fly.
What do you care about? Spoiler, it is absolutely not the bill. A bunch of developers have been running the infrastructure.

Be nice! They built something that's succeeded well enough to hire your ass; they don't deserve your scorn or mockery.
Read 17 tweets
6 Oct
One of the hands down most sobering conversations I’ve ever had was with a bunch of Very Savvy Investment Bankers about what exactly a total failure of us-east-1 would look like economically.

The *best case* outcomes closely resembled a global depression.
You want to talk five nines?

That’s comfortably within their probability models for “a US civil war.” They’ve drawn up maps that show likely sides for such an event and they plan accordingly.
These people get paid significantly more than most engineers do to consider risk.

This is why you’ll not find even the most die-hard all-in cloud customer who’s publicly traded who doesn’t have “rehydrate the business” level backups either on-prem or in another provider.
Read 4 tweets
5 Oct
So, folks are asking how I did this. Thread time!
While I do enjoy Twitter, I believe it's important to "own my platform." As such, Twitter's not material to the functioning of my business.

But I do talk to a lot of folks here, and a "subscribe" button for @LastWeekinAWS in my profile can't hurt anything...
I started by emailing @revue and checking their Terms of Service. As of today, there's nothing against using their sign-up function and exporting the list to another platform unless I'm directly monetizing the subscribers via subscriptions.

I am not.
Read 11 tweets
4 Oct
And now, a thread of Ancient Sysadmin Wisdom: an incomplete list of things we have learned from decades of outages.
"It's always DNS." Yup. Everything relies upon DNS, those relationships are non-obvious, and some things like to cache well beyond your TTL.
"If an outage lasts more than ten minutes, it's likely to last for hours." Yup. Usually related to electric power, but this is a good rule of thumb for "do we activate our DR plan" decisions.
Read 27 tweets
30 Sep
And now because @gabsmashh made a wish on the monkey's paw that is The Cloud:

A meme dump thread of @awscloud memes.

Let's begin.
"Bad at names," "the AWS Partner Network," and a tagline I shockingly did not have to alter led to this:
Less relevant now, but still annoying when iterating on Lambda @ Edge.
Read 87 tweets
29 Sep
Time to put on my Cloud Economics Pants and do a bit of math around @Cloudflare's R2 pricing model as described herein.

blog.cloudflare.com/introducing-r2…
So today I'm going to store 1GB of data in @awscloud's S3 and serve it out to the internet. The storage charge is 2.3¢ per month the tier 1 regions.
Someone on the internet grabs that 1GB of data once. I'm paying 9¢ to send it to them. You read that right; just shy of four months' of storage charges to send it to the internet once.
Read 14 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(