8 min read
By Element Dong

Pactify's New Release: Beyond Export - Building Workflow Connections

After talking with dozens of researchers, I realized exporting AI conversations isn't enough. You need better connections between the tools you already use. Here's what we built, what we didn't, and why I need your help figuring out what matters.

Build in PublicProduct UpdateResearch WorkflowAI Tools

I've been thinking a lot lately.

After talking with dozens of researchers over the past few weeks, I realized something: just exporting AI conversations isn't enough.

The Real Problem

You probably already know this if you're reading this—you use multiple tools daily:

  • Zotero for references
  • Obsidian for notes
  • Overleaf for LaTeX
  • Google Docs for drafts

Your workflow is fragmented by design, because no single tool does everything.

That's not a bug. That's actually how research works.

What I Got Wrong

I initially thought people needed "better export."

What they actually needed was better connections between the tools they already use.

These are two completely different problems. And I almost missed it.

So Here's What We Built

Export to Google Docs

Some of you don't want to download files. You want AI conversations to land directly in your Google Drive, where your drafts live.

Now you can. One click, conversation appears in Google Docs with proper formatting.

Export to Obsidian (Markdown)

Others of you live in Obsidian. Your entire knowledge system is there—notes, links, daily logs.

Now you can export directly to markdown format. Drop it into your vault, link it to existing notes, build your knowledge graph.

Is it perfect from a PKM perspective? No. It doesn't preserve conversation metadata yet. It doesn't support Obsidian's bi-directional links automatically. But it gets you 80% there.

LaTeX Copy on All Platforms

ChatGPT, Gemini, Claude—they all display formulas differently on screen. But now they all have a "Copy LaTeX" button when you need the actual formula code. Small thing. But it saves you from inspecting HTML or manually retyping equations.

Light/Dark Mode Toggle

Some of you work late. Some of you have light-sensitive eyes. Some of you just prefer dark mode. Now you can switch seamlessly without reloading or losing your place.

The Workflow Connection Problem

Here's what I'm trying to solve—and I'm not sure I've got it right yet.

You have an AI conversation with valuable insights buried in round 7, data in round 12, a methodology in round 18. That conversation needs to:

  • Flow into your note system (Obsidian, Notion, Roam)
  • Connect with your references (Zotero, Mendeley)
  • Feed into your writing tools (Overleaf, Google Docs)
  • Preserve enough context so you remember why you asked

Most export tools treat this as a "file format problem." Markdown vs Word vs PDF.

But it's actually a workflow problem. The question isn't "what format?" It's "where does this go in my existing system, and how does it connect to everything else?"

What Didn't Make It In (And Why I'm Telling You)

Things I wanted to build but haven't:

Conversation metadata preservation

timestamps, model versions, prompt history

Obsidian bi-directional links

auto-generating [[links]] between related conversations

Zotero integration

pulling citations directly into reference managers

Collaborative annotations

sharing highlighted sections with team members

Version tracking

seeing how your thinking evolved across conversations

Why didn't I build these?

Honestly? I'm not sure which ones actually matter.

I can build bi-directional links. But do you want that? Or would you rather manually curate connections because that's part of your thinking process? I can preserve metadata. But does timestamp and model version actually help you, or is it just data clutter?

This is where I need you to tell me what's actually useful vs what sounds cool but nobody uses.

Also: We Made Freemium Better

Before

  • 5 conversions/month
  • 100KB per export

Now

  • 30 conversions/month (6x more)
  • 1MB per export (10x larger)

Why?

Because I kept hearing: "I tried Pactify but hit the limit on day 3."

You shouldn't have to upgrade just to test if this fits your workflow. You should upgrade because it genuinely saves you time and you want more capacity.

Ready to Give It a Try?

Install the Chrome extension and start exporting your AI conversations in seconds. It's free, and you get 30 conversions per month to test it out.

Install on Chrome

The Real Question I'm Wrestling With

I've talked to academic researchers, legal professionals, creative writers, consultants. Everyone's workflow is different.

Some of you want:

  • • Fast export, no fuss
  • • Deep tool integration
  • • Format perfection
  • • Quick capture for ideas

Others want:

  • • Conversation search
  • • AI-assisted organization
  • • Multi-conversation synthesis
  • • Team knowledge bases

I can't build all of this at once. And honestly, I'm not even sure which direction matters most.

So here's what I'm asking:

What's the one workflow connection that would actually change how you use AI?

Not "nice to have." Not "would be cool." What's the friction point where you currently lose 15 minutes every single time, and you'd pay money to make it disappear?

Current State: Good Enough, But Not Done

After testing with people around me—researchers, writers, knowledge workers—here's what we've validated:

Daily AI → PKM workflow works

Fragmented conversations become structured knowledge

Export quality meets professional standards

Saves meaningful time in knowledge capture

But I know this only represents a slice of how people actually work.

Your discipline might have different standards. Your tools might have different requirements. Your thinking process might need different support.

Want to Follow the Journey?

Check out the complete Build in Public updates log. See what we shipped, what we learned, and what we're wrestling with—completely transparent.

View Progress Updates

Some Numbers (Because Transparency)

100+

conversions daily

💌

Thank-you emails

(these make my day)

$0

spent on ads

(organic + word-of-mouth)

People have told me I could grow faster with paid marketing or influencer partnerships. Maybe.

But I'd rather grow slowly with people who actually need this, who'll tell me when it breaks, who'll suggest what's missing.

Quality feedback > vanity metrics.

What I Need From You

If you're using Pactify (or thinking about trying it), I have specific questions:

1. What workflow connections matter most to you?

Google Docs? Obsidian? Something else? Why?

2. What's still broken or missing?

Be specific. "Better formatting" doesn't help. "LaTeX equations in tables render incorrectly" helps.

3. How do you organize AI conversations now?

Do you save them? Search them later? Let them disappear? Why?

4. Would features like metadata preservation or bi-directional linking actually change how you work?

Or would they just add complexity you'd ignore?

Reach me:

Final Thought

I've spent 3 years building AI products. Most failed because I built what I thought people needed, not what they actually needed.

This time, I'm trying something different: build, share, listen, iterate.

Pactify isn't perfect. It won't solve every problem. But if it saves you time on the workflow connections you use daily, then it's worth building.

And if it doesn't? Tell me what would.

✨ The new version is live now. Try the Google Docs or Obsidian export and let me know what breaks.

Seriously—I want to know.

https://pactify.io →

Built for researchers, by researchers 🎓

Transform your AI conversations into actionable research outputs with Pactify.

What Matters to You?

I'm building this in public because I don't have all the answers. Your workflow, your needs, your pain points—they matter. Tell me what should come next.