My first three professional years were in an office in Taiwan, building web applications for an enterprise software company. Digital transformation on the brochure. Approval chains in the hallway.

That combination matters if you have only worked at startups or solo. Software does not leave your laptop and land in production because it compiles. It passes through people who were not in the sprint review.

"Small change" is a sentence, not a size

I once watched a one-line copy update travel through product, compliance, and operations before it could go live. Nobody was being difficult on purpose. Each group protected something real: customer trust, audit trails, staff workflows that break if the wording shifts.

Enterprise web work taught me to scope for the organization, not for the diff. If three teams touch the form, the project is bigger than the form.

CMS and internal tools are where staff live

Not every enterprise project is a customer-facing splash screen. A lot of the value is the internal tool the operations team uses forty times a day, or the content platform marketing relies on when a regulation changes.

Those systems fail quietly. The UI is ugly but "fine." Then the one person who knew the workaround is on leave, and everyone remembers the software exists.

Building for that reality means clearer permissions, saner defaults, and error messages a non-engineer can act on.

In-person collaboration has a different texture

I am remote now, but I am glad I started in an office. I saw who actually signs deploy requests. I heard the questions QA asks that never make it into a ticket. I learned when to walk over to someone's desk instead of sending another chat message.

Remote work did not erase those lessons. It made me deliberate about recreating them in writing: decision logs, explicit owners, screenshots when words are not enough.

Why this still matters to small clients

Business owners are not banks, but they have their own version of approval chains. The spouse who handles invoices. The manager who will not use a tool if it adds one more login. The staff member who will keep using Excel unless the new app is obviously safer.

Enterprise years trained me to look for those humans early. Custom software succeeds when it fits how the business already decides - not when it wins a architecture debate in isolation.