Index cards with handwritten notes sorted into three piles on a kitchen table

FIELD GUIDE Choosing a web platform

Choose the platform
around the work.

Who edits it. What connects to it. Who looks after it. Those decisions tell you more than a list of platform names.

Platform guide / ORYNX AXIOMUpdated September 2026

The brief before the tool

Six questions
to answer first.

They decide more than any feature list.

The customer task

What does someone need to find, understand or complete? Name the important journeys before listing features.

What you post and update

What changes regularly, and what information has a structure? Pages, projects, products and bookings have different needs.

The editing team

Who updates content, who reviews it and what must stay protected? Editing a paragraph is not the same as changing a layout or access policy.

The connections

What needs to read or write business records? Identify existing systems, authorized access and who owns each field.

Who keeps it running

Who manages updates, backups, accounts and failures? A platform decision includes the work that continues after launch.

Can you take it with you?

What needs to be exportable, maintainable or transferable? Files, account control and software licenses are separate questions.

Editing and responsibility

The design and the editor
are separate choices.

A laptop open to a content editor beside a monitor showing the published page
The editor on the laptop, the published page on the monitor.

A site can have a highly individual design and still use an established content platform. The important question is what your team can change, how that content is structured and what happens before publication.

Try a representative task with the people who will do the work: edit an introduction, replace a project image, update a product detail and preview the result. Review permissions and recovery as well as the happy path.

Three project situations

Three common
situations.

Pick the one closest to yours and compare these first.

Independent architectural website direction
Editorial website

01 / EXAMPLE

An editorial company website

A small team publishes services and project stories. Its existing platform may remain useful even when the visual identity changes.

Start the comparison with: content types, image handling, preview, permissions and maintenance.

Illustrative product collection
Product catalog

02 / EXAMPLE

A substantial product catalog

The storefront needs more than attractive category pages. Product options, search, inventory and the systems behind the order shape the implementation.

Start the comparison with: product structure, transaction rules, authorized data connections and operating cost.

A project handover book and checklist on a studio desk
Shared workflow

03 / EXAMPLE

A shared business workflow

Different people need to work with records, permissions and changing task states. A page builder cannot describe that application.

Start the comparison with: roles, validation, record ownership, failure recovery and ongoing technical responsibility.

What to compare

What to ask
each platform.

Question Ask each option to show Keep in the decision record
Design freedom A relevant page and interaction, not only a theme gallery. What is configured, customized or constrained.
Content and commerce Your representative content or product model. Required modules, custom work and limitations.
Connected systems The actual access and integration route. Field ownership, update behavior and failure handling.
Continuing cost The build plus recurring operating requirements. Hosting, licenses, apps, support and further development.
Portability An explanation of exports and dependencies. Files, accounts, formats, licenses and migration work.

Named platforms

Where each platform fits,
and where it doesn't.

Use this after the six questions above, not instead of them. Use it to start the conversation.

PlatformFits well whenCheck before you commit
WordPressThe site is mostly content, your team edits often, and a large choice of plugins helps.Every plugin adds updates and security work. Decide who maintains the site before it launches.
ShopifyA retail store that wants hosting, security and checkout handled by the platform.Monthly apps add up, and payment providers other than Shopify Payments carry an added Shopify fee. The theme runs only on Shopify.
WooCommerceA store inside an existing WordPress site, or checkout rules a hosted platform does not support.You run the hosting, updates and security. Card-data compliance is the store owner's responsibility.
BigCommerceLarger or B2B catalogs that need built-in catalog depth without running your own servers.Since June 2026, payment providers outside BigCommerce's embedded list carry a monthly platform fee on self-serve plans.
Magento Open Source / Adobe CommerceVery large catalogs, complex pricing and deep integrations, with a team to operate it.It needs specialist hosting and a developer on call, and upgrades are ongoing work.
Custom buildThe design, speed or a specific workflow matters more than a plugin catalog.Plan editing from the start, through NXT Lab CMS or another content system, so your team is not waiting on a developer for routine changes.

Website builders

Website builders:
know the limits.

A hosted builder is a sensible choice for a placeholder, a short campaign or a first version. Check these limits before the site has to rank, sell or move.

BuilderThe limit to check
WixThe site runs only on Wix. You can export some data, such as CMS collections, but not a working site to host somewhere else.
SquarespaceExport produces a WordPress-compatible file with basic pages and blog posts. Store, portfolio and several other page types stay behind, and so does the design.
GoDaddy AiroAI drafts the pages and copy quickly. Rewrite the copy for your business, and get in writing what you can export before you build on it.
CanvaContact forms come from embedded third-party tools; Canva has no built-in form. A custom domain needs a paid plan.
Figma SitesPaid plans add custom domains, page titles and descriptions, and a CMS in beta. Figma hosts the published site, so confirm your export options before you plan a future move.

What local businesses actually use

In our 2026 study of 490 local service businesses, about 75 percent ran a do-it-yourself builder or WordPress. In 10 of 14 categories, at least two-thirds did.

Keep the domain yours

Whichever builder you choose, register the domain in your own business name. It is the one piece that should always move with you.

Outgrowing a builder

When the site needs to rank, sell or connect to other systems, plan the move early. Content, redirects and the domain are what carry over.

Put the questions to work

Write the brief
before picking a platform.

You do not need to arrive with a technical solution. Start with the people, information and current systems the website needs to support.

Illustrative project materials
Good questions.
A clearer starting point.

Pick your answers, then send them with your quote request.

Your platform

Ready for
ORYNX AXIOM?

Bring the requirements. We can work through the implementation.

ORYNX AXIOM

Site navigation

Find a service

ORYNX AXIOM

contact@orynxaxiom.com
ORYNX AXIOM

More information