Nuto — Software Engineering & Business Solutions

01 — Work

Selected Projects

Systems I have built that are in real use. All were delivered for the company I work at, so company names and internal details stay confidential — my role on each is stated on the card, and the problem and the approach can be discussed in more detail.

Maintenance 832+ requests a month

Maintenance Request System

Role: Sole developer — database design through to production.
Problem: Repair requests arrived by phone, chat, and paper forms, so nobody could tell which jobs were still open, who owned them, or whether they had been closed.
Approach: One place to submit a request, with clear status, assignee, photo attachments, notifications, and a per-asset history of what was repaired and when. The system takes an average of more than 832 requests a month.
Tech: VueNestJSPostgreSQL

Property SaaS product

Dormitory Management System

Role: Team of two — I designed the architecture and chose the stack.
Problem: Tenants, contracts, rent, utility meter readings, and room availability were tracked separately, and every month the charges were calculated and chased by hand.
Approach: Rooms, tenants, contracts, and meter readings in one system, with monthly charges calculated automatically, invoices issued from that data, payment status tracked, and occupancy visible at a glance. Built as a SaaS product serving multiple properties from one platform.
Tech: NuxtNestJSPostgreSQLDocker

Integration Microsoft Dynamics 365

ERP System Integration

Role: Sole developer — sync design through to production.
Problem: An operational system and Microsoft Dynamics 365 held the same data, so it had to be entered twice — and when the two disagreed, there was no way to find where it went wrong.
Approach: A synchronization service between the operational system and Dynamics 365, with explicit data ownership on each side, retry handling when a transfer fails, and a log of every record moved so any mismatch can be traced.
Tech: Microsoft Dynamics 365REST APIWebhookNode.js

Billing 200+ users a day

Billing System

Role: Sole developer, end to end.
Problem: Billing ran on separate Excel files. Data was re-typed from purchase orders and delivery notes, and tracking which bills had been issued or paid was manual work.
Approach: Bills generated from data already in the system, organised into billing cycles, with each bill carrying a status from prepared to issued to paid, plus an outstanding-receivables report. Supports more than 200 users a day.
Tech: NuxtNestJSPostgreSQL

02 — Sound familiar?

Have a Problem With Your Software or Business Process?

You do not need to describe it in technical terms.

Your team spends too much time on Excel, repetitive data entry, or manual processes.

Your application or API is slow, unstable, or difficult to maintain.

Your systems cannot communicate, or data is copied manually between them.

Your business needs a system that does not fit standard off-the-shelf software.

Your application works locally but is difficult to deploy or maintain in production.

You know the problem, but you are not sure what solution is needed. That is a normal place to start.

03 — Services

Four Areas of Work

01

Business Systems

Systems built around the way your business actually works.

Internal applications
Workflow & approval
Sales & inventory systems
Reporting dashboards
Custom business applications

02

ERP & Integration

Experience with ERP systems and complex business workflows.

ERP integration
API integration
Data synchronization
Custom workflows
ERP reporting

03

Technical Problem Solving

Find the root cause, not just the symptom.

Slow API & database queries
High server resource usage
System architecture
Performance optimization
Production troubleshooting

04

Infrastructure & Deployment

From development to production.

VPS setup · Docker · Nginx
SSL & domain
CI/CD
Server migration
Backup & monitoring

Technical capability Node.jsNestJSExpress.jsVueNuxtNext.jsVuetifyPostgreSQLSQL ServerDockerNginxVPSREST APIWebhook

Performance work starts with investigation. I investigate performance problems and identify practical improvements — no fixed promises before the system has been reviewed.

04 — Background

Business & ERP Experience

Software should fit the way a business works. My experience working with ERP systems has given me practical understanding of the business processes behind them.

That means a conversation can start with your process and your constraints — not with a list of technologies.

Modules worked with

01

Inventories

Stock movement, warehouse operations, and inventory accuracy.

02

Accounting

How transactions from operations land in the accounts.

03

Report

ERP reporting and the numbers each team needs to see.

04

Planning

Demand, purchasing, and production planning workflows.

05

Manufacturing

Production orders, routing, and shop-floor data.

06

Asset

Asset registers, maintenance history, and asset lifecycle.

Also Sales Purchasing Warehouse Operations Workflow & Approval

05 — How I work

A Clear Sequence, From Problem to Production

Each step has an output you can review before the next one starts.

01

Understand

The business problem and current process.

02

Analyze

Requirements, constraints, root causes.

03

Design

A practical solution for the actual requirements.

04

Build

Develop and integrate the solution.

05

Deploy

Into the appropriate environment.

06

Support

Support and improvements when needed.

06 — How I take on work

No Guesswork.
No Overpromising.

I believe good software starts with understanding the problem first.

Before development begins, requirements, scope, technical complexity, and expected outcomes are discussed clearly.

If something is outside what I can do well, you will hear it before the work begins — not after.

Scope

Agreed before we start

Requirements, price, and delivery date written down before any code is written.

Contact

You work with me directly

No account manager in between. The person you talk to is the person building it.

Limits

Limits named up front

If a project is beyond what I can deliver alone, you hear it in the first conversation — along with which part I would take, or who should be added.

Most work I do myself. When a project needs more hands, I bring in people I have worked with and trust — and you hear who and why before the work starts, not after.

07 — About

Hi, I'm Nu.

I build software for businesses — internal systems, integrations, and the unglamorous parts that make a process actually work.

So far that has meant a maintenance system taking over eight hundred repair requests a month, a billing system supporting more than two hundred users a day, a dormitory platform running as SaaS, and an integration between an operational system and Microsoft Dynamics 365 — most of them built alone, from the first design through to production.

I work directly with the people who will use the system, I want to understand the problem before writing any code, and I would rather tell you something is out of scope than take the work and hope.

— Nu

08 — FAQ

Questions Clients Usually Ask

Do you work alone?

Yes. Nuto is one engineer, and the person you talk to is the person who writes the code. For work that needs more hands, I bring in people I have worked with before, and you are told who and why before anything starts.

Do you have a full-time job as well?

Yes. I work as a programmer at a company and take on outside projects only in time I can genuinely commit — calls and meetings on weekday evenings and at weekends. I keep few projects running at once so each gets proper attention, and if the schedule is full I say so at the first conversation.

Can you handle large projects?

It is evaluated on scope, complexity, and timeline first. Work I can deliver alone, I do alone. For anything larger, I can bring in people I have worked with and trust — and you will know who is doing what before the start, rather than the work being accepted first and staffed later.

How is pricing worked out, and can it be split?

Priced per project from the agreed scope — never a figure quoted before the problem is understood. Payment is normally split into stages: a deposit at the start and the rest as each part is delivered. The figures and the stages are written down before any work begins.

Is there a contract or a written scope?

Yes. Before work starts there is a document setting out scope, deliverables, price, payment stages, and timeline, so both sides have the same reference. If something comes up beyond what was agreed, it is discussed first — never added quietly at the end.

Who owns the source code?

You do. Once payment is complete as agreed, the code and the right to use it, change it, or hand it to someone else are entirely yours. The repository and the documentation needed to maintain it are handed over with it.

Do you only work with ERP?

No. ERP experience helps in understanding complex business processes, but Nuto also works on custom software, automation, integrations, performance, and infrastructure.

Can you fix an existing system?

Yes. Existing systems can be reviewed to identify technical problems, performance issues, or areas that need improvement.

Can you deploy the system?

Yes. Deployment support can include VPS, Docker, Nginx, SSL, CI/CD, and production setup.

09 — Contact

Have a Problem? Let's Talk.

You do not need to know exactly what technology you need. Tell me what you are trying to improve, and we can discuss a practical approach.

A short conversation about the problem and the current process.

An honest view of scope, complexity, and what is realistic.

A proposed approach — including who would be involved.

When we can talk

I currently hold a full-time job, so calls and meetings work best on weekday evenings and at weekends — which is usually when business owners have time anyway.

Budget

Projects usually start from 30,000 THB

The real figure comes after the scope conversation — no number is quoted before the problem is understood.

Prefer to write directly?

hello@nuto.dev