Operating outcomes and portfolio
Select only the customer, growth, intelligence, operations, or people services required for the agreed result. Shared delivery capabilities are included only where the signed scope needs them.
Custom package for large organisations
A governed ONSET rollout when a standard package is not enough.
Define the outcomes, account structure, integrations, provider costs, approval boundaries, and acceptance evidence before implementation begins. The result is a written service order, not an open-ended technology promise.
Published commercial floor
Enough pricing context to qualify the engagement before a call.
RM15,000+
implementation starting floor
RM3,000+
managed service per month
50%
implementation mobilisation
6 months
initial managed-service term
The final quotation may be higher where the work needs more integrations, data preparation, environments, users, providers, support, or change control. The complete amount, milestones, and exclusions are disclosed before acceptance.
What is scoped
Four decisions make the custom package concrete.
Accounts, users, and approval boundaries
Define account structure, owners, roles, service access, approval responsibilities, and the actions that must remain manual.
Data, providers, and integrations
Review source systems, customer-owned provider accounts, how third-party usage will be paid and approved, data handling, and each proposed integration before it enters the service order.
Evidence, acceptance, and support
Write measurable acceptance criteria, proof artefacts, rollout stages, support windows, reporting, and change control into the engagement instead of relying on broad promises.
When custom makes sense
Choose it for real complexity, not status.
If these conditions do not apply, Starter, Growth, Pro, Growth Pilot, or one specialist service is usually the clearer and lower-risk route.
- Multiple teams, brands, locations, or operating accounts need one governed rollout.
- A standard package does not cover the required integrations, controls, volume, or delivery support.
- Procurement needs a clear scope, milestone plan, provider-cost rule, and acceptance process.
- The organisation wants a staged implementation before expanding access or workflow authority.
Commercial and delivery sequence
No activation before the agreement and commencement payment.
01
Fit review
Confirm the outcome, constraints, systems, users, and whether custom work is justified.
02
Service order
Write the exact scope, exclusions, term, provider rule, milestones, and acceptance evidence.
03
Implementation
Begin after signature and mobilisation payment; release each milestone against its agreed proof.
04
Managed go-live
Start only after acceptance and first monthly payment; expand later through change control.
Commercial FAQ
What procurement and finance should know first.
What is the starting investment?
Custom implementation starts from RM15,000. Managed service starts from RM3,000 per month. These are floors, not automatic quotations; the written scope confirms the complete price before approval.What is paid before work starts?
The signed service order and a 50% implementation mobilisation payment are required before build work starts, unless an agreed milestone schedule says otherwise. The first managed-service month is paid before production go-live.How long is the managed-service contract?
The standard initial managed-service term is 6 months after go-live, billed monthly in advance. Implementation milestones and the managed-service term are stated separately so project work is not confused with the recurring retainer.Is there a separate security retainer?
Not by default. Implementation uses the written milestone payments, while the recurring managed service uses the first monthly retainer before go-live. Any exceptional credit-security requirement would have to be disclosed and accepted in the service order.Are cloud, LLM, messaging, and transaction fees included?
Customer-owned provider keys are the default. Managed-provider usage is offered only when a written allowance and an enforceable account budget are configured; otherwise it remains unavailable. Unpriced provider calls stay visible and are never presented as zero-cost usage. Customer-owned account charges are paid directly by the customer. Provider telemetry is labelled as recorded, estimated, or unpriced and never authorises a customer charge.Does custom mean every ONSET module is included?
No. The service order lists the exact customer-facing services, supporting capabilities, users, environments, volumes, and exclusions. Anything outside that written scope is not included or promised.
Bring the requirement, systems, and operating constraints.
We will decide whether a standard package, specialist service, or custom service order is the right commercial route before proposing implementation.
Scope a custom package