Automate the finance, compliance and HR work nobody enjoys.
Three parts, each carrying its true status. Finance runs our own agency today. Compliance tracking was built for a corporate services firm. HR and payroll automation is a build we scope. Everything reads from and writes to one data model, with role-based access and an audit log showing the before and after on every change.
Finance
Recurring invoicing with payment links, billing reconciliation behind a hardened payment webhook, a payment-proof workflow, and an overdue-chase ladder that reminds and never negotiates. Referral and commission ledgers, multi-currency accounting that never adds currencies together, and payroll and commission rules kept as an internal ledger. All of it runs our own agency, before it runs anyone else's.
Contracts move through the same system: a deal becomes a quote, a quote becomes a contract, and e-signature at a public link converts the prospect straight into an active client.
Compliance
LexOS, built for eCSI, a Makati corporate services firm: SEC GIS, BIR, SSS, PhilHealth, HDMF and PEZA deadlines tracked per client entity, a document chase sent to their team and their clients, a Google Calendar sync, and AI-drafted documents that require human legal review before they go anywhere, exposed as tools an agent can call.
Piloted with their team. It is a deadline tracker, not legal advice, and not something a new client can sign up for today.
HR and operations
Roster, salary and commission rules, payroll exception validation where the system flags anomalies and a person approves, activity reporting, recruitment intake, membership and retention systems, and AI-drafted employee-relations documents.
Built on the same finance and approval modules that already run our own payroll, with the Data Privacy Act (RA 10173) handled by design, not bolted on after.
You do not need more capacity. You need accountability, method and measurement wrapped around the capacity you already have. The Command Centre tracks whether its own features are actually used, which is the same discipline this page is asking you to trust with your finance, compliance and HR work.
Every source feeds one model. A person signs off before anything leaves it.
Bank feeds, payroll files, government portals and calendars all land in the same platform. Nothing becomes a reminder, an invoice, a document or a deck without passing the approval gate first.
Sources
Bank & payment webhooks, payroll files, government portals, calendars.
The platform
Finance, contracts, compliance tracking, HR & payroll.
A person approves
Nothing skips this
Outputs
Reminders, invoices, documents, decks.
Questions about the finance and compliance work
What part of this actually runs today?
Finance: recurring invoicing, billing reconciliation, payment proof and overdue chasing run our own agency right now. Compliance tracking was built and piloted for one client, eCSI. HR and payroll automation is a build we scope, not something built yet.
What is LexOS?
Compliance deadline tracking software built for eCSI, a Makati corporate services firm. It tracks SEC GIS, BIR, SSS, PhilHealth, HDMF and PEZA deadlines per client entity, sends a document chase to their team and their clients, syncs with Google Calendar, and drafts documents with AI, though every drafted document requires human legal review before it goes anywhere. It was piloted with their team and is not something a new client can sign up for today. It is a deadline tracker, not legal advice.
Who approves what an agent drafts?
A person, every time. Every write reads from and writes to one data model with role-based access and an audit log that shows the before and after value on every change. Nothing an agent drafts, a reminder, an invoice, a document, publishes or sends without a person approving it first.
Can this replace our accountant or our compliance officer?
No, and we would not build it to. It tracks deadlines, flags anomalies, drafts documents and chases what is overdue. A person still reviews the anomaly, signs the filing, and decides what happens next.
How is this priced?
By contact, after we have seen the workflow. We quote based on how many systems it connects to, how much data moves through it, and how much a person needs to review before something goes out.
We quote after we've seen the workflow.
Bring us the deadlines, the invoices, or the roster you are currently tracking by hand, and we'll tell you what a build against it looks like.