Why Everyone Here
Is a Director.

We are a small team, and on paper, small teams usually reach for small titles. A founder, a couple of leads, maybe a head of this or that once the team grows past a handful of people. We went a different way. Every senior person here carries the title director, and we picked that word on purpose.

Not directors of departments

In most companies, a director sits above a department. They manage people, budgets, and quarterly plans. That is not what the word means here, mostly because we do not have departments to manage in that sense. Nobody at Sealution holds a title just to have one.

Instead, each director owns a specific part of how the platform actually behaves. Not a slice of the org chart. A slice of the system itself.

We are not directors in the usual sense. We are directors because we direct how this system works.

Four people, four directions

Unggul Kirindi is our founder and lead architect, and he directs Architecture and Routes. He owns how the platform is built underneath, and how the route engine decides what a real sea route between two ports actually looks like. When a route comes back wrong, unusually long, or blocked by land that should not be there, that is his problem to solve. We have written at length about exactly how seriously he takes it, down to the individual bugs.

Dimas Raja is our Creative Director, and he directs Experience and Design. His job is not making screens look impressive in a pitch deck. It is making sure a captain who has never used software like this before can open the app on a moving vessel and know what to do immediately. That means saying no to design trends that look good in a screenshot but do not survive contact with someone standing on a rocking deck with one hand free. It also means the platform keeps looking like what it actually is, a serious tool for serious operators, not a generic dashboard that could belong to any company. Every screen an admin, a captain, or a customer opens carries his judgment on what belongs there and what does not.

Yuniar Dwi is our Safety Director, and she directs Safety and Rules. Safety here does not mean physical safety at sea. That is still the captain's call, always. It means who can see what inside the system, what gets logged the moment someone touches a record, and what happens when someone tries to do something their role should not allow. Every action inside the platform leaves a trail, admin accounts sit behind two factor authentication, and permissions are set per role rather than handed out by default. If a client ever asks why their finance records are not visible from a driver's login, the honest answer is that Yuniar decided that boundary on purpose. Nobody just forgot to think about it.

Vielbert Victorio is our Customer Director, and he directs Market and Numbers. Pricing, currencies, tax rules, and what the business needs the platform to prove before anything ships, that is his territory on paper. In practice, a good part of his job is noticing a real problem before the market has a name for it yet. An operator does not usually walk in and ask for a feature by its technical description. They describe a headache. Vielbert's job is recognizing that headache early enough that we can build the actual fix before it becomes a common complaint, ship it fast and reasonably accurate the first time, then use what real clients tell us once they are using it to sharpen it further. That is how a corporate booking flow built for one client's specific mess ended up shipping with every SEALUTION installation.

Four people, four clear directions, one system that has to work as a whole when you put all four together.

Why it matters when you call

The practical upside of this structure shows up the moment a client actually needs help. There is no support queue routing your question through three people before it reaches someone who understands it. You call, and the person who answers usually already knows the exact feature you are asking about, because it likely runs through their part of the system.

That would be hard to promise in a company with fifty engineers and a normal management chain. It is easy to promise when there are four directors and each of them can tell you, in detail, why a feature works the way it does.

Small on purpose

We are not trying to become a large company that eventually needs departments and the titles that come with them. We are trying to stay the right size for the operators we serve, people who want a real answer from someone who actually built the thing they are asking about.

Being small was a choice, not a stage we are passing through. The director title is just the plainest way we found to say that out loud.