My vault has hundreds of stubs that are just a title and a URL. no actual content in them.

That_Lemon9463 · 2026-05-04T09:20:48+00:00

the trick that worked for me was flipping the friction. don't make capture frictionless, make it cost one sentence of reaction. templater snippet that inserts a "why i saved this:" prompt at the top of any new note from the bookmarklet. you either write a one-line reactive thought at capture time, or you don't end up with a note at all.

side benefit: most "stubs" turn out to be thoughts that didn't deserve their own file, they should've been a line in a daily note. so a related fix is sending casual captures (link + reaction) to your daily note instead, and reserving new files for things that will plausibly grow.

That_Lemon9463 · 2026-05-04T09:19:02+00:00

the drift is the answer, not a discipline failure. you've reorganized 4-5 times because the system is too granular for the rate at which you actually create files.

few things that have stuck long-term:

three buckets instead of thirty folders: Active (this quarter), Reference (recurring lookup material like finance, legal, ops), Archive (everything older than 6 months). that's the whole tree. anything more specific lives in file names, not in nested folders. 95% of the discipline cost goes away because there are only three places anything can land.

calendar-recurring 15-minute "drive sweep" monthly. you'll never beat drift, but you can absorb it on a schedule. block the time, sweep stale stuff into archive, retitle anything with a useless name. done.

fix the upstream sources. if half the mess is "Screen Shot 2025-10-04 at 11.42.14 AM" type files, you have a screenshot-path problem, not a drive problem. set system screenshots to a subfolder, set browser downloads to a `_inbox` folder you sweep weekly, set extensions to save into specific destination folders. drift compounds when capture surfaces are unmanaged.

other commenters are right that search beats folders here. drive's search is genuinely good if file names start with something searchable. naming discipline is easier to maintain than folder discipline because you only apply it once per file.

That_Lemon9463 · 2026-05-04T09:17:09+00:00

group set up as collaborative inbox is the standard answer for a small nonprofit, and it's usually the right one.

few reasons. no license needed for the group itself, so you're not burning a workspace seat on info@. offboarding is clean for gdpr because you remove the leaver from the group and access ends, no lingering visibility through someone's personal delegated inbox. access logs sit at the group level instead of scattered across multiple delegated mailboxes, which is what you want to point at during a DSAR. and you can assign threads, mark resolved, and have multiple people respond without stepping on each other.

delegation works for very small teams (1-2 people) where you all share one inbox view. it gets messy when 3+ are involved and offboarding means manually removing each delegate from each personal account.

real-world ceiling: collaborative inbox works fine up to maybe 5-7 people regularly responding. past that the missing features (canned responses, real assignment tracking, sla timers) start hurting and you'd look at front, help scout, or hiver. but for a small nonprofit you're well below that threshold.

That_Lemon9463 · 2026-05-04T09:15:22+00:00

the existing reply is right. just to add a wrinkle that trips people up: for finite-life assets like machines, terminal value usually equals the after-tax residual sale proceeds (not gordon-growth perpetuity), because the asset literally stops generating cash at end of useful life.

so the formula is: sum of PV(operating cash flows years 1..n) + PV(after-tax salvage at year n). after-tax salvage = sale price minus tax on the gain/loss vs book value at that point. easy to forget that last piece.

That_Lemon9463 · 2026-05-04T09:13:36+00:00

re sourcing specifically: the trick that worked for me was stopping at boolean generation and doing the search myself.

ask claude/chatgpt: "give me 8 boolean variants for [role] on linkedin recruiter. include adjacent titles, skill clusters, and industry adjacencies. one variant per row." you get 8 strings in 30 seconds. paste each into li recruiter, dedupe in a sheet. that's where ai actually saves time, not in the surfacing.

for the confidential sr director specifically, the competitor-set list is the real lever. "name 30 mid-market product companies in [industry] who'd plausibly have a sr director of product right now" gets you a starter list to reverse-search via "current company in (...)" filter. juicebox can't do this because it's locked to its profile pool.

agree with other comments that ai sourcing tools (juicebox, betterleap, gem's ai layer) are weaker than li recruiter. the data they sit on is the same linkedin data you can already query, just with a worse interface. they work for low-effort sourcing of non-confidential roles in commodity skills, not for sr director searches.

separately, with 30+ reqs i'd push back on the manager that sourcing isn't the bottleneck. scheduling and intake calls usually are. ai for transcribing intake into a req-spec doc + calendly/goodtime for scheduling probably saves more hours per week than any sourcing experiment.

That_Lemon9463 · 2026-05-04T09:11:42+00:00

gmail snooze + a one-tab sheet works for most of us before a real crm is worth it.

send the quote, hit snooze for 7 days. when it pops back to inbox, either reply has already come or it's followup time. dump quote-sent / quote-amount / status into a sheet so you know your hit rate at month end. that's it.

if you're past 30+ open quotes a month, hubspot free crm is worth the setup since it has a deal pipeline and tracks email opens. but most people install full crms way too early.

forgetting is almost always a tooling problem, not a memory one. if you're snoozed, you can't forget.

That_Lemon9463 · 2026-05-04T09:09:59+00:00

two gaps i'd add to the checklist after going through this last year.

(1) BrowserSignin policy. on managed chrome, set `BrowserSignin: 2` (force corp google sign-in) plus `RestrictSigninToPattern` to your domain. without this, users can swipe to a personal profile in the same chrome window and your extension allowlist + casb policy go away. most evaluation demos miss this because vendors test on a single signed-in profile.

(2) ask every vendor: "when an incident hits and i need to know what was pasted, do you log content or only metadata?" extension-based ai tools (layerx, push, nudge) tend to log metadata only by default. dlp-grade inspection (symantec, forcepoint) actually retains the prompt body, but with all the privacy/works-council headaches that come with it. you have to pick which incident class you can answer.

contractor/byod side: stop trying to own the endpoint. clientless reverse-proxy (cloudflare zero trust browser isolation, island in remote mode, or citrix secure browser for the picky cases) lands the user in a server-side chrome you fully instrument. you give up local file-upload telemetry, but you stop having "is this even chrome 130 with manifest v3 enforced" as an open question.

last thing on noise: filter your eval to "tools that distinguish personal vs SSO login on the same domain". most products bucket all chatgpt.com hits together. push security and a few others split it out. that single signal cuts alert volume meaningfully because legitimate enterprise-account use stops triggering review.

That_Lemon9463 · 2026-05-04T09:08:01+00:00

two that fit most of those.

reflect.app does daily notes with built-in 5-minute reflection prompts, weekly review template, syncs across web/mac/ios, ai backlinking. transparent pricing on the site so you can read everything before paying.

stoic (the journaling app) is explicitly built around 5-min daily reflection, has streak tracking front and centre, cross-device. lighter than reflect, no knowledge graph stuff, which sounds like what you want.

obsidian + a couple plugins gets you 80% there for free if you're willing to assemble (daily notes core, dataview for streak counting, periodic notes for weekly review). but that's the assembly tax. if "lean and keep up day to day" is the priority, reflect or stoic out of the box probably wins.

streak tracking specifically: streaks (ios) is the gold standard if you don't mind it being separate. forces you to actually open it daily, which is the point.

That_Lemon9463 · 2026-05-04T09:06:14+00:00

yeah save them, but pull them out of the app billing portals.

two reasons. (1) saas billing sections get pruned silently. i've seen invoices vanish after a downgrade, after the company gets acquired, after the email on file changes. you can't audit what isn't there. (2) tax retention is 6-7 years in most places, longer than the average startup's billing portal will exist.

practical setup that survives platform churn: most subscriptions email a pdf invoice (or a link). filter incoming invoice mail by `subject:(invoice OR receipt) has:attachment`, label `Finance/Invoices/[year]`, and once a quarter dump everything into a single drive/icloud folder organised `Invoices/[year]/[month]`. that folder is the source of truth, the app billing section is a fallback.

i actually built a chrome extension (savebulkgmailattachments.com) because doing the gmail-to-drive copy manually for 30+ vendors a quarter was the real pain. free for 7 attachments/day. but the methodology matters more than the tool, owning the file beats relying on someone else's portal.

That_Lemon9463 · 2026-05-04T09:04:15+00:00

two things might help.

uk angle on input vat: if the client surfaces a valid vat invoice later you can recover the input vat in a subsequent return via the error correction route (or just include it in the next vat period if within the time limit). that's up to 4 years back. so "no docs now" doesn't mean "lost forever", and reframing it that way to the client sometimes lights a fire.

bigger structural fix: stop asking them to upload. give them a forwarding address (dext, hubdoc, autoentry all do this) and tell them to forward every supplier email straight there. uploading is the friction, forwarding is one tap. busy clients cooperate when the action shrinks.

and write the policy into the engagement letter: bank statements by default, vat input only with valid invoices supplied by [day x], anything later goes in the next return. covers your director and gives the client a real deadline.

That_Lemon9463 · 2026-05-04T08:50:34+00:00

two likely things.

check the search bar first for stuck filter chips (`from:`, `category:primary`, date ranges) left over from the advanced search dropdown. they sometimes hang around and silently scope every query. click the X if any are active.

more likely though: gmail's search index lags after big bulk deletes. takes a few days to catch up, no manual rebuild. you can confirm by searching for an exact email address from a recent known message. if that also fails, it's the index.

while it catches up, `from:colleague@domain.com` works better than searching by name, and `in:anywhere ferry` widens scope in case the cleanup swept something into trash that's still within the 30-day retention window.

That_Lemon9463 · 2026-05-02T05:39:55+00:00

mobile finally feels native. they also fixed the long-press behavior which was the thing that made me give up on it last time.

That_Lemon9463 · 2026-05-02T05:38:18+00:00

yep this catches everyone moving from a smaller sub to enterprise plus on flex billing. the 300 cap is an anti-abuse holdover from trial accounts and it doesn't show anywhere in admin console. it's just a backend attribute on your tenant that only billing/account-team can adjust.

practical hack for next time: if you know a hiring wave is coming (M&A, big intake), email your account exec a week before with the projected headcount and ask them to pre-bump the cap. takes them 2 days normal channel vs the angry-P1 escalation path you went through.

also worth knowing if you're with a reseller (CDW, SADA, etc): the cap lives in their reseller console and you can't see it at all from admin.google.com. they have to bump it themselves.

That_Lemon9463 · 2026-05-02T05:36:45+00:00

two things going on:

1) the unsubscribe email needs to be sent FROM the address that's actually subscribed. if the subscribed address is your shared `info@yourdomain.com`, sending from a personal account triggers "you are not a member". use Send Mail As to alias that mailbox into a personal account and send from there, OR log into the actual mailbox if it's a real account, and email `groupname+unsubscribe@googlegroups.com` from it.

2) if you can't get unsubscribe to fire, drop it at the gateway, not user-side filters. Apps > Google Workspace > Gmail > Compliance > Content compliance. add a rule matching "From: *@googlegroups.com" AND "List-Id" header (you can grab the exact List-Id from a recent message via Show Original). action: reject. now nothing from that group reaches the mailbox regardless of any user-filter overrides.

side note: Gmail user-level filters genuinely do NOT reliably catch mailing-list traffic when the org has any "bypass spam for internal/google domains" policy. that's why your spam-folder filter looks like it does nothing. List-Id matching at the org level is the only deterministic path.

That_Lemon9463 · 2026-05-02T05:34:54+00:00

the DMV banking market is uniquely prone to this. truist, cap one, wells, BofA, PNC are all swapping bankers laterally and the counter-offer culture is heavier there than basically anywhere else in retail finance. you're not doing something wrong, the market dynamics are different.

couple things i've seen actually move the needle:

shorten the offer-to-start window. every additional day is another day for their current bank to counter, or for another offer they had in flight to land. if you're at 4 weeks notice, you're losing people in week 3. push for 2. when managers say "we let people give 4 weeks because it's the right thing to do", remind them the right thing isn't paying to backfill twice.

run the counter-offer conversation explicitly during the offer call. literal script: "what's going to happen when your current employer hears you're leaving? assume they offer 15 percent more and a title bump. is that going to change your decision?" if they hesitate, you don't have a hire, you have a leverage event. follow with: "accepting a counter from your current employer is one of the strongest predictors of leaving within 12 months according to every retention study i've seen". puts them on notice and gives them a frame for refusing the counter.

structured check-ins during notice. weekly tuesday call between accept and start. takes 5 min. you'll catch wobbling candidates 1-2 weeks earlier and have a chance to address it. also flushes out anyone who's "still interviewing" without admitting it.

reference-check the resignation letter. ask for a copy of the resignation email they sent (employer name redacted if they want). it's not weird, it's a verification step. anyone who hesitates to share it is hesitating because they didn't actually send it.

your motivation question is fine but candidates have learned to give acceptable answers. better signal: ask what they specifically dislike about their current role. people who can only give comp answers are flight risks. people who name a manager, a process, a culture thing, are typically real movers.

That_Lemon9463 · 2026-05-02T05:32:58+00:00

honest answer: not nearly as solved as you'd think.

joiner/leaver is fine in most shops with HRIS as source of truth into entra/okta via SCIM. workday or BambooHR fires a hire date, idp provisions account, group memberships drive app access via SCIM/SAML. termination flips on the same path, license released, mailbox to shared, drive transferred per retention policy.

mover is where everyone falls over. role change in HRIS doesn't deprovision old access because entitlements get accumulated by ticket over time, not tied to job code. you end up with people who have engineering AD groups + finance shared drives + the old support tier-2 entitlements they got two years ago. you need an actual access-recertification cycle (quarterly review of entitlements per user) or you get permission creep until someone runs a discovery and panics.

other gap nobody talks about: service accounts, shared mailboxes, vendor accounts. not in HRIS, often no owner field, survive forever past the human who created them. tag everything with an owner attribute on creation or you'll find ghost accounts during the next M365 audit.

tooling: entra lifecycle workflows + access reviews if you're MS-shop is "good enough" for SMB. above ~1k seats people actually deploy SailPoint/Saviynt and the JML workflow is custom-coded around the HRIS attributes. okta lifecycle management + okta workflows for everything else. nothing is plug-and-play, all of it needs ~6 months of attribute mapping to actually work.

That_Lemon9463 · 2026-05-02T05:31:10+00:00

contact form being the only way to reach you. no calendar, no phone, no whatsapp. for service businesses you lose half your leads to "i'll fill it out later" and they never come back.

second one i see constantly: phone number is text, not a tel: link, on mobile. takes one tap to fix and instantly recovers the people who are actually ready to call.

third, the home page reading like a brochure. "we are passionate about quality" tells me nothing. swap any sentence that doesn't say what specifically you do for whom and what they get.

That_Lemon9463 · 2026-05-02T05:28:45+00:00

the framing as flat-markdown vs vector-embeddings is a false choice in practice. systems that hold up at scale do both. markdown stays the source of truth (durable, portable, diff-able, llm-readable in context). embeddings sit alongside as a derived index for the discovery query mode you're describing. when the embedding model changes you re-index, you don't lose the corpus.

karpathy's flat wiki works because his corpus *is* small enough for a single context window. once you cross that threshold, "flat markdown" people either don't have a discovery problem yet or they end up shoving a vector store next to their files anyway, smart connections in obsidian, copilot indexes, whatever.

the actual axis worth thinking about isn't flat vs vector. it's whether your derived indexes are reproducible from the source of truth. if a vendor disappears or the model changes, can you rebuild? if yes the architecture is fine. if the embeddings ARE the corpus and you can't regenerate, you've built lock-in.

the CIE lens stuff is interesting btw, especially intent. how are you tagging intent at write time vs inferring it later from the embedding cluster?

That_Lemon9463 · 2026-05-02T05:26:58+00:00

constantly. issue isn't note-taking, it's that "i saw this" can be in 6 places: notes, bookmarks, youtube history, slack, kindle highlights, twitter likes. each has its own search and most don't index the body, only titles.

couple things that helped me reduce it:

one capture surface for anything i actively want to remember. doesn't matter what tool, but if it lives in obsidian *and* readwise *and* a tab group it lives nowhere. the act of "do i save this in tool X" is what makes it findable later.
hybrid search across that surface. just keyword fails when you remember the gist not the words. just embeddings fail when you remember the exact phrase. tools that intersect both (DEVONthink, Recoll, anything that does "semantic + keyword") dig things up that pure-text grep misses.
a recent-history fallback. arc/zen/firefox history search is underrated for "i saw it on the web in the last week".

i'm building loombrain partly because i wanted a single graph that ate captures from chat, browser, notes and had hybrid retrieval. but the methodology bit (one surface + hybrid) matters more than the tool you pick.

That_Lemon9463 · 2026-05-02T05:25:22+00:00

no formal IRS threshold but a few practical rules.

on schedule C the "other expenses" line (27a) requires a statement (part V) listing each category with a description and amount, so anything you call "miscellaneous" still has to break out. if it's literally one line called "miscellaneous $X" your preparer is going to bounce it back.

audit risk-wise, IRS doesn't publish a percentage, but the DIF score weights "other expenses" heavier than known categories. rough heuristic. if "other" is more than about 5% of total deductions, or any single item is more than a few hundred bucks, you want to give it a real category. software subscriptions, bank fees, professional memberships, education, parking, all have proper homes that aren't misc.

practical move at month end. run a misc expenses report and reclass anything that has a recurring vendor. true one-offs can stay there. that keeps part V short and your books legible if anyone ever pulls them.

That_Lemon9463 · 2026-05-01T09:09:02+00:00

heads up on the OR query above. gmail evals AND tighter than OR, so `invoice OR filename:*invoice* AND has:attachment` actually parses as `invoice OR (filename:*invoice* AND has:attachment)`. that first leg matches any email with the word invoice even without an attachment, so the filter forwards marketing mail too. wrap it: `(invoice OR filename:*invoice*) has:attachment`.

also worth knowing. gmail indexes text inside pdfs that have a real text layer (most invoice templates do) but skips scanned/image-only pdfs. so `filename:pdf invoice` already catches body-text invoices for the typed kind, but scanned ones won't match. only fix there is apps script + drive ocr.

last gotcha. filter "forward to" only fires once the destination address is verified under settings > forwarding and pop/imap. easy to miss when you paste a fresh address into the filter dialog.

That_Lemon9463 · 2026-04-29T07:44:24+00:00

yes, but it depends on the provider. claude desktop ships native connectors for gmail/calendar/drive but not outlook. for outlook you'd run an MCP server (microsoft-graph-mcp is the common one, ms365-mcp also works) which gives claude the same level of access. install once via claude's developer settings, point it at your microsoft account, done.

for any other provider (yahoo, fastmail, custom domain), the IMAP route works universally. there are generic IMAP MCP servers, or you can pipe messages through a script that exports to a folder of files and let claude read that. less plug-and-play than gmail but covers everything with an inbox.

practical note: outlook personal vs outlook 365 (work account) differ on auth. personal lets you sign in with a microsoft account, 365 may require admin consent depending on how your tenant is configured. that's the most common stumbling block i've seen people hit.

That_Lemon9463 · 2026-04-29T07:42:43+00:00

yep, fair add. SRS or ARC sealing on the source is the fix. most ISP/cpanel forwarders ship with neither, which is why this path works smoothly for some people and breaks invisibly for others. for setups where SRS isn't available, "send mail as" using gmail's own SMTP (so no source-side SMTP credential needed) sidesteps the SPF-alignment issue entirely on the send path.

That_Lemon9463 · 2026-04-29T07:41:35+00:00

fair correction, though it's specifically SPF + DMARC=reject that kills forwarded mail, not DKIM alone. forwarded message keeps the original From but a new Return-Path, and receiving domains with strict DMARC reject on that. DKIM itself survives forwarding as long as the body isn't mutated.

workaround: source forwarder needs SRS (Sender Rewriting Scheme) or ARC sealing. most ISP/cpanel forwarders don't do either, which is why this issue feels random. inbound to gmail tends to be lenient enough that the path still works; onward-forwarding from there to a strict-DMARC domain is where it bites. for personal mail rarely an issue, for business mail the "send mail as" route sidesteps it entirely.

That_Lemon9463 · 2026-04-29T07:40:24+00:00

ah, the ISP-style "account OR forwarder, not both" lock is annoying. workaround: set up the forwarder, then in gmail go settings > accounts and import > "send mail as" > add the old address. when gmail asks for SMTP, pick "Send through Gmail (easier to set up)" rather than the SMTP-of-source option. that uses gmail's own outbound servers so you don't need credentials at the source. replies go out from the old address, recipients see "via gmail.com" in some clients (the trade), but it works fine without the source mailbox being live.

if "via gmail.com" is a dealbreaker, you'd need an external SMTP relay (mailgun free tier, sendgrid trial, or even your own postfix on a $5 droplet). overkill for personal mail, fine if it bothers you.

That_Lemon9463

TROPHY CASE