Before you configure your workspace, it helps to understand how Qwoty is structured. This page walks you through the five domains that make up the platform and how they connect across the quote-to-revenue flow.Documentation Index
Fetch the complete documentation index at: https://docs.qwoty.io/llms.txt
Use this file to discover all available pages before exploring further.
You don’t need to know every entity to start using Qwoty. This page is for admins and technical leads who want to model their business correctly from day one.
The five domains
Qwoty’s data model is organized around five functional domains. Each domain owns a set of entities, and together they form the backbone of every deal you run.Workspace & users
Your organization, teams, users, and the settings that apply everywhere: currencies, taxes, languages.
Catalog & pricing
What you sell and how you price it: products, catalogs, bundles, pricebooks, discounts.
Customers
Companies you sell to and the people inside them: accounts, contacts, addresses.
Template & sales configuration
How a quote is pre-configured: templates, payment terms, contracts, approval workflows.
Sales cycle
The deal itself: quotes, line items, dealrooms.
How the domains connect
Here’s a simplified view of how data flows from your workspace setup all the way to a signed deal.Key relationships to remember
Four relationships drive almost everything in Qwoty: A Template bundles your sales configuration. When a sales rep creates a new quote, the Template they pick pre-configures the Catalog, Pricebook, Payment terms, Contract, Approval workflow, and Discount rules. One click replaces dozens of manual selections. A Customer can own its own Catalogs, Pricebooks, and Templates. If you set these directly on a Customer (or a Customer segment), Qwoty will use them first and fall back to the Template defaults only if nothing is defined. This gives you per-client pricing and branding without duplicating anything. A Quote is composed of Line items. Each Line item links to one Product and one Price. The Price comes from the Pricebook selected at quote creation — if the product has no price in that pricebook, Qwoty falls back to the default pricebook. A Dealroom is the customer-facing view of a Quote. Publishing a quote to a Dealroom is what makes it visible, commentable, and signable by the buyer. One Quote has one Dealroom.Explore each domain
Workspace & users
The Workspace is the top-level container for everything in Qwoty. It defines the currencies you operate in, the taxes you apply, and the languages your data can be translated to. Users are grouped into Teams, and optionally split into Business units when your company has multiple entities.| Entity | Description |
|---|---|
| Workspace | Your Qwoty instance — all data lives here |
| BusinessUnit | Separate entity within your organization (optional) |
| Users | People who log in and work in Qwoty |
| Teams | Groups of users (Sales, Ops, Finance…) |
| Language | Available locales for translations |
| Currency | Currencies you accept on quotes and orders |
| Taxes | Tax rates you apply (VAT, sales tax…) |
Catalog & pricing
This domain describes what you sell and at what price. A Catalog groups your Products and Bundles. Each Product has one or more Prices, organized into Pricebooks — one Pricebook per customer segment or geography. A Bundle is a ready-made package of multiple Products sold as a single unit. Discounts can be applied on top of any price.| Entity | Description |
|---|---|
| Catalog | Group of Products and Bundles available to sell |
| Products | What you sell (goods, services, subscriptions) |
| Bundle | Package of multiple Products sold together as one unit |
| Pricebook | Price list for a segment, geography, or customer |
| Price | A Product’s price in a specific Pricebook |
| Discount | Price reduction rule applied to one or more Products |
Product variants exist as a feature in Qwoty but are not yet represented as a separate entity in this model. A variant is stored as a Product with shared parent metadata.
Customers
Customers are the companies you sell to. Each Customer has one or more Contacts (the people you email and invite to Dealrooms), plus billing and shipping addresses used on quotes and orders.| Entity | Description |
|---|---|
| Customer | The company you sell to |
| Contact | An individual at the customer |
| Billing address | Where invoices are sent |
| Shipping address | Where products are delivered |
Template & sales configuration
A Template is the single most important object for admins. It bundles everything a quote needs: which Catalog to use, which Pricebook applies, which Payment terms, which Contract text, which Approval workflow, which PDF layout. Sales reps pick a Template at quote creation and the rest is pre-configured.| Entity | Description |
|---|---|
| Template | Sales funnel configuration (bundles Catalog + Pricebook + rules) |
| Payment term | Billing frequency and due dates (Net 30, monthly…) |
| Contract | Legal document template with dynamic variables |
| Approval workflow | Rules that govern when a quote needs validation |
| Content library | Reusable text and media blocks |
| PDF template | Layout and branding of exported PDF quotes |
| Checkout form | Custom form shown to the buyer in the Dealroom |
Sales cycle
The sales cycle is where deals actually happen. A Quote is created for a Customer using a Template. It contains one or more Line items — each tied to a Product and a Price. Once published, the Quote becomes visible to the buyer through a Dealroom, where they can review, comment, and sign.| Entity | Description |
|---|---|
| Quote | Priced proposal sent to a Customer |
| Line item | One product entry in a Quote, with quantity and price |
| Dealroom | Buyer-facing space to review, comment, and sign the Quote |
What’s not in this model yet
The current data model (v1) does not include:- Order — Orders are automatically generated from accepted quotes. They share most of their structure with Quote and Line item, and will be modeled explicitly in the next iteration.
- Sales Agreement — A framework contract with volume commitments and negotiated pricing. Sales agreements apply to multiple Orders and will be added to the model in a future release.
Orders and Sales Agreements are live in the product — you can create and manage them today. Their omission here is purely in the diagram, which will be updated as the model evolves.
Next steps
Set up your workspace
Configure currencies, taxes, languages, and business units before importing data.
Create your first catalog
Start modeling what you sell with products and categories.
Understand Templates
Learn how Templates bundle catalog, pricebook, and contract configuration.
Quote lifecycle
Follow a quote from draft to signed deal.