Take the numbers at face value for a second: 1,900 to 61 is 3.2% visitor-to-signup, and 61 to 4 is 6.5% signup-to-paid. Neither of those is broken for cold traffic. Depending on the source they are unremarkable.
The bigger question is how many of the 1,900 were bots. Crawlers, uptime checkers, link previewers and scrapers are a genuinely large fraction of raw traffic on small sites, and most edge dashboards count them by default. Strip known bots before you draw any conclusion about your conversion rate, or you will 'improve' a denominator that was never human.
Same lesson here, and the version that stung was that my lender would not let me draw any of it back later without a full remortgage application. Money in the house is not a savings account with a slightly better rate, it is a different asset entirely.
Drifting back is the part I've never solved. Even with the instruction pinned it still slows down the second I hesitate, which is the exact moment a real person would just keep going.
Mind the runway maths. Four months of savings is not four months of product time, because you have to start job hunting in month three if it isn't working. Your real deadline is more like ten weeks. Price for money this quarter, not for a gentle ramp.
Two months buys you one experiment, so pick the one you can read fastest. A free-tier limit change gives you signal in about 14 days. An onboarding rewrite takes six weeks to build and another six to read. A pricing change takes a quarter because of cohort lag. That ordering makes the decision for you.
Politely, the copycats are not your problem and the posting did not cause them. Your problem is that the product is cloneable in a weekend, which was true before anyone found you. Somebody would have found you through search or a directory eventually.
The interesting question is what makes month six of running it hard, because that is what actually stops a clone. Data that gets better the longer a customer stays. An integration that took you three weeks of arguing with someone's API. A support reputation. Being the one who answers on a Sunday. None of those show up on a landing page, which is exactly why the clone's landing page looks identical and their product does not.
Mild disagreement, in the interest of not overspending. Nothing is wrong with a cheap pull-through for the three cheap knives in the drawer. They are soft, they will never hold much of an edge whatever you do, and the scratches do not matter on a knife you bought as a set. Keep the pull-through for those, and use a proper method on the two German knives and the gyuto. Buying a guided system to sharpen a drawer knife is like taking a hire car to a specialist.
My numbers, for calibration. I ran a slow surplus for fourteen months: roughly 250 calories over, gained about 0.25kg a month, went from 71kg to 75kg. Upper arm went 32.5cm to 34.5cm over that whole period, and about a third of that was fat I later lost.
So the honest timeline for visible arm size on bodyweight training, eating properly, is measured in years, not months. Nine months at maintenance is not a plateau, it's not having started yet.
Ask for a referral in the break-up email. The person who ghosted you usually carries enough low-grade guilt to introduce you to a peer at another company, and that intro converts far better than anything cold.
The screws thing sounds like a joke until you are on your hands and knees at midnight with a phone torch looking for one standoff screw. Bowl on the floor from minute one.
Four to eight weeks for visible new growth is the normal range after losing half the roots, and longer if the light is average or the temperature is cool. The plant is rebuilding a root system before it spends anything on leaves, which is the correct order and also completely invisible from the outside. Losing a couple of old leaves in that period is expected: the reduced root mass cannot support all the existing foliage. What you want to see is the newest leaves staying firm and green, not the count going up.
It's twenty minutes of video and one afternoon of ruining a cheap knife. The knife you buy afterwards will actually stay sharp, which is the thing you're trying to buy.
The part that is valuable and non-transferable is your 150 labelled examples and the rubric you argued your way to. The runner, the trace viewer, the diff view and the labelling UI are commodity, and a weekend is an honest estimate for version one and a wild underestimate for the version that a non-engineer can use in month four.
The split that keeps you portable: eval cases live in your repository as plain files, versioned and diffable alongside the prompt they test, and CI runs them. The vendor gets traces and the labelling interface. Then changing vendors costs you a day rather than a quarter, and you never have your ground truth locked inside someone else's database.
Fair, and the board point is genuinely underrated. I moved from a composite board to end grain wood and every knife in the house started lasting noticeably longer between sharpenings.