Forvyn

ForvynProcess to System

Operations-first software development

Your business has a process.
We make it work better.

We turn your company’s processes into working software.

Still managing approvals, records and reminders across spreadsheets, WhatsApp and email? We turn scattered workflows into practical, custom-built systems your team can actually use.

Discuss your workflow Explore QMS Hub
  • Process-first
  • Written scope
  • Tested handover

01 — What we do

Most companies already have a process. It just lives in the wrong places.

  1. It starts scattered.

    A spreadsheet one person understands. Approvals in a WhatsApp group. Paper forms in a drawer. Licence dates on someone’s calendar. It works until that person is on leave, or an auditor asks for last March.

  2. We map how work really moves.

    Who records what, who approves it, what has to be kept and for how long. We write it down in plain language before anyone writes code, and we tell you honestly if an existing tool already does the job.

  3. Then it becomes a system.

    One place for the records, clear roles, automatic reminders and a trail you can show an auditor. Built around your process, not a template you have to bend to.

02 — Services

Custom systems first.

Our core work is building the software that runs your process. Advisory and AI automation sit around that when they help the same outcome.

Core

Custom business systems

Web apps and back-ends that run a real workflow, not brochure websites. We specify, build, test and ship systems shaped around how your team records, checks and approves work.

What it usually includes

  • Registration and receiving forms with the fields your records need
  • Approval flows with clear owners at each step
  • Imports from the spreadsheets you already have
  • Dashboards and printable reports
  • Role-based access, so people see what their job needs
  • Email or Telegram notifications and expiry reminders
  • Scheduled cloud backups

You receive

  • A written specification you approve before build
  • A working system, tested against your own records
  • User guides for each role
  • A handover note: where it runs, how it is backed up, how to change it

Around the build

Operations and process advisory

An outside operator’s look at how your work actually flows, including quality and compliance. You get a clear diagnosis and a recommendation, even when the answer is “don’t build anything yet.”

Where we look

  • Hand-offs where work stalls or gets re-typed
  • Records you are required to keep, and the ones you keep out of habit
  • Quality and compliance routines, such as complaints, receiving checks and licence renewals
  • Build versus buy: when an off-the-shelf tool is the better answer

You receive

  • A process map your team recognises
  • A prioritised list of fixes, with what each one costs you today
  • A plain-language recommendation: change the process, buy a tool, or build

Efficiency layer

AI automation

When a custom system is in place, we add AI where it removes repetitive load — drafts, triage, watches — with a human owner and clear limits on what may go out without approval.

Roles we set up

  • Growth and marketing
  • Inventory watch
  • Customer service drafts
  • HR admin
  • Regulatory checks
  • Email triage
  • Competitor tracking

You receive

  • A written role for every assistant: inputs, outputs, boundaries
  • Review steps where a person approves before anything goes out
  • A routine your team can run, check and switch off

We run this kind of multi-assistant setup day to day inside a medical-supplies distributor. What we recommend, we use.

03 — How we work

Diagnose. Specify. Build. Hand over.

Short cycles, written decisions and testing on real records. You always know what is being built and why.

  1. 01

    Diagnose

    We sit with the people doing the work and follow a real record from start to finish: a delivery, a complaint, a renewal. We note every re-type, every wait and every “ask Aunty Lim, she knows.”

    You receive

    • A process diagnosis and problem list
    • A plain-language feasibility note
  2. 02

    Specify

    We write the system down before it exists: roles, records, rules, screens and reports. You review it in plain English and sign off. This is where most of the expensive mistakes get caught.

    You receive

    • A written specification
    • A quote, milestones and acceptance criteria
  3. 03

    Build and test

    The system is built in small, usable pieces. Each piece is tested with your own data and your own staff before the next one starts, so problems surface in week two, not at launch.

    You receive

    • A working version you can operate
    • Test notes and stage acceptance
  4. 04

    Hand over and support

    Training for each role, backups that are switched on and checked, and documentation you own. After launch, changes are handled as clear requests, not surprises.

    You receive

    • The system, guides and backup setup
    • A clear note on how changes are requested

Before you spend

How is the fee set?
After Diagnose and Specify. You approve a written scope, milestones and price before Build starts. No open-ended build without that sign-off.
What if the scope changes?
Changes are written as a short change note with effect on price and timeline. Nothing moves until you agree.
Who owns the software and data?
You do. Source, documentation, backups and your records stay with you.
What happens if something breaks?
Handover includes how to reach us for support. Critical issues are handled as agreed in the support note for that project.
Can another developer maintain it later?
Yes. We hand over documentation and access so your team or another developer can continue without lock-in.

04 — Selected work

Systems we have shipped.

Custom business software for distributors, ecommerce operators and growing teams across the region.

Flagship — QMS Hub

A contact-lens and medical-supplies distributor has to keep quality records that stand up to inspection: what arrived and when, which complaints were raised and how they were closed, which licences expire next. Records like these tend to spread across spreadsheets, paper files and message threads, which is exactly what makes an audit slow.

What was built

QMS Hub is a web application designed around the company’s own quality routines. The system was specified against real records, reviewed with the people who use them and developed with the team. It was built for this company’s process, not adapted from a generic template.

Where it stands

QMS Hub is a developed in-house quality system, not a mass-market product. Its structure can be customised for other SMEs with similar quality and compliance work, such as distributors, clinics’ suppliers and small manufacturers.

Illustrative layout, not a screenshot. Client data is never shown.

QMS Hub capabilities

  • Receiving registrationIncoming goods logged with the details the quality record needs.
  • Complaint approvalsComplaints raised, reviewed and closed through a defined approval path.
  • Data importsExisting spreadsheets brought in, so history is not lost.
  • Audit reportsRecords pulled together in the format an audit asks for.
  • Licence expiry remindersRenewals flagged before they lapse, not after.
  • Email and Telegram notificationsThe right person hears about the right event.
  • Role-based permissionsStaff, Quality lead and Top Management each see and approve what their role requires.
  • Cloud backupsScheduled backups to Google Drive.

Other client systems

  • Ecommerce

    Ecommerce website system

    A custom storefront and backend for an ecommerce operator: catalogue, orders and the day-to-day workflows the team actually runs.

  • Hong Kong

    HR management system

    An HR system for a Hong Kong client, covering the people records, approvals and routines the company needs to run without chasing spreadsheets.

  • Singapore

    Automatic reconciliation

    For a Singapore ecommerce client: automatic matching of orders, payments and bills so the books close without manual line-by-line checks.

Running similar operations, quality, HR or finance work on spreadsheets? We can adapt an existing system pattern rather than rebuild from zero.

Tell us what you need

05 — About

An operator who ships systems.

Forvyn comes to software from the operations side. We have run day-to-day work at a regulated distributor, so we know what a missed licence renewal or a lost receiving record actually costs.

On every project we act as product and project owner: we work out what the system must do, write it down, review every build, test it against real records and decide when it is ready to ship. We stay accountable for the result. That is how QMS Hub was made.

How we think about the work

  • Process before software. If a five-minute change to how people work fixes it, we will tell you, and you won’t pay for a system.
  • Write it down. Every system starts as a document you can read and argue with.
  • Test with real records. Demo data hides the problems that matter.
  • People approve, tools assist. Automations and AI assistants work inside limits, with a named person responsible.
  • You own what we build. Your data, your backups, your documentation.

“Good advice is a plan. A working system is the advice, carried out every day.”

06 — Contact

Tell us which process hurts.

A few sentences are enough: what the work is, who does it and where it goes wrong. We will reply with honest next steps, including whether you need us at all.

WhatsApp
+852 4415 9685

A good fit if you

  • run a growing SME with a process that has outgrown spreadsheets
  • have quality, compliance or approval work that must be traceable
  • want AI working inside operations, with people still in charge
What do you need help with?

Submit sends your enquiry to Forvyn. We reply by email. WhatsApp is also open if you prefer a short message first.