With AI, anyone can build a Power Pages portal fast, and it keeps telling you it's going well. What it won't tell you is whether the architecture underneath actually holds. Three real, anonymized examples of decisions that looked fine at build time, and got expensive later.
AI Validates That the Code Runs, Not That the Architecture Holds
The fast part is AI's job. Ask it to build a document upload, a customer record, a page that remembers a selection, and it delivers working code, every time. What AI checks is whether the request compiles and runs. It doesn't check whether the underlying architecture survives contact with real usage six months from now. That gap is where the following three examples come from.
Storage: The Demo File Was Two Pages
Document upload worked fine in the demo, a two-page PDF, done, AI called it solid. Three weeks before go-live, someone uploaded a 500 MB technical drawing, and the storage choice made on day one couldn't hold it. Not a setting to change anymore. A different architecture, built under deadline pressure.
The pattern: AI validates that the code runs. It doesn't ask how big your real files will get.
Data Model: AI Shipped It, Not Customer Seven
Customer one onboarded smoothly, AI shipped the feature, everyone moved on. Customer seven onboarded by recreating the same five records from scratch, because the data model was built for one customer, not many. What should be a lookup into a shared structure became a re-entry, every single time.
The pattern: working code isn't the same as a model that scales past customer one.
UI Context: AI Built the Page Exactly as Asked
A user picked the item they were working on. Two clicks later, they were picking it again, the app had forgotten. Nobody had asked AI to carry that choice across pages, so it didn't. So the user carries it, in their head, on every single screen.
None of these are bugs. AI didn't get anything wrong either. They're architecture decisions nobody made on purpose, at kickoff, before AI ever entered the picture. AI will never flag the one you skipped, because skipping it doesn't break the code. It just breaks later, usually right when it's already expensive to undo.
The Fast Part Is AI's Job. The Right Part Is Mine.
An Architecture Workshop maps exactly these gaps before a single Power Pages table gets built: data model, roles, authentication, integrations, licensing. Two structured sessions, one prioritized roadmap.
Book Free Consultation