The product website goes live, the platform is being hardened for production, and demo requests are open.
PMOlikePRO is moving from private development to production. What that means in practice:
- This website — pricing structure, guides, changelog and support are now public, with more arriving weekly.
- Production hardening — the launch checklist is being worked through: registration with company-email verification, billing, and operational monitoring.
- Demo program — walkthroughs with the founder are open now. Request a demo and see the platform on scenarios that look like your operation.
Pricing tiers are published; per-seat numbers are announced at launch.
Members and viewers now load only their own slice of the organization, completed work archives cleanly, and write-permissions were locked down org-wide.
A release about trust and speed at the same time — because they turn out to be the same work:
- Role-scoped reads. Member and viewer accounts now receive only the projects, tasks, clients and contacts they are actually assigned to — enforced at the database layer. Privacy improves, and so does performance: each session carries a fraction of the data it used to.
- Archive & data lifecycle. Finished engagements move to an archive tab — out of the daily working set, still fully reportable. Auto-archive can sweep long-finished work on a schedule you control, and reports include archived history on demand.
- Write-gate lockdown. Every write path was re-audited and re-gated by role, with a permanent automated guard added to the development pipeline so regressions can’t slip in silently.
- Windowed loading. The calendar and the time ledger now load by visible period, keeping the interface fast regardless of how much history the organization accumulates.
Finished, cancelled and paused work now follows one rule everywhere — keep the past, cut the future — and recurring work became one task instead of a pile of clones.
- One lifecycle rule, applied everywhere. Finishing, cancelling or pausing a project or task keeps every hour already worked and releases every future allocation. History stays truthful; capacity comes back to the team automatically.
- Recurring work, remodeled. A weekly duty is now a single task worked over time — one journal, one time history, one progress record — with its schedule materialized onto the dates it recurs. No more clone armies burying the board.
- Schedule polish. Frozen name columns, cleaner drag behavior, overallocation surfacing and a shared legend across every list — the planning surface got a coat of rigor.
Time moved into a first-class append-only ledger, financial data became server-gated by role, and reports learned to carry the whole story.
- A real time ledger. Time entries moved into a dedicated, append-only store — browsable by period, rolled up per task, per project and per person, and built to survive scrutiny.
- Server-side financial gating. Rates, budgets and costs are now delivered only to manager and admin sessions. Accounts that shouldn’t see money never receive it — not hidden in the interface, simply never sent.
- Dual margins. Effort (planned vs. worked hours) and money (budget vs. actual cost) are reported side by side, so neither can masquerade as the other.
- Structured reports. Branded PDF and Excel exports with delivery status, time and financials — ready for steering meetings and client reviews.
Enforceable two-factor authentication, a hardened sign-in, an audit trail and rate limiting — the trust layer every tenant stands on.
- Enforceable MFA. TOTP two-factor authentication for every account — and organizations can require it outright, holding un-enrolled accounts at the door until they comply.
- Hardened sign-in. Bot-challenged login and rate-limited authentication endpoints.
- Audit trail. Sign-ins, permission changes and destructive operations are recorded, so “who did that?” has an answer.
- Isolation, verified. Tenant isolation and role boundaries re-audited end to end — with the fixes applied and regression guards added to the pipeline.