KWAYZER Revenue

What it does

• One CRM, one identityContacts, companies and deals — with merges that stay merged.

  A merged record keeps a pointer to its survivor, and every read in the product honours it, so a merge does not resurrect the old row in a report three screens away. The merge is reversible by a compensating write rather than by deletion, so the history of what was merged survives the undo.

• Enrichment that charges onceOne waterfall across providers, with a 30-day cache.

  Providers are tried in order and the first useful answer wins; the result is cached for thirty days, so asking the same question twice in a month costs once. Every attempt records which provider answered and what it cost, so a bill can be traced to the calls that produced it.

• Campaigns and journeys on one engineA single workflow engine, not one per feature.

  Every automation runs on the same two-pass tick over one node catalogue. That is why a journey and a campaign behave identically on retry, on pause and on failure — there is no second engine with its own idea of what a step is.

• Audiences in plain EnglishDescribe the segment; it compiles to the same rules the engine already runs.

  The interpreter's only output is the existing segment shape, over a closed vocabulary of fields and operators. It cannot produce a rule the engine could not already evaluate, which is what stops a natural-language front end from quietly becoming a second audience model.

• Metering you can auditOne balance, one ledger, and they are not the same thing.

  Credits have a single source of truth and an append-only ledger beside it. The ledger is never read as a balance — a distinction that sounds pedantic until a refund and a spend land in the same second.