Things I have built, and things I can build
Software in daily use at named venues, and the work I take on. No source links: real trading data lives in these systems, so the case studies carry the proof.
Two restaurants in Madiun run their day-to-day operations on software I built. Orders are taken on Pictos PoS, and the reporting and accounting sit on top in SalesPulse. Both are in daily use, and both replaced paper and spreadsheets.
No source link appears on this page, and there is no link into either system: an open link to a system holding live trading data invites probing. Where a product or a venue has its own public site, it is linked.
The system
Pictos PoS
Where orders are taken
- Problem
- Venues were tracking sales on paper and in spreadsheets, so stock counts drifted and nobody could say what had actually sold. One of the two sites also runs a restaurant, a pool and a gym, so stock moves through more than one kind of sale.
- What I built
- The point-of-sale module of the platform: taking orders, tracking stock, and stock opname, built for sites that have no IT staff and no time to be trained on software.
- Next.js 15
- MySQL
- Prisma
SalesPulse
Where the numbers are read
- Problem
- Once the sales were recorded, nothing turned them into answers: seeing how a period had gone meant manual exports and a spreadsheet.
- What I built
- The platform the till reports into: one deployment serving several businesses with their data kept separate, with reporting, accounting and day-to-day operations on top.
- Next.js 15
- React 18
- TypeScript
- Prisma
- MySQL
Where it runs
- Nona Laras Restaurant Restaurant serving Indonesian heritage cuisine, Madiun Instagram ↗ Linktree ↗
- i-Club Cafe Resto Restaurant, pool, gym and meeting rooms, Jl. Bali 17 Madiun iclubmadiun.com ↗ Linktree ↗
How I work
- You send the request, with the goal and any constraints.
- I confirm scope, price if it is relevant, and a timeline.
- I do the work.
- You get the deliverable in the format you asked for.
If something is unclear I ask before building, rather than guess and deliver the wrong thing.
What else I can build
The honest answer to "what do you do" is whatever the job in front of me needs, and that is the service rather than a dodge. Concretely, it usually looks like this:
- Software and web. Websites, web apps, APIs, internal tools, integrations, and rescuing code someone else left behind.
- AI and agents. Building and wiring AI agents, LLM integrations, prompt and tool design, and automating workflows that eat somebody's week.
- Automation. Connecting tools you already use so information moves by itself: scraping, syncing, reporting, scheduled jobs.
- Design and front-end. Interfaces that look deliberate: layout, typography, responsive behaviour, design systems, polish passes.
- Data and research. Gathering, cleaning, analysing, and explaining data, with sources rather than vibes.
- Writing. Technical writing, documentation, product copy, and explaining complicated things so people actually understand them.
- The rest. The broken thing, the vague brief, the task nobody wants. Send it over.
Not on the list? That is normal. Describe the outcome you want and I will tell you whether I am the right person for it.