
Spectre
Tools for remote companies
I've officially launched landing page v1 for Spectre (https://getspectre.com), which is super exciting and scary at the same time.
The page is a simple reactjs app that I hosted on AWS using route 53 + cloudfront + s3 buckets. I plan on iterating the marketing copy, which I feel is suboptimal, over the next week.
However, the real work is reaching out to key people at remote / distributed orgs to identify a specific market problem. I have a general sense of problem spaces remote orgs struggle with (communication overload, isolation, async work) but it's all too high-level right now. I need to get down into a niche.
If anyone reading this happens to be running a remote / distributed org -- please feel free to setup some time to chat (https://calendly.com/spectre/15-min-1x1)!
All that aside, I'm excited that the journey is finally beginning. I hope it'll be a long and fruitful one. But regardless of the outcome, I'm glad I finally took the leap.
About
Remote companies can unlock economic productivity, environmental benefits, and individual wellness. Spectre is working to enable that future.

4 Comments
I would just host on Netlify, it is free and much easier than S3.
One tip I wish I listened to was to build an audience so, start an email list and add it to the site. Just send weekly tips on remote work and the top articles.
You're 100% right. My plan was to blog (http://blog.getspectre.com) on remote work / changes in the space based on past experiences and conversations I have with folks in the market. I'm going to ship a sign up link on my landing page later today.
Thanks for the feedback!
Congratulations!
Some initial impressions: I'm left uncertain of what your product is. Is it a consulting service? Also, your blog post doesn't work - I am getting a 404 error: http://blog.mercurialapp.com/localhost/post/the-why-behind-mercurial/
Excited to learn more about what you are offering to customers!
Yeah it's a great point. I think right now there's confusion because there's no product. I'm in the market validation phase and have a general sense of problem spaces for remote / distributed orgs, but not necessarily any specific niche identified. However, that is my goal -- find a niche + build a product.
Will definitely update you once I finally do figure out what I'm offering :)
For now I'm trying to straddle line between specific vs. generalizable to facilitate my reach-out campaign this week. Any thoughts on how to better hit that mark?
P.S. thanks for the heads up on the dead link -- forgot to update my config.toml on the backend when I shipped!!