Blog · Building Hellofew, week by week, part 5 of 8
Weeks of 21 September 2026 to 5 October 2026: the quiet weeks, and the first two replies
Adarsh Mamgain · 31 October 2026
Three weeks, six commits, all of them on 30 September. If you are reading this series to learn how a product gets built, this is the part where I say that it mostly gets built by one person who also has a job, and that three weeks of near silence in the log is what that looks like. The one account on the product, mine, kept running through it. The admin report for the week of 14 September 2026 shows the first two replies the product ever got. Two.
From the admin report on 2026-10-30. One workspace, mine, not yet publishing its sent and accepted columns, so only the replies are shown. Two in the week of 14 September, one in the week of 5 October, nothing between.
Show as a table
| Week of | Replies |
|---|---|
| 7 Sept | 0 |
| 14 Sept | 2 |
| 21 Sept | 0 |
| 28 Sept | 0 |
| 5 Oct | 1 |
Check it: the numbers page, where the same account's weeks are published now
The six commits
- The landing page had been saying the warm-up took two weeks. It takes three: 5 a day, then 10, 15, 18, and 20 from the fourth week. A wrong number in public is worse than no number, and this one had been live for three weeks. The fix was the sentence; the lesson became the rule that no limit is ever typed into a page as a literal, only read from the constant.
- The markdown route served the home page for every path. A model asking for a comparison page as markdown got the landing page instead. Fixed, and tested.
- The robots file was taught to say what a crawler may do with a page, not only whether it may fetch it: index it, quote it, train on it. The policy is the same for every public page and it is written down once.
- One way to describe a page, to people, to search engines and to models, from one helper, because the share cards had drifted from the titles which had drifted from the descriptions.
- A solutions page for every chair the buyer sits in: by business, by role, and by both. The question each page answers is written at the top of its entry in the reader's own words, which became the rule for every public page after it.
- The LinkedIn connect wizard moved onto a subdomain of our own, so the page a customer signs in to LinkedIn on carries our name rather than the provider's.
What the quiet taught me
The first two replies were to messages written the way the previous week's post describes: from something the person had written, not from their job title. I have the two threads. They were both short, both polite, and neither became a customer. I mention that because the series would be worth less if every number in it went up.
What the quiet weeks did do was show the shape of a product that nobody is tending. The digest went out each week saying what had happened, which was little, and why, which was that the one account had used its queue and the owner had not approved more. That digest was built in week three and improved in week four, and this is the first stretch where it did its job unattended. A product that can say nothing is happening, and here is the one thing to do about it, without a person writing the email is the difference between a customer who churns quietly and one who presses the button.
The other thing the quiet made plain was that the limits were working as described, which sounds like nothing and is the whole point. One account, under the ramp, under the ceiling of 20 a day, with the breaker watching, for a month, and no restriction. One account is not evidence of much. It was enough to go and ask three friends to lend theirs, which is the next post. The limits it ran under are on the limits page.