Skip to content

MAGIK Tech / Custom systems

Built for how your business actually runs.

If it runs on paper, it can run on a system.

Tell us the problemWhatsApp us

One request, from paper to report

Custom systemsRequest 014
  1. 1Requested
  2. 2Approved
  3. 3Issued
  4. 4Filed
  5. 5Reported

On paper

1 · Stock request filled inRequester

The requester writes the item and quantity on a form and carries it to a supervisor.

As a system

Requester, then Supervisor, then Storekeeper, then Accounts

  1. Requested
  2. Approved
  3. Issued
  4. Filed

Waiting with

  • Supervisor
  • Storekeeper
  • Accounts

The request is a record from the start: numbered, with the requester filled in, and sent to the supervisor.

Request · filled in by the system

014

Requested by · filled in by the system

Requester

Item

Printer paper

Quantity

5 reams
PreviousNext step
  1. 1Who does what, in what order
  2. 2Records
  3. 3Reports
  4. 4Roles

Before you ask

Good to know.

At handover
  • The system, on the hosting agreed at the start.
  • An account for each role, with the right permissions.
  • Your existing records brought across and checked.
  • The forms and reports you actually use.
  • A short guide for each role, in plain words.
What shapes the quote
  • Processes covered
  • Users and roles
  • Records to bring across
  • Number of sites
  • Reports you need
  • Connections to what you run
  • Working through power cuts
  • Training
  • Support after handover
  • Where it runs
Questions
How long does it take?
It depends on how many processes it covers and how many records have to come across. The timeline is agreed once the scope is.
What if the power or the network goes down?
Decide this early, because it changes the build. Tell us which parts of your day cannot stop, and the design follows.
Who owns the data?
Your records are yours, with an export you can run at any time. Who owns the software itself is agreed in writing before work starts.