PMO Portal

The Operating System for Project Business.

Every division on the same page.

PMO Portal is one portal for contractors and project-based firms: site, purchasing, warehouse, project and finance staff work in the same record, so directors see today's figures.

Apply to be a design partnerComing soon

Budget impact · MaterialsWithin budget
Budget (RAP)IDR 24,000,000,000
Spent15,800,000,000
Committed in POs4,200,000,000
This request360,000,000
Left after approvalIDR 3,640,000,000

Routed to the project manager, the project's approver. The site engineer who raised it can't approve it.

Simplified view · sample data

See PMO Portal in 53 seconds.

From the first lead to a paid milestone, on one record. Press play for sound.

The showreel uses sample data throughout.

Every division keeps its own file.

One person stitches them together. The site team has a spreadsheet. Purchasing lives in email and WhatsApp. The warehouse has a stock card, the project team a progress file and finance an accounting file. A project admin retypes and reconciles them after hours, and the directors see the result weeks late.

Today

  • Siteown spreadsheet
  • Purchasingemail and WhatsApp
  • Warehousestock card
  • Projectprogress file
  • Financeaccounting file
Project adminretypes and reconciles, after hours
Directorslast month's figures

With PMO Portal

  • Site
  • Purchasing
  • Warehouse
  • Project
  • Finance
PMO Portalone shared record. Each person sees only what their role allows. Nothing is retyped.
Directorstoday's figures, every project

From tender to ledger, in the order the money moves.

PMO Portal covers the project side of the business. Your ERP keeps the books.

  1. SalesPipeline and tendersWin, then contract value is locked
  2. ProjectsBQ and RAP budgetPhases, tasks, progress curveDocuments
  3. PurchasingRequest, approval, POReceipt, vendor billSubcontracts
  4. SiteCentral and site warehousesIssues to projectSite cash floatsTimesheets, expenses
  5. BillingProgress claims on BQ linesBerita AcaraDown payment recoveryInvoices
  6. CashReceivables and ageingPayables, paymentsStatements
Controls, across every moduleApproval routed by budget · requester can't approve their own spend · every change logged with who and when
VisibilityDirectors' dashboard · budget vs actual · AI assistant that answers from the same records
Your ERP: Odoo Community or ERPNextGeneral ledger · PPN and e-Faktur · bank · fixed assets · financial statements. Approved documents go down; statuses and payments come back.
The project money flow, left to right

Purchasing, with the budget in view before anyone approves.

A site engineer raises a request. Whoever approves it sees what it does to the project's budget for that category, and the PO, the receipt into a site warehouse and the vendor bill all stay attached to it.

  1. 1Budget (RAP) against spent and committed, for this category, before the request is approved. It updates as each PO and bill is approved.
  2. 2Within budget goes to the project's approver. Overhead or over budget goes to senior approvers.
  3. 3Nobody approves their own request. The server refuses it, and the approver can't also pay.
PMO Portal/ Approvals / Purchase requests
PR-26-0142 · 2.8 MW Carport PV
Cable tray and supports
Requested by the site engineer · 2 days ago
ItemQtyAmount
Cable tray 300 mm400 m220,000,000
Supports and brackets350 pcs98,000,000
Fixings1 lot42,000,000
Total IDR, excl. PPN360,000,000
1Budget impact · MaterialsWithin budget
Budget (RAP)IDR 24,000,000,000
Spent15,800,000,000
Committed in POs4,200,000,000
This request360,000,000
Left after approvalIDR 3,640,000,000

2Routed to the project manager, the project's approver. 3The site engineer can't approve their own request.

ReturnApprove
Simplified view · sample data

Billing against a signed Berita Acara, not against a promise.

Progress is recorded per BQ line. The claim becomes an invoice only once the client's signed completion certificate is attached to it, and down payment is recovered on each claim.

  1. 1Quantities claimed per BQ line: this claim, previous claims and to date.
  2. 2Down payment recovered on each claim, shown as its own line.
  3. 3No invoice until the signed Berita Acara is attached. Subcontractor bills can't exceed verified quantities either.
PMO Portal/ Projects / 5.5 MW Rooftop PV / Contract & billing
Progress claim 3
Period to 31 Oct 2026 · prepared by the project manager
Evidence attached
1BQ lineContract qtyPreviousThis claimTo dateAmount
PV modules, supply and install9,820 pcs4,1002,40066%IDR 7,680,000,000
Mounting structure5,500 kWp2,3001,35066%2,970,000,000
Inverters and cabling1 lot20%30%50%3,600,000,000
2Down payment recovered (20%)− 2,850,000,000
Claim, excl. PPNIDR 11,400,000,000

3Berita Acara 03/BA/HLP/X/2026 · signed by the client · from the project's document register

Raise invoice
Simplified view · sample data

The directors' view: every project, in rupiah and dollars.

The dashboard reads from the same records the site and finance teams work in, so there is no weekly pack to assemble. Each contract keeps its own currency, side by side. An AI assistant answers questions from the same records.

  1. 1Contract on hand in IDR and USD, approvals waiting for you, projects at risk and overdue receivables.
  2. 2Budget used per project, split into spent and committed. Open a project for budget against actual by category.
PMO Portal/ Dashboard
1Contract on hand
IDR 320.0B
+ USD 13.1M
Waiting for you
3
approvals
At risk
1 of 6
active projects
Overdue from clients
IDR 0
no overdue invoices
2Spending against contract, largest first
ProjectContractBudget usedUsed
5.5 MW Rooftop PVIDR 102.4B
52%
HQ Fit-OutIDR 80.0B
15%
2.8 MW Carport PVIDR 57.6B
81%
6.0 MW Ground-Mount PVUSD 7.8M
91%
Simplified view · sample data
2.8 MW Carport PV · budget vs actualIDR · excl. PPN
SpentCommitted in POsRemaining
CategoryBudgetSpentCommittedRemaining
Materials
24.0B15.8B4.2B4.0B
Equipment
9.6B6.1B1.9B1.6B
Subcontractors
10.4B5.2B3.4B1.8B
Labor
3.2B2.4B00.8B
Contingency
0.8B000.8B
Total48.0B29.5B9.5B9.0B
Budget against actual and committed spend, per category · simplified view · sample data

What the server enforces, whatever the screen shows.

These rules live in the database and on the server, not only in which buttons are visible. A person who tries to go around the screen still gets refused.

  • Each person sees and does only what their role allows. A site engineer, a purchasing officer, a project manager and a finance officer open the same record and see different things.
  • Nobody approves their own request. The server refuses it, and the approver can't also be the person who pays.
  • Approval is routed by budget. Within budget goes to the project's approver. Overhead or over budget goes to senior approvers.
  • No invoice without a signed Berita Acara. A progress claim can't become an invoice until the signed certificate is attached. Down payment is recovered on every claim.
  • Subcontractor bills can't exceed verified quantities. The server stops a bill that goes above the quantities verified.
  • An append-only audit trail. Who did what, and when. Entries are added, never edited or deleted.

Sign-in is by email, magic link, or Microsoft 365.

Runs on your terms: your ERP stays the books.

PMO Portal sits on top of a standard ERP. Your team works only in PMO Portal and never needs to log in to the ERP.

Your ERP keeps the ledger

Odoo Community or ERPNext keeps the general ledger, PPN and e-Faktur, bank and financial statements. Approved documents go down to it. Statuses and payments come back.

Hosted by us, or on your server

We run it for you, or it runs on a server you own. Either way it is the same product and the same record.

Live in about a month

Onboarding takes about one month, from kick-off to your team working in it, with your own data loaded from templates and your own users signed off.

On the roadmap, not in the product today: equipment and fleet, an offline phone app, HR and payroll, and Lark and Google Workspace.

Help shape PMO Portal as a design partner.

PMO Portal is coming soon. We are choosing a small group of project-based companies to build it with, starting with Indonesia.

What you get

  • Early access, with onboarding by us
  • Direct influence on the roadmap
  • A say in which features ship first
  • Preferential terms when PMO Portal launches

What we ask

  • A pilot with real projects
  • A monthly feedback session
  • Permission to write a case study after go-live