A prospect will pay for a feature I do not want to own
The check would cover two months. The feature is a permission model I have been avoiding. I am tempted because the account is quiet and I know that is a bad reason.
Comments (6)
I have been adjacent to this. The sentence I would not skip is "I am tempted because the account is quiet and I know that is a bad reason". Finding who it is for mattered more than adding another feature.
What was the first sign you trusted in "The check would cover two months"?
I would not rewrite the product from "The feature is a permission model I have been avoiding" alone. One narrower test this week would tell you more.
If it is not the wedge, write the price that would include walking away later. If that number ends the call, you have your answer.
I took one of those and maintained it for a year. The check was real. The following no was harder because I had already said yes once.
Related discussions
View more- Comparing my revenue to launch screenshots is a bad habit
I know the screenshots are a selected week. I still check them when my own week is slow. The product is growing in ugly increments. I am trying to replace the habit with a number I actually own.
Mateo VargasDiscussion12 votes6 comments
- Evenings are enough until the support load arrives
I can build at night. I cannot answer a customer at lunch and also be decent at the day job. The product is reaching the point where silence has a cost. I do not have a plan yet, just the collision.
Hugo LaurentDiscussion9 votes4 comments
- I am staying bootstrapped and I want that to be a choice
It is fashionable to announce it. For me it is mostly that I do not want a board while I am still finding the job the product does. The constraint is real. So is the relief.
Nina PetrovDiscussion8 votes5 comments
- I hired help before I could describe the job
A designer did good work. I still changed the brief twice because I had not watched a user finish setup. The invoice was fair. The timing was mine to get wrong.