What I build
- ERP-style systems. Hexenex ERP covers catalogue, costing, quotations, purchases, inventory, sales invoices and returns, customer ledgers, payments and reports, with a NestJS and Prisma API and a Next.js web app.
- Inventory and operations. StockFlow connects purchasing, FIFO stock, sales and the supplier and customer ledgers behind them.
- School and institution systems. FaceAttend runs attendance from the timetable inside a wider school platform with students, staff, fees, exams and score cards.
- CRM and client systems. Customer, supplier and order records connected, so finances and operations tell the same story.
Build or buy?
Buy when a mainstream tool already fits 80 percent of your process. Build when the remaining 20 percent is where you make money, when you are paying for five tools that do not talk to each other, or when your data needs to stay in your hands. I wrote more about this in custom software vs SaaS.
How a project runs
- Discovery call. Free, and no technical brief needed.
- Written scope. What will be built and why, before any code.
- Architecture. Modules, data and permissions designed around your workflow.
- Build and deploy. Short cycles, automated tests where they matter, and a pipeline that ships on every merge.
- Support and improve. Agreed as part of the engagement.
What you get
- A written scope with modules, data and permissions, agreed before any code is written.
- A system designed around your workflow, shipped in useful pieces rather than one big launch.
- A clear data model you own, with exports you control.
- An automated pipeline that builds, checks and deploys every change.
- Documentation for the people who use it and the people who maintain it.
