The Current Way of Companies and Work Is Over
MAEUM.io stays on 24 hours a day. People will work about four hours. As the company grows, the system gets busier — and more life is returned to the humans.
You don't have to show up at the office at nine in the morning.
You can have a late breakfast with your spouse, visit your parents on a weekday afternoon, and if a child comes along, walk them to school or go with them to the hospital. If the weather is good you can go outside; you can travel for a few days. Meanwhile the company does not stop. Customers use the service, applications come in, data accumulates, automations execute, and the systems that need to run keep running. A person spends a few hours a day on the judgment and the new work that genuinely require a human, and returns to their own life. I am not saying I want to build such a company someday. I am building MAEUM this way now, and my life is already showing the possibility. I run a business, but I don't experience my life as busy. If anything, it is very unhurried. I meet people, go to cafés, wander events, travel, write, spend time with someone I love, and sometimes go out to sing. All the while I build and operate systems for multiple customers, build new products, keep changing MAEUM.io, and think up new business. From the outside, the variety of what I do might look frantic, but the reality is different. I don't hold work continuously — I concentrate when needed, build the structure, and let go. When something repeats, I don't keep processing it myself; the moment it repeats, I try to turn it into a system. So even as the work grows, my labor hours don't necessarily grow with it. This is not a hypothesis I hope to prove someday — it is a fact I am already confirming at small scale in my own life. MAEUM.io itself is the evidence. The site states that the founder personally designs and builds everything from reservations, orders, inventory, CRM, and workflow automation to AI products, and a structure that delivers a working web-app prototype in about ten minutes, free, is actually in operation. Seven products run directly by MAEUM are public on the site, and there are also services built with customers that are actually in operation. Planning, development, deployment, and operations are connected and handled by one person — and yet that one person is not sitting at a desk all day writing programs. This matters. In the old model of a company, more products, more customers, and more systems in operation should mean people get proportionally busier. I am building the company to sever that proportionality from the start. Look at MAEUM's pricing structure and what I want to sell becomes clearer. The SaaS operations tier is not “we built the program, now pay monthly.” Server and infrastructure operation, AI and automation execution, data management, error checking, changes as your work changes, continuous improvement, and proposals for new automation are all included in the operation itself. And what we check each month is not simply how many users came in. How many times automation ran, which tasks no longer needed a human, how many working hours were saved — those are the stated performance indicators. MAEUM has publicly committed to verifying what people actually stopped having to do, not to saying “we installed AI” and walking away. The direction of the company I want to build is already written into the product's own metrics. And I have no intention of building a company that applies this principle to customers but not to MAEUM itself. If we shrink working hours at customer companies through automation while the people building that automation work morning to night, the structure is contradictory. So when people join MAEUM, I think normal working hours will likely be around 20 a week. About four hours a day. Of course, on some days something important will demand more, and on days with little to do, far less. What matters is not the exact number 20 but the principle that the company's output is not measured by hours of human seat-time. In a company that judges the person who worked four hours to build a structure that eliminates a thousand future hours as having done something far bigger than the person who processed repetitive tasks for eight — the reason to demand forty hours a week from anyone steadily disappears. So I don't want to build a company that hires first whenever customer count grows. The target in my head right now: one person can be responsible for roughly 20 customer companies and still not need to work more than about four hours a day. If every added customer permanently adds one more consultation, one more report, one more check, one more data cleanup to a human's pile, you can survive to 20 customers — but at 200 you will need ten times the people. I choose the opposite direction: as customers grow, find the common problems, lift them into the product, add automation, and let the system take more of the work. Then customers increase while the kinds of work humans do directly can actually decrease. When the company grows, it should be the system that gets busier, not the people. That is the standard I keep checking as I run MAEUM. This way of working changes what company life even means. Until now we've thought of the capable worker as the one who processes a great deal of work — sends email fast, cleans data fast, answers inquiries fast, stays late to finish a lot. In an environment with AI and software, the question must change: why is a human still sending that email, why is a human still cleaning that data, why is a human still answering the same inquiry? Making today's hundred tasks cease to exist tomorrow is greater productivity than processing a hundred tasks today. MAEUM's diagnostic process is designed exactly this way — find the current workflows and the repetitive work, set automation priorities, and turn them into systems. In the end, what I do for customers and what I do inside my own company are the same: not making people work harder, but removing the work people have to keep doing. Follow this far enough and it becomes natural how I got from thoughts about family to the problem of the labor system. If I marry and have a child, I don't want to be someone who only brings home money. I want to be there when my spouse needs me, to actually exist at my child's important moments, and not to keep postponing time with my parents using work as the excuse. The time a family needs does not arrive only during company-designated vacation weeks. A child's sick day isn't booked for Friday evening, and a spouse's hard day doesn't land on the date you filed leave for in advance. What living properly with a family requires is less a number of vacation days than decision rights over your own time. And I already live with much of that decision right now. On days without appointments I can start late; if I want to see someone, I go; I can spend days in another region. I can give a day to an event, spend long hours with people, and if I suddenly want to write something new, I do. All the while MAEUM.io does not switch off. The site keeps receiving customers, the real services keep working, and the systems already built do their work whether or not I am watching. That the products on the MAEUM homepage and the real customer services stay alive is the most direct evidence that the hours I sit at a computer and the hours my company exists have already begun to separate. I want to make that separation bigger. Make what is possible in one person's life the operating mode of the whole company, and then make it possible at customer companies too. If MAEUM employees work 20 hours a week and produce enough, if MAEUM's customers stop doing what they used to repeat daily, and if those customers' employees get their own time back, then a single piece of software has done more than make one task convenient. One company's way of spending human time changes; when such companies keep multiplying, the labor structure of an industry changes. So the 20 hours I'm describing is not a welfare pitch. I'm not saying “we're a kind company, we send people home early.” That kind of policy can vanish whenever the company struggles. What I want is to build the economic and technical structure itself in which 20 hours is enough. What can run without a human runs without a human; what AI can do, AI does; and people concentrate on what only people can do — judgment, relationships, creation, responsibility. Then a person working four hours becomes not the company's sacrifice but the proof that the company is well designed. In a company built that way, strange scenes will appear. An employee having lunch with family at two on a Monday afternoon. Someone exercising midday Wednesday. Someone going to meet a friend because the weather is good. A person with a new baby spends real time with the child and still continues their work; a person in love stops postponing the relationship for the company's sake. Someone studies, someone travels, someone makes music, someone does nothing at all. And the company still moves. Customers use the service, revenue occurs, automation keeps executing, and people step in only at the moments that matter, to solve the problems that matter. The company enters a person's life a little — rather than a person's whole life entering the company. I don't want to end this with “someday, maybe.” So I make my life the evidence. I live this way first, I build MAEUM to run this way first, and I make it work for real customers. Right now MAEUM.io has products that actually work, services actually delivered to customers, offerings that operate automation and AI, and a public commitment to measure the outcome as work humans no longer had to do and hours saved. And the person running that company lives without surrendering whole days to it — meeting people, moving around, loving, thinking, making new things. It is still a small company, and whether the same structure holds at much larger scale is something I will have to keep proving. But at least at the starting point, the words, the life, and the product are already facing the same direction. So I believe the current way of companies and work is over. Handing the best eight hours of your day to the company first and solving family, love, and life with what remains; a model where growth requires feeding in ever more human time; a model where technological progress hands people ever more tasks — none of this deserves to stay the default. If AI and software genuinely raise productivity, part of that productivity must return to humans as time. And I don't intend to stop at arguing the point — I intend to build one company that works this way. MAEUM.io will stay on 24 hours a day. People will work about four hours a day. Eventually it may become four hours a week. As the company grows, the system will work more, and more life will remain for the people. Someday I hope someone looks at MAEUM and, before salary or title, thinks: here, I could work and still properly live my life. And a little more honestly — I want to live inside MAEUM.io too.