Skip to content

Own product · SaaS we build and run

Invollo: Invoicing and Billing Software

Invollo is our own invoicing, time-tracking and billing software for freelancers, agencies and small teams. We design, build, host and support it ourselves: a web app, a client portal, a desktop time tracker and a browser extension. Client payments go straight from the client to each user's own Stripe or PayPal account, and Invollo takes no cut of them.

The problem

What needed solving

Getting paid for client work usually involves several tools: one to track time, one to write invoices and quotes, a shared folder or email thread for the client, and a payment provider on top. Freelancers who sell through marketplaces also need proof of the hours they worked.

We wanted one product that covers the whole path from tracked time to a paid invoice. Running it ourselves also keeps us honest about what production software needs once real customers depend on it: security, payments that reconcile, backups, monitoring and a way to recover when something breaks.

Constraints

What the build had to respect

  • Many companies, one database

    Invollo is multi-tenant. Every company's data is separated by row-level security in Postgres, scoped to the signed-in company, and a blanket "allow all" policy is banned by the project rules.

  • Money must reconcile

    Amounts are stored in minor units, payments are recorded idempotently so a repeated webhook cannot pay an invoice twice, and an invoice's balance is derived from its payments.

  • Users get paid directly

    Clients pay through the user's own Stripe or PayPal account. Invollo's own subscriptions are billed through Stripe and, for Bangladesh, bKash.

  • Secrets stay server-side

    Payment and AI-provider credentials are kept in Supabase Vault, email recipients are always read from the database rather than from a request, and super-admin access needs two-factor authentication.

What we built

The build, part by part

The web app is React and TypeScript on Supabase, hosted on Netlify; the marketing site runs separately on Hostinger.

Billing

  • Invoices and recurring invoices, payment reminders and dunning
  • Quotations with e-signature
  • Multi-currency invoicing with exchange rates
  • Expenses and reports

Time and work

  • A time tracker in the web app
  • An Electron desktop tracker with optional screenshots and tokens stored in the operating system's keychain
  • A Chrome extension with timers, proof screenshots and an AI reply helper for marketplace messages

For the user's clients

  • A client portal with invoices, payments, time logs and a work diary
  • Public invoice pages the client can pay by card

Business tools

  • Clients, projects and team members
  • A W-8BEN form generator for freelancers paid from the US
  • An AI assistant inside the app

Invollo is released in small, versioned steps, each tagged in git. In September 2026 a series of security releases isolated webhooks and money handling, moved secrets into Vault, added two-factor authentication for the super admin and introduced a payment ledger.

From tracked time to a paid invoice
  1. Track time

    Web, desktop or browser extension

  2. Invoice or quote

    One-off or recurring

  3. Client portal

    The client sees and approves

  4. Client pays

    Into the user's Stripe or PayPal

  5. Payment recorded

    Once, even if a webhook repeats

  6. Reminders

    Until the balance is zero

Stack and integrations

Apps
  • React
  • TypeScript
  • Vite
  • Tailwind
  • Electron
  • Chrome extension
Backend
  • Supabase Postgres
  • Edge functions
  • pg_cron
  • Supabase Vault
  • Netlify
Payments
  • Stripe
  • PayPal
  • bKash
Operations
  • Cloudflare R2 backups
  • Axiom logs
  • Cloudflare Turnstile
  • GitHub Actions

Handover

How we run it

There is no handover for our own product, so the same discipline goes into running it. This is the part clients benefit from: the habits we use on Invollo are the ones we bring to their systems.

  • Nightly encrypted database backups to Cloudflare R2, with an alert if the latest good backup is older than expected
  • A health endpoint, scheduled jobs for reminders, dunning, reconciliation and exchange rates, and logs shipped to Axiom
  • Written runbooks for deploys, rollbacks, secrets, incidents and disaster recovery
  • Continuous integration that lints and builds the app, checks that database migrations are append-only and scans for credentials, plus a secret scanner before every push
  • Security reviews followed by fixes: an audit in February 2026, a hardening pass in April 2026 and a full customer-journey audit in October 2026

One honest gap: the database plan we use has no point-in-time recovery, so the nightly backup is the recovery point. The gap and the restore steps are written down in the disaster-recovery runbook.

Status and link

Where it stands

Live at invollo.com, with releases shipped through November 2026. The marketing site carries no testimonials or star ratings on purpose: we removed them until there are real ones to show.

Visit invollo.com (opens in a new tab)

What we leave out

What we do not claim

No user numbers, revenue or growth figures: we have not audited any we could publish. What we can show is the product itself, how it is built and how we run it, and you can try it at invollo.com.

Next step

Need something like this?

Tell us what you have today and what should change. We reply within one business day. You get a written scope and a fixed quote before anything is built.