4 min read
Clients often ask what working with us on a gaming project looks like. We are a web and app development company, so our role is the technical and documentation side: preparing the systems, records and policies that a licence application and later audits depend on. Legal advice and the application itself stay with your lawyer and the regulator. Here is our usual workflow.
| Step | What happens | Main output |
|---|---|---|
| 1. Scoping call | Understand model, market and licence category | Technical requirements list |
| 2. Requirements document | Write the specification, reviewed by your legal team | Approved specification |
| 3. Build and configure | Staged build with demos | Working systems with compliance features |
| 4. Documentation pack | Describe architecture, data flows and controls | Documentation for regulators and auditors |
| 5. Testing and review | Test journeys, reports and logs | Fixed issues and test records |
| 6. Launch and support | Launch, monitor, update | Stable operation and change records |
Step 1: Scoping call
We start by understanding your business model, target market and the licence category your legal adviser has recommended. From this we list the technical requirements that apply to you, such as identity verification, transaction records, player limits and reporting.
Step 2: Requirements document
We turn those requirements into a written specification covering the website or app, the admin back office, integrations with platform and payment providers, and the data you will need to keep. Your legal team reviews it so nothing important is missed.
- Player journeys: registration, verification, deposits, play, withdrawals
- Responsible gaming controls and how they are enforced
- Back-office roles, permissions and approvals
- Reports and the data each one draws on
- Data retention, privacy and security requirements
Step 3: Build and configure
We build or configure the systems in stages and demo each stage to you. Compliance features such as age checks, KYC flows, deposit limits, self-exclusion and audit logs are built in from the beginning rather than added at the end.
Step 4: Documentation pack
Regulators and auditors want to see how your systems work. We prepare clear documentation: system architecture, data flows, security measures, backup and recovery, and user roles in the back office.
Step 5: Testing and review
We test the full player journey on real devices and check that reports and logs match actual transactions. Any gaps are fixed before your application or audit.
Testing includes the unhappy paths: failed verification, blocked withdrawals, limit changes, self-exclusion and staff actions that should require a second approval.
Step 6: Launch and ongoing support
After approval, we help with launch, monitoring, updates and changes required by new regulations or renewals.
What we do not do
We do not promise approval, deal with regulators on your behalf or help anyone avoid regulation. Every project must be lawful and properly licensed.
We do
Specifications, builds, integrations, documentation, testing and technical support for licensed or licensing businesses.
We do not
Give legal advice, guarantee approval, represent you before regulators or work on unlicensed operations.
Frequently asked questions
Do you submit the licence application?
No. Your lawyer and your company handle the application. We prepare the technical systems and documentation it relies on.
Can you work with our existing platform provider?
Often yes. We can integrate with or configure existing systems, provided they can meet the regulator’s requirements.
What happens when rules change?
We update systems and documentation to match new requirements as part of ongoing support.
This article is general information, not legal advice. Gaming rules in the Philippines change, so always confirm current requirements directly with PAGCOR and a qualified Philippine lawyer before you apply or launch.
