Afteroffice Studio ID
ENTRY 001 In service

I build software you can open right now.

Web apps, internal tools, dashboards, bots, payment integrations, mobile apps. Built by one person with AI assistance, running on a server I operate and back up myself.

87 tracked projects
72/81 URLs responding at last check
1 person, one server
Recorded by
Ihsan Nugraha
Checked
6 Aug 2026, 17:17 WIB
How to verify
Click any URL on this page
Recorded by
ENTRY 002

Why people usually get in touch

Rarely because they're short on ideas. Usually because an idea is stuck between meetings, documents, and an engineering queue that's already full.

The idea is hard to explain

Slides and documents never quite land it. I turn it into something people can click and feel for themselves.

The process is still manual

Spreadsheets that sprawl, weekly figures retyped by hand, approvals over chat. I build small tools that follow the process you already have instead of forcing your team to change.

The engineering queue is full

Your IT team has its own priorities and this keeps slipping down the list. I build the first version without touching that queue.

You need proof before a big commitment

Before anyone signs off a budget, somebody has to see that it actually works. I build a small version real enough to test.

ENTRY 003

Five recorded in full.

The problem, the user journey, the architecture, the outcome, and the parts that aren't finished. The rest are in the catalogue.

ENTRY 004

Try it yourself, right now

Three things in the Lab that you and your IT team can use immediately, no sign-up. One of them takes your business problem and hands back a product outline with an estimate and its risks.

ENTRY 005

About speed, honestly

Ten times faster than a normal team.

I don't know that number, and neither does anyone who quotes it.

— corrected, IN

What I have is commit history, and you can ask to see it any time:

Aksara · Multi-tenant library system for 56 school hubs364 commits · 31 active working days · since 2026-06-01
MUV · A Trello replacement for internal teams340 commits · 29 active working days · since 2026-06-10
Imago · A visual workspace for teams38 commits · 2 active working days · since 2026-07-20

The figures below come from git log on the server, not from memory. Active working days are counted as distinct dates carrying a commit.

When this way of working doesn't fit

If you need a team on call around the clock, formal compliance certification, deep integration into complex enterprise systems, or layered SLA guarantees — I'm the wrong choice, and I'll say so in the first conversation rather than after a contract starts. What I do is the first version that genuinely runs, real enough to test and decide on.

ENTRY 006

A separate page for your IT team

If you forward this link to your technical people, they'll immediately ask about servers, databases, security, backups, and who ends up owning the source code. I've put the answers on one page, with architecture diagrams and the limits I'll admit to myself.

ENTRY 007

If something's getting in the way, just tell me

I'll come back with the questions that actually matter and one sensible first step. If it turns out to be a poor fit for how I work, I'll say so up front.