Services
Any ERP module built to order, complete custom ERP systems, and the bespoke pieces around the edges — a screen nobody else has, an integration with a system only you use, a report only your finance team wants.
Seven modules already written and running in production. Configured for your branches, roles and formats rather than built from scratch.
Any module an ERP needs, built to your process — or the complete system where nothing off the shelf matches how you run.
Internal platforms and customer portals built to your process, rather than your process bent around off-the-shelf software.
One codebase for Android and iOS, built as a companion to the web portal so both sides always show the same data.
Company websites, product pages and landing pages — built to load fast, read well on a phone and be found on Google.
This site is one of them. Designed, written and built here — no template, no page-builder. What you are looking at is the standard.
The part most people forget. Domain, hosting, SSL and updates looked after, so the site does not quietly break or expire.
Connecting the software you already pay for, so data moves once instead of being retyped between departments.
SQL-backed reports over your real data, refreshed on a schedule, so the number in the meeting matches the number in the system.
Not every process justifies a portal yet. Dashboards and forms built directly onto the Google Sheets your team already uses.
Getting years of history out of the old system and into the new one, without losing the parts finance depends on.
Set up properly on your own cloud account, so nothing critical lives on a machine you do not control.
Software is not finished at go-live. Fixes, small changes and monitoring on a monthly or annual arrangement — optional, never a condition of the build.
Process
Not a year-long build with a reveal at the end. One module into production first — it earns trust, and it makes the next one easier.
I ask to watch the person who actually does the job. The register, the group chat, the workaround nobody mentions in meetings — the real rules are always in there.
Screens, scope and a delivery plan in writing before development starts, so cost and sequence are agreed rather than assumed.
Into production, used by real staff. Every release is verified on the live server afterwards, with a timestamped backup kept for instant rollback.
Your server, your database, your source code, documented. Support if you want it — but you are never stuck with me to keep the lights on.
How to start
Which one fits depends on how close your process is to something already built.
Pick a module, I configure it for your branches, roles and formats, and deploy it on your server.
Start from an existing module and change what does not match — extra fields, a different approval chain, your own reports.
Your process is genuinely different. Built from scratch, one working module into production first, then the next.
Technology
Mature, well-supported tools — so whoever inherits your system in five years can still maintain it.
You do not need a specification. Describe how the work gets done today and where it hurts — that is enough for a first conversation.
