Skip to content
VEXA
Call +6017-725 5992

What we build, and what each one costs you in time.

Six kinds of system. Each section says what is included, what is not included unless you ask for it, and who it suits. If your problem sits between two of them, that is normal — most do.

01Replaces a Facebook page, or a site nobody has been able to edit since 2019.

Company website

A site that holds up when a buyer checks you out before a meeting. Written as pages about your business, not filled into a template.

What you get

  • Up to eight pages, written with you
  • Built mobile-first and checked on real phones
  • An enquiry form that reaches an inbox you own
  • Search Console, analytics and a sitemap configured
  • Page titles and copy structured around what your customers actually search for

Not included unless quoted

  • Logo design and brand identity
  • Photography and video
  • Ongoing content writing after launch
  • Paid advertising management

Suits — Companies who need to look established the moment someone looks them up.

Company website wireframeA browser window showing a page wireframe: a navigation bar, a headline with a call to action, three proof columns, and an enquiry form flagged as the element that reaches the client’s inbox.
FIG. 08 — Company website, as a wireframe

Redrawn from a system we built. Sample values, not client data.

02Replaces the weekly status email, and five people asking the same question.

Operations dashboard

One screen that answers what your managers ask every morning, reading from the systems you already run.

What you get

  • Logins by role, so people see their own operation
  • Figures read live from your own records
  • Filters by site, team and period
  • Export to Excel and PDF
  • A record of who changed what, and when

Not included unless quoted

  • Cleaning up historical records
  • Hardware
  • Connecting to systems that cannot share their data at all

Suits — Operations that have the data but cannot see it in one place.

Modules

  • Staff
  • ▸ Devices
  • Email analytics
  • Access control
  • Reports

Devices by department

AsseMachQualStorLogiMainPlanFinaHRITSaleAdmi

IT · 9 devices awaiting return from leavers

Devices assigned
214
Unassigned in stores
26
Access reviews due
3
FIG. 04 — Operations dashboard

Redrawn from a system we built. Sample values, not client data.

03Replaces a shared spreadsheet, a whiteboard, and a WhatsApp group.

Stock and warehouse system

Receiving, transfers and reorder alerts, with the stock figure held in a database instead of a file people take turns editing.

What you get

  • Bin-level stock with reorder points your supervisor sets
  • Goods receiving against purchase orders
  • Transfer and adjustment logs carrying operator and timestamp
  • Low-stock alerts by email
  • Barcode or QR scanning from a phone
  • Count sheets, variance reports and a finance export

Not included unless quoted

  • Accounting postings
  • Label printers and scanners — we specify them, you buy them
  • Integration with an ERP that cannot export

Suits — Warehouses where the number on screen and the number on the shelf disagree.

Stock · Receiving
Stock on handGoods receivingTransfers
All itemsBelow reorderLocation: Plant 1
SKUDescriptionBinOn handReorder ptStatus
AL-6061-T6-25X3Aluminium bar 25mm x 3mA-04-231280OK
SS-304-SHT-1.5Stainless sheet 1.5mmA-07-19640OK
FST-M8-40-ZPHex bolt M8 x 40 zincC-11-11840600OK
BRG-6204-2RSBearing 6204 2RSC-02-424060OK
SEA-NBR-70-32O-ring NBR 70 32mmD-01-3604250OK
PNT-EPX-GRY-5LEpoxy primer grey 5LE-09-22812OK
FIG. 01 — Stock on hand

Redrawn from a system we built. Sample values, not client data.

How a stock record is keptThree kinds of record: items, locations, and every movement. Each movement records which item, which location, how many, when and who, so stock can only change with a trace, and the system will not let a count go below zero.ItemsCodeDescriptionReorder levelLocationsAreaShelf and binEvery movementWhich itemWhich locationHow manyWhenWho
FIG. 02 — How stock stays accurate

04Replaces retyping the same data into three places, then formatting a PDF.

Workflow automation

Rules that read what arrives, file it, and produce the documents your process requires. You can read every rule.

What you get

  • Email monitoring with rules written in plain terms
  • Documents generated from the record instead of typed
  • Scheduled reports to the people who need them
  • File and folder organisation that survives staff changes
  • Nadcap and ISO 9001 paperwork produced from the job record

Not included unless quoted

  • Anything that depends on a system that cannot share its data
  • Sign-off on your quality manual
  • Dealing with your auditor

Suits — Teams whose month-end is a person, a folder and a long evening.

How complaint email is sortedEmail arrives, is sorted by plain rules, sent to quality, logistics or sales, logged, and summarised in a daily report at six in the evening. Three example rules are shown: a mention of a rejection is marked urgent, mail from a key customer goes to quality, and anything unanswered for two days is escalated.
FIG. 03 — Complaint email, sorted automatically

Redrawn from a system we built. Sample values, not client data.

05Replaces numbers typed into a spreadsheet at month-end, and decisions made on last month's picture.

Data collection and analysis

Capture the numbers where they happen — the floor, the counter, the van — hold them in one database, and turn them into reports your managers read without asking anyone for a spreadsheet.

What you get

  • Data capture on phones and tablets: forms, barcode scans, photos, signatures
  • One database with the definitions agreed, so two reports can never disagree
  • Daily and monthly reports produced on a schedule rather than assembled by hand
  • Trend and exception views: what moved, what is late, what is drifting
  • Exports to Excel and to whatever format your accountant uses

Not included unless quoted

  • Cleaning years of historical spreadsheets, unless quoted
  • Statistical consulting or forecasting models
  • Dashboards for data you have not yet started collecting

Suits — Small and mid-sized companies making decisions on instinct because the numbers arrive too late to matter.

Data collection and analysis pipelineThree stages in sequence: capture on a phone, scanner or form; storage in one place with one agreed set of numbers; and scheduled reports. Beneath them, a twelve-week bar chart of a sample figure rising from 42 to 66, with one week in eleven flagged where it dropped to 47.
FIG. 05 — From the floor to the report

Redrawn from a system we built. Sample values, not client data.

06Replaces five off-the-shelf tools, none of which quite fit, and a person bridging the gaps by hand.

Custom software to your requirements

A system built around the way your company actually works — your approval chain, your exceptions, the report your director wants on Monday. Scoped with you, built in drops you can test, and yours at the end.

What you get

  • A written scope drawn from a walkthrough of your process, not from a template
  • Screens for each role, with the approvals and exceptions you actually use
  • Integration with the systems you are keeping: accounting, email, spreadsheets
  • Built in drops you can try, so nothing at launch is a surprise
  • The software, its database and a plain handover guide, all in your company's name

Not included unless quoted

  • Changing your process to fit the software (we do the reverse)
  • Off-the-shelf licences resold with a margin
  • Anything the scoping call shows a spreadsheet already does well

Suits — Companies whose process is their edge, and does not fit inside a package.

Purchase approval chainFour stages in sequence: a request from any staff member, a supervisor check on quantity, a finance check on budget, then approval and a purchase order. A branch marked over limit routes requests above a threshold to a director before finance.
FIG. 09 — An approval chain, with its exception

What buyers ask before they commit.

How much does a system cost?
It depends on how many screens and how much of your existing data has to come across. We scope the work on a 30-minute call and send a written fixed price within 3 working days, with the exclusions listed. We do not bill by the hour for defined work.
Who owns the code and the data?
You do. The software, its database and the accounts it runs on are registered to your company and transferred on final payment. If you stop working with us, everything keeps running and any other developer can pick it up.
Can our own IT person maintain it afterwards?
Yes, and it is built for that. We use widely known, well-documented tools rather than anything exotic, and at handover you get a plain guide: how the system runs, where the backups are, and what to check when something looks wrong.
Do you work with companies outside Malaysia?
Yes. We work remotely with companies anywhere, and on-site in Malaysia. For a stock or warehouse system we want at least one walkthrough of the floor before quoting: in person where we can, on video where we cannot. Our hours are 09:00-18:00 UTC+8, and we will find an overlap with yours.
Can you connect to our accounting package or existing ERP?
If it can share its data, by an export or a connection other software can use, then yes. That covers AutoCount, SQL Account, Xero, QuickBooks and most business systems. If it cannot, we will tell you on the call rather than after the quote; that is the single most common reason we say no to a project.
What happens after launch?
Thirty days of fixes at no charge. After that you can either take it in-house or keep us on for support, and the terms for that are agreed in writing before launch, not improvised afterwards.

Send us your current process — the spreadsheet, the form, the WhatsApp group. We will tell you what is worth automating and what is not.

Book a 30-minute scoping callWritten quote within 3 working days of the call.
CallWhatsAppBook a call