Skip to content

ArifLab / PROJECT PROCESS

From your workflow to a working system.

Requirements → scope and quotation → development → joint testing → handover. Each project begins with agreement on the work and outcome.

  1. Understand the requirements

    Share your business type, current process, main problem, people using the system, estimated budget and target timeframe. We review whether an existing base can fit or a custom build is needed.

  2. Agree scope, quotation & payment

    Write down deliverables, exclusions, responsibilities, milestones, project price, hosting and optional maintenance. Any deposit or staged payment, revision allowance and cancellation handling are agreed before acceptance.

  3. Build & configure

    Develop or configure the agreed workflow. Provide the authorised data, accounts and feedback specified in the project plan. Requests outside the scope receive a change estimate before extra work starts.

  4. Test with you

    Walk through the real business tasks, check totals and roles where relevant, and record defects or open items against the acceptance checklist. The agreed deployment must pass its own security, backup and core-journey checks.

  5. Hand over & support

    Deliver the agreed access, files, documentation and walkthrough. Confirm hosting ownership, usage/source-code rights, data export, support and any optional maintenance. The project quotation governs the scope after handover.

What we agree to deliver.

System scope
The workflow, screens, fields, roles and reports agreed in your project quotation. Starting packages reuse an existing base; a from-scratch build is separately scoped.
Build & configuration
Configure or develop the agreed system and test the core tasks with you. New requests after scope agreement are reviewed as changes.
Starting data
You supply authorised business data in an agreed format. Bulk import, cleaning and migration are separate unless explicitly included.
Onboarding & handover
A walkthrough, quick-start reference and acceptance checklist. The quotation states session count, delivered files, accounts and access responsibilities.
Ownership & hosting
Agree usage rights, source-code ownership, third-party licences, hosting accounts, data export and access after handover in writing before work starts.

A handover you can check.

The checklist belongs to your project. It records what was accepted, who owns each account and what happens next.

  1. 01 / SYSTEM

    Scope and acceptance.

    Check the delivered screens, fields, workflows and roles against the agreed quotation. Record open items and their owners.

  2. 02 / ACCESS

    Files, accounts and data.

    Confirm admin access, hosting/provider ownership, credentials handover, licences, agreed source files and export arrangements.

  3. 03 / CONTINUITY

    Guidance and support.

    Complete the walkthrough, hand over documentation and confirm support, maintenance, backup and change-request responsibilities.

Download handover preview ↗Download example-system quick-start ↗

Dates and ongoing costs.

We set a delivery plan after the scope and dependencies are understood. The quotation states the customer inputs needed and how delays or changes affect milestones.

Hosting is quoted separately or explicitly included. Optional maintenance has a defined task list, effort allowance and support schedule. New features, major changes and third-party charges are separate unless included.