This is the work we do every week. Each engagement below is an enterprise-grade implementation — scoped, staffed and delivered to the standard a regulator, an auditor or a board will hold it to, not a proof of concept that stops at the demo.
With AI doing the assembly, all of it moves fast. And with 500+ specialised implementations behind us, the speed does not cost you accuracy: we have met your requirement before, so we understand what you are asking for and deliver it.
The same scope, planned twice. Above is how we deliver it now, with the agents doing the assembly and every build workstream running at once. Below is what that same work took when it was built conventionally — and still does, nearly everywhere else.
Scope in a day. The whole build in five, every workstream concurrent. Enablement and go-live a day each.
Sequential phases, one system at a time, and a discovery cycle before any of it starts.
Eight days is the plan for a clean scope. Anything with unusual data, an awkward integration or a regulator with its own format lands inside the month. Workstreams you do not need come out of the plan and off the price — nothing here is a fixed package.
Every engagement is run by a solution architect who stays with you from scoping through handover. You always know who is building what.
We sit with your specialists, map the workflow you run today and write down what the platform will do and what it will not.
Anything the platform can be configured to do, we configure. Anything it cannot, our team builds into your tenant — enabled under your licence, with the specification documented.
Training, documentation and a shadow period. The success test is that your people can make the next change in the application themselves, without calling us.
Scoping runs through the same assessment every time: what the knowledge work is, what the technology and AI work is, and how it has to be deployed. That is what produces the number, and it is why the first figure reaches you in days rather than weeks.
No meeting required. This part runs on the scoping form.
You tell us what you deliver, to whom, and under which obligations. The Komplee and OpsCon forms ask different questions.
We assess the knowledge work, the technology work, the AI work and every component that has to be built, configured or connected.
We assess how it should be deployed — tenancy, environments, integrations, data residency — and what each option carries.
You get one-off fees, subscription fees and AI credits if the build needs them, itemised and separate so you can see what each layer costs.
One-off feesSubscription feesAI credits, if neededOnly once you want to proceed.
A solution architect goes through the estimate line by line, corrects anything the assessment read wrong, and re-sends it as final commercials.
Terms are signed and your application is switched on. The implementation plan on this page starts from that date.
Engagements are quoted as a fixed scope with a change process, so a longer build does not quietly become a bigger invoice. Subscription and managed-run agreements are annual and cancellable. See platform pricing →
Connectors for the ERP, meter and HR systems common in Philippine and regional enterprises, plus a documented API for everything else. Integration work is delivered with its reconciliation tests.
Two forms, because the questions are different. Komplee scoping asks about frameworks, entities and reporting obligations. OpsCon scoping asks about hazards, assets, thresholds and who has to be told.
Komunidad is licensed software, delivered the way any enterprise SaaS is. The short version: the platform stays ours, your data stays yours.
No. Komunidad is proprietary SaaS. Source code is not provided, escrowed or handed over — not for the platform, and not for anything built for you on top of it. That is the same arrangement you already have with every other enterprise SaaS vendor you buy from, and it is what lets us keep shipping improvements to every customer at once instead of maintaining forks.
What an engagement delivers is a configured, running application under licence, with its documentation, its configuration and its data — not a codebase.
You do. Every record you ingest, every document you upload, every figure your team enters and every output calculated from them remains your property throughout the engagement and after it. We process it to run the service you are paying for, and for nothing else.
You can download all of it, at any time, without asking us — in open formats (CSV, XLSX, JSON, PDF for rendered reports) with the lineage and audit trail attached. There is no exit fee for your own data and no hostage period at the end of a term.
No. Every customer runs in its own tenant with schema-level isolation, so there is no shared table any query could cross. No tenant can see, search, reference or infer another tenant's data, and that holds for our own staff outside a named support request you raise.
Your data is never used to train models that serve anyone else. We operate the same controls any serious SaaS provider does: least-privilege access, logged administrative actions, encryption in transit and at rest, change control, and a documented incident process. The detail is in the security pack, available on request under NDA.
Configuration, models, calculators, workflows, integrations and interfaces built for your requirement and enabled in your tenant. You get the use of them under your subscription, the specification behind them, and the right to keep running them for as long as you hold a licence. What you do not get is the code that implements them.
Yes, and we prefer it. Your team works against our documented API and the platform's configuration layer rather than inside our codebase — joint delivery usually means a shorter engagement and a much shorter handover.
Most customers take a managed-run agreement for the first year: a named engineer, quarterly framework updates and incident response. It is annual and cancellable. The platform subscription continues separately; the application keeps running whether or not you keep the managed-run.
A shaping conversation with a solution architect, not a sales call. Bring your current process.
The two forms ask different questions. Pick the one that matches the work.
This is where the scoping form opens. It is not connected yet — we are wiring it to the live form next.
Prefer to talk it through first? Send us the shape of it and a solution architect will reply.
Both platforms open at launch. Reserve your place now and your access opens with them.
Reporting, assessment and compliance
Monitoring, early warning and operations
One email, on launch day. Nothing else.
New to Komunidad? Become a partner, free