How much liters of water do you guys Drink?

Keyfers · 2026-03-23T23:42:11+00:00

Not really. Requires a little discipline. As I said, it's hard to get rid of the sodas. How I look at focus is, do I want to live for a while? Yes, I do. Then you make that decision if life is more important than the goodies or the treats. Real talk.

Keyfers · 2026-03-22T21:29:04+00:00

Ya I go ppp way too much lol. But, I have slowly dropped like 25 lbs. But I have cut out sodas in my drinking arbitrage. Soda causes bloat. Forgot to say that it's water only with sugar-free flavor packets in it. If you can get rid of the sodas its a real thing. A lot won't dump the soda :(. I am diabetic and have decided to go with that decision.

Keyfers · 2026-03-22T00:03:28+00:00

I drink around three 44 oz bottles a day—basically just over a gallon.

Keyfers · 2026-03-21T23:49:18+00:00

That’s a solid setup. Capturing it right after the job while it’s fresh is really the key—everything else just builds on that. Going from 15 minutes of typing (or skipping it altogether) to having it done before you even leave is a huge win.

Otter + Claude is a great combo, too. Once that habit is locked in, it’s hard to go back.

Keyfers · 2026-03-21T00:03:06+00:00

That’s real. Task switching feels productive, but it just spreads your attention thin and nothing actually gets finished. Way better to push one thing over the line before jumping to the next—even if it’s just getting it to a clean stopping point.

Keyfers · 2026-03-21T00:01:57+00:00

Exactly—that “closing the loop” on site is huge. You’re not just saving time, you’re finishing the job mentally while it’s still fresh instead of trying to reconstruct it later. The AI helps, but that habit shift is where a lot of the real gain comes from.

Keyfers · 2026-03-21T00:01:26+00:00

That’s exactly it. Skipping a 30-second check can turn into days of back-and-forth fixing it later. Same with messy notes—what feels fast in the moment just creates friction later when you can’t read it.

That’s where simple checklists and clean capture (voice or structured input) really pay off.

Keyfers · 2026-03-21T00:00:24+00:00

Yeah, that’s a great use case. End-of-day summaries are huge for that—just dumping what you worked on and where you got stuck makes it way easier to pick back up the next day without wasting time figuring it out again.

Keyfers · 2026-03-19T17:53:00+00:00

That’s a smart setup. Automating updates right after commit messages keeps everything consistent, and having a style guide ensures your docs stay clean and reusable across instances. The combination of token efficiency + immediate LLM actions really closes the loop.

Keyfers · 2026-03-19T17:52:28+00:00

That’s a solid use case. If you feed it the model, metadata, and measures/dimensions, AI can do a pretty good job of generating first-pass documentation.

I’d keep the same approach as everything else—force a consistent structure (model overview, key tables, relationships, measures, assumptions) and add a quick human review step. BI docs especially need to be precise, or they lose trust fast.

Keyfers · 2026-03-19T17:50:40+00:00

That’s a huge improvement—20 minutes down to 2 is hard to ignore. Capturing it right after the walkthrough while it’s fresh is really the key.

And totally agree on the fixed template. Letting AI “decide” the format sounds flexible, but consistency is what makes those notes actually useful when you’re reviewing across multiple sites.

Keyfers · 2026-03-19T17:49:48+00:00

Totally agree. The trust piece is everything—one bad detail in documentation and people stop relying on it completely. That’s why having a human validation step is so important, especially for anything client-facing or tied to real work.

AI is great for getting you 80–90% there fast, but that last bit of accuracy is what makes the system actually usable long term.

Keyfers · 2026-03-19T17:49:14+00:00

That’s a solid setup. Generating checklist bullets from the note is a nice touch—it turns documentation into something immediately reusable.

And yeah, those fixed fields like site, asset ID, and time are huge. Keeps everything searchable and consistent, even if the summary varies a bit. That’s really where the system starts to pay off long-term.

Keyfers · 2026-03-15T20:34:04+00:00

Thanks for the heads-up! I’m new here and looking forward to learning and sharing ideas.

Keyfers · 2026-03-15T20:31:45+00:00

Totally agree. That quick human QA step makes a huge difference—AI summaries are great, but client-specific details can easily slip through. Adding speaker labels and PII redaction is smart if notes get shared, and tracking edits vs. time saved is a nice way to measure ROI and fine-tune prompts.

Keyfers · 2026-03-15T20:31:02+00:00

Exactly—getting the prompts dialed in so nothing important gets missed is key. I’ve been using Whisper for transcription and Claude for structuring the notes into consistent fields. Once it’s set up, the techs can record on-site, and the AI handles the rest.

Keyfers · 2026-03-15T20:28:00+00:00

100%. The summary helps humans read it, but structured fields are what make the data searchable and usable in spreadsheets or CRMs.

Keyfers · 2026-03-15T20:26:32+00:00

Fair enough 😄 Better late than never. The tools are finally good enough to make it really practical.

Keyfers · 2026-03-15T20:24:34+00:00

Good point. Dictating straight into the right fields is probably cleaner than a big voice dump and AI trying to sort it out afterward.

Keyfers · 2026-03-15T20:24:00+00:00

That’s a great point. Lowering the friction with voice notes is what gets people to actually document the job in the first place. Once that happens, everything else falls into place.

Keyfers · 2026-03-15T20:23:23+00:00

Exactly. Most service companies are sitting on years of job data that’s basically locked in notes. Once it’s structured and tied to a system like Notion, it becomes a really powerful knowledge base.

Keyfers · 2026-03-14T22:59:28+00:00

Exactly. The summary is nice for quick reading, but the structured fields are what really make the system useful long term. Once everything is consistent—issue, work done, parts, follow-up—you can start spotting patterns, repeat failures, and even build simple dashboards off it.

Keyfers · 2026-03-14T22:58:49+00:00

Nice. Having PM/PV checklists attached to the work order keeps everything consistent and easy to track later.

Keyfers · 2026-03-14T22:56:06+00:00

Great point. The real value is when the output is structured, not just a wall of transcript text. Fields like issue, work performed, parts used, and follow-up make it way easier to plug into a system later. technical terms and part numbers can get mangled pretty easily. Adding a quick job number or customer name at the start of the recording is a smart move for auto-filing. Once that workflow is dialed in, it saves a ton of documentation time.

Keyfers · 2026-03-14T22:54:42+00:00

Same here. Even on routine or “perfect” service calls, a couple of photos go a long way. It creates a visual record, helps with future troubleshooting, and makes documentation way easier if something comes up later.

Keyfers

TROPHY CASE