Building Pactify: Updates & Learnings
I'm building Pactify in public—sharing what I'm learning, what's confusing, and what's not working. Not marketing, just honest progress updates.
Your feedback shapes this project
These updates reflect real conversations with users. If something doesn't make sense or you have different needs, please reach out: contact@pactify.io
Try What We've Built So Far
Connect AI chats to Google Docs, Notion & Obsidian • One-click workflow integration
Remember spending 5-10 minutes copy-pasting ChatGPT conversations into Notion? Losing formatting, manually adding metadata, fixing broken tables?
After hearing this frustration from dozens of researchers and consultants, I built what should have existed from day one: one-click Notion export.
Now your AI conversations land directly in your Notion workspace—formatted, organized, and ready to use.
No more workflow friction. No more context switching. Just click, export, done.
What's New
- →One-Click Notion Export: Export ChatGPT, Claude, and Gemini conversations directly to Notion with a single click
- →Multi-Platform Support: Works seamlessly across all three major AI platforms with consistent quality
- →Format Preservation: Tables, code blocks, LaTeX formulas, and formatting maintained perfectly
- →Smart Metadata: Auto-includes conversation date, platform, model info, and token count
- →Instant Speed: Complete export in under 5 seconds—no waiting, no processing delays
- →Flexible Organization: Choose target database, add custom tags, customize export location
What I Learned
- ✓Export friction isn't a minor inconvenience—it's a workflow killer that makes people abandon valuable AI conversations
- ✓The real problem isn't "saving AI chats" but "integrating them into existing workflows where actual work happens"
- ✓High-frequency users (5+ conversations/day) lose 30-60 min/week on manual export—time that should go to actual thinking
- ✓Different users need different organization: some by project, some by date, some by topic. One-size-fits-all doesn't work
- ✓Quality matters more than speed: a 5-second export that preserves formatting beats a 1-second export that loses context
After talking with dozens of researchers, I realized something: just exporting AI conversations isn't enough.
You use Zotero, Obsidian, Overleaf, Google Docs. Your workflow is fragmented by design.
What people actually need is better connections between the tools they already use.
This led us to completely rethink what Pactify should be—and what we built next.
What's New
- →Connect to Google Docs: AI conversations land directly in your Google Drive where your drafts live
- →Connect to Obsidian (Markdown): Drop conversations into your vault, link to existing notes, build knowledge graphs
- →LaTeX Copy on All Platforms: ChatGPT, Gemini, Claude—all standardized with one-click copy
- →Light/Dark Mode Toggle: Switch seamlessly without reloading, perfect for late-night work
- →Freemium Upgrade: 30 conversions/month (6x), 1MB per file (10x), all templates available
What I Learned
- ✓Format problem ≠ workflow problem. The real question is "where does this go in my system?"
- ✓You shouldn't need to hit limits on day 3 just to test if something fits your workflow
- ✓I don't have all the answers—metadata preservation, bi-directional links, Zotero integration? Need your feedback
- ✓Quality feedback beats vanity metrics. Would rather grow slowly with people who actually need this
- ✓Building in public means admitting uncertainty and asking for help, not showing off what's "done"
After two weeks of 14-hour days, I shipped what users asked for.
LaTeX copying, Claude and Gemini support, Markdown exports, better formatting—real problems from real researchers.
But here's what keeps me up: did I build what people actually need, or what I think they need?
Am I solving core problems, or just enabling workarounds?
What's New
- →LaTeX Copy Button: Click "Copy LaTeX" on ChatGPT formulas, paste directly into your editor
- →Claude & Gemini Support: Custom handling for each platform's quirks to maintain export quality
- →Markdown Export: Academic-standard formatting with proper LaTeX delimiters and citation formats
- →LaTeX Formula Fixes: ChatGPT's non-standard delimiters ([...] vs $$) now render correctly in Word
- →Styling Improvements: Tables, headers, lists spacing and alignment match academic standards
- →Testing Obsession: 20 academic scenarios × 3 platforms × 100+ test cycles = 97%+ accuracy
What I Learned
- ✓Every change breaks something else—fixing LaTeX broke table spacing, improving Claude changed ChatGPT citations
- ✓Multi-platform support might be enabling workarounds rather than solving core problems
- ✓"Ready to use" means different things to different people—need more clarity on what quality bar matters
- ✓Infrastructure is invisible when it works. You only notice when it breaks.
- ✓The goal isn't just "export"—it's "ready to use without manual cleanup"
After 3 years building AI products that didn't work, I finally admitted something:
I don't know what people actually need.
So I'm building Pactify in public—starting with my own problem (2-4 hours/week wasted organizing AI conversations).
But I'm openly asking: is this even a real problem worth solving?
What's New
- →Built minimum viable export: ChatGPT conversations → professional Word documents
- →Academic document standards: LaTeX formulas, tables, proper formatting
- →Enterprise-grade security: Temporary storage, auto-deletion, no third-party exposure
- →Chrome Extension: One-click export directly from ChatGPT interface
- →Started with my own pain point: AI saves 30 minutes, but organizing takes 90 minutes
What I Learned
- ✓Closed-door development never works—spent 3 years building things nobody used
- ✓Everyone's AI use cases are completely different: research, creative, legal, technical
- ✓The gap isn't AI capability—it's the bridge from "AI generated" to "actually usable"
- ✓Most export tools just save as plain text. When there are formulas, tables, code—everything breaks
- ✓Need to hear real user scenarios before building more features, not assume I know what they want
Help Me Build Better
I'm not trying to sell you something—I'm trying to understand if this direction makes sense. Your real-world scenarios and feedback matter more than anything else.