Ready to accelerate your digital transformation? Get your FREE Digital Readiness Score today!

Illustration of business colleagues scoping users, outlets, devices and responsibilities before a Lark quotation.

Planning a Lark rollout in Malaysia: what to scope before requesting a quote

Share

Two Lark quotations can look different because they describe different work. One covers user licences. Another includes a workflow, data preparation and onboarding. A third assumes that your team will configure and maintain the process internally.

Before comparing prices, describe the people, process and responsibilities you want the quotation to cover. A short, specific brief gives both sides a useful starting point and makes exclusions easier to identify.

You do not need a complete technical specification to begin. You do need a business owner, an example of the work and a clear explanation of what should be better when the first rollout is in use.

Choose the first process and its finish

Select one process that causes repeated follow-up or unclear ownership. Describe how it starts, who makes the decision and what counts as completion. An approval process may end with a decision, while the operational work continues through ordering or delivery. State which part the implementation must cover.

Use a recent type of request to explain the current process. Remove personal or confidential details from material shared for an initial discussion. A blank form, a simplified process diagram or an anonymised example can be enough to show the structure.

Include the exceptions that affect the scope. A changed amount, an absent approver or a request returned for correction can require a different route. Decide who has authority to settle these rules. The supplier can configure a process, but the organisation must define its decision authority.

List users by role and device

Provide the expected number of workers, managers and administrators, plus the sites or teams involved. Identify who needs to submit, approve, review reports or change the setup. A total headcount alone may conceal different access and plan requirements.

Record the devices each group will use and any shared-device arrangements. Include connectivity conditions and language requirements where they affect the task. Ask for any uncertain device behaviour or entitlement to be checked against the current Lark plan information.

Separate the pilot group from a possible later expansion. The initial quotation should show what it covers now and how a wider rollout would be scoped. It should not assume every possible future workflow is included.

Distinguish licences, implementation and ongoing responsibility

Licences determine product access under the selected terms. Implementation covers the agreed configuration and related work. Onboarding helps the intended users understand their roles. Ongoing support needs its own description.

Ask the quotation to identify these components clearly. Check whether data preparation, integration, user setup, testing and post-launch changes are included or excluded. Agree who maintains the process after acceptance and how additional work is requested.

Current prices and entitlements should come from the relevant quotation and vendor terms. A general article cannot determine the plan, contract or support arrangement for your organisation.

State where information will remain

List the documents and records the workflow needs. Decide whether existing files stay in their current location and who must be able to open them. Identify any information that should not be collected in the new process.

If a connection to another system is required, name the exact information and purpose. “Integrate with our ERP” is too broad to price reliably. A more useful requirement identifies the event, fields, direction, timing and responsible owner when a transfer fails.

Use the official Base and Approval documentation to examine the proposed capabilities. Confirm the chosen design through a walkthrough and testing rather than assuming every connection or rule is available by default.

Use this scoping worksheet

Complete the parts you know and mark unresolved decisions explicitly.

Scope question What to put in your brief
Business problem A recurring delay, missing decision or handover that needs attention.
First process Start, decision and completion boundaries, with the main exceptions.
Sponsor and process owner Who approves scope and who maintains the process.
Users and sites Roles, initial numbers, locations and possible later expansion.
Devices and access Personal/shared/company devices and the actions each role needs.
Information Required fields, supporting documents and access restrictions.
Existing systems What stays where and any specifically required connection.
Implementation responsibilities Configuration, data preparation, onboarding and testing owners.
Acceptance Observable tasks and outcomes that must pass before rollout.
Ongoing support Required coverage, exclusions and change-request arrangements to discuss.

This worksheet is a discussion aid. It does not create an agreed price, delivery date or service commitment.

Agree acceptance before the build expands

Write acceptance criteria in terms that the process owner can check. A worker can submit a complete request. The right manager can review it. A returned request reaches its originator. The person acting on approval can identify the correct decision and supporting version.

Test relevant access restrictions, an unavailable owner and a failed or uncertain submission. Check mobile and manager tasks separately. Include the person who will support ordinary users after launch.

Agree how pilot issues are recorded and which must be resolved before expansion. If the organisation changes a business rule during the work, record the change and its scope implications. This prevents a small first process from becoming an undefined company-wide project.

MatrixC offers Lark licensing, workflow implementation and onboarding. Request a scoped Lark quotation with your first process, users and sites. Include the main exception and the person who will own the workflow so the discussion can establish what the initial rollout should cover.

Contact Our Team

Are you interested to learn more about our products?

Do you wish to speak to us for professional advice on digitalizing your business? Click on the button below to book a complimentary 1-on-1 consultation with an expert from our team.

You may also like