Draupnir

Draupnir: subscriptions in ServiceNow, from order to end

Draupnir turns every catalog order into a subscription: this customer has this offering, in this quantity, from this date, paid by this account. It follows the item through approval, delivery, changes and cancellation, so you always know who has what, and who pays for it.

In Norse myth, Draupnir is Odin’s gold ring that drips eight new rings every ninth night. Recurring, by nature.

Illustration of Draupnir (screenshots follow)

What you get

Orders that know who pays

The order form shows who will be billed and a price estimate before the user submits. An order that cannot be billed is stopped on the form, with the reason.

Your process, or ours

Draupnir follows the approval and delivery your catalog items already have. For items without a process, it can run the approval and the delivery itself: by a task, a system call, an automated flow, or nothing at all.

Approvals that do not get stuck

The party that pays approves: the contract’s business contact, or the manager. An approver who does not answer is reminded, and the approval moves to the support group.

Pay from delivery

A subscription is billable from the later of the requested start date and the delivery date, so a customer never pays for something not yet delivered.

Support without tickets to IT

Support staff change quantity, owner, item and cost center straight in the form. The change flow starts by itself, and every change is written to the subscription’s history with who, when and why.

One set of rules

Form, file, catalog and integration all go through the same validation, which never lets a change touch a period already billed.

Add-ons and bundles

Backup on a server, insurance on a laptop: add-ons are subscriptions of their own on a parent, and end with it.

One-time orders too

An offering can be ordered as a one-time charge without a subscription, for items that need no history.

Thousands at once

Existing subscriptions are loaded from files of up to 50,000 rows, with a reason for every row that is refused, and a whole file can be taken back while nothing from it is billed.

Several legal entities, one instance

Each legal entity sells its own offerings at its own prices, and staff see only the entities they work for.

What your customers see

My subscriptions. In the Employee Center: what they have, its status, and whether it is invoiced; Change and Cancel on every row, with the end date and what happens to days already paid. People who act for a company switch to its accounts and contracts. Recent one-time orders are listed too.

Built on what you have

Draupnir uses the platform’s own catalog, offerings, contracts, companies and cost centers. Everything that can differ between instances is read through one adapter that your own small app can override, so the product itself is never changed and upgrades stay simple.

Together with Gungnir

Draupnir knows what every customer has; Gungnir bills it. With both, every subscription is billed in Gungnir’s billing runs, and the customer follows it from the order to the invoice. Together they are FairyWare Order to Invoice.

Need something that isn’t in the box? We build that too. See our services.

Try both products for 14 days

The trial installs on your own ServiceNow instance with both products and all add-ons. Install the demo data, place an order, run a billing run and read the invoice.