Master architecture-review

I’m looking for an independent technical review of an MVP architecture and a developer’s proposed change in direction.

This is not intended to become a conventional equipment-listing website. The initial product is Equip-Ex, a marketplace and transaction-intake layer for industrial equipment. Over time, the same underlying system is intended to support broader infrastructure opportunity routing through Power-Ex / Energy Exchange.

The operating principle is:

Thin public-facing applications connected to a shared, durable operational spine.

Proposed MVP stack:

• WordPress for the public website, content management, SEO, landing pages, knowledge base, and initial marketplace/directory functions
• GeoDirectory and potentially WooCommerce for mature listing, account, search, and transaction functionality
• Base44 for rapid prototypes, workflow validation, and selected internal interfaces
• Zoho CRM and Zoho Inventory as operational systems of record
• Zoho Creator where specialized operational applications are required
• n8n as the orchestration layer connecting forms, websites, CRM, inventory, communications, enrichment, and external services
• Cloudflare for domains, DNS, security, routing, and related infrastructure
• Google Workspace for business identity and communications
• Instantly for the separate outbound-email operation
• APIs and webhooks used to prevent the website from becoming the system of record

The initial MVP does not need to be the final version of the entire platform. It needs to:

1. Publish equipment and opportunity listings
2. Capture seller, buyer, project, site, and partner inquiries
3. Route each submission into the correct workflow
4. Create or update the appropriate CRM records
5. support controlled document and image handling
6. Track opportunity status and ownership
7. Produce a credible public-facing experience
8. Remain understandable and maintainable by future developers
9. Generate commercial activity before the larger platform is built

The developer moved toward a custom Next.js implementation and characterized WordPress as legacy. My concern is not that Next.js is inherently wrong. My concern is that the architectural change appears to replace a deliberately modular MVP with a custom application before the business workflows have been proven.

A custom Next.js system may require us to build or select replacements for:

• Content management
• Administrative interfaces
• Listings and directory management
• User accounts and permissions
• Search and filtering
• Form management
• Media handling
• SEO controls
• Marketplace functions
• Plugin-provided capabilities
• CRM and inventory synchronization
• Documentation and nondeveloper administration

I have not yet seen a clear architecture decision record showing:

• Which verified requirement WordPress cannot satisfy
• Which component Next.js is replacing
• The expected difference in development time and cost
• The ongoing maintenance burden
• The proposed source of truth for each data object
• How n8n, Zoho, Cloudflare, Workspace, and Instantly fit into the new architecture
• What portion of the system becomes dependent on the original developer
• What measurable MVP outcome becomes easier or faster

I am not looking for “WordPress good” or “Next.js good” answers.

I would appreciate opinions on these questions:

1. Does the modular stack make sense for an early commercial MVP?
2. What concrete requirements would justify moving the public application to Next.js now?
3. Would you use WordPress as the public shell while keeping Zoho as the operational source of truth?
4. Is n8n appropriate as the integration and orchestration layer at this stage?
5. Which architectural documents should a developer provide before changing the agreed stack?
6. What acceptance tests would you require before approving the build?
7. Is the proposed custom architecture solving a demonstrated limitation, or introducing premature complexity?

I’m especially interested in responses from developers who have built marketplaces, directories, CRM-connected platforms, or systems that began as modular MVPs and were later hardened into custom applications.