Build a website
- 01Choose a theme
- 02Add pages
- 03Install plugins
- 04Add content
- 05Publish
Build a SaaS for your market: customize its pages, data, workflows, permissions, and branding, then offer it to customer organizations under your own name. Start with the professional page foundation or an available published template. BuildWithHQ provides the shared application capabilities and tenant administration underneath.
FieldOps shows how a vertical SaaS can bring work orders, crew scheduling, maps, customer records and operational reporting into one branded product.
WordPress did not eliminate developers. It eliminated the need to hand-build the same foundation every time. BuildWithHQ applies that principle to SaaS: the recurring platform work lives underneath, while builders focus on the product, workflow, market and customer experience.
A website page displays information. A SaaS page displays information and does work.
Add scheduling, availability, resources and appointments.
Add approvals, automations, queues, notifications and jobs.
Add permission-aware knowledge, assistants, retrieval and actions.
Connect APIs, webhooks and outside systems—or your own services.
Customer. Property. Claim. Patient. Reservation. Vehicle. Contract. Work Order. BuildWithHQ lets the vocabulary and relationships of the business become the structure of the application.
One SaaS is your product. A tenant account is a customer organization inside it, and a tenant user is a person in that organization. Each SaaS has its own databases; organizations within it are separated by server-enforced permissions. Page design never grants access to another organization's records.
A click does not have to mean “open a page.” It can run a governed server-side action chain that validates, saves, integrates, communicates and records what happened.
Build the application, define plans, invite customers and turn the software itself into recurring revenue.
Deliver the project → charge hosting → charge maintenance → find another customer.
Build the product → sell it repeatedly → charge monthly subscriptions → grow recurring revenue.
A BuildWithHQ template is a starting application—not a cage. Pull it into your private application, then change the fields, workflows, data model, APIs, UI, permissions and branding until it becomes your product.
WordPress stayed useful because developers could go deeper. BuildWithHQ follows the same principle: work visually, edit structured JSON, connect APIs, or build custom services in the isolated code layer.
Explore the architecture →
Domain → Theme → Pages → Content → Publish
Domain → Template → Data → Logic → Users → Pricing → Publish
You concentrate on the part no platform can invent for you: your market insight and product idea.
It is a SaaS application platform built around the same principle that made WordPress successful: assemble first, customize second, code only when necessary. The comparison explains the experience—not the underlying architecture.
Start with a working foundation. Make it yours. Publish software under your own brand.
Compose React pages in the Puck page designer, configure themes, assets, menus and User Types, and publish a reviewed page version. User Types select the experience; DataRoles and Locations control access to business records. A saved draft is separate from the version customers see.
Read the guideUse the enabled app modules for contacts, organizations, work orders, tasks, checklists, conversations, files and knowledge. Availability and allowed create, view, edit and removal actions depend on the published app, entitlement and your permissions. Search and activity views lead back to the native record; removal may archive or deactivate records to preserve history.
Read the guideUniversal Inbox brings work needing attention into one place while conversations, form submissions and business records remain their original sources. Refresh a changed item before approving an action. GoClaw research and planning are read-only; material changes require the configured approval policy and permission for the specific action.
Read the guideUse the current generated OpenAPI reference and versioned Developer Kit for headless apps, typed clients, webhooks and supported MCP tools. Keep app credentials on a trusted server. Delegated user identity, scopes and action permissions still apply. Sensitive MCP tools require app-level approval; installing an MCP client does not grant write access.
Read the guideChat rooms and messages require current room membership as well as DataRole and location access, including when opened through Graph, Activity or Favorites. Find them in native Chat Rooms search; general and AI search exclude chat content. Administrators add eligible members, and saves check current authority again. Room removal preserves history through soft deletion; an authorized restore does not revive independently removed messages.
Read the guide