PT ACTA Solusi Teknologi · AV systems integration · 2026

ACTA OS — an AV integrator’s back office, rebuilt as one system

From the first lead to the final invoice. One workspace for the whole operation.

Internal toolsBusiness operationsFinanceClient portal
acta-os.vercel.app
ACTA OS — interface illustration with sample data
INTERFACE PREVIEWPrivate system

Interface preview · sample configuration

Private system — walkthrough on request

The business

PT ACTA Solusi Teknologi integrates commercial audio-visual systems — design, installation, and long-term support for meeting rooms, auditoriums, and venues across Indonesia.

Category
Internal tools
Industry
AV systems integration
Stack
React, Vite, TanStack Query, Supabase, PostgreSQL

What was breaking

An integrator’s work crosses every function at once: a lead becomes a site survey, a survey becomes a priced quotation, a quotation becomes a procurement run, an installation, a handover, and a warranty period. Each stage lived in its own spreadsheet or chat thread, and the same numbers were typed in four times before anyone could tell whether a project made money.

What we built

One operating system covering the whole path. CRM, quotations, vendor hub, finance, project timelines, project tracking, and a company HQ layer read and write shared records, so a value entered at the lead stage can reach the profit-and-loss. It installs as an app, sends push notifications to the field team, and publishes client-facing timelines as public share links.

The workflow it carries

  1. 01

    Lead

    Qualified in the CRM, site survey attached.

  2. 02

    Quotation

    Priced from the price book. One record, versioned.

  3. 03

    Procurement

    The vendor hub picks up what the quotation committed to.

  4. 04

    Project

    Timeline, tasks, installation, and handover.

  5. 05

    Finance

    Invoices, bills, cash, payroll, tax, per-project P&L.

  6. 06

    Client view

    A share link. No account, no login, no chasing.

What changed

An operator moves from CRM to finance without a page load or a re-key. The parts that differ between companies — numbering schemes, document templates, price books, brand catalogues — are configuration rather than code, which is what makes a second deployment a setup task instead of a rebuild. Built as a single-page React app on Supabase with TanStack Query holding the cache. The cover illustrates the project tracker with sample project names and values.

What shipped

  • 01A lead qualifies into a quotation, the quotation becomes a project, and the project rolls up into its own profit-and-loss — one record, no re-keying between modules.
  • 02Finance runs the full ledger in-house: invoices, bills, cash, payroll, tax, and per-project P&L, with document numbering and templates set per company.
  • 03Clients follow a build through a tokenised share link — a live project timeline that needs no account, no login, and no chasing for a status update.
LET’S MAKE IT HAPPEN

What are you
imagining?

Tell us a little. We’ll help you find the next step.