Services
What I actually do.
Four kinds of work, all of them coming from the experience listed on the history page. Pick whichever is closest to your problem.
Business Systems
Turning manual work into a system people actually use daily.
Who it is for: Businesses still tracking orders or stock in chat threads and spreadsheets.
- Mapping the workflow as it runs today, including where it gets stuck.
- Writing the requirement list before any code is written.
- Building the system: data, admin interface, and order flow.
- Testing it against real working conditions, not just the smooth path.
Evidence: Mafia Blox runs in production; the Rollerskool BRD was used as the development baseline.
More about Business SystemsWeb & Landing Pages
A website whose content you can edit yourself.
Who it is for: Anyone who needs an online presence without calling a developer for every text change.
- Designing the interface from scratch, shaped by your content — not an off-the-shelf template.
- Building frontend and backend together.
- Adding an admin panel so content can be updated in-house.
- Keeping it fast and readable on phones.
Evidence: The Tasty Food landing page and admin panel, built with Laravel during an internship at Cyberlabs.
More about Web & Landing PagesAnalysis & Documentation
Writing down the requirements before they become expensive.
Who it is for: Teams that keep adding features nobody ends up using.
- Interviewing users and mapping the current process.
- Writing a functional requirements document (BRD).
- Setting priorities: what ships first, and why.
- Handing over a document a development team can work from directly.
Evidence: The Rollerskool system BRD at PT. Fath Synergy Group.
More about Analysis & DocumentationBots & Automation
Taking over repetitive work so nobody does it by hand.
Who it is for: Work that repeats the same steps every day.
- Finding which steps are worth automating — and which are not.
- Building the bot or script that takes them over.
- Connecting it to the services you already use.
- Handing over notes on how to run it and fix it.
Evidence: Discord bots and automation scripts, built since before university.
More about Bots & AutomationNot everything needs software
When I tell you not to build an app.
When the problem is one step
Three people editing one file and copy-pasting the wrong version? That is solved with one template and a naming rule. No application needed.
When nobody wants to use it
Software only helps if people are willing to leave the old way behind. If they are not, I say so up front instead of building something that gets abandoned.
Why me
I graduated from a vocational school in Software Engineering, and I am now studying Information Systems. That puts me on both sides: writing code, and tidying the business process behind it. The second one is usually what decides whether the software gets used at all.
More about me
Ready when you are
Tell me how the work runs today.
If it turns out a new app is not the answer, I will say so. Not every problem needs software.