Month 1 Update: 40k views, 4 waitlist signups, and what i'm doing about that gap
posted this a few weeks ago about losing my painter's number and building something to fix it. wanted to come back with real numbers.
here's where things actually stand after month 1:
40k views on a reddit post.
22k impressions on x.
262 site visits from 27 countries.
4 people on the waitlist.
14 clicks from google.
that gap between reach and conversion is the whole story of early distribution and i'm not going to pretend otherwise.
what's working: the origin story resonates. every time i tell it plainly -- lost the best contractor i ever hired, couldn't find the number -- people say "that's happened to me." the problem is real. i just haven't found the channel that converts yet.
what i shipped: 20 blog posts. shared product catalog so the second person to scan a barcode gets instant results. AI recommendations cached so gemini only gets called once per item. PWA so it installs on any phone without an app store.
what i'm figuring out: how to get from "that resonates" to "i use this every day." if you've cracked that for a utility app with a quiet use case, i'd genuinely like to hear how.
app is live at getkeptapp.com. no download required.
the painter's name was Dave. he's still in there.
The "Dave is still in there" ending is doing a lot of heavy lifting — that's the actual product story. One angle I haven't seen mentioned: the people who interact with contractors every day aren't homeowners, they're the contractors themselves. Dave hands out his number to 10 new clients a week. If Dave had a QR code that saved him into Kept on the client's phone in 3 seconds, he'd use it — it solves his problem (clients losing his number and not calling him back). That flips the distribution model: instead of waiting for homeowners to discover the app during a pain moment 8 months later, Dave is handing it to them at the exact right moment. Have you talked to any contractors about whether they'd actually hand something like that out?
this is a genuinely good angle and i haven't talked to contractors about it yet. the framing flips the whole model. instead of waiting for homeowners to feel the loss, you get there right after the job when the contact is fresh and the contractor has standing to make the ask. i can see a painter handing out a qr at the end of a job way more easily than a homeowner remembering to open an app six months later. going to think about this more seriously. might be worth a small test.
The painter QR example is exactly the right way to think about it — the job completion moment is one of the only times a contractor has both the client's attention and a genuine reason to make the ask. That's a rare combination. The small test framing makes sense too: you don't need to know if it works at scale, you just need to know if one contractor will actually do it consistently. Would be curious whether the friction ends up being the contractor remembering to do it, or the homeowner actually scanning in the moment. Both are solvable, but they're different problems.
Joe, the Dave detail at the end is what made me actually click the link. That's the whole pitch right there.
Here's the tension I keep sitting with on utility apps with quiet use cases: the 40k views aren't really your funnel. People nodding at "I've lost a contractor's number too" aren't in pain right now — they'll be in pain in 8 months when their sink leaks again. By then they've forgotten you exist. So conversion isn't really the problem. Recall is.
If I were in your shoes, I'd probably stop optimizing for waitlist signups and start asking: how does someone remember Kept exists at the exact moment they need it? That might be a browser extension that fires when they're googling "plumber near me," or a one-line SMS reminder six months after they save Dave. The PWA helps, but only if they open it.
I'm Shirley, building ZooClaw — I've been deep in user discovery too, so I know how lonely month 1 numbers feel. Curious: of those 4 waitlist folks, did any of them describe when they'd use it? That answer is probably worth more than the next 40k views.
"recall is the problem, not conversion" is actually more useful than anything i've read about conversion optimization. you're right. someone nodding at a reddit post in april isn't going to remember kept when their sink leaks in october. the PWA install helps but only if they've already added it. haven't asked the 4 people specifically about timing but you've convinced me that question is worth more than chasing the next traffic spike. going to reach out and ask. also curious what you're building with ZooClaw, the "lonely month 1 numbers" line landed.
You have a distribution problem, but it starts one layer earlier as a behavior problem.
People agree the pain is real.
They just do not feel it often enough to change behavior today.
Losing a contractor number is a real frustration.
It is just not a daily pain, which means “that happened to me” creates nods, not habit.
That usually means the wedge is too emotionally true, but too infrequent to pull people into repeated use.
The product probably gets stronger when it shifts from “save people you might need later” to “your home memory layer.”
Not just contractor recall.
Paint colors, appliance models, filter sizes, warranty info, parts, repairs, installer notes, replacement history.
That turns it from a one-time recovery tool into something people reopen every time their house needs something.
you're right about the distribution problem, and honestly right about the framing too.
the contractor story lands emotionally but it's a low-frequency moment. it makes people nod, not download.
what i haven't figured out how to show yet is that kept isn't for the rare "oh no i lost that" moment - it's for the tuesday afternoon at home depot when you can't remember your furnace filter size. the warranty question when the dishwasher dies. your kid's shoe size in the checkout flow. those happen constantly.
the product is already the memory layer - filter sizes, paint colors, appliance models, contractor contacts, warranty dates, vehicle info. the marketing is still leading with the single dramatic failure instead of the everyday friction.
going to work on content that shows a week of use rather than a single pain moment. that's probably the right fix.
Exactly.
“A week of use” is the right shift.
The product should stop being framed around one dramatic miss and start being framed around all the small moments where the house asks you a question and you don’t have the answer.
Filter size.
Paint color.
Warranty date.
Appliance model.
Contractor name.
Shoe size.
Repair history.
That’s much stronger because it turns kept from “save this in case you need it” into “this is the memory layer for your home.”
The only thing I’d pressure-test next is whether “kept” carries enough weight for that.
It’s simple and clean, but it may still feel more like a personal notes app than the system your household relies on.
fair pressure test. "kept" is deliberately quiet, the brand logic was that it doesn't shout, it just holds things. but you might be right that it signals personal notes more than household operating layer. the honest answer is i'm not going to rename it at month one, but it's worth watching whether people describe it back to me as "an app i use" vs "the place my house info lives." those are different things and the product needs to earn the second one.
That’s the right test.
If people describe it as “an app I use,” kept is doing the quiet-notes job.
If they describe it as “where my house info lives,” then it’s becoming the household memory layer.
But that difference is exactly why the name matters early, not later.
Because users start forming the mental category from day one.
If the name teaches them “quiet place to store stuff,” you may get usage.
If it teaches them “system my home depends on,” you get reliance.
Those are very different outcomes.
I wouldn’t wait too long to pressure-test that, because by the time the product earns habit, the name has already taught people what kind of habit it is.
the "what kind of habit does the name teach" framing is one i'll keep sitting with. you're probably right that early users are already forming the mental category and i don't get to redefine it later. the honest check i'm running right now is whether people describe it back to me as a tool they use vs a place their house info lives. if it's consistently the first one, that's a signal worth taking seriously. not ready to rename at month one but i'm watching.
Joe, one practical follow-up on the kept thread.
I remembered this because your product had a very specific positioning risk: not whether the idea is useful, but whether people describe it as “an app I use” or “where my house info lives.”
That difference probably decides the whole category.
If you have talked to even a few early users since then, this is the right moment to audit the naming and positioning properly before the first mental label gets too fixed.
I’m doing focused naming/positioning audits for early products now: current name risk, category framing, what habit the name is teaching, landing-page direction, and whether the product is being understood as a tool, system, or memory layer.
For kept, I’d specifically look at whether the name and copy are helping users see it as the household memory layer, or quietly making it feel like a notes app for home stuff.
Not a long consulting thing. Just a sharp written breakdown you can use before more users, examples, and habits build around the current frame.
I’m doing a few at $99 while refining the format.
If useful, best place to discuss privately:
https://www.linkedin.com/in/aryan-y-0163b0278/
That’s fair.
I wouldn’t frame this as “rename now” either.
I’d frame it as: test what category the name is teaching before the product gets locked into that habit.
Because month one is exactly when people start forming the first mental label.
If they say “kept is where my house info lives,” you’re fine.
If they say “kept is a notes app for home stuff,” that’s the ceiling showing early.
The risk is not that the name is bad.
The risk is that it quietly trains the wrong habit while the product is still becoming the right one.
"That resonates" → "I use this every day" is the exact gap I've been sitting with too.
What I noticed building a workflow system for vibe coders: the pain that resonates isn't always the pain that converts. "AI loses context between sessions" — everyone nods. But the converting moment is different: it's the Tuesday morning when you open a new chat and spend 40 minutes re-explaining what you built last week. That's present-tense pain.
The story that got shares was "I rebuilt my project from scratch twice." The story that got buys was "you open a new chat and your AI has no idea what you did yesterday."
Same product, completely different entry point.
40k views to 4 signups is a 0.01% conversion. That gap is almost always either intent or message, not traffic. I had a similar month last year, 28k views and 6 signups, before I figured out the views were coming from a single Twitter thread that promised a different product than the landing page sold. Cut the thread, the traffic dropped 80%, conversion jumped to 1.3%. Worth checking which channel is dumping the traffic and what those people thought they clicked on. The traffic is not the asset, the alignment between channel and page is.
This is the kind of founder update more people should share — real numbers, real uncertainty, real iteration. The interesting signal here is that the story clearly resonates, which usually means the pain is real. The next challenge probably isn’t awareness, it’s finding the moment when losing contact info becomes painful enough to create a habit around solving it.
appreciate that. you're right that the moment matters more than the volume -- "i've lost a contractor number" creates recognition but it's not the moment the pain is actually active. the everyday version of that problem (standing in the aisle at home depot, can't remember the filter size) is present-tense. that's where kept needs to show up, and that's the content shift i'm working on.
That 40k → 4 gap is painful but the diagnosis matters: "origin story resonates" tells me the problem is real, while Reddit/X traffic is mostly bystanders, not people in pain right now. From my own small indie utility app — a lightweight memo tool — what moved the needle wasn't broader reach; it was placing the offer next to the moment of pain. For "lost the painter's number" that probably means a search query like "how to find a contractor i hired last year" rather than feed scrolling. PWA + barcode is great execution; the missing piece sounds like an entry trigger that fires only when someone is actively trying to recover info. Question — have you instrumented the 4 signups' first action? Did they all scan something within 60 seconds, or just save names?
"next to the moment of pain" is the right frame. you're correct that the reddit and x traffic are mostly bystanders, not people actively trying to solve the problem right now. the search traffic is different -- 14 clicks from google is tiny but those are people who typed something and found a result, which is why i'm building out blog content around the specific lookup moments. on the 4 signups: i don't have first-action instrumentation that granular, which is a gap. don't know if they scanned or just saved a name. worth adding.
I think the problem is relatable, but it probably doesn’t happen often enough for people to instantly sign up.
The “home memory layer” angle feels much stronger though - filter sizes, warranty dates, appliance models, paint colors, etc. That stuff is actually useful day to day.
Also respect for sharing the real numbers publicly instead of only posting wins 😄
you're right on both. the contractor story is a single miss, it gets nods but it doesn't pull people into daily use. the home memory layer framing is where the product actually lives: filter sizes, paint codes, warranty dates, appliance models, shoe sizes by brand. stuff you look up constantly. the origin story is real but it undersells what kept actually does. working on content that shows the tuesday-at-home-depot moment instead of the dramatic one. and yeah, real numbers felt more useful than a highlight reel.
Honest breakdown That reach vs conversion gap is real in early stages. The problem clearly resonates, now it’s more about tightening the value prop and finding the right distribution channel. Keep iterating once it clicks, those numbers can flip fast
thanks. the value prop tightening is the real work right now, taking it one step at a time. the problem resonates but i'm still leading with the single dramatic story when the everyday use case is probably what pulls people in. distribution channel is the other half. still figuring out where the people who actually feel this friction are hanging out when they feel it.
The frequency point is real. "I lost Dave" sticks in your head, but it is rare. The Tuesday at Home Depot when you cannot remember your furnace filter size is the everyday version of the same problem.
One angle that might help: those everyday moments are mostly speech, not writing. When someone mentions their HVAC contractor at a dinner party, or you spot a model number while standing in front of the dishwasher, that is a dictation moment, not a typing moment. If Kept captured those as voice notes you could clean up later, the product would be collecting information in the flow of your actual life instead of making you remember to open an app and type something.
That framing, "your house asks you questions, you answer on the spot," might bridge the gap between the emotional story and the frequent-use behavior you are after.
the voice angle is interesting and you're right that most of those moments are spoken not typed. standing in front of the dishwasher, on the phone with the contractor, walking past the furnace, none of those are "open app and type" moments. i've thought about voice but haven't built it yet. the honest version of the roadmap is: get the core save-and-retrieve loop working well for people who will type it once, then figure out what reduces that friction further. voice is probably on that list.
This kind of gap makes sense: the story resonates, but the CTA asks people to do a future-oriented action. The pain moment is "I lost Dave"; the conversion moment has to be "save Dave before you lose him".
If it were me, I'd test a single channel that lines up with that timing: contractor referral/invoice QR, text-to-save (send someone a link they can tap while they're on the phone), or even a super simple "Add to contacts" moment inside the first job.
Also curious: for the 4 waitlist signups, what did they say in the signup flow? Did they understand the promise? Sometimes the issue isn't volume, it's clarity of "what do I get right now" versus "join a waitlist".
the waitlist flow doesn't ask why, which is probably a mistake i should fix. the CTA is "be first when the native app launches" which is future-oriented by design since the PWA is live now and native iOS/Android is coming. but you're pointing at something real: if someone lands and the answer to "what do i get right now" isn't clear, the waitlist ask is too much friction. might be worth adding a secondary CTA that just says "try it now" more prominently alongside the waitlist.
that 40k → 4 gap is brutal but tbh super common for utility apps with low frequency use case. the issue often isnt the funnel, its that "i lost dave's number" is a once-a-year pain — by the time it hits, ppl already googled or asked a friend and forgot you exist. might be worth flipping the angle: instead of fighting for top-of-mind on the rare-pain side, lean into "save before you lose it" right after first contractor interaction (qr on invoice, sms reminder, whatever). reframe from "find dave again" to "never lose dave in the first place". diff intent, prob way higher conversion bcs you catch ppl when the contact is fresh. also imo 40k reddit views = real signal the story works, dont over-rotate on conversion math this early. curious what activation looks like for the 4 ppl who did sign up — do they actually come back and use it?
"save before you lose it" is a stronger frame than "find dave again," you're right. the retention question is the honest one i don't have a clean answer to yet. what i do know is the people who've added a few things tend to open it the next time they need one of those things, that's the loop i'm trying to build on. the barcode scan making it fast to add stuff helps. still early.
yeah the "save before you lose it" framing only works if you can intercept the first contractor interaction — invoice, sms, qr on the truck. once theyre home and the kitchens dry the moment is gone. one cheap test: ask the 4 waitlist ppl how they first heard about the painter/plumber they actually lost. if its mostly word-of-mouth, the entry point is probably "friend just recommended X — save them now" not search. curious if youve seen the activation pattern on those 4 yet.
That's a brutal ratio but at least you know the traffic is real — sounds like the landing page or messaging might be the bottleneck, which is way easier to fix than getting views in the first place.
yeah that's the more optimistic read and probably closer to true than "the product is wrong." the story works at the reddit level, 40k views says the problem resonates. what doesn't work is the path from "that's me" to "i'm opening this app." the landing page probably still leads with the single emotional story when it should lead with the everyday use case. easier to fix than finding the audience in the first place.
What stands out to me is that the story clearly resonates, but resonance and behavior are not always the same thing.
Losing a trusted contractor number is memorable. A lot of people will immediately relate to it. But the harder question is whether the pain stays active long enough for someone to change their habits before it happens again.
I think that is a very different problem from distribution.
I have noticed something similar in another space. People strongly agree a problem exists, but still do not adopt a tool unless the pain feels present right now, not just familiar in hindsight.
That gap between “I relate to this” and “I need this today” is probably where the real signal is.
Curious whether the people joining the waitlist are recent cases where this just happened, versus people who simply recognize the situation.
that distinction between "i relate to this" and "i need this today" is exactly the gap. the contractor story is retrospective, people recognize it as something that happened, not something happening. the everyday version (tuesday at home depot, can't remember the filter size) is present-tense pain. i just haven't been telling that story as loudly. curious whether you're seeing the same pattern in what you're building, sounds like you've sat with this problem before.
Yeah, I think I am seeing something very similar.
In the WordPress space, people often strongly relate to stories about broken sites, plugin conflicts, or admin clutter. But those are usually retrospective pains too. They remember the frustration after it happened.
The stronger behavioral signals tend to appear during active moments of friction:
That is when the pain becomes present-tense instead of historical.
Your Home Depot example feels important because it shifts the story from “this once happened to me” into “this is interrupting me right now.”
This comment was deleted a month ago.