VASCOM TECHNOLOGY AUTOMATION CO., LTD

Custom software

Written around your process, source code handed over.

See how we work
Built around the real process

Where the process is specific, the software is built for it

When packaged software does not fit the way a company works, there are usually two choices: change the process to suit the software, or build software to suit the process. VASCOM takes the second route, and says plainly when the first is the better one.

  • Assessment covers the steps done verbally and recorded nowhere
  • The core is built early enough to trial, not held back to the end
  • Web and mobile interfaces, permissions by role
  • Source code, documentation and user training handed over
Step by step

Four steps, each with something to review

Step 1

Process assessment

Map the flow as it actually runs, including the steps done verbally. Record who enters, who checks, who approves, and where errors tend to occur.

Step 2

Trial build

Build the core first so it can be used and commented on. The trial runs on one month of real data, not sample data.

Step 3

Completion

Add permissions, reports, notifications and edge cases. Tested against the company’s own real situations.

Step 4

Handover

Source code, documentation, user training; agreed arrangements for maintenance and future extension.

Measurable

Three questions worth answering before signing

Who uses it dailyHow many people open the software each day, and what work it saves them.
Time to a trial buildFrom the end of assessment to a build that can be trialled.
Who maintains it after handoverSomeone inside the company or VASCOM, under which arrangement.
”What

”What

Frequently asked questions

Before you start

How long does it take?

A narrow process usually takes a few weeks to reach a trial build. Most of the time goes into assessment and testing rather than writing code.

Is there a dependency on VASCOM alone?

No. Handover includes source code and documentation, so another provider can continue if a change is ever wanted.

What if the software needs changing later?

Changes are made on the existing foundation, or by adding another module. The architecture and documentation are written to be read by people other than the author.

Describe a process still done by hand

Write down the three steps that take the most time. VASCOM sets out which parts can be built and which parts should not be.

Zalo ☎
VASCOM
Call 0822.577.579 Get a consultation