The experiments includes Forbes in publishing metadata from selected Forbes articles to the blockchain through Civil.
The approach I have come up with which I cannot believe should be unique or even my invention is to budget against my time. At the moment, my service has £0 revenue so I need to give 80% of my time to “the suits” in order to pay for everything. I need to get to £X revenue before I can get away with giving 0% of my time to “the suits”.
You may then think that this means I have 20% of my time to go toward increasing revenue, but that is just the most conservative option. I could find a way to loan myself 40% time (go down to a 40% contract, or take a 100% contract for W weeks in return for giving myself 1.5*W weeks of focus, or something else) on the understanding that I will “pay back” that loan by either increasing revenue, or by paying off the debt by doing more work for “the suits” later.
All that really means is that I’ve given myself a way to increase the number of steps between the two extremes of “work until I’m making enough revenue not to work” and “not work”.
Edited to add: yes, being able to go part-time is a privilege, I accept that, but it is more accessible than people realise. I went from 100% to 80% by asking my manager and being told “yes”, with no resistance from them and just a bit of negotiation over what would happen to 20% of my job and how holiday allowance would work. Many people who do not believe their managers would allow them to go part time, including myself up to that point, have not yet asked.
I don’t think it’s useful to guess at her reasons when you could just read her explanation of her reasons.
As an example of why it’s not useful, one of the reasons she mentions near the end is being able to pay artists.
I have a shorter explanation if it’s her we’re talking about: she likes to do drawings, lots of people like her posts with drawings, and why not make some money off it. She’s already most of the way to a product and audience. Others trying this might similarly want to test and iterate some free ones on their web site first like she did.
Articles like that are better fit for technical forums. This one is dedicated to aspects of running a small business such as marketing and pricing. Also, case studies on them.
By doing the crawling locally, it means you can check as many sites as you want as often as you want including localhost sites. This is especially useful during active development as you can perform checks locally and on staging sites instead of only checking production sites when issues have went live. A cloud-based implementation would have to come with limitations on how often you can perform crawls and can be expensive to run.
I’ve mostly been reaching out to web developers on forums and online communities so far. I’ve had a lot of positive feedback about the interface and how Checkbot is finding issues missed by other tools.
Huh, interesting - why is it an extension, so the user is crawling themselves instead of you running a server? That seems like an odd technical decision.
But more to the topic of this as a product, how did you choose to do this? I’ve seen website checkers with similar featuresets for a long time, so it’s nice that there’s a market - how will you reach that market?
Great article, thank you. I come from the world of Mac/iOS software where Indie has been used for the last couple of decades to mean “micro-ISV”: a small, independent company that aims to sustainably deliver its software products. It’s the kind of business I want to create, and I think addresses the “king” side of the Rich vs. King distinction in leadership.
Totally agreed. I’ve had similar experiences.
I might be wrong, but this seems like you received bad advice in so many ways! I see problems at every step.
What a person claims they’re willing to pay and what they actually do when asked to enter their credit card info are not the same.
Let’s assume optimizing is about maximizing profit. Let’s simplify, as many startups do, by looking to maximize revenue and assuming that costs won’t dramatically change, though people point out that cheap customers have higher costs (support requests, complaints, etc).
Okay, so let’s maximize revenue. Revenue is price multiplied by number of customers.
Let’s replace the two survey questions with a more pointed question: “what is the maximum price you’d be willing to pay?”
Once you conduct your survey, the graph won’t have straight lines but a distribution that might look like one of these curves, where X is price and Y is number of answers. Given that at any price point all customers below that price will buy too, you’ll want to calculate the cumulative distribution curve, which looks like one of these S curves (but flipped around because it’s going to be a decreasing function). You’ll end up drawing rectangles similar to the way they are on this graph and picking the one with the maximum area (price times total customers).
Spot on! Your list at the bottom resonates fully with how I’m approaching building my company, HostedMetrics.com.
Wow! Just wow! What an insightful, detailed, and informative piece of content. Thank you a million times!
This is something need of the time. Great article with great encouragement.
Product retention is what most of the organizations are trying to improving some changes expected by the customers and the main source for it are the feedback they received. Mapping your customers journey is the best way to know your customers and for the retention as well as new acquisitions.
I find it strange that you get that amount with your amount of email subscribers.
Getting a 404 on this page and root domain
Valuble talk. Thanks for posting!
The use of “complex” in this article roughly means “causing the user to work harder to do things in your product” (search, fill out forms, etc.).
Not what I expected from reading only the title.
This article is about making things easy for the user—specifically making forms valid by default rather than invalid by default, and tolerating a possible increase in incorrect data.
Interesting read, although I think it’s easy to convince readers that “valid by default” generally leads to a smoother user experience, and consequently, I would have preferred a discussion on when or why tolerating incorrect data makes sense and a focus on techniques to reduce incorrect data.
I recently discovered https://www.heavybit.com/library/. So far I’ve watched Dearing on Pricing and Civilized Discourse… But How? (previous thread). I enjoyed both. This seems like it may be a good resource overall. If you’re aware of any other videos on here that are worth watching, please say which.
One piece of advice given to potential founders of startups is looking for pain points people have. Then, solve them. The high cost and inflexibility of electronic hardware plus non-hands-on education were obstacles to hobbyists. The author went from solving their own problem into bootstrapping a business solving others' problems on the cheap. Only got better from there.