InboxToDrive

Automatically save email invoices to Google Drive & Sheets

Visit Website
July 1, 2026 Submitted my AI invoice tool to Uneed — launch date locked in for Sep 28

Quick update on InboxToDrive, the side project I’ve been grinding on lately.

It started as a classic “scratch my own itch” build. I was wasting hours every month manually punching line items, totals and tax numbers from invoice PDFs into spreadsheets — mind-numbing, error-prone work that felt like pure busywork. So I put together an AI tool that parses invoice attachments automatically and dumps all the structured data straight into Google Sheets and Excel.

I submitted it to Uneed’s free queue today, and got assigned a September 28 launch.

Full transparency: I didn’t expect the free line to be almost 3 months long. That caught me off guard. But honestly, it’s probably a blessing in disguise — gives me way more time to iterate instead of rushing a half-baked launch.

Here’s what I’m prioritizing between now and launch:

  • Product polish: Keep tightening up parsing accuracy, add support for more invoice formats, and work through all the feedback from early testers

  • Launch assets: Put together a solid demo GIF, clean up product screenshots, and keep tweaking the landing page copy

  • Cold start prep: Line up a small group of early users to help with initial traction on launch day, and map out my community promotion plan

I’d love to pick the brains of anyone who’s launched on Uneed before.

What actually moves the needle for ranking well on launch day? Is it all about cramming upvotes in the first few hours, or do comments and discussion carry just as much weight? Are there any common noob mistakes I should watch out for?

Also curious how you’d spend a 3-month lead time — is there anything obvious I’m sleeping on in my plan?

Any tips or war stories are much appreciated!

Comment

June 24, 2026 What’s new in InboxToDrive — manual uploads & line-item breakdowns

InboxToDrive — June update

Three new capabilities:

1. Direct upload — Drop PDF/PNG/JPG receipts on the dashboard. No email forwarding required.

2. Line items — AI extracts individual charges. Edit descriptions, amounts, and categories in review. Mismatched totals are flagged for you.

3. Better exports — Excel and Google Sheets now output one row per line item, ready for bookkeeping.

Same Magic Inbox, two input methods: forward by email or upload files directly.

Comment

June 23, 2026 i built an automated invoice parser on my daily 4-hour train commute. here's why (and the tech stack)

Hey everyone,

I’m Ruizhi, a backend developer from China, and I wanted to share my very first micro-SaaS side project that I’ve been building slowly over the past few months.

Like a lot of us in our late 30s in tech, I’ve been dealing with constant layoff pressure and age-related anxiety lately. My company is trimming headcount right now, and it’s hard not to feel uneasy about the future.

Instead of just stressing passively after work, I decided to make good use of my extremely long daily commute — I spend around 4 hours every day traveling by train between Beijing, where I work, and Tianjin, where my family lives. Some days the train internet is spotty, so I planned most features offline and coded whenever I got a stable connection, little by little.

That slow, fragmented development process eventually turned into my tiny tool: https://inboxtodrive.app

I built it purely to solve my own pain point. Every month, I get dozens of invoices from AWS, Stripe, OpenAI, Shopify, and all sorts of SaaS subscriptions. Downloading PDFs, renaming files, sorting folders, and logging every expense into spreadsheets is such repetitive, tedious work. I got tired of wasting hours every month on manual bookkeeping that should just be automated.

The workflow I built is super simple and privacy-friendly.

You just set up a one-time auto-forward rule in your Gmail to the unique custom inbox we generate for you. We even auto-approve Google’s confirmation email, so you don’t have to manually copy any verification codes yourself.

After that, our AI parses every incoming invoice, extracts vendor names, dates, amounts, taxes, and currency details, then renames each file into a clean, consistent format like 2026-06-23_Shopify_$39.00.pdf. It automatically sorts everything into nested Google Drive folders and syncs all structured data straight to Google Sheets, or you can export it as Excel files for your own records or accountant.

Privacy was my top priority while building this tool. We never read your main inbox at all — we only process emails you actively forward to your custom address. All processed files and data get automatically shredded from our servers within 7 days, so nothing is stored long-term on our end. Your sensitive invoice data always stays inside your own Google Drive account.

Since this is a developer community, I’ll quickly share my ultra-low-cost stack I put together to keep hosting overhead super small:

- Frontend: Vite + React hosted on Cloudflare Pages (the free tier bandwidth is incredible for small indie tools)

- Backend: Python FastAPI running on a €5/month Hetzner VPS in Germany, using Docker Swarm for smooth rolling updates

- Database: Neon Postgres for local development, self-hosted Postgres container for production

- Payments & Mail: Creem (Estonia MoR) for global compliant payments, Resend for transactional emails

The product is fully live now. Google OAuth and Creem payment billing are both stable and ready to use.

For Indie Hacker community members, I’m locking in a permanent founding discount. Use code IH50 for 50% off forever — just $7.50/month instead of the original $15/month.

I’d really appreciate some honest feedback on the landing page, onboarding flow, feature set, or anything you think I could improve. This is my first real micro-SaaS, so all suggestions are more than welcome.

Alright, back to my daily commute coding grind!

10 Comments

  1. 1

    I've seen this pattern before with tools like InboxToDrive. strong utility but early stage posts often over-index on workflow detail while under indexing on trust signals and repeat usage proof.

    Without visible retention or external validation it reads more like a smart automation script than something people already depend on daily.

    1. 1

      This is such honest, spot-on feedback, I really appreciate it.

      You’re exactly right. I originally built this little automation script just to solve my own daily hassle, and we only launched this week. We don’t have long-term retention data or lots of customer case studies yet, that’s definitely our current gap.

      Still, we’ve embedded trust into our core design from launch with two key features:

      - Privacy by Design: We never request full mailbox permissions — users only need to forward relevant emails to us. All uploaded files get wiped from our servers in 7 days, and every financial document remains stored exclusively in your own Google Drive.

      - Passive Retention: Our one-time forwarding setup means users don’t have to keep logging back in. The tool works quietly in the background, which naturally guarantees ongoing, repeat usage.

      Given how many similar early-stage tools you’ve reviewed, could you share which trust signals or landing page tweaks you’d advise for our brand-new MVP to win over first-time visitors faster?

      1. 1

        Right now your business only has 1 page indexed on Google, so even Google doesn’t really trust the domain yet. If Google doesn’t trust it, users won’t trust it either. I have proof and screenshots.
        https://inboxtodrive.app/

        1. 1

          Thanks so much for checking this out. You hit the nail on the head — we just launched a few days ago, so our new domain is still waiting for Google to finish its initial crawl and indexing.

          What you’re seeing with low public indexing is actually somewhat by design, since we prioritized privacy from the ground up:

          1. Our dashboard and all internal workflow pages are locked behind user logins. We blocked search bots with robots.txt to make sure none of our users’ financial information gets crawled or exposed online.

          2. We never hold onto invoice files for good. Every processed PDF goes right into your Google Drive and gets wiped from our servers in 7 days, so there’s little need for lots of public website pages.

          We’ve already sent our sitemap to Google Search Console, and our homepage is already indexed.

          Would you like to give our app a spin? We’d love your honest feedback on receipt extraction speed and how well the Google Drive sync performs. 🚀

          1. 1

            It makes sense that the dashboard and any page with user data should stay blocked that's the right call. But that's a separate issue from public marketing pages. Robots.txt should only be blocking logged-in/app routes, not your homepage, pricing, or any content pages those need to be indexed for people to find and trust you. If it's really just the homepage indexed right now, the gap isn't privacy; it's that there's no other public content yet (use cases, comparisons, how-it-works pages) for Google to index in the first place.

  2. 1

    One thing I'd be careful with is that the pain point that motivates someone to build a product and the reason someone eventually pays for it aren't always the same thing.

    Reading this, I found myself wondering which part of the workflow is actually doing the work when a customer decides this is worth paying for.

    That's the part I'd be most curious about.

    1. 1

      Hey Aryan, thanks a lot for this great point. It’s such a sharp observation, exactly the kind of positioning feedback I needed.

      You’re totally right. I built this tool to avoid the boring repetitive work of downloading PDF receipts manually. But what really makes users willing to pay lies elsewhere in our workflow.

      Here are the four main reasons users convert to paid plans:

      - It makes tax work way easier for freelancers. You can share a neat Google Sheet with clickable receipt links directly with your accountant, cutting weeks of tedious paperwork down to seconds, and helping you stay away from tax penalties.

      - Super simple setup. Unlike Hubdoc which needs tons of custom email rules, you only need one forwarding rule here. Our AI filters out junk emails and keeps all your invoices automatically.

      - Far better pricing than mainstream enterprise tools. We offer 500 invoices per month for $15, half price for early users, enough for most solopreneurs’ annual business needs.

      - Your financial data stays safe. We only use your own Google Drive and wipe our server data within 7 days, so you never need to worry about sensitive financial information leaking.

      Would love your opinion: are these selling points focused correctly? Did I miss any important perspective?

      1. 1

        I'm not sure I'd feel comfortable answering that confidently from a thread.

        What stood out to me is that all four points sound reasonable, but they don't necessarily imply the same explanation for why someone buys.

        I've got a few thoughts on that, but it's probably more than I'd try to unpack properly here.

        What's the best email to reach you on?

        1. 1

          That's totally fair, Aryan. I appreciate you wanting to take the time to give a proper, deeper answer.

          I’d love to hear your thoughts on this and unpack those different buying explanations with you.

          You can reach me directly at: support [at] inboxtodrive [dot] app

          Looking forward to your email!

          1. 1

            Appreciate it. Just sent a note over.

About

I built InboxToDrive to automate the painful monthly chore of manually downloading, renaming, and saving SaaS invoices to Google Drive. A zero-touch, privacy-first tool for busy solopreneurs.