I built the product. Now I’m questioning whether users will build the habit.

That’s a useful point, especially the physical file/folder system.

I’m realizing I shouldn’t assume an existing system is bad just because it isn’t digital. If someone can reliably find the warranty or proof when they need it, VaultlyKeep has to offer something meaningfully better rather than simply replacing the folder.

What I’d really like to understand is where that system breaks down.

Have you personally used a physical file for receipts or warranties, and if so, what tends to go wrong first — forgetting to put something in it, struggling to find the right document later, or discovering the information is incomplete when you need it?

That’s exactly the risk I’m trying to understand.

Right now VaultlyKeep isn’t passively pulling purchases from someone’s email or photo library. The current flow is intentional: capture or upload the receipt, let VaultlyKeep suggest some of the purchase details where supported, review them, and save the record.

So I’m definitely not assuming the manual part is solved just because I’ve made it faster.

Your point about “I’ll do it later” is probably the dangerous moment. If saving an important purchase still feels like admin, even a useful product could lose to doing nothing.

I’m curious where your own threshold is: after buying something expensive, would a quick photo + review feel lightweight enough, or would you still expect the purchase to appear automatically before you’d consistently use something like this?

That distinction between a feature problem and a product-engineering problem is useful.

I’m starting to see the same pattern in the feedback here: VaultlyKeep can already organize the record, track return and warranty dates, and surface reminders once something is saved. The bigger unanswered question may be whether enough people ever get through that first capture consistently.

Automation keeps coming up, but I’m trying not to jump straight from “manual capture is a risk” to “therefore build every possible integration.”

I’d rather find the smallest change that actually alters the behavior — whether that’s a much faster capture flow, forwarding a receipt email, a reminder at the right moment, or eventually something more automatic.

The experiment I need now is probably less “which feature should I add?” and more “what is the minimum effort people will reliably tolerate at the moment of purchase?”

That’s a really useful reframing.

I’ve been thinking about the habit as “will someone remember to save purchases consistently?”, but maybe that’s too broad. It may be enough if VaultlyKeep becomes the thing someone reaches for when a purchase feels important enough that losing the receipt, warranty details, or return deadline would actually hurt.

Electronics and appliances are already categories I’m especially interested in testing for that reason.

The immediate-payoff point also keeps coming up. VaultlyKeep can already track return windows, warranty expiry and reminders, so I’m starting to wonder whether the bigger opportunity is making that value much more obvious immediately after the first save.

If you think about your own purchases, what makes something cross that threshold for you — price, warranty length, difficulty replacing it, likelihood of returning it, or something else?

That distinction between “prepare now for a future problem” and “get something useful immediately” is really interesting.

VaultlyKeep already tracks things like warranty countdowns and return windows once the purchase details are saved, so one thing I probably need to test is whether I’m surfacing that immediate value strongly enough rather than treating the save itself as the finish line.

The email-forwarding idea is interesting too, although I don’t want to jump straight to automation before I know which friction is actually bigger.

If you had to choose between the two, which would matter more to you personally: making the current photo + review flow almost effortless, or getting a much clearer immediate payoff right after you save the purchase?

Not yet — and I’m trying not to call something a signal before I have enough actual usage behind it.

My current hypothesis is that past pain may matter more than general interest. Someone who has already lost a receipt, missed a return window, or struggled to find purchase proof seems more likely to understand why saving the record now is worth the effort.

But even that doesn’t tell me whether they’ll actually build the habit. I’m trying to separate three things: whether someone signs up, whether they save a real purchase, and whether they come back and do it again without me prompting them.

That last one is the signal I’m most interested in.

I’m curious about the parallel you’re seeing with AI answers — what does “acting before they need it” look like in your case?

Really appreciate this. The shift from building to getting real people to actually use something has definitely felt like a completely different skill set.

Your point about momentum taking time resonates, although I’m trying to be careful not to mistake traffic or attention for actual usage. Right now I’m especially interested in what gets someone from “this looks useful” to actually using VaultlyKeep with a real purchase and then coming back again.

You mentioned that you’re starting to see momentum with NexusDocs — what changed first for you? Was there a particular channel, piece of content, search query, or user conversation where you started seeing people actually use the product rather than just visit the site?

That monitor example is exactly the kind of failure I’m trying to understand — especially because you already had a system and it still wasn’t reliable when you actually needed the proof.

The checkout point seems important too. If the receipt email is already sitting in front of you, maybe the question isn’t whether you’d remember VaultlyKeep later, but how little extra action you’d tolerate right then.

For your own workflow, would forwarding that receipt email to a VaultlyKeep address feel automatic enough, or do you think even that one extra step would eventually get skipped unless the capture happened without you doing anything?

Yeah — I’m increasingly convinced I may have framed the problem too much as “how do I build the habit?” when the stronger question is “how much of the remembering can I remove?”

Right now VaultlyKeep still requires an intentional action: capture or upload the receipt, review the suggested purchase details where available, and save it. It isn’t passively pulling purchases from an inbox or photo library.

Your point is useful because those are very different levels of friction. Making the current flow faster might help once someone remembers to start, but it doesn’t solve “I never thought about VaultlyKeep at all.”

I don’t want to assume full passive capture is the answer before testing it, though.

For your own behavior, would something like forwarding a purchase email or sharing a receipt photo into VaultlyKeep be low-friction enough, or do you think even that still loses unless the record is created automatically?

That’s making me question whether I’ve been using “habit” too loosely.

Maybe the behavior I actually need isn’t “remember VaultlyKeep regularly.” It’s much narrower: when a purchase has a meaningful future consequence, can the user get it into VaultlyKeep with so little effort that the reminder/retrieval value later justifies that one action?

The deadline angle is interesting because VaultlyKeep already tracks return windows, warranty expiry and reminders. So there may be a positioning/onboarding problem here as much as a feature problem: perhaps I should be making “what happens next with this purchase?” much more prominent immediately after it’s saved.

On audience, I’m currently testing primarily with consumers — electronics buyers, homeowners, renters, families, people managing warranties and higher-value household purchases. I haven’t been treating self-employed/business users as the primary market.

But your point makes them interesting as a comparison group because the motivation is already externally imposed.

I think the question I need to test now is less “can I make receipt-keeping a habit?” and more “which purchase situations already create enough pressure that saving the record feels obviously worth doing?”

That business/private split is probably the most useful distinction anyone has given me on this so far.

You’re right — I was still thinking a lot in terms of “which purchases feel important enough to save?”, but your behavior suggests the trigger may be less about price and more about expecting a future consequence.

With the business receipts, someone is going to ask. With the private ones, you’ve effectively decided in advance that the possible future loss isn’t worth the effort today. That’s a much tougher thing for VaultlyKeep to compete with than another receipt app.

It makes me want to test whether the strongest use cases are the ones where there’s already a clear future event attached to the purchase — a return deadline, warranty, resale, insurance documentation, something like that — rather than assuming people should archive everything.

And yes, absolutely run your tool on VaultlyKeep. Blunt is useful. Use the public site and send me whatever it produces — I’d be interested to see both what it gets right and where it completely misunderstands the product.

One thing I’m curious about from your own split: for a personal purchase, what future event would make you think “I should actually keep this one”?

That monitor example is really useful because the receipt existed — the system failed at retrieval, not capture.

You remembered the brand, but the evidence was filed under the reseller and buried in a generic attachment. That’s a different problem from simply losing the receipt.

It makes me want to separate two failure modes in the testing: “I never saved it properly” versus “I saved it somewhere but couldn’t retrieve it when I needed it.”

I’m not ready to assume email/photo search is the solution yet, but that distinction could change what I prioritize.

And I completely agree on the interview question. “Walk me through the last time you needed proof of purchase” is producing much better evidence than asking whether someone likes the idea.

Thinking back to the monitor case, if you’d had a reliable way to search across the receipt information you already had, would that have solved the problem for you — or was there still something else missing?

This is probably the most useful experimental framing I’ve heard in the thread.

The “untested vs disproven” distinction especially stands out. If I recruit too few people, or most never get through the first real-purchase save, then a lack of second saves doesn’t necessarily tell me anything about retention — I may never have had a valid habit test in the first place.

I also like the idea of writing the decision rule before seeing the result. That would make it much harder for me to move the goalposts once I’m emotionally attached to the outcome.

For VaultlyKeep, I’m thinking the sequence needs to be something like: qualified tester → first real purchase saved → then start measuring for a second unprompted qualifying purchase.

How would you decide the minimum number of people who need to complete that first save before you’d consider the retention test valid rather than underpowered?

Appreciate the disclosure — and I think the trigger point is still very useful.

I’m increasingly convinced the better question is not “how do I make people remember VaultlyKeep?” but “what already happens at purchase time that VaultlyKeep can attach to?”

Email confirmations, checkout moments, and similar triggers are all interesting hypotheses, but I want to validate the behavior before committing to a specific integration.

The one part I’d probably change in your test is the “10 times in a month” threshold. Some users may only have one or two purchases worth tracking in that period, so I’d rather measure whether they capture the next few relevant purchases without prompting.

For a low-frequency product like this, would you still use a fixed repetition target, or measure adoption across the next 3–5 qualifying purchase events instead?

That’s really useful because you’re describing the reason you actually stopped using other tools, not just what you prefer in theory.

I’m starting to think I need to treat every extra step in the purchase-saving flow as something that has to earn its place.

For you personally, where does a workflow start to feel like “too much”? If it were something like take/upload a receipt → confirm a few suggested details → save, would that still feel lightweight, or is even that already close to the limit?

I think “workflow after an event” is a better framing for me than “daily habit.”

If someone only needs VaultlyKeep when an important purchase happens, then daily retention could actually be a misleading metric. The more meaningful behavior may be whether they naturally capture the purchase while the receipt is already in front of them — and whether they do that again on the next relevant purchase.

I especially like your suggestion to reconstruct the last three real purchases instead of asking what people think they would do. That should expose the actual sequence: where the receipt appeared, what they did with it, what they ignored, and where friction entered.

The share sheet/email forwarding ideas are interesting too, but I want to understand that existing behavior first before assuming which capture mechanism is the answer.

I think the deferred-reward gap is the part I’m underestimating the most.

The user is being asked to do something now for a payoff that might not arrive for months, so even a decent capture flow may still feel like unnecessary admin.

I also want to be careful with the assumption that the need is already proven. People definitely have messy systems, but I still need to see whether that pain is strong enough to change behavior consistently.

Your under-10-second idea gives me a useful experiment, though: compare a very low-friction capture path against the current intentional save-and-review flow and see whether people actually come back for the next important purchase.

If you were running that test, would you judge success mainly by second unprompted save, or by something earlier in the funnel?

I think you’re pointing at two separate questions that I need to be careful not to collapse together.

The first is capture friction. An order-confirmation email is interesting because it already exists at the moment of purchase, so using that as a trigger could remove a lot of the “remember to do this later” problem. I wouldn’t want to assume forwarding/import is the answer from one conversation, but it’s a hypothesis worth testing.

The second is a much bigger question: whether the consumer is actually the right buyer.

I’m deliberately trying to validate the consumer case first before moving toward contractors, practices, or other business users. If consumers understand the problem but still won’t adopt or pay even when the workflow is very low-friction, that would be meaningful evidence that I may need to reconsider the buyer.

What evidence would convince you that the consumer use case is strong enough to keep pursuing rather than moving toward a business user?

I really like the distinction between the first useful save and the second unprompted save.

The first tells me someone understood the workflow and saw enough value to complete it. The second is much closer to evidence that VaultlyKeep actually found a place in their behavior.

I also agree that “habit” here probably shouldn’t mean daily use. If someone naturally returns whenever an important purchase, return, warranty, or similar event happens, that may be the real behavior I should care about.

The tricky part is measurement speed, since those events might be weeks apart. How would you test for that second unprompted behavior early without artificially prompting the user and contaminating the signal?

That’s a useful distinction, especially the idea that predictability can matter more than polishing the experience around an inconsistent trigger.

I’m not sure the fixed-time part maps directly to VaultlyKeep, though. A digest has something naturally recurring every day, whereas saving a purchase is irregular — someone might buy nothing worth recording for weeks and then suddenly buy an appliance or expensive device.

My concern would be that a daily 9am-style reminder quickly becomes irrelevant noise.

The principle I’m taking from your example is probably “attach the behavior to a reliable existing trigger,” rather than necessarily “attach it to a clock.”

For something low-frequency and event-driven like this, what kind of trigger would you test before resorting to scheduled reminders?

I’m leaning much more toward the second idea.

Daily notifications feel like they could easily become noise, especially for something people don’t need every day. The more interesting question is whether VaultlyKeep can connect to a moment that already exists in the user’s purchase workflow.

Right now I’m still testing the basic manual flow rather than claiming I’ve solved that trigger. I want to first learn whether the bigger failure is “saving this takes too much effort” or simply “I forgot to do it at all.”

If it turns out to be the second one consistently, then the trigger itself may be as important as the capture flow.

That’s exactly the signal I’m trying to define carefully.

The first save matters, but I wouldn’t call that a habit. The stronger signal I’m watching for is whether someone saves a real purchase, gets through the workflow, and then comes back later to use VaultlyKeep again for another real purchase or purchase-related need without me having to chase them.

So I’m thinking about it as activation first, then repeat usage. If people register and save one receipt but never return, that would be a pretty clear warning that I’ve created something people understand but don’t naturally keep using.

I don’t have enough data yet to claim the habit is forming, which is why this stage feels so important.

That’s the part I’m wrestling with most.

If VaultlyKeep only asks someone to do extra work today in exchange for a benefit they might feel months later, reducing friction may still not be enough. There probably needs to be some value the user can feel immediately after saving the purchase.

I’m trying to understand what that immediate value should be — clearer warranty/return deadlines, having everything organized in one place, confidence that the important details were captured, or something else.

For a product like this, what would make the first save feel useful immediately rather than just like preparation for a future problem?

This is really useful — especially the distinction between a “receipt habit” and a trigger around purchases that actually matter.

Your current setup is also exactly the kind of behavior I want to test against: the information exists, but it’s fragmented across email, photos, paper, and retailer accounts until something goes wrong.

And yes, I’d really value having you test VaultlyKeep with a real purchase.

Rather than asking you to explore everything, I’d love for you to pick one genuine purchase you’d care about finding again later — ideally something like an electronic, appliance, tool, or other higher-value item — and try saving it in VaultlyKeep.

Then tell me:

1. Where you hesitate or feel the workflow asks too much.
2. What feels unnecessary.
3. Whether you’d realistically do the same thing after your next important purchase.

You can try it here: https://link.vaultlykeep.com/warranty-tracker

I’m much more interested in where the workflow breaks your natural behavior than whether you like the idea.

That’s a useful distinction — use the failure moment as the entry point instead of assuming the habit already exists.

VaultlyKeep already lets someone upload an existing receipt and turn it into a structured purchase record, so the “retroactive save” behavior is something I can test without inventing a completely new workflow.

The question I’d still want to validate is what happens after that first rescue. Does someone save one problematic purchase and disappear, or does the failure actually change how they handle the next important purchase?

If you were testing this, what would you consider the minimum useful retroactive save: just the receipt, or receipt + purchase/warranty details?

That boiler example is exactly the kind of failure I was hoping to understand.

What really stands out is the 18-month gap — at purchase time, taking a photo probably felt completely sufficient, and there was no immediate reason to do anything more.

That makes me think the challenge for VaultlyKeep isn’t just making filing easy; it’s whether I can make the upfront effort feel worthwhile before the future problem exists.

Thinking back to that purchase, is there anything that realistically would have persuaded you to do one extra step at the time — for example confirming the important details were readable — or would even that have felt like unnecessary admin?

That feature-validation vs behavior-validation distinction is really helpful.

I agree that “would you use this?” tells me very little compared with seeing what someone actually does when they’re missing a receipt or dealing with a warranty/return problem.

The part I’m especially interested in now is what happens after that friction moment. A failure might be what gets someone to try VaultlyKeep, but the bigger test is whether that experience is strong enough to make them save the next important purchase before another failure happens.

So I’m starting to think I need to measure two things separately: what triggers the first use, and what creates the repeat habit.

Have you seen products where the pain event drove initial adoption but still wasn’t enough to create ongoing behavior?

That distinction between “I have a system” and “the last time my system failed” is really useful.

I also like your point about catching people close to the actual failure event — return problems, warranty issues, missing proof of purchase — because the pain and current workaround are much easier to observe there than through a hypothetical question.

I probably wouldn’t recruit only people who are mid-failure, though. I want to learn both sides: what makes the pain acute enough to try something new, and whether someone will still use VaultlyKeep on the ordinary purchases between those rare moments.

When you’ve seen these systems fail, what failure seems most common: not being able to find the receipt, missing the deadline, or having incomplete purchase information?

That’s exactly what I’m trying to understand.

Someone who already has a good system is probably a more interesting test than someone who has no system at all. If their setup still breaks down when they actually need the information, that failure point could be really revealing.

Have you personally had a system like that fail — and if so, what went wrong when you needed the receipt or purchase information?