hello@psoi-tech.comReview my manual workflow

Custom workflow software · Singapore

Turn manual operationsinto software your team can run on.

PSOI Tech helps operations-heavy Singapore SMEs—especially logistics teams—replace Excel, email and WhatsApp handoffs with internal tools, automation and customer portals. Most first releases are delivered in 2–6 weeks, depending on scope and integrations.

Review my manual workflowSee our work
  • Published prices
  • Working demo every week
  • Reply within 48 hours
6
published case studies, every build live
2–6 weeks
typical time to a first release
48 hours
to a clear next step on an enquiry
UEN 202633837E
Singapore-registered, code owned by you

Selected work

Live systems, built for real operating problems.

Every entry below is live. Only verified project information is published — no invented metrics and no placeholder quotes.

Representative interface — sample data, not a client system.

01Client projectNS Logistics Global · Logistics and freight forwarding

NS Logistics Global

A responsive multi-page website that sets out freight services and coverage, then captures interest as a structured quote request.

Before
Freight enquiries arrived from several directions and rarely carried the detail needed to quote.
After
Services and coverage are set out publicly, and an enquiry arrives as a structured quote request that can be actioned.

Interface summary

What the site puts in front of a shipper

  • A freight service and coverage overview
  • Quote capture shaped around what a freight quote needs
  • A responsive multi-page layout for mobile and desktop
Read the case study

Representative interface — sample data, not a client system.

02Client projectUnmanned aircraft operations

UA Ops Preflight

A controlled pre-flight release workspace that reconciles weather, authorisation, crew, aircraft and site checks in one place.

Before
Weather, authorisation, crew, aircraft and site checks sit in separate documents and apps, and the pilot in command reconciles them from memory under time pressure.
After
The same checks are reconciled on one screen, and releasing a flight is a deliberate action with the pilot's notes attached to it.

Interface summary

What the pre-flight workspace puts on one screen

  • Live weather read against the operator's own limits
  • A 17-step release checklist run in sequence
  • Authorisation, crew, aircraft and site status
  • Operational alerts and pilot-in-command notes
  • A release gate that a person has to action
Read the case study

Representative interface — sample data, not a client system.

03Client projectDrone building inspection

PFI Sorting

A sorting tool that reads drone photo metadata and splits a building-inspection flight into numbered inspection run folders, using the straight-down camera marker pilots already fly.

Before
An inspection flight comes back as one long photo stream, and someone separates hundreds of images into roof faces, elevations and passes by hand.
After
The tool reads the marker already sitting in the photo metadata and writes the flight out as numbered inspection run folders, with a report of why each folder was started.

Interface summary

What the sorting tool puts in front of an operator

  • A folder plan previewed before anything is written
  • Numbered inspection run folders, one per detected boundary
  • An adjustable pitch tolerance, defaulting to 2°
  • An opt-in altitude-reversal fallback for flights with no marker
  • A CSV report recording why each folder was started
Read the case study
Explore freight quote automation in SingaporeAll case studies, including PSOI group products

What we build

Three kinds of system, built around one operating problem.

Each one starts as a bounded first release with written acceptance criteria, and each has a published price range.

01

Internal tools and operations software

The system your team works in every day, replacing the spreadsheet, inbox and whiteboard version of the same workflow.

  • Job tracking and operations dashboards
  • Approval, checklist and release-gate workflows
  • Internal records, scheduling and reporting
Business App / MVP: scope and price

02

AI and workflow automation

One operational workflow automated end to end, with the permission boundaries, acceptance tests and human review that make it safe to keep running.

  • Document intake, extraction and routing
  • Classification, drafting and triage with sign-off
  • Systems connected so data stops being re-keyed
AI & Workflow Automation: scope and price

03

Customer portals and custom web applications

The surface your customers use, built as production software rather than a form bolted onto a website.

  • Customer self-service portals
  • Booking, application and ordering flows
  • Web applications with accounts and permissions
Business App / MVP: scope and price
Published price ranges, with the example scope at each endExcel workflow automation for Singapore SMEsCustom internal tools for operations teamsLogistics job tracking systems

How the work runs

Built like part of your team, not a vendor you file tickets with.

The same four commitments on every engagement, whatever the size of the build.

  • One engineer scopes, builds and answers for the work — no account manager relay

  • Working software in week one, a demonstration every week after

  • Code, credentials and documentation handed over — a system another engineer could pick up

  • A clear next step on any enquiry within 48 hours

How delivery runs

Three steps from problem to production.

The same six-stage delivery, told the way it is experienced from your side.

  1. 01Step one

    Scope and acceptance criteria

    We agree the workflow in scope, the boundaries and what has to be true for the work to be accepted — in writing, before anything is built.

  2. 02Step two

    Week one, then weekly

    Build, demonstrated weekly

    Working software in the first week, then a working demonstration every week after it, so nothing is a surprise at handover.

  3. 03Step three

    Release and handover

    Acceptance testing with you, then deployment, code, credentials, documentation and training handed over — a system another engineer could pick up.

Most first releases: 2–6 weeks, depending on scope and integrations

The six stages, the checks and what happens after launch

Who you work with

Direct access to the person responsible for the work.

One engineer scopes the work, builds it and answers for it. There is no account manager relaying questions to an unnamed delivery team.

Matthew Tan

Co-founder, PSOI TECH

A Singapore-based engineer who trained in mechatronics and robotics before moving into software and unmanned systems.

Full profile and how an engagement runs

FAQ

Practical answers before you enquire.

01How quickly can a first release go live?

Most first releases are delivered in 2–6 weeks, depending on scope and integrations. That assumes a bounded first release and timely access to decision makers, content, data and any systems the build connects to. The first working walkthrough is targeted for week one, and the schedule is confirmed in writing after scoping. Larger or higher-risk products are phased rather than forced into an unsafe deadline.

02What types of projects are a good fit?

Internal tools, operations software, workflow automation, customer portals and bounded AI pilots — anything with a defined business problem, one primary workflow and an accountable decision maker.

03Who owns the code?

You do, once agreed fees are paid: the project-specific code named in the contract. Pre-existing tools, open-source software, hosted platforms and third-party services keep their own licence terms, and the agreement lists any exceptions before work begins.

04How are changes to scope handled?

The agreed scope and acceptance criteria are the baseline. A new request is either swapped for work of similar effort, moved to a later release, or written up as a change with any fee and timeline adjustment approved before it is built.

05How does payment work?

The proposal sets out the fee, the payment milestones and any third-party costs. Builds normally need an initial payment before capacity is reserved, with later payments tied to agreed stages.

Delivery questionsCommercial questions

Next step

Tell us what needs to exist.

Four fields is enough to start: your name, your email, what you need and roughly when. You will receive a clear next step within 48 hours.

Already have a defined project? Send the full brief instead

Quick enquiry

Tell us what you need

Four fields

Enough to start a useful conversation. Avoid passwords, private keys, regulated information or sensitive personal data.

You will receive a clear next step within 48 hours.

Fields marked * are required.

A couple of sentences is plenty.

By sending this message you agree that PSOI Tech may use your details to respond to your enquiry. Read the privacy notice.