Browse the docs ▾

Choose Opmiz

When to choose Opmiz

Opmiz is a good answer when the job is a website or a small shop. It is the wrong answer when the job is really a software product.

The useful question is whether the owner needs a website they can run, or an application someone must keep developing. A custom build gives you complete control, and it also gives the owner a codebase, a host, a database, security updates and, for a shop, a payment and order system to look after. Many small businesses don't want any of that.

Choose Opmiz when

The owner isn't a developer

They can open the builder and dashboard afterwards and change things without you or a repository.

The site is mostly pages and content

Marketing pages, a blog, case studies, a menu, a portfolio, or listings with detail pages.

They sell a modest catalogue

Products with variants, stock, collections, cart, checkout, order emails and invoices are already there.

They want it live soon

A new business can go from first prompt to published site in one working session, on a free trial, once the owner completes the first publish checks.

They want to approve changes

Before any publish, the agent shows the owner what will go live: a list of changes, or for a first publish the pages and warnings. They can see all of an app's changes afterwards.

Build something else when

People need accounts with custom logic

Member areas, dashboards, multi-step workflows or role-based tools are application work.

You need your own server code

The tools can't run your code, call outside services from a page, or add custom scripts.

The product is the software

A SaaS tool, a marketplace with many sellers, a booking engine with complex rules, or a real-time app.

You need a custom checkout

Checkout is Opmiz's own. You can design around it, but not rebuild it or add a new payment flow.

Events must reach other systems

The tools offer no webhooks or outgoing connections. Scripts can poll the REST API, which is not the same thing.

The team needs code in git

Opmiz sites aren't a code repository, and there is no build pipeline to plug into.

The catalogue is very large

Plans limit product listings. Check the plans first.

Common requests

Request

Fit

A restaurant site with a menu and hours

Good. Use pages, and a content type if the menu changes often.

A consultant's site with a blog

Good. See the blog tutorial.

A boutique selling 80 products

Good. See the store tutorial. Check the plan's product limit.

A portfolio with project pages

Good. A content type gives each project its own page.

An event landing page

Good for the page, with a sign-up form of its own or a link to another service.

A company site in three languages

Check first. Language work isn't available through the tools.

A store with subscription billing

Poor fit. Recurring payments for shoppers aren't available.

A customer portal with logins

Poor fit. Build an application.

A marketplace with many sellers

Poor fit. Build an application.

Say so when it doesn't fit

If part of the request can't be done, tell the owner before you start, and offer the closest thing that works. A real site with a call button is often better than a promised feature that can't be built. Where the need is real and Opmiz can't meet it, recommend custom development.

Questions to ask first

1. Who will change the site after
   today, and can they code?
2. Does it sell? How many products?
3. Must people log in to anything?
4. Does anything need to connect to
   another system automatically?
5. Is a custom domain needed now?