2
11 Comments

I built a tool that turns CSV data into branded PDF reports with AI — here's what I learned

I'm Deepanshu, a freelance data analyst based in India.

Every client engagement ended the same way. The analysis was done. The insights were solid. Then came the report — 2-3 hours in Word or Canva, manually copying numbers, building charts from scratch, making sure the logo was in the right place. The actual work was finished. I was just making it look like work.

I couldn't find a tool that did what I needed. BI tools cost $300+/month. Canva doesn't understand data. Nothing existed for a solo analyst who just needs clean, professional reports fast.

So I built Naxely.

What it does:
Upload a CSV or connect Google Sheets. Pick your branding. Naxely generates a full PDF report in under 30 seconds — executive summary, KPI cards, charts, AI insights, anomaly detection, and recommendations.

Tech stack:
FastAPI, React, Supabase, ReportLab, Python. AI runs on BYOK — bring your own key. Groq, DeepSeek, OpenAI, Gemini, Claude, Mistral all supported. Zero server-side AI cost.

What I learned building this solo:

  • PDF generation is underrated hard. ReportLab's Y-axis goes upward, not downward. Spent 2 weeks getting the logo to render correctly.

  • Async Python has footguns nobody warns you about. Chaining on un-awaited coroutines fails silently.

  • The first 90% takes 10% of the time. The last 10% takes 90%.

Pricing:
Free tier — 3 reports, no card needed
Pro — $29/month
Agency — $79/month (white-label PDFs, Google Sheets, PowerPoint export)

Live at naxely.com — would love feedback from anyone who does client reporting.

posted toAvatar for product Naxely
Naxely
  1. 1

    The ‘making it look like work’ line is exactly it the invisible tax on every analyst. Smart move keeping AI on BYOK too, removes the biggest objection for client-sensitive data.

    1. 1

      Yeah the "invisible tax" framing is exactly it. And the BYOK thing came from real feedback — people were nervous about sending client data through a shared API key. Seemed like the obvious fix.

      1. 1

        That’s exactly how the best product decisions get made real feedback, obvious fix, ship it. The fact that you’re already listening that closely to users early on is a good sign. Are you on Telegram or Discord? Would love to connect and talk through the growth side.

        1. 1

          not on discord much but happy to connect. you can reach me at naxely.com or just reply here, easier to keep the thread going.

          1. 1

            Checked out naxely.com but couldn’t find a direct contact. Happy to keep it here then I help founders with distribution and growth after the build is done. Would love to talk through how that could work for Naxely. What does your current growth plan look like?

            1. 1

              best way to reach me is hello@naxely.com — happy to chat. what kind of distribution do you work on?

  2. 1

    The line that stood out to me was that the analysis was already finished—you were just spending hours making it presentable.

    A lot of workflow improvements don't come from automating the hardest part. They come from removing the repetitive work that happens after the real value has already been created.

    1. 1

      That's a cleaner way to put it than I had. The analysis was done, I was just manually making it look finished. That's the part that felt pointless to keep doing.

      1. 1

        That's exactly what I was getting at.

        Your reply made me think about one implication that could end up changing how you think about the product, but it's probably too much to unpack properly in a thread.

        Happy to explain what I mean if it's useful. What's the best email to reach you on?

          1. 1

            Just sent it over. Looking forward to hearing your thoughts once you've had a chance to read it.