Jianguo Zhuang

Hey PH community, Jianguo here.

Over the past few months, my team and I have been building ObjectStack, and we hit a major realization about AI and software architecture.

80% of enterprise SaaS (like vertical CRMs or PSA tools) is just forms, tables, workflows, and permissions. When we try to let AI agents write raw code for these, they eventually break the logic or create a mess of unmaintainable legacy code.

We took a different approach: Everything is Metadata. By abstracting the entire application layer into structured metadata, the entire context stays extremely lightweight (well under 150k tokens). Now, our AI engine (ObjectOS) doesn't write code; it manipulates the metadata. The result? Instant application generation with strict data isolation and zero runtime syntax errors.

Let s be brutally honest for a second: Everyone hates forms.

As product builders, we spend countless hours obsessing over UI/UX, tweaking dropdowns, optimizing multi-step wizards, and adding helpful tooltips. But the reality in the B2B world especially for sales reps and field workers is that data entry is universally despised. No matter how "beautiful" your CRM interface is, your users will still take notes in their native notes app or send themselves a Slack message, only to begrudgingly do batch data entry at the end of the month (often faking half of it just to get management off their backs).

For a long time, the industry's answer to this was just better UI. Recently, the trend is slapping an LLM chatbot wrapper on top of a legacy system. But the underlying architecture is still strictly form-driven. The AI is just a polite receptionist for a rigid database.

While building our next-gen platform, we realized that to truly fix this, we had to stop fighting human nature. We decided to kill the form entirely.