TechGuy

Software Engineer & Builder of Things That Run Themselves

[TechGuy @IAakashM]

@llavaApp @_Melvin_Chukwu Good approach, ship with pilot lawyers first. Stripped finals on round 3+ kept surfacing in my interviews too, especially when payment or indemnity moved with zero markup.

Are your pilots mostly getting Word redlines back, or clean PDFs they have to diff manually?

[TechGuy @IAakashM]

@moezshabbir The dissent on one edge case is the interesting bit. Do you run that on first-pass reads only, or also when a counterparty sends a clean PDF after round 3 with no track changes?

[TechGuy @IAakashM]

@NainsiDwiv50980 Multi-vendor PDF compare is where spreadsheets break down.

Do you find table extraction enough, or do you still need clause-by-clause diff when payment terms drift between versions?

[TechGuy @IAakashM]

@Seeing_Redlines The 65-page MSA with a quiet indemnity tweak is exactly why skim requests fail.

Do you ever diff against their last sent draft, or is it always a full read because you can't trust what changed?

[TechGuy @IAakashM]

@strowhiro Option 2 works until the counterparty strips track changes and sends a clean PDF on round 4. That's when side-by-side Word compare stops helping.

Curious if in-house folks still demand a PDF redline every round or accept clean Word + trust.

[TechGuy @IAakashM]

@livingagentic @sridharfyi Should work now 👍

[TechGuy @IAakashM]

@livingagentic @sridharfyi Appreciate that. DM whenever, no rush.🤝

[TechGuy @IAakashM]

@kohgfex1316 まさにその方向で作っています。実質的な変更とノイズを分けて、オンオフできるようにしたいです。作っているものはこちらです https://t.co/qMk016SaE1

[TechGuy @IAakashM]

@livingagentic @sridharfyi Same here, still validating. Happy to swap notes as we both ship.

[TechGuy @IAakashM]

@livingagentic @sridharfyi Got it. We're more on the other side. ChangeLens compares two versions after negotiation rounds and surfaces what actually changed. Payment, deadlines, scope. Feels complementary.

Do your users ever ask for that?

[TechGuy @IAakashM]

@lukashanren1 Building ChangeLens for that. Compare two contract versions and flag what actually matters: payment terms, deadlines, scope, clause changes. Not just raw diff noise. Want to try it when it's ready?

[TechGuy @IAakashM]

@lukashanren1 Curious what your current workaround is. Full reread or do you have some diff trick you use?

[TechGuy @IAakashM]

@tryklaroai The "reasonable revisions" clause problem is bad, but the one that gets people more quietly is when the client sends back a "final" PDF with payment terms quietly tweaked and nobody notices until it's signed.

Do you see that pattern too or is it mostly the scope creep version?

[TechGuy @IAakashM]

@v_shakthi The Word integration is great until the counterparty sends a scanned PDF. That's where most tools break.

Does the Word agent have a path for PDF-only input or is clean text a requirement?

[TechGuy @IAakashM]

@StevePulver Exactly this. An attorney who moves fast but misses a clause change on round 5 loses more than they saved.

Has your experience been that the missed-changes problem is actually more common than the speed problem?

[TechGuy @IAakashM]

@livingagentic @sridharfyi Same audience you're targeting. Solo attorneys priced out of Harvey are also the ones spending the most time on diff-ing what changed between contract rounds.

Is REDLINE doing comparison between versions or more the initial review pass?

[TechGuy @IAakashM]

@SolarionHQ That "I already read this one, nothing changed" feeling right before signing is exactly where it bites people.

Does AURA handle native PDFs or does it need a Word conversion first?