← Products & white-label offerings

Proposed white-label offeringEight optional modules

RZIFI Business OS

Keep the customer moving.
Keep the context with them.

Sales closes the deal. Delivery needs the scope. Finance needs the milestone. Support needs the history. Build one connected operating experience around those handoffs.

Try the handoff demo Discuss your workflow

Product design and synthetic demo. Selected foundations and integrations still need implementation; this is not a running business backend.

Explore the operating experience

A useful handoff starts
with checked evidence.

Choose a task, then change the record condition. See what the proposed assistant can summarize, when it must stop, and who owns the next action. Everything here is scripted with synthetic records.

Customer workspace / Northstar StudioSynthetic · no live integrations

Work to prepareRecord condition

Source context

Linked records

Customer link: PARTY-DEMO-042 · Twenty / Odoo
Signed scope: ENV-DEMO-018 · Documenso
Proposed work: Prepare a delivery handoff for review.

Sample IDs only. No customer data is retrieved.

Proposed AI assistance

An evidence-led next step.

Choose a task and check its linked records.

For this example, the assistant would bring together the accepted scope, customer identity and named delivery owner before preparing a handoff.

I reviewed the sample evidence and suggested owner.

This demo prepares a local note. It does not create projects, sign documents, issue invoices, send replies or run an AI model.

One product, selectable modules

Connect the work
your business actually does.

Start with the handoff that loses the most time. Add modules when they solve a defined problem. Keep your existing system where it already does the job.

01 / Twenty CRM

Relationship management

Qualify leads, keep the next action visible and hand accepted customers into operations.

Record ownership & implementation scope

Owner of the record: Twenty owns prospects, contacts and opportunity stages. Odoo owns the finance-side customer record after conversion; link the two with a stable party ID.
Work to scope: Twenty and Odoo overlap in CRM. Define field ownership, duplicate handling and a tested conversion adapter before syncing customer data.
Edition and licensing: AGPL-3.0 core includes an application exception for separate apps using published interfaces; some components have separate commercial terms. Confirm the exact edition and distribution model.

02 / Documenso

Agreement signing

Prepare an agreement, route it to named signers and track the envelope through completion.

Record ownership & implementation scope

Owner of the record: Documenso owns the signing envelope, recipient state and completed artifact reference. Odoo owns approved commercial terms and the sales order.
Work to scope: Connect completed envelopes to approved orders with an immutable artifact reference. Configure and protect the signing certificate, then review signer evidence and jurisdiction requirements.
Edition and licensing: AGPL-3.0 Community with separately licensed Enterprise features. Embedded authoring white-label is Enterprise-listed; self-hosting needs an operator-provided signing certificate.

03 / Plane

Delivery management

Turn agreed scope into owned work, milestones and customer-visible progress.

Record ownership & implementation scope

Owner of the record: Plane owns delivery projects and work-item status. Link the signed scope and commercial record rather than copying them into a second task system.
Work to scope: Odoo Project overlaps this module. Choose one delivery task owner and build a tested contract-to-project handoff, status mapping and reconciliation path.
Edition and licensing: Community Edition is AGPL-3.0. Commercial and Airgapped editions have separate licensing and feature sets; no rebranding or reseller right is assumed.

04 / Odoo Community

Business operations and invoicing

Keep the accepted customer, approved order and invoice in one operational finance system.

Record ownership & implementation scope

Owner of the record: Odoo owns the finance-side customer, sales order and invoice records. Other modules link to those IDs and show scoped summaries.
Work to scope: Confirm the Community branch and modules, country localization, tax and e-invoicing scope, and whether the offer covers operational invoicing or statutory accounting.
Edition and licensing: Odoo Community source is LGPL-3.0. Enterprise apps and services have separate terms; review the selected modules and localization rather than implying all features are included.

05 / Relay support experience on a Chatwoot foundation

Customer support (Relay)

Bring customer conversations into one queue, assign an owner and link authorized business context.

Record ownership & implementation scope

Owner of the record: Relay owns the customer-support workflow and conversation context; Chatwoot is the underlying inbox foundation. Reuse one inbox and case ID.
Work to scope: Payment context and consequential actions need explicit authorization. Provider approval, credentials, templates and delivery receipts remain channel-specific; begin with scoped read-only record links.
Edition and licensing: Chatwoot core is MIT, with separately licensed Enterprise components. Custom branding is excluded from Community and listed in paid self-hosted plans; confirm exact edition rights before white-label use.

06 / AppFlowy, with AFFiNE as an alternative to assess separately

Knowledge and team workspace

Keep procedures, onboarding notes and decision documents findable beside the work they support.

Record ownership & implementation scope

Owner of the record: The selected workspace owns its native pages and documents. Plane, Relay and Odoo keep links and identifiers instead of duplicate document bodies.
Work to scope: AppFlowy's desktop client is not its complete collaborative backend. The former AppFlowy-Cloud repository is archived; current self-hosted cloud uses a separate commercial codebase and license. AFFiNE requires its own hosting and integration review and is not a drop-in replacement.
Edition and licensing: AppFlowy client code is AGPL-3.0, while current commercial cloud/self-host backend terms are separate. AFFiNE has separate terms. No blanket white-label right is assumed.

07 / Penpot

Product design workspace

Create interface designs and prototypes, then link reviewed files to delivery work.

Record ownership & implementation scope

Owner of the record: Penpot owns native design files, libraries and prototypes. Plane holds linked implementation work and review status.
Work to scope: This supports product design; it is not the production interface or customer record. Review permissions, backups, optional service terms and third-party asset rights.
Edition and licensing: MPL-2.0 core with file-level and third-party asset notices to check. Self-hosting alone does not grant RZIFI resale, trademark or white-label rights.

08 / Mattermost

Internal collaboration

Coordinate team conversations and incident rooms while keeping decisions and work in their owning systems.

Record ownership & implementation scope

Owner of the record: Mattermost owns internal messages and channels. Plane, Documenso, Odoo and Relay stay authoritative for work, signatures, invoices and customer cases.
Work to scope: Link canonical records rather than treating chat as the task or audit ledger. Source, compiled edition, enterprise overlay and trademark conditions differ; confirm terms for the exact edition and branding.
Edition and licensing: Mixed terms: source licensing and compiled MIT distributions differ, with separately licensed Enterprise code/features. Trademark policy applies to derivative branding; no automatic resale right is claimed.

AI with a clear job

Less context gathering.
A better prepared next step.

The proposed assistant retrieves authorized records, cites its sources and suggests the responsible team. Approval and execution stay with the workflow owner. Model selection and evaluation belong to the implementation.

Before the handoff

Summarize the signed scope, exclusions and promised dates. Flag a missing signature or an unassigned delivery owner instead of treating a closed deal as ready to start.

When a customer complains

Connect the conversation to permitted project and invoice context. Suggest delivery, billing or support ownership with the evidence behind the suggestion; route uncertain cases for review.

For the operating review

Group recurring handoff failures, overdue milestones and unresolved cases. Compare observed trends with agreed definitions before claiming an improvement in SLA, CSAT or NPS.

Measure retrieval permissions, source freshness, routing accuracy, unsupported answers, reviewer edits and cost per completed task. These are evaluation targets; no measured AI performance is claimed.

The work between the modules

One experience needs
clear record ownership.

Eight installed applications do not make a connected product. Shared identity, source permissions and reliable handoffs are the core implementation work.

Qualify a lead
Track the prospect, contact, opportunity owner and next step. At customer acceptance, map the record to the Odoo partner ID instead of creating a second customer identity.
Record owner: Twenty
Agree the scope
Odoo holds the approved quote and commercial terms. Documenso routes the agreement for signature and returns its envelope state and completed artifact reference.
Record owner: Odoo + Documenso
Deliver the work
Create delivery work from the accepted scope, assign owners and milestones, and link the contract and customer IDs. Plane remains the delivery status owner.
Record owner: Plane
Issue the invoice
Create the invoice from the accepted order within the configured company and country scope. Other modules show a linked status rather than keeping a second invoice record.
Record owner: Odoo
Support the customer
Handle conversations in Relay, link authorized customer, order or project context, and assign follow-up. Case closure does not mean an invoice is paid or a payment has settled.
Record owner: Relay (Chatwoot-backed)

One customer identity

Link CRM, signed scope, delivery and invoice IDs. Give each field one owner so a name change does not create another customer.

Reliable handoffs

Version event contracts, deduplicate retries and reconcile failures. A signed agreement should create one delivery handoff, even if its webhook arrives twice.

Scoped access

Keep company, team and document permissions intact across search and AI summaries. A link to a record does not grant access to it.

Recoverable operations

Record the actor, source and result. Provide retry queues, backup and restore checks, and an owner for upgrades and incidents.

Compare the complete operating cost

When does a tailored
suite earn its place?

A managed product can be the right choice for standard workflows. A tailored implementation needs a specific integration, data boundary or experience requirement that justifies owning its operation.

HubSpot Sales Hub

Compare CRM pipeline, contact context and sales automation with the proposed Twenty-to-Odoo handoff.

Hosted plans and included capabilities vary by tier, seats and billing terms. Use the current vendor selector and quote for a like-for-like scope.

View current vendor pricing ↗

Atlassian Jira

Compare issue tracking and cross-team delivery planning with the proposed Plane-led project workspace.

Public plans depend on user band, deployment and billing choice. Validate the current edition and selector for the team size.

View current vendor pricing ↗

Intercom

Compare a managed customer-support suite with Relay's Chatwoot-backed, separately scoped support workflow.

Seat, AI outcome and add-on charges can apply. Compare the same channels, volume and support scope against the current pricing page.

View current vendor pricing ↗

Microsoft Dynamics 365 Business Central

Compare integrated accounting, sales and operations with the proposed Odoo Community-led back-office scope.

Subscription and implementation scope vary by region, user type and partner. Use the regional product page and a current quote.

View current vendor pricing ↗

RZIFI Business OS: scoped implementation, quoted after discovery.

Compare licenses and edition fees, hosting, model usage, connectors, migration, backup, upgrades and support over the same period. Open source does not mean zero operating cost. These are vendor comparison links, not normalized quotes or a savings claim.

Build around one useful outcome

Prove the handoff.
Then expand the scope.

Designed for service businesses, internal operations and product teams connecting sales, delivery and support. Regulated institutions need an additional data, identity and control assessment.

01 / Scope the pilot

Choose a workflow, its systems of record, the users and a small set of accepted outcomes. Agree the edition, branding permissions and data boundary before implementation.

02 / Test the integration

Prove the normal journey and the missing, stale, duplicate, unauthorized and unavailable cases. Measure the time and errors at each handoff against a baseline.

03 / Own the operation

Agree monitoring, recovery, upgrades, training and support. Release only the capabilities that have passed acceptance, then decide which module to add next.

Before you decide

Scope, ownership and delivery.

Is RZIFI Business OS one integrated application?

No. It is a descriptive name for optional product foundations and proposed integrations. Shared identity, records, permissions and workflow handoffs still need to be built and tested for the selected scope.

Where does the customer record live?

Twenty owns the prospect and opportunity. After acceptance, Odoo owns the finance-side customer record. A linked party ID and explicit field ownership are needed to prevent duplicate records from drifting.

How does Relay fit with Chatwoot?

Relay is the suite's customer-support workflow on a Chatwoot inbox foundation. The suite reuses one Relay/Chatwoot conversation system instead of creating a second support inbox. Chatwoot custom branding requires a paid self-hosted plan.

Can I use AppFlowy or AFFiNE for team knowledge?

They are alternative workspace foundations, not interchangeable services. AppFlowy's client repository is AGPL, but its former cloud repository is archived and current cloud/self-host backend terms are commercial. AFFiNE needs its own license, hosting and integration review before selection.

Can the whole suite use one brand and one sign-in?

Branding and identity depend on each product edition and license. Chatwoot branding is paid, Documenso lists embedded white-label authoring in Enterprise, and Mattermost has separate branding and trademark terms. Shared SSO and blanket rebranding are not included by default.

Does the suite guarantee compliant invoices or signatures?

No. Odoo modules, accounting setup, tax, e-invoicing and retention need country-specific review. Documenso requires a signing certificate and selected signer-evidence controls; legal effect depends on the jurisdiction and implementation.

Start with the difficult handoff

Where does your team
lose the customer context?

Bring the workflow, systems and teams involved. We can map the gap and define a first implementation worth testing.

Discuss Business OS →Explore all offerings